- Inkscape Translators - Inkscape Mailman

Potential additional translations
by Matiphas 20 Jun '06

20 Jun '06

Hi all, here is the result of the analysis of the po files found in Gnome cvs for Sodipodi. I've simply downloaded then synchronized them with current Inkscape strings : the status is not really brilliant. I guess merging them in our svn is not really worth the effort. (on the other hand, it also simply means that Inkscape has evolved a lot, which is a good thing :) ) Regards, matiphas Total number of localizable strings: 2148 am translated: 83 ( 3 %), fuzzy: 318 ( 14 %), untranslated: 1747 ( 81 %), total: 2148 az translated: 178 ( 8 %), fuzzy: 634 ( 29 %), untranslated: 1336 ( 62 %), total: 2148 be translated: 170 ( 7 %), fuzzy: 638 ( 29 %), untranslated: 1340 ( 62 %), total: 2148 da translated: 115 ( 5 %), fuzzy: 681 ( 31 %), untranslated: 1352 ( 62 %), total: 2148 en_CA translated: 186 ( 8 %), fuzzy: 659 ( 30 %), untranslated: 1303 ( 60 %), total: 2148 en_GB translated: 186 ( 8 %), fuzzy: 659 ( 30 %), untranslated: 1303 ( 60 %), total: 2148 et translated: 114 ( 5 %), fuzzy: 627 ( 29 %), untranslated: 1407 ( 65 %), total: 2148 fi translated: 181 ( 8 %), fuzzy: 634 ( 29 %), untranslated: 1333 ( 62 %), total: 2148 ga translated: 55 ( 2 %), fuzzy: 206 ( 9 %), untranslated: 1887 ( 87 %), total: 2148 gl translated: 96 ( 4 %), fuzzy: 667 ( 31 %), untranslated: 1385 ( 64 %), total: 2148 hr translated: 185 ( 8 %), fuzzy: 632 ( 29 %), untranslated: 1331 ( 61 %), total: 2148 ja translated: 185 ( 8 %), fuzzy: 634 ( 29 %), untranslated: 1329 ( 61 %), total: 2148 ko translated: 170 ( 7 %), fuzzy: 634 ( 29 %), untranslated: 1344 ( 62 %), total: 2148 mk translated: 0 ( 0 %), fuzzy: 355 ( 16 %), untranslated: 1793 ( 83 %), total: 2148 mn translated: 185 ( 8 %), fuzzy: 630 ( 29 %), untranslated: 1333 ( 62 %), total: 2148 ne translated: 186 ( 8 %), fuzzy: 659 ( 30 %), untranslated: 1303 ( 60 %), total: 2148 pa translated: 134 ( 6 %), fuzzy: 514 ( 23 %), untranslated: 1500 ( 69 %), total: 2148 pt translated: 211 ( 9 %), fuzzy: 709 ( 33 %), untranslated: 1228 ( 57 %), total: 2148 rw translated: 58 ( 2 %), fuzzy: 689 ( 32 %), untranslated: 1401 ( 65 %), total: 2148 sk translated: 213 ( 9 %), fuzzy: 698 ( 32 %), untranslated: 1237 ( 57 %), total: 2148 sq translated: 69 ( 3 %), fuzzy: 240 ( 11 %), untranslated: 1839 ( 85 %), total: 2148 sv translated: 215 ( 10 %), fuzzy: 716 ( 33 %), untranslated: 1217 ( 56 %), total: 2148 tr translated: 176 ( 8 %), fuzzy: 706 ( 32 %), untranslated: 1266 ( 58 %), total: 2148

2 1

Re: [Inkscape-translator] [Inkscape-devel] [Inkscape-tester] New translations we need?
by Ben Fowler 20 Jun '06

20 Jun '06

On 20/06/06, Bryce Harrington <bryce@...1...> wrote: > On Mon, Jun 19, 2006 at 10:59:49AM +0100, Ben Fowler wrote: > > On 12/06/06, Alexandre Prokoudine <alexandre.prokoudine@...5...> wrote: > > > On 6/11/06, Bryce Harrington wrote: > > > > Of these, we have some at >80% already. The ones in Inkscape that are > > > > not at 80% are: > > > > > > > > bg, en_CA, en_GB, fi, nb, ne, nl, pl, pt, pr_BR, ru, sk, sr, sv, uk, vi > > > > Apologies if I missed the beginning of this thread or I am out of > > place, but is there really a deficiency in en_GB translations? If so, > > there cannot be a good reason for this as there are plenty of > > Inkscapers in Albion. > > The above list was generated by looking at what translations GNOME had > at 50% or greater, and en_CA and en_GB were there. I thought it'd make > a good goal to have Inkscape get >80% translations for the same set of > languages that GNOME has the best support for. I was surprised too that > en_CA and en_GB showed up there; I assume they ranked high due to it > being relatively easy to do them, compared with going from English to a > non-English language. Thank you, I had to read that twice before I grasped it. GNOME is reporting on GNOME translations, not on Inkscape translations. At the moment, Inkscape's en_GB is arguably at 0% as there is no en_GB.po file. Assuming that this file is needed, there are three possibilities: 1) There is a volunteer who has made contact with one of the regulars on the translators list; 2) I can start the ball rolling by copying the inkscape.pot file to en_GB.po and adding it to the tracker, if this is not premature and 3) I can cajole the Huddersfield Linux User group into maintaining this file. Obviously (1) has priority, but I think that partial and exploratory translations are considered helpful as stepping stones. I looked at a version of inkscape.pot of a few weeks ago, and it had 2175 entries, so my admiration for the work of the translation teams which was already high is increased by my seeing the magnitude and repetitive nature of the task. Personally, I feel that if an en_GB translation is welcomed, then we should see to it that it is done very speedily, as it would be ridiculous for an English to English translation to take a significant amount of time, wouldn't it? Ben

2 1

Babelfish translation on www.Inkscape.org
by vonHalenbach 19 Jun '06

19 Jun '06

Hi Inkscape translators ! I have just tried to use the babelfish translation on our homepage. Did you try it too? It is located on the bottom of the page. translate to [ Chinese French German Italian Japanese Korean Portuguese Spanish ] When i use the German button, the translation is terrible, to be polite. It produces nonsens and bullshit with no sense at all. It is useless. A relict from old times,when inkscape had no translation of the homepage. Currently we have german, french, italic and spanisch translation which is maintained. It could be improoved. Maybe. I think the best solution is to disable babelfish completly. How do you think about that? Please try that link in your language and give your feedback in this mailinglist.

1 0

Missing Russian dialog image
by Jon A. Cruz 17 Jun '06

17 Jun '06

The tutorial-tracing.ru.svg that's in the latest set of tutorial updates in a patch (#1506381) is missing the potrace-ru.png shot of the dialog. We have potrace.png, potrace-de.png and potrace-fr.png. If someone could attach a potrace-ru.png to the patch, that would let me commit it. Thanks http://sourceforge.net/tracker/? func=detail&aid=1506381&group_id=93438&atid=604308

2 1

Re: [Inkscape-translator] [Inkscape-user] [Inkscape-tester] New translations we need?
by unknown＠example.com 14 Jun '06

14 Jun '06

Hi Kinsley > > I get the feeling that > > American English that is more regarded as standard than British > > English. > > Eeek! > > Someone please tell me how I update the *proper* English en_GB > language file. I'll do it today. > The file doesn't exist yet. Potential solution if you volunteer for maintaining an en_GB 'translation' of Inkscape is Take a look at : http://wiki.inkscape.org/wiki/index.php/InterfaceTranslation#Interface_Tran… It indicates where to download inkscape.pot. Once you've got this file, rename it to en_GB.po and modify it with the appropriate tool (poedit or kbabel). A complete translation of Inkscape interface can consume a lot of time, but I guess, translating from en_US to en_GB might be faster. Sorry, i have not a lot of time for providing you long explanations today. But the translator community will surely be able to help you (i've cc'ed the translator list). Regards, matiphas

2 1

Vietnamese translation
by Clytie Siddall 14 Jun '06

14 Jun '06

Hello everybody :) I'm here in response to the matiphas' email to the Deb18n list. I'm willing to translate Inkscape into Vietnamese. I've had a look at your wiki page (information for translators), which is very helpful. I have a couple of questions. ;) 1. What is your timeline? I'd hope to get the interface file translated for release. 2. At the bottom of the status page, you note that: > GNOME has the following at >50%. > bg, ca, cs, de, en_CA, en_GB, es, fi, fr, nb, ne, nl, pl, pt, > pt_BR, ru, sk, sr, sv, uk, vi, zh_CN, and zh_TW I also translate for GNOME, and I can't find Inkscape on the GNOME l10n status pages [1]. If it had been there, I would have translated it long ago, and kept it updated for releases. Where does Inkscape fit in with GNOME? Would I do better to get the interface PO file from GNOME (and if so, how, please?), or directly from SVN? Thanks for your help. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN [1] http://l10n-status.gnome.org/index.html

4 7

Re: [Inkscape-translator] Authors needed for Inkscape 0.44 articles
by unknown＠example.com 13 Jun '06

13 Jun '06

> Today's Topics: > > 1. Re: Authors needed for Inkscape 0.44 articles (cedric GEMY) > 2. Re: Authors needed for Inkscape 0.44 articles (cedric GEMY) > I think it could be useful to publish a little newsarticle on Wikinews for the 0.44 release, to make it really public. http://en.wikinews.org/wiki/Main_Page http://fr.wikinews.org/wiki/Accueil http://de.wikinews.org/wiki/Hauptseite http://it.wikinews.org/wiki/Pagina_principale I alreddy thought about writing some flashy lines for the german wikinews. Maybe other Inkscape users, especially translators could do that for their language. Greetings vonHalenbach

1 0

Re: [Inkscape-translator] Inkscape translation
by unknown＠example.com 13 Jun '06

13 Jun '06

Hi Jean-Christophe, > You have maybe noticed that I fwded your mail to the OmegaT user > group list. Yes thank you very much. This is very kind of you. > I also checked your translation pages and here are a few bits and > pieces of information that you could use for updating the information > on the wiki: > > http://wiki.inkscape.org/wiki/index.php/DocumentationTranslation > > A release candidate/beta version of OmegaT to be published sometimes > this week will have a prototype DocBook support. I tested the pre- > release version and Maxym, the dev lead, is working on the few > obvious bugs I found. > > Currently OmegaT stable (obsoleted by the recent RC versions) does > not even have proper HTML support. I use a personal hack to do > DocBook, but I would not advise "normal" translators to use it. > > OmegaT will also have a prototype PO file support in the same soon to > come RC release, so it will be possible to handle DocBook files > directly, man pages through po4a (converts nroff to PO and back) etc. > > You may want to point at the po4a page, the documentation is a little > bit outdated and the supported formats now include latex/tex/text > along with the advertized SGML, nroff etc... > > As far as > http://wiki.inkscape.org/wiki/index.php/WebSiteTranslation > > is concerned, you may want to know that the current RC8 version of > OmegaT has _very good_ html support. If the files are declared as > html files in the file filters preference settings (by adding .inc to > the html files list) OmegaT will parse them without any problem. > Ah, this is very useful information. Once again, thanks a lot. This kind of proactive help is really appreciated. I'll take a look at out Translation pages, and update OmegaT information according to your mail (when I get home). For the moment, I cc this answer to our translation mailing list. Best regards, matiphas

1 0

Unmaintained translations?
by Bryce Harrington 12 Jun '06

12 Jun '06

Hi all, Kees mentioned today that he saw another project that modified its makefile to only install translations that were at least XX%. The idea being to avoid installing really poor quality translations. Do you guys think that'd be worthwhile to do for Inkscape too? (And is anyone interested in hooking in the appropriate logic to the makefiles?) Alternatively, I know many of our translations are unmaintained since Sodipodi days, and the percent translated for many are very low (under 10%). Is it at all worthwhile to have these files in our codebase? If they are of no true use, why don't we just eliminate them entirely? This would remove cruft, and improve build/install time. Bryce

4 3

0.44 plan of attack
by Aaron Spike 11 Jun '06

11 Jun '06

Bug fixing energy seems to be dwindling. To me this means it is release time. I'd like to get input from others on a few topics. 1) Translation status. Translation is an eternal project. I don't know how to quantify what is good enough for release. Arpad, Matiphas, how are we doing? I think it is time to get serious about this hard freeze and turn to patches, but I want to make sure you are ready. 2) Quality assurance. I looked through the bug tracker. We have some new issues. The font selector crash [1501150] is easy to reproduce, but also quite easy to avoid. Jon was looking into [1501156] last I heard. I've been waiting to hear from bbyak about the snapping bugs [1429049]. I think we are going to hear about [1497837] libgc-6.7 a lot but there seems to be a solution. Are we release quality? If not, I think we are very close. What do others think? 3) Stable branch. We're switching things up a bit this time. We have had a slightly warmed over freeze. And we plan to maintain a stable branch for 0.44. Could we perhaps tie up loose ends and tighten down our committing habits tomorrow, Thursday June 8th? Then in the evening US Central time, I will branch 0.44 we can begin the absolute freeze on that branch, all fixes going into the tracker, and reopen HEAD for those eager to wreak havoc. If all goes well cut the release from the branch on Tuesday. Sound like a plan? Speak up now. :-) Aaron Spike

8 14