FYI: Help TOC will be fixed a little
dynamis
During our QA, we found problem not only in our locale (ja/ja-JP-mac)
but also in en-US. I filed a bug about it:
https://bugzilla.mozilla.org/show_bug.cgi?id=353332
Ahhh, and this was marked as dupulicate of bug 352968 just now.
https://bugzilla.mozilla.org/show_bug.cgi?id=352968
I believe this fix will be included in firefox2.
You can include this fix for all locales to avoid l10n impact but this
indicates that QA time for english help was unhapply not enough. Of
cource not enough for l10n help.
# As you see not us but some locales have not catched up with en-US's
# update yet.
So IMHO we should have some more time to fix/improvement help contents
without approval isn't it?
# not required, just suggestion to rethink about close of the branch
And one question:
When will be the deadline to fix our locale files and request approval1.8.1?
We continue QA and some problem (only on help at this time) was found
unhappily but I don't want to file a bug every time we found new tiny
problems. I want to file a bug only few times to improve our l10n.
# for example: one time for each release of RC2, RC3 and Final
To do so I will wait more and gather more feedbacks and then file a bug
about l10n inprovement. Deadline time information for l10n fix will help
us to make QA plan.
Thanks.
- dynamis (Manager, L10N Center)
Mozilla Japan : http://www.mozilla-japan.org/
L10N Center : http://www.mozilla-japan.org/jp/l10n/
Translation Div : http://www.mozilla-japan.org/jp/td/
Michele Dal Corso
> So IMHO we should have some more time to fix/improvement help contents
> without approval isn't it?
I agree, also us (Italian team) we have a pending bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=353204
related to an issue found on help yesterday...
Michele
Axel Hecht
See my other post, 5pm PDT today is landing deadline for RC1, and there
may not be any RC2.
Axel
Ricardo Palomares Martinez
> dynamis wrote:
>> Ahhh, and this was marked as dupulicate of bug 352968 just now.
>> https://bugzilla.mozilla.org/show_bug.cgi?id=352968
>>
>> I believe this fix will be included in firefox2.
Funny, the bug was filed regarding version 2.0, but it has been marked
as RESOLVED / FIXED after commiting the patch just in TRUNK. :-?
>> And one question:
>> When will be the deadline to fix our locale files and request
>> approval1.8.1?
>> (...)
>> Deadline time information for l10n fix will help
>> us to make QA plan.
>>
>
> See my other post, 5pm PDT today is landing deadline for RC1, and there
> may not be any RC2.
Let me get this straight, filing a bug to catch up with en-US help
changes done after L10N lockdown is not possible anymore?
Ricardo.
--
If it's true that we are here to help others,
then what exactly are the OTHERS here for?
Axel Hecht
> Axel Hecht escribió:
>> dynamis wrote:
>>> Ahhh, and this was marked as dupulicate of bug 352968 just now.
>>> https://bugzilla.mozilla.org/show_bug.cgi?id=352968
>>>
>>> I believe this fix will be included in firefox2.
>
>
> Funny, the bug was filed regarding version 2.0, but it has been marked
> as RESOLVED / FIXED after commiting the patch just in TRUNK. :-?
There is the fixed1.8.1 keyword indicating that bugs are fixed on the
branch, too.
>>> And one question:
>>> When will be the deadline to fix our locale files and request
>>> approval1.8.1?
>>> (...)
>>> Deadline time information for l10n fix will help
>>> us to make QA plan.
>>>
>> See my other post, 5pm PDT today is landing deadline for RC1, and there
>> may not be any RC2.
>
>
> Let me get this straight, filing a bug to catch up with en-US help
> changes done after L10N lockdown is not possible anymore?
>
You can file a bug and attach a patch, but we will not respin for that.
If we respin for other reasons, we may want to take it.
Axel
Ricardo Palomares Martinez
> Ricardo Palomares Martinez wrote:
>> Axel Hecht escribió:
>>> dynamis wrote:
>>>> Ahhh, and this was marked as dupulicate of bug 352968 just now.
>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=352968
>>>>
>>>> I believe this fix will be included in firefox2.
>>
>>
>> Funny, the bug was filed regarding version 2.0, but it has been marked
>> as RESOLVED / FIXED after commiting the patch just in TRUNK. :-?
>
> There is the fixed1.8.1 keyword indicating that bugs are fixed on the
> branch, too.
I didn't notice about the keyword, but I'm sure that the patch hadn't
been landed on branch when I wrote my previous message.
>
>>>> And one question:
>>>> When will be the deadline to fix our locale files and request
>>>> approval1.8.1?
>>>> (...)
>>>> Deadline time information for l10n fix will help
>>>> us to make QA plan.
>>>>
>>> See my other post, 5pm PDT today is landing deadline for RC1, and there
>>> may not be any RC2.
>>
>>
>> Let me get this straight, filing a bug to catch up with en-US help
>> changes done after L10N lockdown is not possible anymore?
>>
>
> You can file a bug and attach a patch, but we will not respin for that.
> If we respin for other reasons, we may want to take it.
After seeing the above statment, I haven't bothered to update latest
en-US help changes not ported to es-ES (actually, no big deal, since
just one change had relevance for users), much less to file a bug
about it, but as Marek Stepień writes in "Localization process" thread:
http://groups.google.es/group/mozilla.dev.l10n/msg/f1b34f3ee812f2f6?hl=es
I would also willing to have the feeling of having es-ES fully in sync
with en-US if there is a real chance.
Axel Hecht
> Axel Hecht escribió:
>> Ricardo Palomares Martinez wrote:
>>> Axel Hecht escribió:
>>>> dynamis wrote:
>>>>> Ahhh, and this was marked as dupulicate of bug 352968 just now.
>>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=352968
>>>>>
>>>>> I believe this fix will be included in firefox2.
>>>
>>> Funny, the bug was filed regarding version 2.0, but it has been marked
>>> as RESOLVED / FIXED after commiting the patch just in TRUNK. :-?
>> There is the fixed1.8.1 keyword indicating that bugs are fixed on the
>> branch, too.
>
>
> I didn't notice about the keyword, but I'm sure that the patch hadn't
> been landed on branch when I wrote my previous message.
>
And that bug didn't have that keyword set, thus, it wasn't fixed on the
branch.
Axel