Closed Bug 350462 (fx20-ZA) Opened 18 years ago Closed 17 years ago

[ZA][af,en-ZA,nr,nso,ss,st,ts,tn,ve,xh,zu] Ship Firefox 2

Categories

(Mozilla Localizations :: Other, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Pike, Assigned: dwayne)

Details

(Keywords: fixed1.8.1.1, Whiteboard: [Fx 2.0.0.1])

Attachments

(2 files, 1 obsolete file)

I guess we'll have just one bug for the South African locales, at least for starters.

Dwayne, could you file a bug to get a component for your locale/locales?
Alias: fx20-ZA
Requested component in bug 350551

Yes please only one bug for now it will save lots of noise.
Summary: [ZA][af] Ship Firefox 2 → [ZA][af,en-ZA,nr,nso,ss,st,ts,tn,ve,xh,zu] Ship Firefox 2
We need to setup the CNAMES for the south african locales, still.
Version: unspecified → en-ZA / English (South African)
Assignee: nobody → dwayne
Component: Other → za / South Africa
QA Contact: dwayne
Version: en-ZA / English (South African) → unspecified
Dwayne, to get the SA released, we should good in terms of search for now, but I'd like the bookmarks.html files to follow the scheme to have all links replace en-US with the locale name. Even if we don't use, it can't hurt to add that now.
Axel, all bookmark files updated to replace en-US with correct locale information.  I am not sure what needs to be changed in the search.  I'd like to do that but am unsure and couldn't find docs on what can be changed.
Re bookmarks, can you change both 'en-US'?

http://tn.add-ons.mozilla.com/en-US/firefox/bookmarks/
                              ^^^^^
and friends for all your locales. Yeah, tedious, sorry.

Re search, you wouldn't have to do anything actually. If you're using the en-US list.txt, you're fine from a product/BD point of view. It'd be too late to get some south african engines in, really.
As the build process picks up search engine files of the right name from en-US, you can cvs remove all your copies of the en-US search engine xml files, and just keep a copy of list.txt in each of your locales.

HTH
Whiteboard: bookmarks still partly en-US
(In reply to comment #5)
> Re bookmarks, can you change both 'en-US'?
> 
> http://tn.add-ons.mozilla.com/en-US/firefox/bookmarks/
>                               ^^^^^
> and friends for all your locales. Yeah, tedious, sorry.

Fixed my scripts to do s/en-US/$locale/g - so now changes everything.  These changes have been committed to CVS.

Is it safe to change these?

HREF="http://ve.fxfeeds.mozilla.com/ve/firefox/livebookmarks/"
FEEDURL="http://ve.fxfeeds.mozilla.com/ve/firefox/headlines.xml"
Whiteboard: bookmarks still partly en-US
Dwayne, the tree is closed. Any change that you want to land needs a bug, request blocking-firefox2, and a patch for which to request approval1.8.1.
(In reply to comment #5)
> Re search, you wouldn't have to do anything actually. If you're using the en-US
> list.txt, you're fine from a product/BD point of view. It'd be too late to get
> some south african engines in, really.

This is not an issue for this release.  We will address that in a future release.

> As the build process picks up search engine files of the right name from en-US,
> you can cvs remove all your copies of the en-US search engine xml files, and
> just keep a copy of list.txt in each of your locales.

Removed all *.xml from ZA locales.
Axel, sorry didn't check the tree status before those commits.  I can revert and go the approval route if needed.  Do we have any concept of string freeze in Mozilla? As I've been watching quite a few string addtions and changes.
Please don't revert, that's just another check-in.

In terms of string freeze, we're frozen, but help is 'insert colorful non-public language'.

File bugs, request blocking, that's the only way I have for you.
Moving over to 2.0.0.1.
Blocks: fx2001
No longer blocks: fx20l10n
Whiteboard: [Fx 2.0.0.1]
Any news on the ZA locales for release on 2.0.0.x?
We ahve translations in for Afrikaans which we're busy creating a diff for against current Afrikaans in CVS.  Will complete that review tomorrow and be able to submit a patch.
Updates to 2.0.0.1 for Afrikaans
Attachment #246280 - Flags: approval1.8.1.1?
Comment on attachment 246280 [details] [diff] [review]
Updates to 2.0.0.1 for Afrikaans

[af] translation update for the 1.8 branch approved.

This patch is pretty huge, and deals with a whole bunch of untranslated strings. I guess we should make an assessment of the build after this patch landed and the resulting builds got some QA.
Attachment #246280 - Flags: approval1.8.1.1? → approval1.8.1.1+
Attachment #246306 - Flags: approval1.8.1.1?
This includes changes to help and RDF files that where missing from the last patch
Attachment #246306 - Attachment is obsolete: true
Attachment #246308 - Flags: approval1.8.1.1?
Attachment #246306 - Flags: approval1.8.1.1?
Comment on attachment 246308 [details] [diff] [review]
Updates to 2.0.0.1 for South African English (en-ZA)

[en-ZA] catch-up patch approved for 1.8 branch. Looking at my diff against en-GB, there seem to be US-isms left, I found at least manBookmarksCmd.label in browser.dtd. One has to ignore the casing of the accesskeys when looking at the diff, sadly, as well as some formatting diffs. I need to file a bug on en-GB about summaries vs. live titles, though.
Attachment #246308 - Flags: approval1.8.1.1? → approval1.8.1.1+
Blocks: fx2002
No longer blocks: fx2001
Keywords: fixed1.8.1.1
Let's move this meta bug off the shipping list, Friedel, Dwayne, please file individual bugs for locales as appropriate.
No longer blocks: fx2002
Marking FIXED.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Component: za / South Africa → Other
QA Contact: dwayne
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: