Jump to content
Sign in to follow this  
fer

Translation Req. from BAS f (02/03/2008)

Recommended Posts

Do you speak one of the following languages natively?

<ul>[*]Czech

[*]German

[*]Polish

[*]Russian

[*]Spanish

[*]French

Can you spare 10 minutes to translate some phrases? If yes, the BAS f team would appreciate your assistance translating new elements in its stringtable.csv file. To do this, please follow these suggested steps:

1. Download the file from http://www.ballisticaddonstudios.com/downloa....eme.csv (use the Save Link As... option in your browser)

2. Open the file in a UNICODE-capable editor.*

3. Add translations for your language, replacing the appropriate instances of REPLACEME

4. Email your file to: fer@ballisticaddonstudios.com

Many thanks in advance!

- Fer <TZW> smile_o.gif

* The easiest way to edit the file is using OpenOffice's sCalc application, which supports UNICODE characters in CSV files (unlike MS Excel, which does not).

Share this post


Link to post
Share on other sites

German sent smile_o.gif

Share this post


Link to post
Share on other sites

sCalc strangely truncates empty fields, so you may end up with something like this :

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">"str_string_name","string_en",

instead of

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">"str_string_name","string_en",""

like what Excel or a saved MySQL query would output. That said, I've had better success with OpenOffice for projects due to specific processing requirements. The BIS stringtables tools however will accept either 'version', though these are not designed for any useful community purpose.

Also note that BIS products do not use a standards-based stringtable.csv file format, the quotes will need to be stripped from the first column.

Lastly, either Unicode or UTF-8 file formats will be accepted by the engine. With the languages listed, you probably would be ok with UTF-8, though there's a chance you might need expanded Unicode for Russian support. The ArmA engine does not conform to Unicode protocols in that it does not use the Windows text libraries, but instead uses its own text loading and processing mechanism, using Unicode character addressing.

Share this post


Link to post
Share on other sites

Many thanks to those kind folks who have contributed translations so far, however we still need help with:

<ul>[*]Czech

[*]Polish

[*]Spanish

[*]French

Can anyone help fill these gaps?

Share this post


Link to post
Share on other sites

Many thanks to WOlle, a certain Mr Kaspersky, and Rainbow. However, we still need the following languages:

<ul>[*]Czech

[*]Spanish

[*]French

This is so we can release the v1-1 build of BAS f.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×