This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Greek Translation
#1
Hey everyone!

I just thought I'd do a Greek (EL) translation of JPCSP (that's the least I can do to thank all people involved to the project) with (possibly) the most accurate and formal technological terminologies to match as perfectly as possible to JPCSP's functions yet be majorly understandable to people who use often emulators and the ones who don't.



Attached Files
.rar   gr_EL.rar (Size: 3.66 KB / Downloads: 146)
Reply
#2
As this is a new language, a new line is needed in common.properties (to be displayed in the language selection) and a flag icon.

Thanks!
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Reply
#3
No prob.
You need also to deal with the cyrilic text and the encoding of the file otherwise the text will appear as a mess in JPCSP, dunno what to do in that but I bet you do.
Reply
#4
(12-10-2012, 09:46 AM)VIRGIN KLM Wrote: No prob.
You need also to deal with the cyrilic text and the encoding of the file otherwise the text will appear as a mess in JPCSP, dunno what to do in that but I bet you do.
The characters inside the gr_EL.properties have to be unicode-encoded. See the other .properties file for examples. I cannot check if the result is correct or not Wink
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Reply
#5
(12-10-2012, 10:42 AM)gid15 Wrote: The characters inside the gr_EL.properties have to be unicode-encoded. See the other .properties file for examples. I cannot check if the result is correct or not Wink
Big Endian or Small Endian? Whatever format you save it it doesn't mess it up so don't worry (it doesn't contain any weird/unsupported letter so the text editor won't come up with the message that you might mess up the file), all encoding methods work correct with the text I use the thing is that when I put it back on JPCSP myself from the source the text in all 4 versions I save it (UTF-8, ANSI, Unicode SE, Unicode BE) results in jiberish or completely missing text, so that's what I meant that possibly you have to deal with something I am not aware from your side.

Reply
#6
(12-10-2012, 12:51 PM)VIRGIN KLM Wrote:
(12-10-2012, 10:42 AM)gid15 Wrote: The characters inside the gr_EL.properties have to be unicode-encoded. See the other .properties file for examples. I cannot check if the result is correct or not Wink
Big Endian or Small Endian? Whatever format you save it it doesn't mess it up so don't worry (it doesn't contain any weird/unsupported letter so the text editor won't come up with the message that you might mess up the file), all encoding methods work correct with the text I use the thing is that when I put it back on JPCSP myself from the source the text in all 4 versions I save it (UTF-8, ANSI, Unicode SE, Unicode BE) results in jiberish or completely missing text, so that's what I meant that possibly you have to deal with something I am not aware from your side.
I'm not doing anything special on my side, I just take the file as you posted. You can test your file by replacing the one from another language.
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Reply
#7
(12-10-2012, 03:44 PM)gid15 Wrote: I'm not doing anything special on my side, I just take the file as you posted. You can test your file by replacing the one from another language.

That's what I'm saying. Tried all 4 encodings I posted and all showed up garbage or nothing at all, I can post screenshots if you want. I have no clue what causes such thing.
Also the original files inside the jar file show up as ANSI not unicode.
Reply
#8
I could convert your file using the JDK command line (after renaming your file to gr_EL.properties-native):
Code:
native2ascii.exe -encoding windows-1253 gr_EL.properties-native gr_EL.properties
Attached is the result file. Is the display now correct?


Attached Files
.7z   gr_EL.7z (Size: 4.34 KB / Downloads: 146)
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Reply
#9
(12-14-2012, 12:07 PM)gid15 Wrote: I could convert your file using the JDK command line (after renaming your file to gr_EL.properties-native):
Code:
native2ascii.exe -encoding windows-1253 gr_EL.properties-native gr_EL.properties
Attached is the result file. Is the display now correct?
Great this one worked!
BTW, now that I was able to see it inside the GUI, I corrected 2 small issues and I also noticed that you added 3 new lines to the newest commits in the svn that I just added to the translation too:

Code:
sceUtilitySavedata.LISTLOAD
sceUtilitySavedata.LISTSAVE
sceUtilitySavedata.LISTDELETE


Also since r2929 "Use Shaders" is not anymore an experimental feature, I removed the "exprerimental" word from the translation too!
Do exactly the same converstion you did on the new file I'll attach in this post and put it straight to the new svns!

PS: Sorry for the trouble, I guess it's always tough when you have to deal with non-latine characters...


Attached Files
.rar   gr_EL.rar (Size: 3.7 KB / Downloads: 129)
Reply
#10
Added in r2932.
Still missing:
- native Greek name for language selection menu
- Greek flag for language selection menu
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)