-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Language file updates #2
Comments
Portuguese (Portugal) to be added soon. |
Russian to be added soon. |
Updated Portuguese (Brazilian) translation |
Thank you, added it with the latest commit. |
Hi, I cann't upload any files to github.com with my internet browser. By the way, the language file Chinese.ini could be rename to Chinese (traditional).ini. |
Thanks, I'll add it with the next update. |
Every thought of using something like http://pootle.translatehouse.org/ or https://www.transifex.com/ ? |
Actually, no, I didn't think about using it. I didn't even know about the services. Might be interesting to look at, even if I think it's a bit overkill for a rather simple project as UniExtract... |
Russian_16.10.26 |
Bulgarian_16.11.10 |
French was quite outdated. A lot of translations were missing even in the previous release. |
@zorbao Thanks for your contribution, I added the translation and it will be included in the next update. |
Greek added |
Thanks to @jfcherng, @igorruckert and @gvp9000 for your pull requests. |
Changes Beta 4 to RC 1
|
Updated Portuguese (Brazilian) translation |
Updated French (France) translation |
Updated Russian translation |
Changes RC 1 to RC 2
|
Traducción al español desde English.ini. |
Greek translation ... |
Updated French translation based on English.ini (SHA-1: eb60c1d) |
Updated german translation file, spelling and grammar corrected. |
Updated French translation based on English.ini (SHA-1: fee4d0f) |
Updated and fixed Hungarian translation for Universal Extractor 2.0.0 RC 3 |
Updated and fixed Greek translation for Universal Extractor 2.0.0 RC3 |
Changes RC 3 to RC 4
|
Updated German translation |
English.ini corrected |
Greek.ini corrected |
Updated and corrected Spanish translation. |
Updated Spanish.ini translation |
Traducción al español actualizada y corregida. |
As Zorbao seems to give-up, I updated (and adapted - enhanced - to "Belgian" French) the French localization to RC4. |
Translation updated e revised |
Here is the updated French update (revision) : UniExtract_V2RC4_010322-FR.zip BTW, as the Homepage mentioned is completely obsolete ... |
A big thanks to everyone, who contributed any translation update so far.
Good catch, these items cannot be translated yet as they were originally used as internal status codes only. I put it on the todo list and make them translatable when I have more time. I guess most users don't look at the statistics view anyway ;) |
Thx Bioruebe. |
Hi @Lidgeu, I just read your comments above. And I wanted to take the opportunity to answer. Regarding my legacy website, it reminds me of a far far away epic! Looks like archaeology, nowadays… |
@zorbao Here is the French update according your latest English.ini master file as per today. |
@Lidgeu, |
Ukrainian translation updated according latest English.ini master file as per today. |
Updated Russian language file |
Since the encoding of the Japanese translation file is still UTF-8, re-encode it to UTF-16 and upload it. |
Updated German translation |
Universal Extractor 2 brings many additions and changes, thus most translations are not up-to-date anymore. It would be great, if some of you could help translating UniExtract into your mother tongue.
Getting started is easy: simply open the language file you want to improve (inside the
lang
sub-directory) with a plain text editor. You can find detailed instructions at the beginning of the translation file.Note: Submitting the translation via pull request breaks the file encoding. I run scripts to fix this when I update the language files, so you can simply ignore those encoding differences.
When updating language files, please check my last comment in this issue for information about breaking changes.
The text was updated successfully, but these errors were encountered: