Update all language files for SVG-Edit 2.4 Final

[GoogleCodeExporter]

Since we don't expect to add any new UI features to SVG-Edit 2.4, all 
translators are encouraged to update their lang.xx.js files. See the 
lang.en.js file for the complete list of strings to be translated.

The purpose of this issue is to keep track of this progress.

Notes on changes since last large translation effort:

Element changed: "Polygon" is now "Path"
- Anything with "poly" in its ID should be changed to use "path". Any use 
of the term "polygon" should be changed to the equivalent of the SVG 
"path" element.

Replaced X, Y text fields
- There are only two fields for "X" and "Y", so image_x, image_y, rect_x, 
rect_y, text_x and text_y can now be removed. Instead, there's just 
selected_x and selected_y.

Fixed ids
- "svninfo_dim" should be "svginfo_dim" and "svninfo_change_background" 
should be "svginfo_change_background"

Additionally, everything after "svninfo_dim" is newly added string with 
the "js_strings" section being a list of strings used in dynamic sections 
of the interface. 

Don't hesitate to post any questions/comments/corrections/attachments to 
this issue.

Original issue reported on code.google.com by adeve...@gmail.com on 8 Dec 2009 at 8:08

[GoogleCodeExporter]

Note that the latest lang.en.js file can be found here:
http://svg-edit.googlecode.com/svn/trunk/editor/locale/lang.en.js

Original comment by adeve...@gmail.com on 8 Dec 2009 at 8:11

[GoogleCodeExporter]

A new Dutch language file as requested.

Original comment by jaap.b...@gmail.com on 10 Dec 2009 at 12:07

Attachments:

• local.lang.nl.js

[GoogleCodeExporter]

I was playing with the language files while doing the image below, and 
according to
the ISO 639 standard,
http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes
the iw code (Hebrew) is now he. 
So our language file should be lang.he.js and not lang.iw.js.

I've made http://imgh.us/SVG-edit_Languages_opera.svg . Opened with Opera, this 
file
will show the SVG-edit SVG logo in the background.
Feel free to modify the file!

Original comment by worms_...@yahoo.com on 10 Dec 2009 at 7:04

[GoogleCodeExporter]

Translations in progress:
- farsi
- japanese
- spanish

Original comment by worms_...@yahoo.com on 11 Dec 2009 at 4:15

[GoogleCodeExporter]

There is a small typo in this (Lable instead of Label):

{"id":"layersLable","textContent":"Layers:"},

Original comment by worms_...@yahoo.com on 11 Dec 2009 at 5:15

[GoogleCodeExporter]

Yes, this was a typo on Narendra's part.  We'll have to update the code and all 
the
language files...

Original comment by codedr...@gmail.com on 11 Dec 2009 at 6:41

[GoogleCodeExporter]

In the lang.en.js file, there are two identical lines:

http://code.google.com/p/svg-edit/source/browse/trunk/editor/locale/lang.en.js#1
03
http://code.google.com/p/svg-edit/source/browse/trunk/editor/locale/lang.en.js#1
17

{"id":"svginfo_dim","textContent":"Canvas Dimensions"},

Original comment by worms_...@yahoo.com on 11 Dec 2009 at 6:42

[GoogleCodeExporter]

There is also a duplicate ID, but with two different textContent:

http://code.google.com/p/svg-edit/source/browse/trunk/editor/locale/lang.en.js#8
5
{"id":"svginfo_change_background","textContent":"Canvas Background"},

and
http://code.google.com/p/svg-edit/source/browse/trunk/editor/locale/lang.en.js#1
23
{"id":"svginfo_change_background","textContent":"Editor Background"},

Original comment by worms_...@yahoo.com on 11 Dec 2009 at 6:54

[GoogleCodeExporter]

Added nl and fixed the typo/ID issues for en, fr, nl in r1026. Thanks jaap.blom 
for 
your contributions!

I suggest the "Canvas Background" be the entry to be scrapped, btw (which I 
have 
done already for the lang files I mentioned)

Two other notes:
- It is no longer necessary to include the [keyboard shortcut] at the end of 
translated strings (see issue 355).

- There are four more "js_strings" added  for this purpose:
"key_up":"up",
"key_down":"down",
"key_backspace":"backspace",
"key_del":"delete"

Original comment by adeve...@gmail.com on 11 Dec 2009 at 8:40

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

A few minor adjustments and the correct dutch translation for the new 
"js_strings"
members.

Original comment by jaap.b...@gmail.com on 12 Dec 2009 at 10:05

Attachments:

• local.lang.nl.js

[GoogleCodeExporter]

I have made the rest of the language files which translations for 2.4 haven't 
started
yet "ready for 2.4", that means:

- removed image_x, image_y, rect_x, rect_y, text_x, text_y
- changed tool_path to tool_fhpath for the pencil tool,
- changed tool_poly to tool_path for the path tool,
- removed svninfo_change_background (Canvas Background)
- added all the missing strings
- removed all references to [shortcuts].

I have added a lang.he.js for Hebrew. The file lang.iw.js should be removed for 
the
folder (obsolete name)

I haven't touched:
lang.nln, lang.fr (already up-to-date)
lang.es, lang.fa and lang.ja which are currently being translated.

It would be great if the files in the attached zip could be checked-in. Thanks!

Original comment by worms_...@yahoo.com on 14 Dec 2009 at 9:04

Attachments:

• locales.zip

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Romanian. With thanks to worms invasion for assistance.

Original comment by Christia...@gmail.com on 16 Dec 2009 at 1:54

Attachments:

• lang.ro.js

[GoogleCodeExporter]

Attached please find updated czech locales.

Labels that remain untranslated (no ID yet or I'm getting blind :)
the 'home' icon label reading 'SVG-edit Home Page'
the 'powered by' in right-lower corner
the 'N/A' value when there's no fill

best
Jan

Original comment by jan.pta...@gmail.com on 18 Dec 2009 at 11:01

Attachments:

• lang.cs.js

[GoogleCodeExporter]

Issue 362 has been merged into this issue.

Original comment by codedr...@gmail.com on 18 Dec 2009 at 3:56

[GoogleCodeExporter]

Hi,
here it is the Spanish translation.

Alicia

Original comment by alicia.p...@gmail.com on 21 Dec 2009 at 5:33

Attachments:

• lang.es.js

[GoogleCodeExporter]

Hello,

Thank you, Alicia, for this very valuable contribution!

I hope we'll be able to see the Spanish version of SVG-edit very soon :-)

Original comment by worms_...@yahoo.com on 21 Dec 2009 at 6:53

[GoogleCodeExporter]

Yes, thanks Alicia, great work!

Added in r1077.

Original comment by adeve...@gmail.com on 21 Dec 2009 at 8:09

[GoogleCodeExporter]

After testing the program in Spanish, and having the program itself in front of 
me, I
detected some errors and parts that could be improved.

Here is the right one,
Alicia

Original comment by alicia.p...@gmail.com on 21 Dec 2009 at 10:13

Attachments:

• lang.es.js

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

dreimark noticed that the "opac:" word wasn't translated at all in the UI, in
other words, we do not have a 
{"id":"opacityLabel","textContent":"opac"}, (or something) in the English file.

Original comment by worms_...@yahoo.com on 23 Dec 2009 at 5:27

[GoogleCodeExporter]

Attaching translation from issue 375 here.

Original comment by codedr...@gmail.com on 23 Dec 2009 at 5:40

Attachments:

• german_diff.patch

[GoogleCodeExporter]

Issue 375 has been merged into this issue.

Original comment by codedr...@gmail.com on 23 Dec 2009 at 5:40

[GoogleCodeExporter]

Merged in German translation in r1097

Original comment by codedr...@gmail.com on 23 Dec 2009 at 5:41

[GoogleCodeExporter]

Attaching the japanese language file made "ready for translation" for 2.4

Original comment by worms_...@yahoo.com on 23 Dec 2009 at 7:23

Attachments:

• lang.ja.js

[GoogleCodeExporter]

minor changes. The bot failed today so here is the log  (stripped off unrelated 
messages)

09:58 < wormsxulla> i was using the german translation and there are two or 
                    three things which should be changed in it, i think
09:59 < dreimark> ok
09:59 < dreimark> just tell
10:00 < wormsxulla> there is "speichern" for tool_docprops_save and 
                    tool_source_save, but we changed that between 2.3 and 2.4 
                    to tell "apply changes" and "ok"
10:00 < wormsxulla> it mustn't mean "save" because it actually doesn't save
10:01 < wormsxulla> see 
                    http://code.google.com/svg-edit/wiki/TranslationGuidelines
10:01 < dreimark> hmm, it hink i haven't looked on old translation strings that 
                  much
10:01 < wormsxulla> yeah, i supposed that, that's why i did it a bit :)
10:02 < wormsxulla> also, i think we could use "Pfad" for "path", rather than 
                    "linien mit fûlling

Original comment by rb.p...@gmail.com on 23 Dec 2009 at 7:58

Attachments:

• second_german_translation.patch

[GoogleCodeExporter]

fixed some more issues (typos missing translation)

Original comment by rb.p...@gmail.com on 23 Dec 2009 at 8:36

Attachments:

• second_german_translation.patch

[GoogleCodeExporter]

Here is the Spanish translation after having resolved the "pathtool" issue.

Regards,
Alicia

Original comment by alicia.p...@gmail.com on 23 Dec 2009 at 9:17

Attachments:

• lang.es.js

[GoogleCodeExporter]

Awesome. 
Thank you again, Alicia and rb_proj. 
Happy holidays, and merry Christmas! :-) 

Original comment by worms_...@yahoo.com on 23 Dec 2009 at 10:16

[GoogleCodeExporter]

Last spanish and german file updated by r1110 and r1113

Original comment by worms_...@yahoo.com on 24 Dec 2009 at 12:33

[GoogleCodeExporter]

New dutch translation, fresh from the press.

Original comment by jaap.b...@gmail.com on 24 Dec 2009 at 7:38

Attachments:

• local.lang.nl.js

[GoogleCodeExporter]

Dutch translation freshly updated in r1115, thank you!

Original comment by worms_...@yahoo.com on 25 Dec 2009 at 10:29

[GoogleCodeExporter]

added missing translation for {"id":"tool_node_link","title":"Link Control 
Points"},

i think the engl. msg should be "pair or separate control points for 
manipulating the
path" or something similiar too. may be also bezier curve should be added also 
to the
message. 

At the first time i tried this feature i used a rect. There it is not showing 
any
difference and I didn't get what "Link Control Points" should be.

Original comment by rb.p...@gmail.com on 3 Jan 2010 at 12:10

Attachments:

• lang.de.js.patch

[GoogleCodeExporter]

Final spanish translation for Arbelos by Alicia.

Original comment by worms_...@yahoo.com on 7 Jan 2010 at 3:18

Attachments:

• lang.es.js

[GoogleCodeExporter]

Farsi translation file by Payman Delshad <payman@opera.com>

This translation contains all the strings, including the four ones which were 
added
later (up/down/backspace/delete).

The problems which still exist are:

- The keyboard shortcuts figuring letters (X, B, U, N, etc.) don't make much 
sense in
Farsi, I suppose this will also be the case for languages with non-european
characters. Payman could give us the necessary farsi letters to replace them, 
but
would we be able to make them appear automatically?

- The keyboard shortcuts figuring numbers do mean something, but they do not 
display
correctly (one sees for instance: 
2] something in Farsi] 
or
4] something in Farsi/Shift+4]

see the attached screenshot.

- The main problem is that the HTML layout doesn't really suit RTL languages, 
one
sees things like:

:something in Farsi |value|
whereas it should be
|value|:something in Farsi

I guess it's a bit close to the release to change that and solve this problem 
for all
the future RTL languages that we could have?

Anyway, I am attaching the Farsi file, if we want to include it in 2.4 Arbelos 
as such!

Thank you very very much, Payman, it's really great to have a non-European 
language! :-)

Original comment by worms_...@yahoo.com on 8 Jan 2010 at 4:06

Attachments:

• lang.fa.js
• SVG-edit-Farsi.jpg

[GoogleCodeExporter]

Excellent, I've added it to the 2.4 branch in r1170.

Some good points there, indeed it's too late to fix these things for 2.4. 
Still, I
think it's fair to say the language is more useful like this than to not have 
it at
all. I suppose the keyboard shortcuts will still be useful for Farsi speakers 
that
for whatever reason use latin alphabet keyboards...

Original comment by adeve...@gmail.com on 8 Jan 2010 at 4:27

[GoogleCodeExporter]

Seeing as how we want to release on Monday, is there anything left on this bug 
to do
or can we close it?

Original comment by codedr...@gmail.com on 9 Jan 2010 at 11:24

• Changed state: NeedsInfo

[GoogleCodeExporter]

We can close it I think. All "good" language files were updated for Arbelos. Big
thanks to all the translators!

Original comment by worms_...@yahoo.com on 11 Jan 2010 at 10:01

[GoogleCodeExporter]

Original comment by adeve...@gmail.com on 11 Jan 2010 at 7:02

• Changed state: Done