new strings and translation statistics for trunk (2009-03-31)
Hello, I ran update_po_files.sh in trunk again and commited in r21020.
I also ran some quick statistics; Table 1 shows statistics for trunk before the update, Table 2 after the update. The columns file name, show: total strings, translated strings, fuzzy strings, untranslated strings, translated strings (%), fuzzy strings(%), untranslated strings (%).
Regards ~~helix84
Table1: am.po strings: total: 4779 | 86t 1347f 3346u | 1%t 28%f 70%u ar.po strings: total: 4779 | 449t 1949f 2381u | 9%t 40%f 49%u az.po strings: total: 4779 | 172t 1885f 2722u | 3%t 39%f 56%u be.po strings: total: 4778 | 3158t 970f 650u | 66%t 20%f 13%u bg.po strings: total: 4779 | 2773t 1151f 855u | 58%t 24%f 17%u bn.po strings: total: 4779 | 24t 296f 4459u | 0%t 6%f 93%u br.po strings: total: 4779 | 3225t 892f 662u | 67%t 18%f 13%u ca.po strings: total: 4779 | 3225t 861f 693u | 67%t 18%f 14%u ca@...196... strings: total: 4779 | 2151t 1448f 1180u | 45%t 30%f 24%u cs.po strings: total: 4779 | 2163t 1442f 1174u | 45%t 30%f 24%u da.po strings: total: 4779 | 1841t 1675f 1263u | 38%t 35%f 26%u de.po strings: total: 4779 | 2696t 1121f 962u | 56%t 23%f 20%u dz.po strings: total: 4778 | 0t 0f 4778u | 0%t 0%f 100%u el.po strings: total: 4779 | 298t 2288f 2193u | 6%t 47%f 45%u en_AU.po strings: total: 4779 | 1307t 1871f 1601u | 27%t 39%f 33%u en_CA.po strings: total: 4779 | 182t 1947f 2650u | 3%t 40%f 55%u en_GB.po strings: total: 4779 | 3702t 629f 448u | 77%t 13%f 9%u en_US@...197... strings: total: 4779 | 2115t 1474f 1190u | 44%t 30%f 24%u eo.po strings: total: 4779 | 3676t 625f 478u | 76%t 13%f 10%u es_MX.po strings: total: 4779 | 303t 2338f 2138u | 6%t 48%f 44%u es.po strings: total: 4779 | 4288t 277f 214u | 89%t 5%f 4%u et.po strings: total: 4779 | 117t 1870f 2792u | 2%t 39%f 58%u eu.po strings: total: 4779 | 3268t 865f 646u | 68%t 18%f 13%u fi.po strings: total: 4779 | 2971t 1011f 797u | 62%t 21%f 16%u fr.po strings: total: 4835 | 4690t 27f 118u | 97%t 0%f 2%u ga.po strings: total: 4779 | 56t 1072f 3651u | 1%t 22%f 76%u gl.po strings: total: 4779 | 1857t 1581f 1341u | 38%t 33%f 28%u he.po strings: total: 4779 | 4049t 384f 346u | 84%t 8%f 7%u hr.po strings: total: 4779 | 2820t 1166f 793u | 59%t 24%f 16%u hu.po strings: total: 4779 | 3229t 893f 657u | 67%t 18%f 13%u hy.po strings: total: 4779 | 545t 598f 3636u | 11%t 12%f 76%u id.po strings: total: 4779 | 122t 749f 3908u | 2%t 15%f 81%u it.po strings: total: 4779 | 3194t 898f 687u | 66%t 18%f 14%u ja.po strings: total: 4779 | 1958t 1569f 1252u | 40%t 32%f 26%u km.po strings: total: 4779 | 3702t 626f 451u | 77%t 13%f 9%u ko.po strings: total: 4779 | 4194t 232f 353u | 87%t 4%f 7%u lt.po strings: total: 4779 | 1982t 1524f 1273u | 41%t 31%f 26%u mk.po strings: total: 4779 | 1t 1805f 2973u | 0%t 37%f 62%u mn.po strings: total: 4779 | 181t 1878f 2720u | 3%t 39%f 56%u nb.po strings: total: 4779 | 2109t 1469f 1201u | 44%t 30%f 25%u ne.po strings: total: 4779 | 1702t 1738f 1339u | 35%t 36%f 28%u nl.po strings: total: 4816 | 4216t 24f 576u | 87%t 0%f 11%u nn.po strings: total: 4779 | 1413t 1880f 1486u | 29%t 39%f 31%u pa.po strings: total: 4779 | 827t 1797f 2155u | 17%t 37%f 45%u pl.po strings: total: 4779 | 4330t 273f 176u | 90%t 5%f 3%u pt_BR.po strings: total: 4779 | 3105t 968f 706u | 64%t 20%f 14%u pt.po strings: total: 4779 | 2720t 1161f 898u | 56%t 24%f 18%u ro.po strings: total: 4811 | 950t 944f 2917u | 19%t 19%f 60%u ru.po strings: total: 4805 | 4477t 135f 193u | 93%t 2%f 4%u rw.po strings: total: 4779 | 67t 1925f 2787u | 1%t 40%f 58%u sk.po strings: total: 4779 | 3820t 571f 388u | 79%t 11%f 8%u sl.po strings: total: 4779 | 3807t 531f 441u | 79%t 11%f 9%u sq.po strings: total: 4779 | 72t 1141f 3566u | 1%t 23%f 74%u sr@...158... strings: total: 4779 | 3057t 957f 765u | 63%t 20%f 16%u sr.po strings: total: 4779 | 3057t 957f 765u | 63%t 20%f 16%u sv.po strings: total: 4779 | 1181t 1834f 1764u | 24%t 38%f 36%u th.po strings: total: 4779 | 1043t 1414f 2322u | 21%t 29%f 48%u tr.po strings: total: 4779 | 1110t 1770f 1899u | 23%t 37%f 39%u uk.po strings: total: 4779 | 4293t 276f 210u | 89%t 5%f 4%u vi.po strings: total: 4779 | 3163t 1027f 589u | 66%t 21%f 12%u zh_CN.po strings: total: 4779 | 2909t 973f 897u | 60%t 20%f 18%u zh_TW.po strings: total: 4778 | 0t 0f 4778u | 0%t 0%f 100%u
Table2: am.po strings: total: 4885 | 85t 1372f 3428u | 1%t 28%f 70%u ar.po strings: total: 4885 | 448t 1979f 2458u | 9%t 40%f 50%u az.po strings: total: 4885 | 169t 1916f 2800u | 3%t 39%f 57%u be.po strings: total: 4885 | 3146t 1015f 724u | 64%t 20%f 14%u bg.po strings: total: 4885 | 2769t 1183f 933u | 56%t 24%f 19%u bn.po strings: total: 4885 | 23t 305f 4557u | 0%t 6%f 93%u br.po strings: total: 4885 | 3219t 926f 740u | 65%t 18%f 15%u ca.po strings: total: 4885 | 3219t 895f 771u | 65%t 18%f 15%u ca@...196... strings: total: 4885 | 2148t 1480f 1257u | 43%t 30%f 25%u cs.po strings: total: 4885 | 2160t 1474f 1251u | 44%t 30%f 25%u da.po strings: total: 4885 | 1838t 1707f 1340u | 37%t 34%f 27%u de.po strings: total: 4885 | 2690t 1155f 1040u | 55%t 23%f 21%u dz.po strings: total: 4884 | 0t 0f 4884u | 0%t 0%f 100%u el.po strings: total: 4885 | 297t 2318f 2270u | 6%t 47%f 46%u en_AU.po strings: total: 4885 | 1304t 1902f 1679u | 26%t 38%f 34%u en_CA.po strings: total: 4885 | 179t 1978f 2728u | 3%t 40%f 55%u en_GB.po strings: total: 4885 | 3694t 669f 522u | 75%t 13%f 10%u en_US@...197... strings: total: 4885 | 2112t 1506f 1267u | 43%t 30%f 25%u eo.po strings: total: 4885 | 3668t 665f 552u | 75%t 13%f 11%u es_MX.po strings: total: 4885 | 300t 2369f 2216u | 6%t 48%f 45%u es.po strings: total: 4885 | 4279t 316f 290u | 87%t 6%f 5%u et.po strings: total: 4885 | 114t 1901f 2870u | 2%t 38%f 58%u eu.po strings: total: 4885 | 3262t 899f 724u | 66%t 18%f 14%u fi.po strings: total: 4885 | 2965t 1045f 875u | 60%t 21%f 17%u fr.po strings: total: 4885 | 4685t 62f 138u | 95%t 1%f 2%u ga.po strings: total: 4885 | 55t 1094f 3736u | 1%t 22%f 76%u gl.po strings: total: 4885 | 1851t 1615f 1419u | 37%t 33%f 29%u he.po strings: total: 4885 | 4041t 423f 421u | 82%t 8%f 8%u hr.po strings: total: 4885 | 2814t 1200f 871u | 57%t 24%f 17%u hu.po strings: total: 4885 | 3223t 927f 735u | 65%t 18%f 15%u hy.po strings: total: 4885 | 544t 621f 3720u | 11%t 12%f 76%u id.po strings: total: 4885 | 119t 767f 3999u | 2%t 15%f 81%u it.po strings: total: 4885 | 3188t 932f 765u | 65%t 19%f 15%u ja.po strings: total: 4885 | 1955t 1601f 1329u | 40%t 32%f 27%u km.po strings: total: 4885 | 3694t 666f 525u | 75%t 13%f 10%u ko.po strings: total: 4885 | 4181t 284f 420u | 85%t 5%f 8%u lt.po strings: total: 4885 | 1979t 1556f 1350u | 40%t 31%f 27%u mk.po strings: total: 4885 | 0t 1835f 3050u | 0%t 37%f 62%u mn.po strings: total: 4885 | 178t 1909f 2798u | 3%t 39%f 57%u nb.po strings: total: 4885 | 2106t 1501f 1278u | 43%t 30%f 26%u ne.po strings: total: 4885 | 1699t 1770f 1416u | 34%t 36%f 28%u nl.po strings: total: 4885 | 4209t 56f 620u | 86%t 1%f 12%u nn.po strings: total: 4885 | 1410t 1912f 1563u | 28%t 39%f 31%u pa.po strings: total: 4885 | 824t 1828f 2233u | 16%t 37%f 45%u pl.po strings: total: 4885 | 4312t 322f 251u | 88%t 6%f 5%u pt_BR.po strings: total: 4885 | 3099t 1001f 785u | 63%t 20%f 16%u pt.po strings: total: 4885 | 2716t 1193f 976u | 55%t 24%f 19%u ro.po strings: total: 4885 | 949t 970f 2966u | 19%t 19%f 60%u ru.po strings: total: 4885 | 4439t 196f 250u | 90%t 4%f 5%u rw.po strings: total: 4885 | 66t 1953f 2866u | 1%t 39%f 58%u sk.po strings: total: 4885 | 3811t 612f 462u | 78%t 12%f 9%u sl.po strings: total: 4885 | 3799t 571f 515u | 77%t 11%f 10%u sq.po strings: total: 4885 | 71t 1168f 3646u | 1%t 23%f 74%u sr@...158... strings: total: 4885 | 3051t 991f 843u | 62%t 20%f 17%u sr.po strings: total: 4885 | 3051t 991f 843u | 62%t 20%f 17%u sv.po strings: total: 4885 | 1178t 1865f 1842u | 24%t 38%f 37%u th.po strings: total: 4885 | 1040t 1445f 2400u | 21%t 29%f 49%u tr.po strings: total: 4885 | 1107t 1800f 1978u | 22%t 36%f 40%u uk.po strings: total: 4885 | 4284t 315f 286u | 87%t 6%f 5%u vi.po strings: total: 4885 | 3158t 1064f 663u | 64%t 21%f 13%u zh_CN.po strings: total: 4885 | 2903t 1008f 974u | 59%t 20%f 19%u zh_TW.po strings: total: 4884 | 0t 0f 4884u | 0%t 0%f 100%u
On Tue, Mar 31, 2009 at 12:51, Leandro Regueiro <leandro.regueiro@...5...> wrote:
I ran update_po_files.sh in trunk again and commited in r21020.
Why is so difficult to generate a .pot file?
See Alexandre's response here: http://sourceforge.net/mailarchive/forum.php?thread_name=200901060816.01179....
Regards, ~~helix84
On Tue, Mar 31, 2009 at 12:56 PM, helix84 <helix84@...150...> wrote:
On Tue, Mar 31, 2009 at 12:51, Leandro Regueiro <leandro.regueiro@...5...> wrote:
I ran update_po_files.sh in trunk again and commited in r21020.
Why is so difficult to generate a .pot file?
See Alexandre's response here: http://sourceforge.net/mailarchive/forum.php?thread_name=200901060816.01179....
But with this we have to checkout the whole code, isn't it?
Bye, Leandro Regueiro
On Tue, Mar 31, 2009 at 13:02, Leandro Regueiro <leandro.regueiro@...5...> wrote:
On Tue, Mar 31, 2009 at 12:56 PM, helix84 <helix84@...150...> wrote:
On Tue, Mar 31, 2009 at 12:51, Leandro Regueiro <leandro.regueiro@...5...> wrote:
I ran update_po_files.sh in trunk again and commited in r21020.
Why is so difficult to generate a .pot file?
See Alexandre's response here: http://sourceforge.net/mailarchive/forum.php?thread_name=200901060816.01179....
But with this we have to checkout the whole code, isn't it?
That's right. And compile it which takes quite some time.
Regards, ~~helix84
On Tue, Mar 31, 2009 at 3:04 PM, helix84 wrote:
Why is so difficult to generate a .pot file?
See Alexandre's response here: http://sourceforge.net/mailarchive/forum.php?thread_name=200901060816.01179....
But with this we have to checkout the whole code, isn't it?
That's right. And compile it which takes quite some time.
It looks like people are not happy. So I volunteer to update POT file in SVN on weekly basis (say, every Friday night) and, additionally, after a major change in strings (like a bunch of new SVG filters added). Any objections?
Alexandre
De : helix84 <helix84@...150...> On Tue, Mar 31, 2009 at 13:02, Leandro Regueiro wrote:
On Tue, Mar 31, 2009 at 12:56 PM, helix84 wrote:
On Tue, Mar 31, 2009 at 12:51, Leandro Regueiro wrote:
I ran update_po_files.sh in trunk again and commited in r21020.
Why is so difficult to generate a .pot file?
See Alexandre's response here:
http://sourceforge.net/mailarchive/forum.php?thread_name=200901060816.01179....
But with this we have to checkout the whole code, isn't it?
That's right. And compile it which takes quite some time.
Not if you compile it regularly from SVN. As you don't need to build the whole code, the compile time is *usually* short.
By the way, did you see this bug (wishlist), helix84? https://bugs.launchpad.net/inkscape/+bug/289240
Do you (and others!) think it's possible (or necessary) to automate the po files updating process, or, at least, have them manually updated more regularly? -- Nicolas
De : Alexandre Prokoudine <alexandre.prokoudine@...5...> It looks like people are not happy. So I volunteer to update POT file in SVN on weekly basis (say, every Friday night) and, additionally, after a major change in strings (like a bunch of new SVG filters added). Any objections?
Thanks Alexandre! -- Nicolas
It looks like people are not happy. So I volunteer to update POT file in SVN on weekly basis (say, every Friday night) and, additionally, after a major change in strings (like a bunch of new SVG filters added). Any objections?
I really think that generating a new POT file on an automated way is a good idea. Another projects do this and also automatically update all the po files. I think it isn't so difficult, creating a script and putting it on cron...
Bye, Leandro Regueiro
On Tue, Mar 31, 2009 at 3:32 PM, Leandro Regueiro wrote:
It looks like people are not happy. So I volunteer to update POT file in SVN on weekly basis (say, every Friday night) and, additionally, after a major change in strings (like a bunch of new SVG filters added). Any objections?
I really think that generating a new POT file on an automated way is a good idea. Another projects do this and also automatically update all the po files. I think it isn't so difficult, creating a script and putting it on cron...
And this script is able to check whether compilation was successful? :)
Alexandre
On Tue, Mar 31, 2009 at 13:26, Nicolas Dufour <nicoduf@...193...> wrote:
De : helix84 <helix84@...150...> On Tue, Mar 31, 2009 at 13:02, Leandro Regueiro wrote:
On Tue, Mar 31, 2009 at 12:56 PM, helix84 wrote:
On Tue, Mar 31, 2009 at 12:51, Leandro Regueiro wrote:
I ran update_po_files.sh in trunk again and commited in r21020.
Why is so difficult to generate a .pot file?
See Alexandre's response here:
http://sourceforge.net/mailarchive/forum.php?thread_name=200901060816.01179....
But with this we have to checkout the whole code, isn't it?
That's right. And compile it which takes quite some time.
Not if you compile it regularly from SVN. As you don't need to build the whole code, the compile time is *usually* short.
By the way, did you see this bug (wishlist), helix84? https://bugs.launchpad.net/inkscape/+bug/289240
Do you (and others!) think it's possible (or necessary) to automate the po files updating process, or, at least, have them manually updated more regularly?
Updating the .pot file in an automated is necessary. Daily basis wouldn't hurt. I don't think it's necessary to update the .po files from .pot so often, as most translators should know how to do it and they might feel it interferes with their work (if the file is updated before their patch is commited). So I suggest to commit .po files updates once a month.
BTW Alexandre, is the release date for 0.47 specified? I didn't find any release schedule.
Regards, ~~helix84
On Tue, Mar 31, 2009 at 1:32 PM, Leandro Regueiro <leandro.regueiro@...5...> wrote:
It looks like people are not happy. So I volunteer to update POT file in SVN on weekly basis (say, every Friday night) and, additionally, after a major change in strings (like a bunch of new SVG filters added). Any objections?
I really think that generating a new POT file on an automated way is a good idea. Another projects do this and also automatically update all the po files. I think it isn't so difficult, creating a script and putting it on cron...
By the way, thanks Alexandre.
Doing the way you were doing, if a translator doesn't do this for some reason, when you finally update the files it encounters that has to update a lot of strings.
If the files are well formed it isn't necessary to check if it Inkscape compiles right with that translations files.
Bye, Leandro Regueiro
Updating the .pot file in an automated is necessary. Daily basis wouldn't hurt. I don't think it's necessary to update the .po files from .pot so often, as most translators should know how to do it and they might feel it interferes with their work (if the file is updated before their patch is commited). So I suggest to commit .po files updates once a month.
Really the updating of .po files only is needed just before a new version is going to be built. But generating a .pot file every week or best, every day is necessary. The translators know how to update their .po files using the .pot file, but this .pot file must exist and be updated. This way only the .pot generation needs to be automated.
Bye, Leandro Regueiro
De : helix84 <helix84@...150...>
BTW Alexandre, is the release date for 0.47 specified? I didn't find any release schedule.
There's something here: http://wiki.inkscape.org/wiki/index.php/0.47_Refactoring_Plan But I don't know if it has been widely agreed. -- Nicolas
On Tue, Mar 31, 2009 at 13:49, Nicolas Dufour <nicoduf@...193...> wrote:
De : helix84 <helix84@...150...>
BTW Alexandre, is the release date for 0.47 specified? I didn't find any release schedule.
There's something here: http://wiki.inkscape.org/wiki/index.php/0.47_Refactoring_Plan But I don't know if it has been widely agreed.
Those dates relate to 2008 ;) look at 0.46 release and history of that article.
Regards, ~~helix84
2009/3/31 Leandro Regueiro <leandro.regueiro@...5...>:
It looks like people are not happy. So I volunteer to update POT file in SVN on weekly basis (say, every Friday night) and, additionally, after a major change in strings (like a bunch of new SVG filters added). Any objections?
I really think that generating a new POT file on an automated way is a good idea. Another projects do this and also automatically update all the po files. I think it isn't so difficult, creating a script and putting it on cron...
By the way, thanks Alexandre.
Alexandre, if you volunteer to generate the new file manually every week I can easily set-up a little job on my server and provide an up-to-date pot file. I have already been doing some automation of the process for the Polish translations.
Regardless - if I can be of any help - let me know.
Also - do we envisage putting the .pot into SVN - although it is not a big file perhaps it could be uploaded to a website (inkscape?) as in SVN it can always be update from source code.
BTW. The original discussion was held here: https://bugs.launchpad.net/inkscape/+bug/179209
Regards, Marcin
On Tue, Mar 31, 2009 at 6:17 PM, Marcin Floryan wrote:
Alexandre, if you volunteer to generate the new file manually every week I can easily set-up a little job on my server and provide an up-to-date pot file. I have already been doing some automation of the process for the Polish translations.
Regardless - if I can be of any help - let me know.
Also - do we envisage putting the .pot into SVN - although it is not a big file perhaps it could be uploaded to a website (inkscape?) as in SVN it can always be update from source code.
In fact I was meaning committing a POT fiel to SVN :)
Alexandre
SVN would be the easiest and most handy. In this case you have the pot file and all .po files (you can use other languages as a reference for your own translations) together. And also, everyone knows where to look for the latest pot. :-)
Regards Kris
2009/3/31 Alexandre Prokoudine <alexandre.prokoudine@...5...>:
On Tue, Mar 31, 2009 at 6:17 PM, Marcin Floryan wrote:
Alexandre, if you volunteer to generate the new file manually every week I can easily set-up a little job on my server and provide an up-to-date pot file. I have already been doing some automation of the process for the Polish translations.
Regardless - if I can be of any help - let me know.
Also - do we envisage putting the .pot into SVN - although it is not a big file perhaps it could be uploaded to a website (inkscape?) as in SVN it can always be update from source code.
In fact I was meaning committing a POT fiel to SVN :)
Alexandre
SVN would be the easiest and most handy. In this case you have the pot file and all .po files (you can use other languages as a reference for your own translations) together. And also, everyone knows where to look for the latest pot. :-)
Usually a new translator expects to have the .pot files with the .po files.
Bye, Leandro Regueiro
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I used to translate on battle of Wesnoth, they have a nice site http://www.wesnoth.org/gettext/ on which they keep track of progress. Though I do not know if they do a pot update automaticly it might be useful to contact them (Nils Kneuper aka Ivanovic) to know how they do it. Or some other project, because I guess we do not need to reinvent the wheel.
Foppe
Leandro Regueiro schreef:
Updating the .pot file in an automated is necessary. Daily basis
wouldn't hurt.
I don't think it's necessary to update the .po files from .pot so often, as most translators should know how to do it and they might feel it interferes with their work (if the file is updated before their patch is commited). So I suggest to commit .po files updates once a month.
Really the updating of .po files only is needed just before a new version is going to be built. But generating a .pot file every week or best, every day is necessary. The translators know how to update their .po files using the .pot file, but this .pot file must exist and be updated. This way only the .pot generation needs to be automated.
Bye, Leandro Regueiro
Inkscape-translator mailing list Inkscape-translator@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-translator
Maybe an automated statistics page could be useful to promote competition between the different languages like in other projects (kde or wesnoth for example).
Bye, Leandro Regueiro
2009/4/1 Leandro Regueiro <leandro.regueiro@...5...>:
Maybe an automated statistics page could be useful to promote competition between the different languages like in other projects (kde or wesnoth for example).
I have cobbled one quickly together.
http://mfloryan.statnet.pl/~mfloryan/inkscape/
If people think it makes sense I can automate it and generate as often as needed.
Any comments welcome.
Regards,
Maybe an automated statistics page could be useful to promote competition between the different languages like in other projects (kde or wesnoth for example).
I have cobbled one quickly together.
http://mfloryan.statnet.pl/~mfloryan/inkscape/
If people think it makes sense I can automate it and generate as often as needed.
If it is a lot of work could you add the top list function to list from more translated to less translated? This is for improving competition. And add a link in the Inkscape website. Of course it should be generated automatically, lets say one time per day or per week...
By the way it looks good, a lot of thanks.
Bye, Leandro Regueiro
On Thu, Apr 2, 2009 at 4:34 PM, Leandro Regueiro <leandro.regueiro@...5...> wrote:
Maybe an automated statistics page could be useful to promote competition between the different languages like in other projects (kde or wesnoth for example).
I have cobbled one quickly together.
http://mfloryan.statnet.pl/~mfloryan/inkscape/
If people think it makes sense I can automate it and generate as often as needed.
If it is a lot of work could you add the top list function to list from more translated to less translated? This is for improving competition. And add a link in the Inkscape website. Of course it should be generated automatically, lets say one time per day or per week...
By the way it looks good, a lot of thanks.
Take a look here http://l10n.kde.org/stats/gui/trunk-kde4/toplist/
Bye, Leandro Regueiro
On Tue, Mar 31, 2009 at 11:49:35AM +0000, Nicolas Dufour wrote:
De : helix84 <helix84@...150...>
BTW Alexandre, is the release date for 0.47 specified? I didn't find any release schedule.
There's something here: http://wiki.inkscape.org/wiki/index.php/0.47_Refactoring_Plan But I don't know if it has been widely agreed.
Pretty sure we're well beyond any established dates.
Keep up the good work everyone, Bryce
Hi!
Attached to this message you can find a patch to correct some typos in Inkscape messages (just an aspell checking). Can they be fixed before the realease?
Thanks in advance. Yuri
P.S. BTW To whom can I send an updated Ukrainian translation? It seems our committer is out of business. :(
On Wed, May 6, 2009 at 17:19, Yuri Chornoivan <yurchor@...204...> wrote:
Attached to this message you can find a patch to correct some typos in Inkscape messages (just an aspell checking). Can they be fixed before the realease?
Thank you, I commited your patch in r21291. There's enough time before release, don't worry. I also updated inkscape.pot.
Regards ~~helix84
participants (9)
-
Alexandre Prokoudine
-
Bryce Harrington
-
Foppe Benedictus
-
helix84
-
Kris De Gussem
-
Leandro Regueiro
-
Marcin Floryan
-
Nicolas Dufour
-
Yuri Chornoivan