Author Topic: Process Lasso Localization - How to Translate it to YOUR language  (Read 31488 times)

Offline Jeremy Collake

  • Administrator
  • Member#
  • *****
  • Posts: 5280
  • Gender: Male
  • The Lasso
    • Bitsum
LEGAL NOTICE

When you submit a translation to Bitsum Technologies, you grant Bitsum Technologies and/or Jeremy Collake full rights to use the translation. Since translations are often community efforts with several contributors, you can not later rescind your translation. By submitting a translation, you agree to give Bitsum Technologies full, non-expiring rights to use the translation.



See alternate instructions in next post if this seems convoluted

To translate Process Lasso to YOUR language you need to edit a simple text file. You can find the necessary files for translation in the package at https://bitsum.com/files/pl_localization_files.zip . It is updated with each build of Process Lasso that is released.

Download Process Lasso Localization Pack ~2MB

For new languages, you want to copy the English sub-folder and rename it to your language. In the language folder, you'll see several things that need translating. The most important is the text file, processlasso_strings.txt, as it contains almost all strings that Process Lasso uses.

The text file format
In the text files there are two strings on each line, the UNTRANSLATED (English) string and its TRANSLATED counter-part. Therefore, to translate these files you change the SECOND string on each line to the language of your choice.

To give an example of what the text file format looks like, here are actual samples:

WAS (English->English):
Code: [Select]
"Rules" , "Rules"
"Managing processes for user(s): %s" , "Managing processes for user(s): %s"
"Beginning process management" , "Beginning process management"
 

NOW (English->Brazilian):
Code: [Select]
"Rules" , "Regras"
"Managing processes for user(s): %s" , "Gerenciando processos para o(s) usuário(s): %s"
"Beginning process management" , "Come├žando gerenciamento de processos"
 

Once you finish your work, simply email the translated files to support@bitsum.com . I'll get your language into the next build of Process Lasso. From that point forward your language will be also included in the Localization Pack, which you'll re-download on updates (see section below).

Please note that all text files are to be saved as UTF-16-LE (UNICODE, 16-bit, little endian).

What's in it for you?

Well, first our eternal gratitude! Next, your name will go in the about box of Process Lasso when your language is used (listed as the translator). Additionally, we now have arrangements with many translators, allowing revenue sharing for their respective regions.

Translators receive:
  • Their name in the about box of the translated program (credit to translator)
  • 5 free lifetime license for Process Lasso Pro
  • 20 free licenses to Process Lasso Pro to give away to whomever, or to use yourself.
Again, the latest versions of the localization files can be found at http://www.bitsum.com/files/pl_localization_files.zip. Once you submit to me translated copies, future versions will include your translated text copies with new strings added. Submitting ANY version of these text files translated is fine though, as few strings change or are added.

HOW DO UPDATES TO THE TRANSLATIONS WORK FOR NEW VERSIONS?

When Process Lasso is updated, there are often a few strings that have been added or changed. You simply need to translate these new strings. We make this easy, as during our build process the translated text files you sent us get updated with these changes. New and changed strings are simply added to the bottom, ready for you to translate. So, the process is:

  • Download the localization pack again (be sure to not get a cached copy)
  • Go to the folder of your language (i.e. Serbian)
  • The files there will ALREADY have new strings appended
  • Translate the added strings
  • Email to us at support@bitsum.com the entire file or folder

FAQ:
Q: Does the line ordering matter?
A: NO. The ordering, or the line numbers do not matter one bit.

Thanks to anyone who contributes!
« Last Edit: July 09, 2015, 10:02:28 AM by Jeremy Collake »


Software Engineer. Bitsum LLC.

Offline Jeremy Collake

  • Administrator
  • Member#
  • *****
  • Posts: 5280
  • Gender: Male
  • The Lasso
    • Bitsum
Re: Process Lasso Localization - How to Translate it to YOUR language
« Reply #1 on: May 27, 2009, 01:07:16 PM »
[These are the alternate instruction set. Same thing. Described differently.]

Instructions to create a new translation:

1. Download the latest localization pack at http://www.bitsum.com/files/pl_localization_files.zip
2. Create a new folder named after your translation (i.e. French)
3. Translate string and bitmaps into your language
4. Submit all files to Bitsum Technologies
5. Receive your 11 free license (1 + 10 giveaway licenses)*
   
Instructions to update an existing translation for a new version released:

1. Download the latest localization pack at http://www.bitsum.com/files/pl_localization_files.zip
2. Go to the already existing folder named after your translation
3. The processlasso-strings.txt file, and others, will have been appended with any new, untranslated strings.
4. Translate untranslated (new) strings and bitmaps into your language
5. Submit updated files to Bitsum Technologies
6. Receive more free give-away licenses upon your request

TIP: *Some* spreadsheet software will import this file as a CSV file. You need to be careful though, as it may not export it correctly to the right text format. It can, at least, make the process of translating the strings easier.

For programmers: It would be pretty simple to create a RAD (Rapid Application Development) language that read this file and allowed translation of individual strings.
« Last Edit: October 10, 2011, 02:21:19 AM by bitsum.support »
Software Engineer. Bitsum LLC.

Offline Jeremy Collake

  • Administrator
  • Member#
  • *****
  • Posts: 5280
  • Gender: Male
  • The Lasso
    • Bitsum
Re: Process Lasso Localization - How to Translate it to YOUR language
« Reply #2 on: July 13, 2011, 02:06:42 AM »
Get automatically notified of changes to the localization pack!


This will let you know every time the localization pack is changed. Do NOT register on the ZIP file, use the HTML file above. That file contains the date and time of the last uploaded ZIP file.
« Last Edit: August 01, 2012, 09:13:46 AM by bitsum.support »
Software Engineer. Bitsum LLC.

Offline Jeremy Collake

  • Administrator
  • Member#
  • *****
  • Posts: 5280
  • Gender: Male
  • The Lasso
    • Bitsum
Re: Process Lasso Localization - How to Translate it to YOUR language
« Reply #3 on: December 17, 2011, 03:13:52 AM »
I forget that most of you aren't programmers, so may not realize the importance of the % characters (and the chars that follow). If these get out of order, or are omitted, the results are unpredictable. A crash can occur on one PC, but not another.

Here are the rules:

The *same* %xxx denotations must appear in the string in the same ordering.

Examples:

VALID: "This is string %d and must contain %s and %d all in this exact order, else the application will crash!", "Some language %d, anything %s, blah %d"
INVALID: "This is string %d and must contain %s and %d all in this exact order, else the application will crash!", "Some language %s, anything %d, blah %d"  (out of order)
INVALID: "This is string %d and must contain %s and %d all in this exact order, else the application will crash!", "Some language %s, anything %d, blah"  (missing %d)

The % indicates a field will be inserted there. %s means a string. %d means a decimal number. There are many escape sequences, and they can even be stuff like %.02f . These must be preserved exactly. They end when the first space is encountered (for the most part).

I added to the localization tools a safety check to help check for these occurrences and found errors in some translations. I'll be contacting you individually if errors were found. If I don't contact you, good job ;). Many translations did pass without a hiccup.
« Last Edit: June 29, 2012, 09:56:49 AM by bitsum.support »
Software Engineer. Bitsum LLC.

Offline Jeremy Collake

  • Administrator
  • Member#
  • *****
  • Posts: 5280
  • Gender: Male
  • The Lasso
    • Bitsum
Re: Process Lasso Localization - How to Translate it to YOUR language
« Reply #4 on: June 24, 2012, 05:06:37 PM »
NOTICE: There is no NEED to translate processlasso-strings_deprecated.txt  - This is where OLD strings go. You can translate it if you wish, but it is up to you. The idea is to have those strings available, in case they are re-used again.
Software Engineer. Bitsum LLC.

Offline hanemach_gt

  • Member++
  • ****
  • Posts: 270
  • Gender: Male
Re: Process Lasso Localization - How to Translate it to YOUR language
« Reply #5 on: July 08, 2013, 05:56:57 AM »
It's possible to automate localization pack downloading very easily. For those of you who are a bit lazy about going to this thread, clicking the hyperlink and decompressing files, you can use cURL and command-line archiver like 7-ZIP, like I do, thus:

Code: [Select]
@echo off
color 06
set _this_path=%~dp0
curl.exe --output "%_this_path%pl_localization_files.zip" --remote-name "http://www.bitsum.com/files/pl_localization_files.zip"
"%_this_path%upload\7z.exe" x "%_this_path%pl_localization_files.zip" -aou -o"%_this_path%whole_unpacked_localization_pack" *.* -r
"%_this_path%upload\7z.exe" e "%_this_path%pl_localization_files.zip" -aou -o"%_this_path%" "Polish\processlasso_strings.txt"
"%_this_path%upload\7z.exe" e "%_this_path%pl_localization_files.zip" -y -o"%_this_path%translation_validator" "checkdata.dat"
"%_this_path%upload\7z.exe" e "%_this_path%pl_localization_files.zip" -y -o"%_this_path%translation_validator" "rcImport.exe"
popd
explorer "%_this_path%"
pause

Above script downloads the localization pack, unpacks whole downloaded file to a separate folder (so you can look up if something has changed in its "structure"), and unpacks 3 files that are updated most often.

A bit of batch knowledge is necessary to make it easier (it's an example), if you need help configuring it, PM me.

Offline Jeremy Collake

  • Administrator
  • Member#
  • *****
  • Posts: 5280
  • Gender: Male
  • The Lasso
    • Bitsum
Re: Process Lasso Localization - How to Translate it to YOUR language
« Reply #6 on: April 06, 2015, 12:26:00 AM »
How to Use Excel to Edit the processlasso-strings.txt the easy way.

1. Download notepad++ or some other free text editor that can save in alternate formats (e.g. UTF-8 /w BOM or UCS).
2. Open the processlasso_strings.txt file.
3. Save as UTF-8 w/o BOM
4. Rename processlasso_strings.txt to processlasso_strings.csv
5. Open in Excel

If all went right, should look like the pic below. I also attached the latest CSV with BOM marker removed. The BOM marker is just two bytes added to the beginning of text files to tell editors what format they are in. Why Excel doesn't support it, who knows.
Software Engineer. Bitsum LLC.