Pidgin is string frozen!
|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
 |
Pidgin is string frozen!
by Mark Doliner
::
Rate this Message:
Hi everybody!
Pidgin/Finch/libpurple is now string frozen pending the release of 2.6.2 hopefully next week on Thursday, September 3rd. There are a few new strings and a few fuzzies. We're pushing this release out so soon after the previous one because it includes fixes for bugs that affect large swaths of people. -Mark _______________________________________________ Translators mailing list Translators@... http://pidgin.im/cgi-bin/mailman/listinfo/translators |
|
|
Re: Pidgin is string frozen!
by F Wolff-2
::
Rate this Message:
Op Vr, 2009-08-28 om 00:50 -0700 skryf Mark Doliner:
> Hi everybody! > > Pidgin/Finch/libpurple is now string frozen pending the release of > 2.6.2 hopefully next week on Thursday, September 3rd. There are a few > new strings and a few fuzzies. We're pushing this release out so soon > after the previous one because it includes fixes for bugs that affect > large swaths of people. Is there any news an all the issues with the English that was reported with the translation round for 2.6.0? Are those the fuzzies that have to get attention? Thanks Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/support-afrikaans-google-translate _______________________________________________ Translators mailing list Translators@... http://pidgin.im/cgi-bin/mailman/listinfo/translators |
|
|
Re: Pidgin is string frozen!
by Mark Doliner
::
Rate this Message:
On Fri, Aug 28, 2009 at 1:13 AM, F Wolff<friedel@...> wrote:
> Op Vr, 2009-08-28 om 00:50 -0700 skryf Mark Doliner: >> Hi everybody! >> >> Pidgin/Finch/libpurple is now string frozen pending the release of >> 2.6.2 hopefully next week on Thursday, September 3rd. There are a few >> new strings and a few fuzzies. We're pushing this release out so soon >> after the previous one because it includes fixes for bugs that affect >> large swaths of people. > > Is there any news an all the issues with the English that was reported > with the translation round for 2.6.0? Are those the fuzzies that have to > get attention? I think we "dealt with" everything that was mentioned. We fixed things that were clearly errors, maybe improved a few that were unclear, and added comments for others. If you see any problems please let us know. Also, I think http://developer.pidgin.im/l10n/pidgin.pot and http://developer.pidgin.im/l10n/ are up to date now (they were a day behind when I sent my first email). -Mark _______________________________________________ Translators mailing list Translators@... http://pidgin.im/cgi-bin/mailman/listinfo/translators |
|
|
Re: Pidgin is string frozen!
by F Wolff-2
::
Rate this Message:
Op Vr, 2009-08-28 om 00:50 -0700 skryf Mark Doliner:
> Hi everybody! > > Pidgin/Finch/libpurple is now string frozen pending the release of > 2.6.2 hopefully next week on Thursday, September 3rd. There are a few > new strings and a few fuzzies. We're pushing this release out so soon > after the previous one because it includes fixes for bugs that affect > large swaths of people. > > -Mark It seems that the --help text of Pidgin was entirely rewritten. Why is does this have two trailing newlines? Usage: %s [OPTION]...\n \n The arguments to long options like --config=DIR and --login=[NAME] is now not translatable any more. DIR and NAME should be translatable. The wrapping with the new --help text is really not very nice, and it seems there are parentheses that span translation units: "enable specified account(s) (optional argument NAME specifies account(s) to use, separated by commas." and "Without this only the first account will be enabled)." Any reason why this can't be part of one translation message (since it is one message anyway). Is there a way we can avoid having to do the wrapping as translators? I attached my updated Afrikaans translation here: http://developer.pidgin.im/ticket/10189 Is it still in time for the release? Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/support-afrikaans-google-translate _______________________________________________ Translators mailing list Translators@... http://pidgin.im/cgi-bin/mailman/listinfo/translators |
|
|
Re: Pidgin is string frozen!
by Mark Doliner
::
Rate this Message:
On Thu, Sep 3, 2009 at 2:55 AM, F Wolff<friedel@...> wrote:
> Op Vr, 2009-08-28 om 00:50 -0700 skryf Mark Doliner: >> Hi everybody! >> >> Pidgin/Finch/libpurple is now string frozen pending the release of >> 2.6.2 hopefully next week on Thursday, September 3rd. There are a few >> new strings and a few fuzzies. We're pushing this release out so soon >> after the previous one because it includes fixes for bugs that affect >> large swaths of people. >> >> -Mark > > > It seems that the --help text of Pidgin was entirely rewritten. The text should be the same, but it was suggested on this list that we divide the string into many smaller strings so there is less work for translators when it changes (and so we don't have two nearly-identical versions--one for Unix and one for Windows). > Why is does this have two trailing newlines? > Usage: %s [OPTION]...\n > \n That's just how it's formatted on the console. I suppose we can separate the newlines from the localizable string. > The arguments to long options like --config=DIR and --login=[NAME] is > now not translatable any more. DIR and NAME should be translatable. Ah, good point. We'll fix that (but not for this release, of course). > The wrapping with the new --help text is really not very nice, and it > seems there are parentheses that span translation units: > > "enable specified account(s) (optional argument NAME > specifies account(s) to use, separated by commas." > > and > > "Without this only the first account will be enabled)." > > Any reason why this can't be part of one translation message (since it > is one message anyway). Is there a way we can avoid having to do the > wrapping as translators? Ah, yes, that is indeed a problem. This is perhaps why the string was previously one big chunk. I'll definitely combine the two separate strings (but not for this release, of course). And I'll try to find a way to avoid doing the wrapping as translators (but I suspect this might be difficult). > I attached my updated Afrikaans translation here: > http://developer.pidgin.im/ticket/10189 > Is it still in time for the release? Yes, I'll make sure we check that in before releasing. Thanks, Mark _______________________________________________ Translators mailing list Translators@... http://pidgin.im/cgi-bin/mailman/listinfo/translators |
|
|
Re: Pidgin is string frozen!
by Ambrose Li-3
::
Rate this Message:
Hi,
2009/9/3 Mark Doliner <mark@...>: > > The text should be the same, but it was suggested on this list that we > divide the string into many smaller strings so there is less work for > translators when it changes (and so we don't have two nearly-identical > versions--one for Unix and one for Windows). The text for one option has been rewritten (I think the one about multiple instances); otherwise they are all the same. I believe the main point was to reduce error, since it is hard to find out what has changed when the string becomes fuzzy. But the other long message has not yet been rewritten, and I think the other point was to reduce inconsistency between the two long strings. -- cheers, -ambrose _______________________________________________ Translators mailing list Translators@... http://pidgin.im/cgi-bin/mailman/listinfo/translators |
|
|
Re: Pidgin is string frozen!
by Sean Burke
::
Rate this Message:
Scríobh Mark Doliner:
>> The arguments to long options like --config=DIR and --login=[NAME] is >> now not translatable any more. DIR and NAME should be translatable. >> > > Ah, good point. We'll fix that (but not for this release, of course). > The policy for GNOME is that marking existing untranslatable strings for translation isn't a violation of string freeze. This seems like solid reasoning to me. If someone doesn't get to the string in time, nothing changes. However, it gives some people the chance to translate a string which would otherwise show up in English, period. Why not adopt a similar policy? Seán de Búrca _______________________________________________ Translators mailing list Translators@... http://pidgin.im/cgi-bin/mailman/listinfo/translators |
|
|
Re: Pidgin is string frozen!
by Mark Doliner
::
Rate this Message:
On Thu, Sep 3, 2009 at 1:32 PM, Sean Burke<leftmostcat@...> wrote:
> Scríobh Mark Doliner: >>> The arguments to long options like --config=DIR and --login=[NAME] is >>> now not translatable any more. DIR and NAME should be translatable. >>> >> >> Ah, good point. We'll fix that (but not for this release, of course). >> > The policy for GNOME is that marking existing untranslatable strings for > translation isn't a violation of string freeze. This seems like solid > reasoning to me. If someone doesn't get to the string in time, nothing > changes. However, it gives some people the chance to translate a string > which would otherwise show up in English, period. Why not adopt a > similar policy? Oh yeah. We've actually been doing that recently. It just didn't occur to me in this instance, maybe because the strings in question are a part of another (non-localizable) string. I guess I'll make that change now. -Mark _______________________________________________ Translators mailing list Translators@... http://pidgin.im/cgi-bin/mailman/listinfo/translators |
| Free embeddable forum powered by Nabble | Forum Help |
