Localizing new bugzilla product and component names

classic Classic list List threaded Threaded
21 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Localizing new bugzilla product and component names

Axel Hecht
Hi,

we've set up a project on localize.m.o,
http://localize.mozilla.org/verbatim/projects/bugzilla_components/, to
gather the translated bugzilla component names.

You won't need all strings if you're just doing Firefox, or just two of
the projects. If you're interested in localizing weave sync, start
filling that out already.

If you're localizing more than one of Firefox, Thunderbird, SeaMonkey,
please translate the toolkit component, too.

The translation don't need to be verbatim (lol), use something that
helps users to file new bugs right. The first string (product context)
will be used on a page similar to
https://bugzilla.mozilla.org/enter_bug.cgi?classification=Client%20Software,
and the other are then on a page like
https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&component=Infrastructure,
the green text in the "Component Description" groupbox.

Not all locales are set up yet, I'm going through that now. If you need
permissions, poke us on #l10n.

Axel
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: Localizing new bugzilla product and component names

Gion-Andri Cantieni
Hi,
could you add Romansh language to Verbatim? And give me (username:
[hidden email]) the rights to do the translation?

Thank you,
chars salids
Gion-Andri

Am 31.03.10 15:27, schrieb Axel Hecht:

> Hi,
>
> we've set up a project on localize.m.o,
> http://localize.mozilla.org/verbatim/projects/bugzilla_components/, to
> gather the translated bugzilla component names.
>
> You won't need all strings if you're just doing Firefox, or just two of
> the projects. If you're interested in localizing weave sync, start
> filling that out already.
>
> If you're localizing more than one of Firefox, Thunderbird, SeaMonkey,
> please translate the toolkit component, too.
>
> The translation don't need to be verbatim (lol), use something that
> helps users to file new bugs right. The first string (product context)
> will be used on a page similar to
> https://bugzilla.mozilla.org/enter_bug.cgi?classification=Client%20Software,
> and the other are then on a page like
> https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&component=Infrastructure,
> the green text in the "Component Description" groupbox.
>
> Not all locales are set up yet, I'm going through that now. If you need
> permissions, poke us on #l10n.
>
> Axel
> _______________________________________________
> dev-l10n mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-l10n
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: Localizing new bugzilla product and component names

Ehsan Akhgari
In reply to this post by Axel Hecht
On Wed, Mar 31, 2010 at 9:27 AM, Axel Hecht <[hidden email]> wrote:
> You won't need all strings if you're just doing Firefox, or just two of the
> projects. If you're interested in localizing weave sync, start filling that
> out already.

I localized all the strings.  Is that a problem?  Should I go back and
remove the extra ones?

--
Ehsan
<http://ehsanakhgari.org/>
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: Localizing new bugzilla product and component names

Axel Hecht
In reply to this post by Axel Hecht
On 31.03.10 22:08, Gion-Andri Cantieni wrote:
> Hi,
> could you add Romansh language to Verbatim? And give me (username:
> [hidden email]) the rights to do the translation?
>

Done, thanks for poking, that slipped through the cracks.

Axel

>
> Am 31.03.10 15:27, schrieb Axel Hecht:
>> Hi,
>>
>> we've set up a project on localize.m.o,
>> http://localize.mozilla.org/verbatim/projects/bugzilla_components/, to
>> gather the translated bugzilla component names.
>>
>> You won't need all strings if you're just doing Firefox, or just two of
>> the projects. If you're interested in localizing weave sync, start
>> filling that out already.
>>
>> If you're localizing more than one of Firefox, Thunderbird, SeaMonkey,
>> please translate the toolkit component, too.
>>
>> The translation don't need to be verbatim (lol), use something that
>> helps users to file new bugs right. The first string (product context)
>> will be used on a page similar to
>> https://bugzilla.mozilla.org/enter_bug.cgi?classification=Client%20Software,
>>
>> and the other are then on a page like
>> https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&component=Infrastructure,
>>
>> the green text in the "Component Description" groupbox.
>>
>> Not all locales are set up yet, I'm going through that now. If you need
>> permissions, poke us on #l10n.
>>
>> Axel
>> _______________________________________________
>> dev-l10n mailing list
>> [hidden email]
>> https://lists.mozilla.org/listinfo/dev-l10n

_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: Localizing new bugzilla product and component names

Axel Hecht
In reply to this post by Axel Hecht
On 31.03.10 22:40, Ehsan Akhgari wrote:
> On Wed, Mar 31, 2010 at 9:27 AM, Axel Hecht<[hidden email]>  wrote:
>> You won't need all strings if you're just doing Firefox, or just two of the
>> projects. If you're interested in localizing weave sync, start filling that
>> out already.
>
> I localized all the strings.  Is that a problem?  Should I go back and
> remove the extra ones?

That's not a problem. As long as the string for toolkit is actually
mentioning the products you're working on, that's fine.

We'll control the generation of the components by using the all-locales
files of the different products.

Axel
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: Localizing new bugzilla product and component names

Ehsan Akhgari
On Wed, Mar 31, 2010 at 4:52 PM, Axel Hecht <[hidden email]> wrote:

> On 31.03.10 22:40, Ehsan Akhgari wrote:
>>
>> On Wed, Mar 31, 2010 at 9:27 AM, Axel Hecht<[hidden email]>  wrote:
>>>
>>> You won't need all strings if you're just doing Firefox, or just two of
>>> the
>>> projects. If you're interested in localizing weave sync, start filling
>>> that
>>> out already.
>>
>> I localized all the strings.  Is that a problem?  Should I go back and
>> remove the extra ones?
>
> That's not a problem. As long as the string for toolkit is actually
> mentioning the products you're working on, that's fine.
>
> We'll control the generation of the components by using the all-locales
> files of the different products.

I'm not sure what that string should be then, since we're not working
on Persian Thunderbird yet, and the toolkit translations are
practically used by Firefox and Fennec for now.

--
Ehsan
<http://ehsanakhgari.org/>
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: Localizing new bugzilla product and component names

Axel Hecht
In reply to this post by Axel Hecht
On 31.03.10 23:00, Ehsan Akhgari wrote:

> On Wed, Mar 31, 2010 at 4:52 PM, Axel Hecht<[hidden email]>  wrote:
>> On 31.03.10 22:40, Ehsan Akhgari wrote:
>>>
>>> On Wed, Mar 31, 2010 at 9:27 AM, Axel Hecht<[hidden email]>    wrote:
>>>>
>>>> You won't need all strings if you're just doing Firefox, or just two of
>>>> the
>>>> projects. If you're interested in localizing weave sync, start filling
>>>> that
>>>> out already.
>>>
>>> I localized all the strings.  Is that a problem?  Should I go back and
>>> remove the extra ones?
>>
>> That's not a problem. As long as the string for toolkit is actually
>> mentioning the products you're working on, that's fine.
>>
>> We'll control the generation of the components by using the all-locales
>> files of the different products.
>
> I'm not sure what that string should be then, since we're not working
> on Persian Thunderbird yet, and the toolkit translations are
> practically used by Firefox and Fennec for now.
>

That'd be

Shared translation tasks, mistakes and regional customizations of
Firefox and Fennec.

then.

Axel
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: Localizing new bugzilla product and component names

Seth Bindernagel
In reply to this post by Axel Hecht


Axel Hecht wrote:
> On 31.03.10 22:08, Gion-Andri Cantieni wrote:
>> Hi,
>> could you add Romansh language to Verbatim? And give me (username:
>> [hidden email]) the rights to do the translation?
>
> Done, thanks for poking, that slipped through the cracks.

Hi Gion-Andri,

We'll need to enter a plural rule for Romansh.  Do you know this?  Here
is some more information about plural rules in general:

http://translate.sourceforge.net/wiki/l10n/pluralforms

As you can see here, there is nothing for Romansh, so we might need your
help defining that.

-Seth

_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: Localizing new bugzilla product and component names

Cédric Corazza
In reply to this post by Axel Hecht
French localization is completed.
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: Localizing new bugzilla product and component names

Axel Hecht
In reply to this post by Axel Hecht
I've probably should've opened this up in .web as well, catching up on
that oversight.

For those in .web that don't follow .l10n or .governance, this is about
restructuring the bugzilla components for l10n, discussed in
http://groups.google.com/group/mozilla.governance/browse_frm/thread/5983760ed8357cfc#.
The beef is wrapped up in
http://groups.google.com/group/mozilla.governance/msg/011a024c7fb39360.

For the folks here, top level summary, there will be a bugzilla
component and a mail alias to watch for just web-facing l10n for each
localization.

Axel

On 31.03.10 15:27, Axel Hecht wrote:

> Hi,
>
> we've set up a project on localize.m.o,
> http://localize.mozilla.org/verbatim/projects/bugzilla_components/, to
> gather the translated bugzilla component names.
>
> You won't need all strings if you're just doing Firefox, or just two of
> the projects. If you're interested in localizing weave sync, start
> filling that out already.
>
> If you're localizing more than one of Firefox, Thunderbird, SeaMonkey,
> please translate the toolkit component, too.
>
> The translation don't need to be verbatim (lol), use something that
> helps users to file new bugs right. The first string (product context)
> will be used on a page similar to
> https://bugzilla.mozilla.org/enter_bug.cgi?classification=Client%20Software,
> and the other are then on a page like
> https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&component=Infrastructure,
> the green text in the "Component Description" groupbox.
>
> Not all locales are set up yet, I'm going through that now. If you need
> permissions, poke us on #l10n.
>
> Axel

_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: Localizing new bugzilla product and component names

Axel Hecht
Just seeing this in at least one example:

The string LANGUAGE is intended to be replaced by your actual language,
it's not some variable that we'd replace with software.

Thanks

Axel

On 01.04.10 00:40, Axel Hecht wrote:

> I've probably should've opened this up in .web as well, catching up on
> that oversight.
>
> For those in .web that don't follow .l10n or .governance, this is about
> restructuring the bugzilla components for l10n, discussed in
> http://groups.google.com/group/mozilla.governance/browse_frm/thread/5983760ed8357cfc#.
> The beef is wrapped up in
> http://groups.google.com/group/mozilla.governance/msg/011a024c7fb39360.
>
> For the folks here, top level summary, there will be a bugzilla
> component and a mail alias to watch for just web-facing l10n for each
> localization.
>
> Axel
>
> On 31.03.10 15:27, Axel Hecht wrote:
>> Hi,
>>
>> we've set up a project on localize.m.o,
>> http://localize.mozilla.org/verbatim/projects/bugzilla_components/, to
>> gather the translated bugzilla component names.
>>
>> You won't need all strings if you're just doing Firefox, or just two of
>> the projects. If you're interested in localizing weave sync, start
>> filling that out already.
>>
>> If you're localizing more than one of Firefox, Thunderbird, SeaMonkey,
>> please translate the toolkit component, too.
>>
>> The translation don't need to be verbatim (lol), use something that
>> helps users to file new bugs right. The first string (product context)
>> will be used on a page similar to
>> https://bugzilla.mozilla.org/enter_bug.cgi?classification=Client%20Software,
>>
>> and the other are then on a page like
>> https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&component=Infrastructure,
>>
>> the green text in the "Component Description" groupbox.
>>
>> Not all locales are set up yet, I'm going through that now. If you need
>> permissions, poke us on #l10n.
>>
>> Axel
>

_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: Localizing new bugzilla product and component names

Danishka Navin
On Thu, Apr 1, 2010 at 4:30 AM, Axel Hecht <[hidden email]> wrote:

> Just seeing this in at least one example:
>
> The string LANGUAGE is intended to be replaced by your actual language,
> it's not some variable that we'd replace with software.
>
> Thanks
>
> Axel
>
>
> On 01.04.10 00:40, Axel Hecht wrote:
>
>> I've probably should've opened this up in .web as well, catching up on
>> that oversight.
>>
>> For those in .web that don't follow .l10n or .governance, this is about
>> restructuring the bugzilla components for l10n, discussed in
>>
>> http://groups.google.com/group/mozilla.governance/browse_frm/thread/5983760ed8357cfc#
>> .
>> The beef is wrapped up in
>> http://groups.google.com/group/mozilla.governance/msg/011a024c7fb39360.
>>
>> For the folks here, top level summary, there will be a bugzilla
>> component and a mail alias to watch for just web-facing l10n for each
>> localization.
>>
>> Axel
>>
>> On 31.03.10 15:27, Axel Hecht wrote:
>>
>>> Hi,
>>>
>>> we've set up a project on localize.m.o,
>>> http://localize.mozilla.org/verbatim/projects/bugzilla_components/, to
>>> gather the translated bugzilla component names.
>>>
>>> You won't need all strings if you're just doing Firefox, or just two of
>>> the projects. If you're interested in localizing weave sync, start
>>> filling that out already.
>>>
>>> If you're localizing more than one of Firefox, Thunderbird, SeaMonkey,
>>> please translate the toolkit component, too.
>>>
>>> The translation don't need to be verbatim (lol), use something that
>>> helps users to file new bugs right. The first string (product context)
>>> will be used on a page similar to
>>>
>>> https://bugzilla.mozilla.org/enter_bug.cgi?classification=Client%20Software
>>> ,
>>>
>>> and the other are then on a page like
>>>
>>> https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&component=Infrastructure
>>> ,
>>>
>>> the green text in the "Component Description" groupbox.
>>>
>>> Not all locales are set up yet, I'm going through that now. If you need
>>> permissions, poke us on #l10n.
>>>
>>> Axel
>>>
>>
>>
> i do not have privileges to submit, but i suggest,
acc_name danishka


>  _______________________________________________
> dev-l10n mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-l10n
>



--
Danishka Navin
http://danishkanavin.blogspot.com
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: Localizing new bugzilla product and component names

flod
In reply to this post by Axel Hecht
  Il 31/03/10 15.27, Axel Hecht ha scritto:
> If you're localizing more than one of Firefox, Thunderbird, SeaMonkey,
> please translate the toolkit component, too.
Just to be sure: if we're translating all projects except for Weave,
this string should be " Shared translation tasks, mistakes and regional
customizations of Firefox, Thunderbird, Fennec, SeaMonkey and
Calendar.". Is it right? I checked a couple of languages and they refer
only to Firefox and Thunderbird.

Francesco
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: Localizing new bugzilla product and component names

Axel Hecht
In reply to this post by Axel Hecht
On 01.04.10 07:40, flod wrote:
> Il 31/03/10 15.27, Axel Hecht ha scritto:
>> If you're localizing more than one of Firefox, Thunderbird, SeaMonkey,
>> please translate the toolkit component, too.
> Just to be sure: if we're translating all projects except for Weave,
> this string should be " Shared translation tasks, mistakes and regional
> customizations of Firefox, Thunderbird, Fennec, SeaMonkey and
> Calendar.". Is it right? I checked a couple of languages and they refer
> only to Firefox and Thunderbird.
>

I'd actually exclude Calendar in the list, it's a tad unclear but I
guess that will be at least extensions-only focused, i.e., lightning
instead of sunbird.

But yes, it should include the toolkit-based apps that you're working on.

Axel
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: Localizing new bugzilla product and component names

Siarhei-2
In reply to this post by Axel Hecht
Hi,

Could you add Belarusian to the list?


With best regards,

Siarhei

_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: Localizing new bugzilla product and component names

Axel Hecht
On 04.04.10 19:23, Siarhei wrote:
> Hi,
>
> Could you add Belarusian to the list?
>
>
> With best regards,
>
> Siarhei
>


Done

Axel
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: Localizing new bugzilla product and component names

Vito Smolej-3
In reply to this post by Axel Hecht
On 31 mar., 15:27, Axel Hecht <[hidden email]> wrote:

> Hi,
>
> we've set up a project on localize.m.o,http://localize.mozilla.org/verbatim/projects/bugzilla_components/, to
> gather the translated bugzilla component names.
>
> You won't need all strings if you're just doing Firefox, or just two of
> the projects. If you're interested in localizing weave sync, start
> filling that out already.
>
> If you're localizing more than one of Firefox, Thunderbird, SeaMonkey,
> please translate the toolkit component, too.
>
> The translation don't need to be verbatim (lol), use something that
> helps users to file new bugs right. The first string (product context)
> will be used on a page similar tohttps://bugzilla.mozilla.org/enter_bug.cgi?classification=Client%20So...,
> and the other are then on a page likehttps://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localiza...,
> the green text in the "Component Description" groupbox.
>
> Not all locales are set up yet, I'm going through that now. If you need
> permissions, poke us on #l10n.
>
> Axel

Cant log on verbatim. I cant even create a new account.

regards

smo
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: Localizing new bugzilla product and component names

Axel Hecht
In reply to this post by Axel Hecht
Gandalf changed that URL to
https://localize.mozilla.org/projects/bugzilla_components/.

Axel

On 31.03.10 15:27, Axel Hecht wrote:

> Hi,
>
> we've set up a project on localize.m.o,
> http://localize.mozilla.org/verbatim/projects/bugzilla_components/, to
> gather the translated bugzilla component names.
>
> You won't need all strings if you're just doing Firefox, or just two of
> the projects. If you're interested in localizing weave sync, start
> filling that out already.
>
> If you're localizing more than one of Firefox, Thunderbird, SeaMonkey,
> please translate the toolkit component, too.
>
> The translation don't need to be verbatim (lol), use something that
> helps users to file new bugs right. The first string (product context)
> will be used on a page similar to
> https://bugzilla.mozilla.org/enter_bug.cgi?classification=Client%20Software,
> and the other are then on a page like
> https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&component=Infrastructure,
> the green text in the "Component Description" groupbox.
>
> Not all locales are set up yet, I'm going through that now. If you need
> permissions, poke us on #l10n.
>
> Axel

_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: Localizing new bugzilla product and component names

Gion-Andri Cantieni
In reply to this post by Seth Bindernagel
Hi,
I think we need plural-rule #1 from this list:
https://developer.mozilla.org/en/Localization_and_Plurals

I think it's the same as here:
http://unicode.org/repos/cldr-tmp/trunk/diff/supplemental/language_plural_rules.html
or here
https://translations.launchpad.net/+languages/rm

Could you add this to Verbatim?

Thank you
Gion-Andri

Am 31.03.10 23:15, schrieb Seth Bindernagel:

>
>
> Axel Hecht wrote:
>> On 31.03.10 22:08, Gion-Andri Cantieni wrote:
>>> Hi,
>>> could you add Romansh language to Verbatim? And give me (username:
>>> [hidden email]) the rights to do the translation?
>>
>> Done, thanks for poking, that slipped through the cracks.
>
> Hi Gion-Andri,
>
> We'll need to enter a plural rule for Romansh. Do you know this? Here is
> some more information about plural rules in general:
>
> http://translate.sourceforge.net/wiki/l10n/pluralforms
>
> As you can see here, there is nothing for Romansh, so we might need your
> help defining that.
>
> -Seth
>
> _______________________________________________
> dev-l10n mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-l10n
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|

Re: Localizing new bugzilla product and component names

Axel Hecht
In reply to this post by Seth Bindernagel
Should be fixed.

Axel

On 28.04.10 11:59, Gion-Andri Cantieni wrote:

> Hi,
> I think we need plural-rule #1 from this list:
> https://developer.mozilla.org/en/Localization_and_Plurals
>
> I think it's the same as here:
> http://unicode.org/repos/cldr-tmp/trunk/diff/supplemental/language_plural_rules.html
>
> or here
> https://translations.launchpad.net/+languages/rm
>
> Could you add this to Verbatim?
>
> Thank you
> Gion-Andri
>
> Am 31.03.10 23:15, schrieb Seth Bindernagel:
>>
>>
>> Axel Hecht wrote:
>>> On 31.03.10 22:08, Gion-Andri Cantieni wrote:
>>>> Hi,
>>>> could you add Romansh language to Verbatim? And give me (username:
>>>> [hidden email]) the rights to do the translation?
>>>
>>> Done, thanks for poking, that slipped through the cracks.
>>
>> Hi Gion-Andri,
>>
>> We'll need to enter a plural rule for Romansh. Do you know this? Here is
>> some more information about plural rules in general:
>>
>> http://translate.sourceforge.net/wiki/l10n/pluralforms
>>
>> As you can see here, there is nothing for Romansh, so we might need your
>> help defining that.
>>
>> -Seth
>>
>> _______________________________________________
>> dev-l10n mailing list
>> [hidden email]
>> https://lists.mozilla.org/listinfo/dev-l10n

_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
12