This one is related to my previous post. My problem is that after I put messages in ValidationMessages.properties in languages other than English (Ukrainian and Czech in my case) I got messed up characters in the end. The encoding of all those ValidationMessages.properties files in the bundle is UTF-8, the same as I use for the other translations, and those work well.
I had a similar issue when reading UTF-8 properties files server-side using the ResourceBundle class. Java assumes that properties files are ISO-8859-1, while GWT assumes they are UTF-8. Oddly enough, there is no "one liner" way to tell java to read it as UTF-8. I ended up implementing this solution for reading it server-side and it works well for me, despite it not being as simple as one would hope.
After taking a look on the Hibernate Validation library and its contents I noticed that there are default translations for languages like Czech and Hungarian and they use JavaScript Unicode notation (like \u0000) for special characters. Looks ugly but works.
I don't know what exactly solved the problem, but as I moved from the GWT Validation to the Hibernate Validation libraries it helped.
Related
We are looking for a suitable solution to translate our GWT application collaboratively. We have a bunch of constants and messages property files that need to be translated by different people. Till now we've emailed the files and manually merged the translated content back which obviously doesn't scale very well.
Is there any tool (preferably an open source project) you can recommend that does play well with the i18n support of GWT and allow for collaboratively translation?
There is a Google Language API for GWT
I hope this doesn't sound like spam, but we built Amanuens, which is a web-based tool designed exactly to solve the problems you're having.
I'm not into GWT, but I assume that you have .properties files. If so, then our solution should work fine (although it's not open source).
It doesn't look like there is a GWT optimized solution for supporting the translation process of .properties files.
We are currently evaluating Pootle. It is easy to use (especially for non-techies), supports the translation process in many ways, supports user management, is open source and lets you import and export property files easily (which is important for integrating with GWT).
I'm looking for some tools that could be used by human translators during the process of translating our GWT application into other languages.
Currently, we have the English version of .properties files containing constants and messages, and need create the files for other languages. This tool should be easy to use, so even non-IT-lover can master it.
Or, do you suggest other method for translation of the texts?
I heard the "community" approach becomes quite popular, by that I mean that one uploads his texts to some (?) forum, and the community there creates the translations into other language - but as I said, I don't know much about this
Are there any online platforms for this purpose?
any other ideas?
See my SO answer for VB 6 source code, speech text is in french want to translate to english. The same answer works if you replace the computer langauge "VB6" by "JavaScript".
I'm creating a new Java project for a concept/construct that's usually referred to with an ampersand (e.g. PB&J). Is it ok to name the project that? Should I avoid it? Are there any symbols that are not allowed in Java project names? Are there any symbols that are generally avoided? Where do symbols come in with regard to Java project naming conventions?
Edit: Sorry for the misunderstanding. It's not a Java project really, it's an Eclipse Java project.
Java itself does not have the notion of "project". What you probably are referring to are IDEs like Eclipse. They might be able to use special characters like "&" in project names, but imho you really should avoid using them. It will make more trouble than it's worth.
Another character which should be avoided is "!", as it has a special meaning within Java for URLs pointing to resources within JAR Files.
As I understand java-project is term of your IDE but not a java term. That's why I think yes, you can.
Special characters such as & really should be avoided even if they appear to be "allowed". They do cause some unfortunate side effects later on and may be difficult to track down why certain things are not working as they should.
In an unrelated example I sometimes see persons using spaces in the names of files which work fine on Windows machines then suddenly break when uploaded to the web because spaces are not fully supported on the platform etc etc.
So its a matter of rather safe than sorry.
Ampersand is especially bad if it might end up in a file name. In most Unix shells, an unquoted ampersand means "run everything up to the ampersand in the background". Baffling bugs result.
Proper filename quoting fixes problems like this, but people inevitably forget a set of quotes and things blow up.
Stick to letters, digits, hypen, underscore, and period.
I have some big documentation to do that will contain pieces of code I'd like to give the conventional "coding language" syntax highlighting. I've searched the styles feature to do such a thing, but there is no way to do that (in fact I could only found a forum where people were fighting about adding this feature or not, but this is not the point).
There is an abandoned extension for OpenOffice, but using it freezes my installation of OpenOffice.
What's the easiest way to do this? Should I try to recompile the extension and debug it (although I'm already having a hard time compiling another Java project), or maybe I should use a macro? How to implement this?
One possibility is to use one of the many code to html tools out there and then include the html in your OpenOffice document (using "File..." on the Insert menu).
One possibility is highlight. Vim has a :TOhtml command that will convert the current file to syntax highlighted html using the current colour scheme. I've not tried it, but this looks promising. There are also a few online ones, such as this. I'm sure there are a great many other options.
Our installation program is written using InstallShield2009, and as part of certification requirements we have to support Unicode throughout.
The application itself is .NET, so supports Unicode natively, however on testing our installation with a Chinese character set we can see problems thrown up by InstallShield dialogs.
Having done a quick google, I found one related post whereby someone has deemed there is no unicode support in IS2008.
I have also emailed Acresso directly, but being the caring developer I am, thought I'd post the question here for future reference, in case anyone else has the same problem.
If anyone has encountered this problem in the past, any help would be appreciated. Thanks.
Turns out that IS2009 does NOT fully support Unicode, as it cannot handle paths containing (amongst others) Japanese characters.