I feel that we should put out a call for translators to the wider community. In preparation for that I updated the Wiki's Translating page and added a winepo script to help translators who don't want to check out the whole Wine source:
http://wiki.winehq.org/Translating
Here's the proposed news message for the website:
Translators wanted!
<p>Wine is looking for translators for the 1.4 release!</p>
<p>Wine's translation <a href="http://fgouget.free.fr/wine-po/">status page</a> shows only 12 complete translations. We'd like to do better for 1.4.</p>
<p>Luckily, starting with 1.4 Wine uses PO files, thus making translations easier than ever before. So check out how to <a href="http://wiki.winehq.org/Translating">get started</a> and help us make Wine usable in your country.</p>
And here is the proposed wine-users message:
Wine 1.4 is making good progress. Unfortunately we still have a lot of translations that are quite incomplete and have no active translators, thus making Wine unusable in many countries. You track progress on this page:
http://fgouget.free.fr/wine-po/As you can see we currently have 12 pretty complete translations and 5 others that are advanced too. But that still leaves 25 languages without much, not counting those that are not in the list. This page also lists some suspected issues that would make easy targets for a translator short on time.
The good news is that Wine now uses standard PO files for localization which makes translation easier than ever before. You even get to choose between working straight on Wine's source or just editing the one PO file for your language. So check out the instructions below and make Wine usable for users in your country!
http://wiki.winehq.org/Translating
Of course if you can help translating Wine, you can also consider this your call to action<g>.
Hello,
On Fri, Feb 17, 2012 at 2:13 AM, Francois Gouget fgouget@free.fr wrote:
I feel that we should put out a call for translators to the wider community. In preparation for that I updated the Wiki's Translating page and added a winepo script to help translators who don't want to check out the whole Wine source:
I would like to help to update the Simplified Chinese translation, but most likely I have no enouth time to complete it before wine-1.4 final release. Could anyone give a deadline?
If anyone would like to translate Simplified Chinese please post a reply here to prevent duplication work.
Also I'll forward this mail to Traditional Chinese community, since as a native Simplified Chinese speaker I can't use Traditional Chinese correctly every time.
Thanks Francois and the Wine community :)
Qian Hong fracting@gmail.com writes:
I would like to help to update the Simplified Chinese translation, but most likely I have no enouth time to complete it before wine-1.4 final release. Could anyone give a deadline?
Seeing how things are progressing, we are probably about two weeks from final release. There will be a 1.4.1 release a couple of months afterwards where we can add the translations that didn't make it into 1.4, so your efforts won't be wasted even if you can't make the deadline.
Hello,
If a group of people translated Wine on a web base platform such as [1], is it allowed to send a single large patch with a commit log which mentions all authors, but without details about which part exactly translated by which people?
Thanks.
[1] http://tryneeds.westart.tw/tryneeds/project/show/project_id/8/project_tree_i... ,
I would go for the more popular options such as Transifex, TranslateWiki, or Pootle.
Is this even an option?
Kind regards, Yaron Shahrabani
<Hebrew translator>
On Fri, Feb 17, 2012 at 12:59 PM, Qian Hong fracting@gmail.com wrote:
Hello,
If a group of people translated Wine on a web base platform such as [1], is it allowed to send a single large patch with a commit log which mentions all authors, but without details about which part exactly translated by which people?
Thanks.
[1] http://tryneeds.westart.tw/tryneeds/project/show/project_id/8/project_tree_i... ,
On 17 February 2012 11:12, Yaron Shahrabani sh.yaron@gmail.com wrote:
I would go for the more popular options such as Transifex, TranslateWiki, or Pootle.
Is this even an option?
See http://wiki.winehq.org/Translating#head-e1a500fef50a1801ecea706ebd9b51457943... "3. Web-based translations systems"
Quoting below for convenience:
--- The Wine project would be very interested in making its PO files available on web-based community translations systems such as Pootle or Launchpad. Our hope is that this would make translating Wine even easier and engage new translators. The reason why it has not happened yet is that all Wine contributions, including for translations, must be attributable to a specific author and that these tools don't make that possible yet. For more details see the wine-devel discussion here and here. Any contributions that would solve this issue would be very welcome. ---
Transifex allows that although Pootle has a much more sophisticated permissions mechanism allowing people to only suggest while other can actually edit the translation.
Transifex has a binary permissions mechanism, a person can either edit or not edit but he cannot suggest.
So yes, that's possible, what else do we need?
Kind regards, Yaron Shahrabani
<Hebrew translator>
On Fri, Feb 17, 2012 at 1:27 PM, Alex Bradbury asb@asbradbury.org wrote:
On 17 February 2012 11:12, Yaron Shahrabani sh.yaron@gmail.com wrote:
I would go for the more popular options such as Transifex,
TranslateWiki, or
Pootle.
Is this even an option?
See http://wiki.winehq.org/Translating#head-e1a500fef50a1801ecea706ebd9b51457943... "3. Web-based translations systems"
Quoting below for convenience:
The Wine project would be very interested in making its PO files available on web-based community translations systems such as Pootle or Launchpad. Our hope is that this would make translating Wine even easier and engage new translators. The reason why it has not happened yet is that all Wine contributions, including for translations, must be attributable to a specific author and that these tools don't make that possible yet. For more details see the wine-devel discussion here and here. Any contributions that would solve this issue would be very welcome.
Can we please discuss about moving the translation to another platform?
Pootle seems the most appropriate so far, do you guys need more details?
Kind regards, Yaron Shahrabani
<Hebrew translator>
On Fri, Feb 17, 2012 at 11:35 PM, Yaron Shahrabani sh.yaron@gmail.comwrote:
Transifex allows that although Pootle has a much more sophisticated permissions mechanism allowing people to only suggest while other can actually edit the translation.
Transifex has a binary permissions mechanism, a person can either edit or not edit but he cannot suggest.
So yes, that's possible, what else do we need?
Kind regards, Yaron Shahrabani
<Hebrew translator>
On Fri, Feb 17, 2012 at 1:27 PM, Alex Bradbury asb@asbradbury.org wrote:
On 17 February 2012 11:12, Yaron Shahrabani sh.yaron@gmail.com wrote:
I would go for the more popular options such as Transifex,
TranslateWiki, or
Pootle.
Is this even an option?
See http://wiki.winehq.org/Translating#head-e1a500fef50a1801ecea706ebd9b51457943... "3. Web-based translations systems"
Quoting below for convenience:
The Wine project would be very interested in making its PO files available on web-based community translations systems such as Pootle or Launchpad. Our hope is that this would make translating Wine even easier and engage new translators. The reason why it has not happened yet is that all Wine contributions, including for translations, must be attributable to a specific author and that these tools don't make that possible yet. For more details see the wine-devel discussion here and here. Any contributions that would solve this issue would be very welcome.
We would love to do this and it is being explored.
The core issue is the ability to directly connect each translation to the translator. None of the platforms we have looked at have this functionality.
If i have more time I can try to explore the pootle code as I have at least passing familiarity with it... But out of the box it does not do what we need.
-aric
On 2/22/12 6:10 AM, Yaron Shahrabani wrote:
Can we please discuss about moving the translation to another platform?
Pootle seems the most appropriate so far, do you guys need more details?
Kind regards, YaronShahrabani
<Hebrew translator>On Fri, Feb 17, 2012 at 11:35 PM, Yaron Shahrabani <sh.yaron@gmail.com mailto:sh.yaron@gmail.com> wrote:
Transifex allows that although Pootle has a much more sophisticated permissions mechanism allowing people to only suggest while other can actually edit the translation. Transifex has a binary permissions mechanism, a person can either edit or not edit but he cannot suggest. So yes, that's possible, what else do we need? Kind regards, YaronShahrabani <Hebrew translator> On Fri, Feb 17, 2012 <tel:2012> at 1:27 PM, Alex Bradbury <asb@asbradbury.org <mailto:asb@asbradbury.org>> wrote: On 17 February 2012 <tel:2012> 11:12, Yaron Shahrabani <sh.yaron@gmail.com <mailto:sh.yaron@gmail.com>> wrote: > I would go for the more popular options such as Transifex, TranslateWiki, or > Pootle. > > Is this even an option? See http://wiki.winehq.org/Translating#head-e1a500fef50a1801ecea706ebd9b51457943f102 "3. Web-based translations systems" Quoting below for convenience: --- The Wine project would be very interested in making its PO files available on web-based community translations systems such as Pootle or Launchpad. Our hope is that this would make translating Wine even easier and engage new translators. The reason why it has not happened yet is that all Wine contributions, including for translations, must be attributable to a specific author and that these tools don't make that possible yet. For more details see the wine-devel discussion here and here. Any contributions that would solve this issue would be very welcome. ---
Hey Aric, can you please explain? In both Pootle and Transifex you can have a language maintainer.
In Pootle you can set permissions for each and every user as the maintainer while in Transifex you can only allow or disallow people who want to assist (And they have full permissions, they can affect the translation without the intervention of the maintainer).
Or am I getting it all wrong?
Kind regards, Yaron Shahrabani
<Hebrew translator>
On Wed, Feb 22, 2012 at 3:45 PM, Aric Stewart aric@codeweavers.com wrote:
We would love to do this and it is being explored.
The core issue is the ability to directly connect each translation to the translator. None of the platforms we have looked at have this functionality.
If i have more time I can try to explore the pootle code as I have at least passing familiarity with it... But out of the box it does not do what we need.
-aric
On 2/22/12 6:10 AM, Yaron Shahrabani wrote:
Can we please discuss about moving the translation to another platform?
Pootle seems the most appropriate so far, do you guys need more details?
Kind regards, YaronShahrabani
<Hebrew translator>
On Fri, Feb 17, 2012 at 11:35 PM, Yaron Shahrabani <sh.yaron@gmail.com mailto:sh.yaron@gmail.com> wrote:
Transifex allows that although Pootle has a much more sophisticated permissions mechanism allowing people to only suggest while other can actually edit the translation.
Transifex has a binary permissions mechanism, a person can either edit or not edit but he cannot suggest.
So yes, that's possible, what else do we need?
Kind regards, YaronShahrabani
<Hebrew translator>On Fri, Feb 17, 2012 tel:2012 at 1:27 PM, Alex Bradbury <asb@asbradbury.org mailto:asb@asbradbury.org> wrote:
On 17 February 2012 <tel:2012> 11:12, Yaron Shahrabani <sh.yaron@gmail.com <mailto:sh.yaron@gmail.com>> wrote: > I would go for the more popular options such as Transifex, TranslateWiki, or > Pootle. > > Is this even an option? See http://wiki.winehq.org/**Translating#head-**e1a500fef50a1801ecea706ebd9b51**457943f102http://wiki.winehq.org/Translating#head-e1a500fef50a1801ecea706ebd9b51457943f102 "3. Web-based translations systems"
Quoting below for convenience: --- The Wine project would be very interested in making its PO files available on web-based community translations systems such asPootle or Launchpad. Our hope is that this would make translating Wine even easier and engage new translators. The reason why it has not happened yet is that all Wine contributions, including for translations, must be attributable to a specific author and that these tools don't make that possible yet. For more details see the wine-devel discussion here and here. Any contributions that would solve this issue would be very welcome. ---
On 2/22/12 8:08 AM, Yaron Shahrabani wrote:
Hey Aric, can you please explain? In both Pootle and Transifex you can have a language maintainer.
In Pootle you can set permissions for each and every user as the maintainer while in Transifex you can only allow or disallow people who want to assist (And they have full permissions, they can affect the translation without the intervention of the maintainer).
Or am I getting it all wrong?
Kind regards, YaronShahrabani
<Hebrew translator>
I admit I have mostly experience with pootle 2.1.6 and not the tip, but I have subscribe to the pootle-dev mailing list to see if i can get some more insight.
The problem comes with if you have 2+ translators for a language.
Translator 'A' is the admin, 'B' and 'C' can just suggest.
if 'B' suggests some translations and 'C' suggests some others. 'A' does have to approve them all however we have no way to go back and generate a report after the fact as to which translations came from 'B' or 'C' or even which 'A' submitted directly.
I am not familiar with Transifex. I will have to look at that.
-aric
Hi,
I just had a very good conversation with the mediawiki people about TranslateWiki. (http://translatewiki.net/wiki/Main_Page)
There are some snags right now but they are really interested in doing work to accommodate us. We will see where that goes but so far it is looking like the most promising path.
-aric
On 02/22/2012 09:09 AM, Aric Stewart wrote:
Hi,
I just had a very good conversation with the mediawiki people about TranslateWiki. (http://translatewiki.net/wiki/Main_Page)
There are some snags right now but they are really interested in doing work to accommodate us. We will see where that goes but so far it is looking like the most promising path.
Maybe the whole problem is that we doing it wrong? Why do we need to track contribution? One of the main reasons I can thing of is LGPL constrains. What if we change license on .po files to something that is less stricter and allows easier integration with translation sites?
Just my 2c.
Vitaliy.
Vitaliy Margolen wine-devel@kievinfo.com writes:
On 02/22/2012 09:09 AM, Aric Stewart wrote:
Hi,
I just had a very good conversation with the mediawiki people about TranslateWiki. (http://translatewiki.net/wiki/Main_Page)
There are some snags right now but they are really interested in doing work to accommodate us. We will see where that goes but so far it is looking like the most promising path.
Maybe the whole problem is that we doing it wrong? Why do we need to track contribution? One of the main reasons I can thing of is LGPL constrains. What if we change license on .po files to something that is less stricter and allows easier integration with translation sites?
It's not so much about license enforcement. It's about trust and accountability. We need to know whom we are working with, whom to contact if there are questions, who should receive credit for the work, who is sending consistently good (or maybe bad) contributions, who is violating the rules should that happen, etc. All these things matter for translations just like they do for the rest of the code.
2012/2/17 Qian Hong fracting@gmail.com:
Hello,
On Fri, Feb 17, 2012 at 2:13 AM, Francois Gouget fgouget@free.fr wrote:
I feel that we should put out a call for translators to the wider community. In preparation for that I updated the Wiki's Translating page and added a winepo script to help translators who don't want to check out the whole Wine source:
I would like to help to update the Simplified Chinese translation, but most likely I have no enouth time to complete it before wine-1.4 final release. Could anyone give a deadline?
If anyone would like to translate Simplified Chinese please post a reply here to prevent duplication work.
I had maintained zh_CN translation for quite some time, but haven't touched it for about a year (since Wine switched to po files).
I might get down to cleaning up zh_CN.po in the near future, but I'll contact you before that.
Also I'll forward this mail to Traditional Chinese community, since as a native Simplified Chinese speaker I can't use Traditional Chinese correctly every time.
Thanks Francois and the Wine community :)
Hi Cheer,
On Sun, Feb 26, 2012 at 10:19 PM, Cheer Xiao xiaqqaix@gmail.com wrote:
I had maintained zh_CN translation for quite some time, but haven't touched it for about a year (since Wine switched to po files).
I might get down to cleaning up zh_CN.po in the near future, but I'll contact you before that.
Great. I'll contact to you via gtalk. BTW, we have meet in Ubuntu Release Party in Tsinghua :)
--- On Mon, 27/2/12, Cheer Xiao xiaqqaix@gmail.com wrote:
2012/2/17 Qian Hong fracting@gmail.com:
Hello,
On Fri, Feb 17, 2012 at 2:13 AM, Francois Gouget fgouget@free.fr
wrote:
I feel that we should put out a call for
translators to the wider
community. In preparation for that I updated the
Wiki's Translating page
and added a winepo script to help translators who
don't want to check
out the whole Wine source:
<snipped>
I had maintained zh_CN translation for quite some time, but haven't touched it for about a year (since Wine switched to po files).
I might get down to cleaning up zh_CN.po in the near future, but I'll contact you before that.
In another thread, I wrote that some of the recent patch 'tries to improves on windows'. IMHO, this is really not a "translation" job, but just the rather tedious task of looking at what localized windows does in equivalent situations.
One should *not* be creative and does one's own thing - the localized message files should be (some version of) what localized windows shows. Anything else is wrong.
There are plenty of people running localized windows everywhere these days... shoud not be difficlt to find.
On Mon, 27 Feb 2012, Hin-Tak Leung wrote: [...]
One should *not* be creative and does one's own thing - the localized message files should be (some version of) what localized windows shows. Anything else is wrong.
Do not do that. That would be copyright infrigement. That's not what we want. This would get your contributions removed from Wine.
--- On Mon, 27/2/12, Francois Gouget fgouget@free.fr wrote:
On Mon, 27 Feb 2012, Hin-Tak Leung wrote: [...]
One should *not* be creative and does one's own thing -
the localized
message files should be (some version of) what
localized windows
shows. Anything else is wrong.
Do not do that. That would be copyright infrigement. That's not what we want. This would get your contributions removed from Wine.
claiming copyright on short phrases like 'loading dlls failed' (in whatever language) seems very far-fetched.
On Mon, 27 Feb 2012, Hin-Tak Leung wrote: [...]
Do not do that. That would be copyright infrigement. That's not what we want. This would get your contributions removed from Wine.
claiming copyright on short phrases like 'loading dlls failed' (in whatever language) seems very far-fetched.
Claiming copyright on a set of such sentences isn't. Not all books are exclusively composed of paragraph long sentences...
On Thu, Feb 16, 2012 at 7:13 PM, Francois Gouget fgouget@free.fr wrote:
Wine 1.4 is making good progress. Unfortunately we still have a lot of translations that are quite incomplete and have no active translators, thus making Wine unusable in many countries. You track progress on this page:
Hi Francois,
I checked the dutch translation, and your site gives 95% for nl. I have a few questions 1) It says there are 39 todo, is it possible to show which ones still need to be done? 2) Most of the consistency errors are false positives (whe use quite a lot english words), is it possible to mark them as false positive or something? 3) There's an consistency ignore list, does that mean that the original english translation is used there? 4) Same for spell list, there are also quite a few false positives there.
I'd like to help get the dutch translation to 100%, but I would need to filter out the false positives first.
Thanks,
Matijn
On Thu, 16 Feb 2012, Matijn Woudt wrote: [...]
- It says there are 39 todo, is it possible to show which ones still
need to be done?
Look for 'fuzzy' in the PO file.
- Most of the consistency errors are false positives (whe use quite a
lot english words), is it possible to mark them as false positive or something?
Sure. Send me an email with the msgids of the false positives and I'll update the Wine PO site so they are ignored.
Note that I've already done an update for the ones I could identify and I've sent a couple of patches with the issues I've identified (and I've CC-ed you).
- There's an consistency ignore list, does that mean that the
original english translation is used there?
The ignore list corresponds to the false positives I could identify. Indeed it only had strings where the translation is identical to the English string. That's what 'potool-flags=translated' says.
- Same for spell list, there are also quite a few false positives there.
Send me a list of the words to add to aspell's dictionary.
On 16-02-2012 at 7:55 PM, Matijn Woudt tijnema@gmail.com wrote:
I'd like to help get the dutch translation to 100%, but I would need to filter out the false positives first.
I started with this a while ago, but every time I was nearly done, more translations were marked as fuzzy, more strings were introduced, and usually Francois changed some strings, which meant that I had to manually apply the patch I was working on (with some conflicts). After a while I just gave up on this (I don't have the time to fix it all in one day), so for me the po system actually works counterproductive...
What I want to say here is that if that if you want to get some small fixes in without actually knowing the language you're working on (like Francois), please don't send separate patches every few days, because that's really annoying. Just send them all at once, or just let translators fix it. Or at least set a string freeze, after which people who are actual translators can translate strings.
@Matijn, please go ahead and update the Dutch translation.
Sven
On Fri, Feb 17, 2012 at 12:40 AM, Sven Baars sven.wine@gmail.com wrote:
On 16-02-2012 at 7:55 PM, Matijn Woudt tijnema@gmail.com wrote:
I'd like to help get the dutch translation to 100%, but I would need to filter out the false positives first.
I started with this a while ago, but every time I was nearly done, more translations were marked as fuzzy, more strings were introduced, and usually Francois changed some strings, which meant that I had to manually apply the patch I was working on (with some conflicts). After a while I just gave up on this (I don't have the time to fix it all in one day), so for me the po system actually works counterproductive...
What I want to say here is that if that if you want to get some small fixes in without actually knowing the language you're working on (like Francois), please don't send separate patches every few days, because that's really annoying. Just send them all at once, or just let translators fix it. Or at least set a string freeze, after which people who are actual translators can translate strings.
@Matijn, please go ahead and update the Dutch translation.
Sven
You may be right on that, especially because there are translators that don't know how to fix things after their patch --merge fails. I didn't start too because I thought that it might conflict with Francois patches too.
Francois: The untranslated errors at the consistency are almost all because of the use of english words in dutch. Would it be OK if I send you the L numbers that can have # potool-flags=translated so you can send a patch?
- Matijn
On Fri, 17 Feb 2012, Matijn Woudt wrote: [...]
Francois: The untranslated errors at the consistency are almost all because of the use of english words in dutch. Would it be OK if I send you the L numbers that can have # potool-flags=translated so you can send a patch?
Line numbers are unreliable. Send me the msgids instead. So for instance if the following in the report is a false positive:
L339:[translated]: not translated: '&Help' msgid "&Help" msgstr "&Help"
Then tell me:
msgid "&Help" is a false positive
On Fri, Feb 17, 2012 at 8:02 AM, Francois Gouget fgouget@free.fr wrote:
On Fri, 17 Feb 2012, Matijn Woudt wrote: [...]
Francois: The untranslated errors at the consistency are almost all because of the use of english words in dutch. Would it be OK if I send you the L numbers that can have # potool-flags=translated so you can send a patch?
Line numbers are unreliable. Send me the msgids instead. So for instance if the following in the report is a false positive:
L339:[translated]: not translated: '&Help' msgid "&Help" msgstr "&Help"
Then tell me:
msgid "&Help" is a false positive
Attached is a list that are all false positives, they are all the same in dutch and english.
- Matijn
On Fri, Feb 17, 2012 at 18:37, Matijn Woudt tijnema@gmail.com wrote:
On Fri, Feb 17, 2012 at 8:02 AM, Francois Gouget fgouget@free.fr wrote:
On Fri, 17 Feb 2012, Matijn Woudt wrote: [...]
Francois: The untranslated errors at the consistency are almost all because of the use of english words in dutch. Would it be OK if I send you the L numbers that can have # potool-flags=translated so you can send a patch?
Line numbers are unreliable. Send me the msgids instead. So for instance if the following in the report is a false positive:
L339:[translated]: not translated: '&Help' msgid "&Help" msgstr "&Help"
Then tell me:
msgid "&Help" is a false positive
Attached is a list that are all false positives, they are all the same in dutch and english.
- Matijn
I'm not sure about some of the false positives you mention 'Product' should be 'Produkt' IMHO Waveform doesn't really look like a false positive Certification Practice Statement (and similar like OCSP) should probably be translated, maybe suffixed with (CPS)... at least in French it is IIRC; not sure about Dutch windows
Maybe I'm wrong, since Dutch is not my first language.
Frédéric
I'm not sure about some of the false positives you mention 'Product' should be 'Produkt' IMHO
Produkt is old spelling, Product is correct now (see for example wikipedia).
Waveform doesn't really look like a false positive
Waveform could be translated as Golfvorm, though in context of the WAV file format (which I suppose it is used), Waveform makes more sense IMO.
Certification Practice Statement (and similar like OCSP) should probably be translated, maybe suffixed with (CPS)... at least in French it is IIRC; not sure about Dutch windows
Maybe I'm wrong, since Dutch is not my first language.
Frédéric
Certification Practice Statement (and those other similar ones), don't have any correct translation. They could be translated word by word, but it is common practice to use the English words in those cases. Couldn't find where it is used on dutch windows, but atleast on Microsoft technet they're talking about Certification Practice Statement and On-line Certificate Status Protocol, so it's probably in windows too.
- Matijn
On Fri, 17 Feb 2012, Sven Baars wrote:
On 16-02-2012 at 7:55 PM, Matijn Woudt tijnema@gmail.com wrote:
I'd like to help get the dutch translation to 100%, but I would need to filter out the false positives first.
I started with this a while ago, but every time I was nearly done, more translations were marked as fuzzy, more strings were introduced, and usually Francois changed some strings, which meant that I had to manually apply the patch I was working on (with some conflicts). After a while I just gave up on this (I don't have the time to fix it all in one day), so for me the po system actually works counterproductive...
What I want to say here is that if that if you want to get some small fixes in without actually knowing the language you're working on (like Francois), please don't send separate patches every few days, because that's really annoying.
That's what I've been trying to do. For the Dutch translation I only sent one round of patches in September (before the conversion of the dialogs to PO files), one after all the dialogs where converted on the 19th of January, two single translation ones on the 23rd and 24th that were unlikely to cause any conflicts, and this round.
Now I did fix English strings as I found issues with them more often. But those impact all translators so no matter when I send them in they will cause conflicts for one translator. So there's no point in delaying those.
That said I'm willing to help translators that have trouble resolving conflicts with their translations.
Just send them all at once, or just let translators fix it. Or at least set a string freeze, after which people who are actual translators can translate strings.
You're in luck, we are in string freeze since the beginning of the week.
On Fri, Feb 17, 2012 at 00:40, Sven Baars sven.wine@gmail.com wrote:
On 16-02-2012 at 7:55 PM, Matijn Woudt tijnema@gmail.com wrote:
I'd like to help get the dutch translation to 100%, but I would need to filter out the false positives first.
I started with this a while ago, but every time I was nearly done, more translations were marked as fuzzy, more strings were introduced, and usually Francois changed some strings, which meant that I had to manually apply the patch I was working on (with some conflicts). After a while I just gave up on this (I don't have the time to fix it all in one day), so for me the po system actually works counterproductive...
To be fair, François' patches aren't occurring that often, just small bursts every couple of months, mostly when "trivial" typographic errors are caught, generally due to changes in the original English versions (mgsids), which implies changes to all translations anyway.
If you want to avoid/limit conflicts, you might want to send smaller patches instead of a big one. This has the advantage of making the progress made visible to other (potential) translators, limiting the risk of edition conflict/duplicate work
Frédéric
-
Alex Bradbury -
Alexandre Julliard -
Aric Stewart -
Cheer Xiao -
Francois Gouget -
Frédéric Delanoy -
Hin-Tak Leung -
Matijn Woudt -
Qian Hong -
Sven Baars -
Vitaliy Margolen -
Yaron Shahrabani