Open GoogleCodeExporter opened 9 years ago
While the Properties format supports only the ISO 8859-1 encoding (see
http://docs.oracle.com/javase/6/docs/api/java/util/Properties.html), until I
could imagine a kind of support of different encodings too, even if it is not a
standard way for properties files. Furthermore next to the Import button, an
Export button could provide ad-hoc exporting possibilities. Yes, good point.
As a workaround, until it is not ready, you can use the standard "native2ascii"
Java command, which support both way conversion.
Finally considering your use case, I would like to know your opinion about the
issue28, which is about a standalone version of editor. Could it help in your
case?
Original comment by ska...@gmail.com
on 5 Dec 2012 at 10:48
Tank you for your quick answer! :)
So you do plan to implement an export and import for different encodings? -->
that would be GREAT!
To answer your question:
Yes! A Standalone Editor would be definitively a great help for our translators.
Original comment by tl...@washtec.de
on 7 Dec 2012 at 7:01
Original issue reported on code.google.com by
tl...@washtec.de
on 5 Dec 2012 at 4:49Attachments: