sky110120 / multiproperties

Automatically exported from code.google.com/p/multiproperties
0 stars 0 forks source link

UTF-8 Import an Export should be working #31

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
--------------------------------------
1. Importet an UTF-8 properties-file which contains russian translation for my 
keys
2. after importing the russian field in the multiproperties file shows 
"привет"

What is the expected output? What do you see instead?
------------------------------------------------------
I expect "привет" in the russian field like it is written in my UTF-8 
properties file.
Instead it shows "привет"

What version of the product are you using? On what operating system?
--------------------------------------------------------------------
1.2.0 on Windows 7

Please provide any additional information below.
------------------------------------------------
My use-case is that I send the property files of each language to a native 
speaker which translates this for me.
Sometimes I have to google-translate some filds for myself.
Therefore it would be very(!) important that it is possible to import AND 
export UTF-8 Files.

Original issue reported on code.google.com by tl...@washtec.de on 5 Dec 2012 at 4:49

Attachments:

GoogleCodeExporter commented 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

GoogleCodeExporter commented 9 years ago
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