Closed Bug 350551 Opened 18 years ago Closed 17 years ago

Bugzilla component for South African locales

Categories

(Mozilla Localizations :: Registration & Management, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dwayne, Assigned: timeless)

Details

bug 350462 refers

I'd like to request a component for the South African locale/locales.  A global locale is very useful as we work on 11 languages simultationsly.  So in instances where we are releaseing all it makes sense to have only one not 11 bug reports.  I suggest:

ZA / South Africa

But in instances where the bug relates to only one language or to adding a component to only one language I would suggest that we also add for the languages:

af / Afrikaans
en-ZA / English (South African)
nr / Ndebele
nso / Northern Sotho/Pedi
ss / Swazi
st / Southern Sotho
tn / Tswana
ts / Tsonga
ve /Venda
xh / Xhosa
zu / Zulu
OS: Linux → All
Hardware: PC → All
I have created the component, and created the other languages as versions that can be selected.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Marcia, can we change za to capital ZA.  In iso639 the language Zhuang has the code 'za'.  I think using capitals will make it clear that this is a region and not a language as most people are used to en-US, en-GB, etc where the region is in capitals.
This is confusing in oh-so-many ways...

These "versions" show up for all components of Mozilla Localization. So we're seeing Dutch or Turkish bugs with "versions" set to "Northern Soto" or "Zulu" (I changed it to "undefined" for the ones I found).

Similarly confusing is the fact that when filing a bug report the user actually sees language names in both fields. 

It is a bit of a mess now and it will only grow, unless stopped.

My proposition:
1) Make ZA languages components of the Mozilla Localization product, just like any other language
2) For bugs common to all these languages, create a "ZA general" (or sth) component of Mozilla Localizations




this corrupted the end user database. we're *NOT* going to do this.

i don't care who you are or how special you think you are. we've had a process in place for a long time, and it worked.

I'm very sorry that people did as you requested, it was a mistake, and everyone regrets it.

if you want keywords, you can have them, as many as you like.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee: registration → timeless
Status: REOPENED → NEW
My mom told me never to be rude to people no matter who they think they are or how special they think they are.

A simple request to help everyone from getting bogged down with N*11 problems as we report issues across 11 languages.  I'm sorry if our organisation doesn't fall into your 1 language 1 team world. ANd I'm sorry for even trying to anticipate a problem.  ANd I'm sorry that anyone tried to even help.

You suggest using keywords but it might be helpful if you suggested exactly how you would sue them.  Since I'm not the Bugzilla guru you seem to be.  Throwing your pants out without telling everyone how you might do it is just silly and has created this note because you didn't create any new or useful info.  Just a rant that solved noone's problem except maybe your own.  I'd put this down to the a general Mozilla'ness but I know other people who'se decision I respect.

So how would you use keywords?  I'm clueless.
Dwayne: it seems that Bugzilla is limited in this sense. (Versions are not the right way to get sub-sub-components.)

Could you explain again why we can't just have eleven components? What sort of bugs do you come across that occur both in the Tswana and the Xhosa language pack?

Gerv
Gerv: we could have 11 components.  But we often find that a bug in one is a bug in all.  If something is wrong with a dialogue size it most likely affects all of our translations.  Terminology also affects others as we will then relook at the terminology across all translations.  But we will of course get the one or two better translation bugs, spelling error bugs, etc
Dwayne: one option is just not to worry which component generic bugs end up in; they have to be fixed just the same, after all.

Alternatively, would you be happy with one generic component and 11 specific ones? It seems to be either that or one component and Status Whiteboard tags or keywords to distinguish the languages, which would be a nasty hack.

Gerv
Gerv:  1 genric and 11 specific.  Yes I'm happy with that.  Isn't that what I proposed in the beginning?
Sure - I wanted to check it was still OK. I'll get to this in the next couple of days.

Gerv
All components created. Let me know if there's any problems.

Gerv
Status: NEW → RESOLVED
Closed: 18 years ago17 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.