l10n status questionaire for Firefox 2 B2
Axel Hecht
we would like to get some feedback from all teams, to understand where
each of several areas are in terms of completion. We will be able to use
this information to help direct beta2 testing resources to the areas
that are finished, and keep them away for areas where work is still in
progress.
Please provide status for the following areas and let us know if any
parts of these are incomplete for Beta 2:
1. Verify version string and build ID in "About Firefox..."
2. Status of menu items and context menus, do they appear and are
translated properly?
3. Key URLs are properly localized
1. Default home page properly localized
2. First run page
3. Other new product pages. See:
http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
Are the URLs in the right format, do they resolve, are the redirects set
up right?
4. Search engines
1. Verify the right ones are listed, logos are in good shape, try a
search in each one.
2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
3. For others Google is first, Yahoo! is second (make sure that you
have bugs filed on exceptions for Yahoo!)
5. Verify Help appears and is properly localized
6. Ensure that dialogs for Extensions and Themes appear properly
7. Verify that bookmarks display properly
8. Layouts for complex dialogs are correct. Try the
Preferences/Options tool and check the various tabs.
It is important for you to let us know what areas are completed and
which ones are still in progress.
Thanks
Axel
Toni Hermoso Pulido
Hash: SHA1
En/na Axel Hecht ha escrit:
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> Are the URLs in the right format, do they resolve, are the redirects set
> up right?
Well, it's not described in the wiki page but, just for reference:
http://{{locale}}.fxfeeds.mozilla.com/{{locale}}/firefox/headlines.xml
http://{{locale}}.fxfeeds.mozilla.com/{{locale}}/firefox/livebookmarks/
are not currently redirecting properly.
- --
* Toni Hermoso Pulido
- ------------------------------------------------------
web: http://www.cau.cat
email: ton...@softcatala.org
gpg: B67B43DC
planet: http://planeta.softcatala.org
- ------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFE8tP63O471rZ7Q9wRAg0JAJ4mAYcygNoV1gMSF+h89Z3W86m9HQCggqOs
dPFJmU8QJD65/ACyRytnZXA=
=qsqp
-----END PGP SIGNATURE-----
Cédric Corazza
> Please provide status for the following areas and let us know if any
> parts of these are incomplete for Beta 2:
> 1. Verify version string and build ID in "About Firefox..."
Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.8.1b2) Gecko/20060821
Firefox/2.0b2
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
This is OK
> 3. Key URLs are properly localized
There are OK, you actually changed them for our locale : bug 348165,
http://bonsai-l10n.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&subdir=l10n/fr/browser/profile&command=DIFF_FRAMESET&file=bookmarks.html&rev1=1.3.2.4&rev2=1.3.2.5&root=/l10n
> 1. Default home page properly localized
KEY is OK, redirection is OK
http://www.google.fr/firefox?client=firefox-a&rls=org.mozilla:fr:official
> 2. First run page
KEY is OK, Redirection not OK
(http://www.mozilla.org/projects/firefox/2.0b2/firstrun/)
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> Are the URLs in the right format, do they resolve, are the redirects set
> up right?
*What's new* : KEY is OK, redirection not OK
(http://www.mozilla.com/firefox/2.0/whatsnew) 404
*Help and tutorials* : KEY is OK, Redirection not OK
(http://www.mozilla.com/firefox/help/) 404
*Customize* : KEY is OK, Redirection not OK
(http://www.mozilla.com/firefox/customize/) 404
*Get involved* : KEY is OK, redirection not OK
(http://www.mozilla.com/firefox/community/) 404
*About us* : KEY is OK, Redirection not OK
(http://www.mozilla.com/firefox/about/) 404
> 4. Search engines
> 1. Verify the right ones are listed, logos are in good shape, try a
> search in each one.
This is OK . Bug 347931
> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
Not applicable
> 3. For others Google is first, Yahoo! is second (make sure that you
> have bugs filed on exceptions for Yahoo!)
OK
> 5. Verify Help appears and is properly localized
This was not the case on 2.0b2. This is now fixed on nightlies. All the
links from the TOC and pages correctly displayed.
But:
*** We are very concerned about the plan to put the help on the
Internet. Will that happen? As you might know, we used entities from DTD
in the help files to stay synced with the interface (bug 247595). If
help will go on Internet for FF 2.0 : we need to test that as soon as
possible.
*** Also, help is not finished yet (in en-US) and we'd like to have soon
the new screenshots images for help because of the new theme and because
we need to localize them too for part of them.
> 6. Ensure that dialogs for Extensions and Themes appear properly
This is OK
> 7. Verify that bookmarks display properly
This is OK
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
We began to do this on Linux only for the moment but we need to do that
for all platforms and also between KDE and Gnome which seem to behave
differently
Last : we need to make a last review for the help files, maybe some
rewording for the new terms or concepts that appeared in this version
and looking for some possible remaining accesskeys conflicts.
Regards
Hasse
> 1. Verify version string and build ID in "About Firefox..."
Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.8.1b2) Gecko/20060821 Firefox/2.0b2
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
Yes
> 3. Key URLs are properly localized
> 1. Default home page properly localized
Yes
> 2. First run page
http://www.mozilla.org/projects/firefox/2.0b2/firstrun/ is a 404
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> Are the URLs in the right format, do they resolve, are the redirects set
> up right?
Updated page
http://www.mozilla.org/projects/firefox/2.0b2/whatsnew/ is a 404
Help -> Release Notes
http://www.mozilla.org/projects/bonecho/releases/2.0b2.html is a 404
Help -> Report Web Forgery
http://sv-se.phish-report.mozilla.com/?hl=sv-SE&url=http%3A%2F%2Fwww.mozilla.org%2F
redirects to
http://www.mozilla.com/?hl=sv-SE&url=http%253A%252F%252Fwww.mozilla.org%252F
which doesn't seem right.
> 4. Search engines
We use the same plugins as en-US.
> 5. Verify Help appears and is properly localized
Yes.
> 6. Ensure that dialogs for Extensions and Themes appear properly
Yes.
> 7. Verify that bookmarks display properly
Get Bookmark Add-ons
http://sv-SE.add-ons.mozilla.com/sv-SE/firefox/bookmarks/
redirects to
https://addons.mozilla.org/
Getting Started
http://sv-SE.www.mozilla.com/sv-SE/firefox/central/
redirects to
http://www.mozilla.com/firefox/central/
Latest Headlines
http://sv-SE.fxfeeds.mozilla.com/sv-SE/firefox/headlines.xml
fails to update live bookmark
Help and Tutorials
http://sv-SE.www.mozilla.com/sv-SE/firefox/help/
redirects to
http://www.mozilla.com/firefox/help/
which is a 404
Customize Firefox
http://sv-SE.www.mozilla.com/sv-SE/firefox/customize/
redirects to
http://www.mozilla.com/firefox/customize/
which is a 404
Get Involved
http://sv-SE.www.mozilla.com/sv-SE/firefox/community/
redirects to
http://www.mozilla.com/firefox/community/
which is a 404
About Us
http://sv-SE.www.mozilla.com/sv-SE/firefox/about/
redirects to
http://www.mozilla.com/firefox/about/
which is a 404
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
Looks OK on Windows.
--
Hasse
sv-SE l10n team
pi
Axel Hecht wrote:
> Hi,
>
> we would like to get some feedback from all teams, to understand where
> each of several areas are in terms of completion. We will be able to use
> this information to help direct beta2 testing resources to the areas
> that are finished, and keep them away for areas where work is still in
> progress.
>
> Please provide status for the following areas and let us know if any
> parts of these are incomplete for Beta 2:
>
> 1. Verify version string and build ID in "About Firefox..."
Mozilla/5.0 (X11; U; Linux i686; eu; rv:1.8.1b2) Gecko/20060826
BonEcho/2.0b2
>
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
Yes
>
> 3. Key URLs are properly localized
> 1. Default home page properly localized
OK
> 2. First run page
http://www.mozilla.org/projects/firefox/2.0b2/firstrun/
404
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> Are the URLs in the right format, do they resolve, are the redirects set
> up right?
We need to make changes in bookmarks.html (is erroneus)
>
> 4. Search engines
> 1. Verify the right ones are listed, logos are in good shape, try a
> search in each one.
> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
not case
> 3. For others Google is first, Yahoo! is second (make sure that you
> have bugs filed on exceptions for Yahoo!)
OK
>
> 5. Verify Help appears and is properly localized
Help appears ok but we dont finish the translation yet
> 6. Ensure that dialogs for Extensions and Themes appear properly
OK
> 7. Verify that bookmarks display properly
OK
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
OK
Marcelo Poli
> 1. Verify version string and build ID in "About Firefox..."
Mozilla/5.0 (Windows; U; Windows NT 5.1; es-AR; rv:1.8.1b2)
Gecko/20060821 Firefox/2.0b2
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
Everything is OK
> 3. Key URLs are properly localized
> 1. Default home page properly localized
OK
> 2. First run page
404
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> Are the URLs in the right format, do they resolve, are the redirects set
> up right?
http://www.mozilla.com/firefox/2.0/whatsnew 404
http://www.mozilla.com/firefox/help/ 404
http://www.mozilla.com/firefox/customize/ 404
http://www.mozilla.com/firefox/community/ 404
http://www.mozilla.com/firefox/about/ 404
> 4. Search engines
> 1. Verify the right ones are listed, logos are in good shape, try a
> search in each one.
Everything OK
> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
N/A
> 3. For others Google is first, Yahoo! is second (make sure that you
> have bugs filed on exceptions for Yahoo!)
Both OK
> 5. Verify Help appears and is properly localized
Help is working, some pages need update for final release. Working on it.
> 6. Ensure that dialogs for Extensions and Themes appear properly
Both OK.
> 7. Verify that bookmarks display properly
Almost every redirection fails.
http://www.mozilla.com/firefox/central/ OK
http://www.mozilla.com/firefox/help/ 404
http://www.mozilla.com/firefox/customize/ 404
http://www.mozilla.com/firefox/community/ 404
http://www.mozilla.com/firefox/about/ 404
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
Everything OK.
Some strings in the Windows Installer are in the wrong encoding.
Giving strings like \000e
Marcelo Poli
Phishing report gives a 403
Axel Hecht
Could you file a bug on that and CC me? A screenshot would help. I
suspect that something in es-AR/browser/installer is not properly utf-8
encoded. Anyway, a bug and screenshot would help, including a comment
what the string should be.
Axel
Axel Hecht
> Hi,
>
> we would like to get some feedback from all teams, to understand where
> each of several areas are in terms of completion. We will be able to use
> this information to help direct beta2 testing resources to the areas
> that are finished, and keep them away for areas where work is still in
> progress.
>
> Please provide status for the following areas and let us know if any
> parts of these are incomplete for Beta 2:
>
> 1. Verify version string and build ID in "About Firefox..."
>
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
>
> 3. Key URLs are properly localized
> 1. Default home page properly localized
> 2. First run page
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> Are the URLs in the right format, do they resolve, are the redirects set
> up right?
Bug 349092 was just resolved, it might be worthwhile to test some of
those redirects again. Sorry for not pressing this earlier.
Axel
A S Alam
> Please provide status for the following areas and let us know if any
> parts of these are incomplete for Beta 2:
>
> 1. Verify version string and build ID in "About Firefox..."
>
Firefox/2.0b2
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
>
> 3. Key URLs are properly localized
> 1. Default home page properly localized
> 2. First run page
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> Are the URLs in the right format, do they resolve, are the redirects set
> up right?
>
> 4. Search engines
> 1. Verify the right ones are listed, logos are in good shape, try a
> search in each one.
> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
> 3. For others Google is first, Yahoo! is second (make sure that you
> have bugs filed on exceptions for Yahoo!)
>
> 5. Verify Help appears and is properly localized
> 6. Ensure that dialogs for Extensions and Themes appear properly
> 7. Verify that bookmarks display properly
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
>
thanks
--
A S Alam
timezone: GMT+5:30
"Either find a way or make one"
Tatjana Jevsikova
here is Lithuanian (lt) Firefox 2 B2 localization status.
> 1. Verify version string and build ID in "About Firefox..."
It is OK:
Mozilla/5.0 (Windows; U; Windows NT 5.1; lt; rv:1.8.1b2) Gecko/20060821
Firefox/2.0b2
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
Yes, they are OK.
> 3. Key URLs are properly localized
> 1. Default home page properly localized
English page is opened (http://www.mozilla.com/firefox/central/),
redirected from http://lt.www.mozilla.com/lt/firefox/central/
> 2. First run page
Two tabs:
Page in English:
http://developer.mozilla.org/devnews/index.php/2006/07/12/firefox-2-beta-1-milestone-released/
and Google Start page (new snippets need to be translated).
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> Are the URLs in the right format, do they resolve, are the redirects set
> up right?
The format of URLs are correct (according to specified Wiki page), but all
they are redirected to pages in English.
> 4. Search engines
> 1. Verify the right ones are listed, logos are in good shape, try a
> search in each one.
They are OK.
> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
> 3. For others Google is first, Yahoo! is second (make sure that you
> have bugs filed on exceptions for Yahoo!)
Google is first, Yahoo is second.
>
> 5. Verify Help appears and is properly localized
It is OK (but need to be updated for Fx 2 features).
> 6. Ensure that dialogs for Extensions and Themes appear properly
They are OK
> 7. Verify that bookmarks display properly
All redirections work, but at the moment all the items are redirected to
pages in English.
News feed http://lt.fxfeeds.mozilla.com/lt/firefox/headlines.xml
is redirected to BBC news in English.
Could we set redirection to news in Lithhuanian, e.g. news feed,
provided by Lithuanian
national radio and television site http://www.lrt.lt/rss/all.php (this
feed was approved and integrated
in Fx 1.5.0.x official versions)? Should I file a bug on this?
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
They are correct.
> It is important for you to let us know what areas are completed and
> which ones are still in progress.
>
Best regards,
Tatjana
Michele Dal Corso
> 1. Verify version string and build ID in "About Firefox..."
BonEcho/2.0b2
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
Ok
> 3. Key URLs are properly localized
> 1. Default home page properly localized
Ok
> 2. First run page
Ok
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> Are the URLs in the right format, do they resolve, are the redirects set
> up right?
Alls are ok, but Italian links produces English pages.
> 4. Search engines
> 1. Verify the right ones are listed, logos are in good shape, try a
> search in each one.
Ok, bug 265209
> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
Not applicable
> 3. For others Google is first, Yahoo! is second (make sure that you
> have bugs filed on exceptions for Yahoo!)
Ok
> 5. Verify Help appears and is properly localized
Ok
> 6. Ensure that dialogs for Extensions and Themes appear properly
Ok
> 7. Verify that bookmarks display properly
Ok
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
Ok
Michele Dal Corso
>> 1. Verify version string and build ID in "About Firefox..."
> Mozilla/5.0 (X11; U; Linux i686; it; rv:1.8.1b2) Gecko/20060821
> BonEcho/2.0b2
Mozilla/5.0 (X11; U; Linux i686; it; rv:1.8.1b2) Gecko/20060821
Mad Maks
Firefox/2.0b2
>
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
Yes
>
> 3. Key URLs are properly localized
> 1. Default home page properly localized
Yes
http://www.google.nl/firefox?client=firefox-a&rls=org.mozilla:nl:official
> 2. First run page
-http://www.mozilla.org/projects/firefox/2.0b2/firstrun/ redirect to
http://developer.mozilla.org/devnews/index.php/2006/07/12/firefox-2-beta-1-milestone-released/
> 3. Other new product pages.
-http://www.mozilla.com/firefox/2.0b2/whatsnew/; 404
bookmarks.html is not updated yet (Bug #350569)
the localized URL are redirect to the en-US version
>
> 4. Search engines
> 1. Verify the right ones are listed, logos are in good shape, try a
> search in each one.
> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
> 3. For others Google is first, Yahoo! is second (make sure that you
> have bugs filed on exceptions for Yahoo!)
OK
>
> 5. Verify Help appears and is properly localized
Help appears, updating in progress [bug 314496]
> 6. Ensure that dialogs for Extensions and Themes appear properly
OK
-http://nl.add-ons.mozilla.com/nl/firefox/2.0b2/extensions/ redirect to
https://addons.mozilla.org/extensions/
-http://nl.add-ons.mozilla.com/nl/firefox/2.0b2/themes/ redirect to
https://addons.mozilla.org/themes/
> 7. Verify that bookmarks display properly
OK
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
OK
>
Marek Stepien
> 1. Verify version string and build ID in "About Firefox..."
Mozilla/5.0 (X11; U; Linux i686; pl; rv:1.8.1b2) Gecko/2006082101
Firefox/2.0b2
This is beta 2 candidate 2, looks OK.
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
They do.
> 3. Key URLs are properly localized
> 1. Default home page properly localized
Redirected Google.pl/firefox, it's OK.
> 2. First run page
Redirected to:
http://developer.mozilla.org/devnews/index.php/2006/07/12/firefox-2-beta-1-milestone-released/
This seems wrong and this is not what
http://pl.www.mozilla.com/pl/firefox/2.0/firstrun redirects to. (?!)
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> Are the URLs in the right format, do they resolve, are the redirects set
> up right?
Set up correctly, but the redirects lead to en-US pages at the moment.
> 4. Search engines
> 1. Verify the right ones are listed, logos are in good shape, try a
> search in each one.
OK.
> 3. For others Google is first, Yahoo! is second (make sure that you
> have bugs filed on exceptions for Yahoo!)
Google is first, the rest are in alphabetical order. There's no Yahoo
for pl, but this is approved.
> 5. Verify Help appears and is properly localized
OK.
Help content is not finalized in en-US, so we'll need to update it,
including screenshots.
The RC 2 candidate build doesn't have the latest 1.8 en-US help
checkins, so does this one. I'll update pl help today.
> 6. Ensure that dialogs for Extensions and Themes appear properly
OK.
> 7. Verify that bookmarks display properly
OK.
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
It looks OK at least on Windows Vista and XP with the default font size
and Novell SLED 10 with the default (10px) and 9px fonts. (It may suck
with lower font sizes as it does in en-US).
I will test Mac later.
> It is important for you to let us know what areas are completed and
> which ones are still in progress.
This week we'll be having some community testing, so some mistakes
in the localization may be found, if there are any, we'll be fixing them
for RC 1.
--
Marek Stępień <mar...@aviary.pl>
AviaryPL - polski zespół lokalizacyjny Mozilli
http://www.firefox.pl/ | http://www.mozilla.org.pl/
Marek Stepien
we need it redirected to http://www.gazeta.pl/pub/rss/wiadomosci.xml
Toni Hermoso Pulido
Hash: SHA1
En/na Axel Hecht ha escrit:
> Hi,
>
> we would like to get some feedback from all teams, to understand where
> each of several areas are in terms of completion. We will be able to use
> this information to help direct beta2 testing resources to the areas
> that are finished, and keep them away for areas where work is still in
> progress.
>
> Please provide status for the following areas and let us know if any
> parts of these are incomplete for Beta 2:
>
> 1. Verify version string and build ID in "About Firefox..."
>
Mozilla/5.0 (X11; U; Linux i686; ca; rv:1.8.1b2) Gecko/20060827
BonEcho/2.0b2
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
>
Ok
> 3. Key URLs are properly localized
> 1. Default home page properly localized
Ok.
http://www.google.es/firefox?client=firefox-a&rls=org.mozilla:ca:official
Note: bug 345479
> 2. First run page
Two tabs:
http://developer.mozilla.org/devnews/index.php/2006/07/12/firefox-2-beta-1-milestone-released/
http://www.google.es/firefox?client=firefox-a&rls=org.mozilla:ca:official
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> Are the URLs in the right format, do they resolve, are the redirects set
> up right?
Getting started -> redirecting fine
Latest News -> redirecting BBC feed
Help and tutorials -> redirecting fine
Customize -> redirecting fine
Get involved -> redirecting fine
About us -> redirecting fine
Pages referred in wiki page as:
First run -> redirect well, but no content:
http://www.mozilla.com/firefox/2.0/firstrun
What's new -> redirect well, but no content:
http://www.mozilla.com/firefox/2.0/whatsnew
>
> 4. Search engines
> 1. Verify the right ones are listed, logos are in good shape, try a
> search in each one.
All they work fine.
> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
> 3. For others Google is first, Yahoo! is second (make sure that you
> have bugs filed on exceptions for Yahoo!)
Google first, Yahoo second. Ok for my locale.
>
> 5. Verify Help appears and is properly localized
Ok. Further help reviews are planned.
> 6. Ensure that dialogs for Extensions and Themes appear properly
Ok
> 7. Verify that bookmarks display properly
Ok
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
>
Ok
I think that's all :)
- --
* Toni Hermoso Pulido
- ------------------------------------------------------
web: http://www.cau.cat
email: ton...@softcatala.org
gpg: B67B43DC
planet: http://planeta.softcatala.org
- ------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFE9CC53O471rZ7Q9wRAiVDAJ9svl9seoroyEVJF+VLGAWU8smhSwCggxvp
JwJhUDmudxLWK6C+cOOiT2w=
=U7GI
-----END PGP SIGNATURE-----
Marcelo Poli
>> Some strings in the Windows Installer are in the wrong encoding.
>> Giving strings like \000e
>
> Could you file a bug on that and CC me? A screenshot would help. I
> suspect that something in es-AR/browser/installer is not properly utf-8
> encoded. Anyway, a bug and screenshot would help, including a comment
> what the string should be.
>
> Axel
didn't go in place at the right time.
Seems that all that I need is to make the installer with the current
files. ¿Do I need to file a bug for someone to do that?
João Miguel Neves
> Hi,
>
> we would like to get some feedback from all teams, to understand where
> each of several areas are in terms of completion. We will be able to use
> this information to help direct beta2 testing resources to the areas
> that are finished, and keep them away for areas where work is still in
> progress.
>
> Please provide status for the following areas and let us know if any
> parts of these are incomplete for Beta 2:
>
> 1. Verify version string and build ID in "About Firefox..."
>
Firefox/2.0b2
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
>
Yes :).
> 3. Key URLs are properly localized
> 1. Default home page properly localized
Yes.
> 2. First run page
Is opening:
http://developer.mozilla.org/devnews/index.php/2006/07/12/firefox-2-beta-1-milestone-released/ (not translated) and the start page.
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> Are the URLs in the right format, do they resolve, are the redirects set
> up right?
>
http://pt-PT.www.mozilla.com/pt-PT/firefox/2.0/firstrun (404)
all the others on that page also give a 404.
> 4. Search engines
> 1. Verify the right ones are listed, logos are in good shape, try a
> search in each one.
pt-PT is using default plugins. Everyone is working (suggestions tested
on google and yahoo).
> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
> 3. For others Google is first, Yahoo! is second (make sure that you
> have bugs filed on exceptions for Yahoo!)
>
> 5. Verify Help appears and is properly localized
Checked.
> 6. Ensure that dialogs for Extensions and Themes appear properly
Checked.
> 7. Verify that bookmarks display properly
Checked.
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
>
General and Advanced need a little more width :(.
> It is important for you to let us know what areas are completed and
> which ones are still in progress.
>
We consider this an alpha release in termos of localization. There are
no strings in English, but our system has identified some
inconsistencies in the translation (and we're also starting to check
against the glossary we've been building). So that's where the work will
go next. We hope to have that fixed by RC1.
There's no one working on mozilla.com pages for pt-PT at the moment. We
have some people working with Mozilla Europe. Is that enough? What
should we do?
Best regards,
João Miguel Neves
Aleks Reinhardt
For Slovene (sl):
> 1. Verify version string and build ID in "About Firefox..."
Mozilla/5.0 (X11; U; Linux i686; sl; rv:1.8.1b2) Gecko/20060821
Firefox/2.0b2
Seems OK.
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
Yes.
>
> 3. Key URLs are properly localized
> 1. Default home page properly localized
Yes.
> 2. First run page
Opens two pages simultaneously in tabs (which is a good touch, I think!):
- the normal start/home page
- http://developer.mozilla.org/devnews/index.php/2006/07/12/firefox-2-
beta-1-milestone-released/
The key is OK I suppose; it points to
http://www.mozilla.org/projects/firefox/2.0b2/firstrun/
There is no locale information here; I think this is going to be implemented
in bug 345805?
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> Are the URLs in the right format, do they resolve, are the redirects set
> up right?
OK.
The URLs lead to English pages, naturally.
I'm curious about the Bookmark Addons link - it leads directly to
addons.mozilla.org without specifically listing the addons for bookmarks.
Is that expected behaviour? (If it is, I need to change the name of the
bookmark in Slovene.)
(There is another URL redirecting to AMO front page - Customize Firefox. I
expect this will change to another page, though?)
> 4. Search engines
> 1. Verify the right ones are listed, logos are in good shape, try a
> search in each one.
I hope the right ones are listed. I'm not sure if we need to explain the
removal of some which are in en-US but not in sl and the addition of a few
others again in a new bug. The list is almost the same as in 1.5, except
that:
- Yahoo! has been left in, as it just seems easier that way
- Slowwwenia has been removed, as they have complained about the search
plugin in Firefox 1.5 and were very rude about it, so we assume they don't
want a search plugin in future versions
> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
> 3. For others Google is first, Yahoo! is second (make sure that you
> have bugs filed on exceptions for Yahoo!)
Google is first, Yahoo! is second.
> 5. Verify Help appears and is properly localized
Help appears and is partially localised (do we need to localise it fully?).
> 6. Ensure that dialogs for Extensions and Themes appear properly
Seems OK.
> 7. Verify that bookmarks display properly
They do.
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
Seems OK.
Another thing: I was wondering about dictionaries on AMO: will we be able to
provide a link to our dictionary somewhere, eg the localised Firefox
Central? And also, will the English dictionary (preferably en-GB?) be
available on the AMO site?
Cheers
Aleks
Ayman Hourieh
For ar (Arabic):
>
> 1. Verify version string and build ID in "About Firefox..."
Mozilla/5.0 (Windows; U; Windows NT 5.1; ar; rv:1.8.1b2)
Gecko/20060823 BonEcho/2.0b2
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
Yes.
>
> 3. Key URLs are properly localized
> 1. Default home page properly localized
Yes.
> 2. First run page
404
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
404
> Are the URLs in the right format, do they resolve, are the redirects set
> up right?
I think we need to localize these pages, I'm waiting for them to be
ready.
> 4. Search engines
We use the same ones as en-US.
>
> 5. Verify Help appears and is properly localized
We didn't localize it.
> 6. Ensure that dialogs for Extensions and Themes appear properly
OK.
> 7. Verify that bookmarks display properly
OK.
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
>
OK.
Thanks.
-Ayman
Alexander L. Slovesnik
28.08.2006 14:28 you wrote:
For Russian (ru) Firefox:
>
> 1. Verify version string and build ID in "About Firefox..."
>
Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.8.1b2) Gecko/20060821
Firefox/2.0b2
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
>
Yes.
> 3. Key URLs are properly localized
> 1. Default home page properly localized
Yes.
>
> 2. First run page
Opens two pages in tabs:
- http://www.google.ru/firefox?client=firefox-a&rls=org.mozilla:ru:official
- http://developer.mozilla.org/devnews/index.php/2006/07/12/firefox-2-beta-1-milestone-released/
>
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> Are the URLs in the right format, do they resolve, are the redirects
> set up right?
>
First-run page - redirects to http://www.mozilla.com/firefox/2.0/firstrun
Updated page - redirects to http://www.mozilla.com/firefox/2.0/whatsnew
Getting Started - redirects to http://www.mozilla.com/firefox/central/
Help and Tutorials - redirects to http://www.mozilla.com/support/
Customize Firefox - redirects to https://addons.mozilla.org/
Get Involved - redirects to http://www.mozilla.org/contribute/
About Us - redirects to http://www.mozilla.com/about/
> 4. Search engines
> 1. Verify the right ones are listed, logos are in good shape, try a
> search in each one.
Right ones are listed, search is ok.
>
> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
n/a
> 3. For others Google is first, Yahoo! is second (make sure that you
> have bugs filed on exceptions for Yahoo!)
Google is first, Yandex is second. See
https://bugzilla.mozilla.org/show_bug.cgi?id=348096 for discussion on
Yandex vs. Yahoo.
>
> 5. Verify Help appears and is properly localized
It appears and localized. Outdated, of course, but it will be updated
when en-US help will be ready.
> 6. Ensure that dialogs for Extensions and Themes appear properly
OK.
> 7. Verify that bookmarks display properly
OK. RSS feed leads to English BBC feed instead Russian one.
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
They are looking OK.
>
>
> It is important for you to let us know what areas are completed and
> which ones are still in progress.
>
> Thanks
>
> Axel
--
Sincerely yours,
Alexander L. Slovesnik a.k.a. Unghost
==>Web-page: http://www.unghost.ru/
==>Jabber ID: a...@mozilla.ru
==>Gmail Talk ID: ung...@gmail.com
==>ICQ: 205497659
==>IRC: ircs://irc.mozilla.org:6697/mozilla-ru
Ricardo Palomares Martinez
>
> 1. Verify version string and build ID in "About Firefox..."
>
Version string: Bon Echo versión 2.0b2
Build ID: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.8.1b2)
Gecko/20060829 BonEcho/2.0b2
I suspect this is wrong (partly due to comments in bug 348082), but I
honestly don't know what I'm supposed to change. I've been reviewing
browser/branding/* and other-licenses/branding/firefox/* and I don't
see any difference between en-US and es-ES files.
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
Yes.
> 3. Key URLs are properly localized
> 1. Default home page properly localized
http://es-ES.start.mozilla.com/firefox?client=firefox-a&rls=org.mozilla:es-ES:official
The web content itself is translated, too.
> 2. First run page
I suppose that because of 1., on first run I get two tabs, one
pointing to a MDC page with Firefox 2 beta 1 documentation, and the
other with the default home page.
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> Are the URLs in the right format, do they resolve, are the redirects set
> up right?
The URLs in bookmarks.html are right, although they end in some
unexpected places (at least for me):
Help and Tutorials goes to http://www.mozilla.com/support/
Customize Firefox goes to https://addons.mozilla.org/
Get Involved goes to http://www.mozilla.org/contribute/
About Us goes to http://www.mozilla.com/about/
Maybe this will change when pages on mozilla.com get localized, or
maybe it another side effect of the wrong version string?
BTW, we are internally voting for a change of the RSS sample live
bookmark. Currently, it shows english results for BBC. We'll file a
bug as soon as we decide it.
> 4. Search engines
> 1. Verify the right ones are listed, logos are in good shape, try a
> search in each one.
The (currently) right ones are listed, although we intend to ask
permission to add Wikipedia (with or without removing Amazon.com, at
Mozilla Foundation will).
Yahoo! searchplugin shipped is the en-US one, but I swear that I've
uploaded a localized version to CVS:
http://lxr.mozilla.org/l10n-mozilla1.8/source/es-ES/browser/searchplugins/yahoo.xml
Also, I've modified eBay searchplugin, since it was verbatim of en-US
and we weren't using spanish version of eBay.
> 3. For others Google is first, Yahoo! is second (make sure that you
> have bugs filed on exceptions for Yahoo!)
This is OK.
>
> 5. Verify Help appears and is properly localized
OK
> 6. Ensure that dialogs for Extensions and Themes appear properly
OK
> 7. Verify that bookmarks display properly
I've just uploaded a modification because it seems that
&brandShortName; is not parsed inside bookmarks.html.
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
A bit small for Unix, patch commited to CVS, waiting for tomorrow's
builds.
> It is important for you to let us know what areas are completed and
> which ones are still in progress.
We're still translating help, as most teams, I guess.
Ricardo.
--
If it's true that we are here to help others,
then what exactly are the OTHERS here for?
Aleks Reinhardt
> Version string: Bon Echo versión 2.0b2
> Build ID: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.8.1b2)
> Gecko/20060829 BonEcho/2.0b2
>
> I suspect this is wrong (partly due to comments in bug 348082), but I
> honestly don't know what I'm supposed to change. I've been reviewing
> browser/branding/* and other-licenses/branding/firefox/* and I don't
> see any difference between en-US and es-ES files.
Have you downloaded your build from
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2.0b2-candidates/rc2/ ?
(I'm not *sure* that's the right place, but I hope it is!)
Cheers
Aleks
Ville Pohjanheimo
For Finnish (fi):
28/08/06 13:28, Axel Hecht kirjoitti:
>
> Please provide status for the following areas and let us know if any
> parts of these are incomplete for Beta 2:
>
> 1. Verify version string and build ID in "About Firefox..."
>
Ok. Mozilla/5.0 (X11; U; Linux i686; fi; rv:1.8.1b2) Gecko/2006082101
Firefox/2.0b2
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
All ok.
>
> 3. Key URLs are properly localized
> 1. Default home page properly localized
> 2. First run page
> 3. Other new product pages.
All URLs redirect apparently correctly.
The destination URLs of course are not yet localized and e.g. the "Get
bookmark add-ons" link redirects to addons.mozilla.org frontpage (and
not to some bookmark extension page)
> 4. Search engines
Ok. Waiting approval though..
> 5. Verify Help appears and is properly localized
> 6. Ensure that dialogs for Extensions and Themes appear properly
> 7. Verify that bookmarks display properly
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
Ok. Minor tweaking with layouts (8) is still left.
-ville
Ville Pohjanheimo
> For Finnish (fi):
>
> 28/08/06 13:28, Axel Hecht kirjoitti:
>> Please provide status for the following areas and let us know if any
>> parts of these are incomplete for Beta 2:
>>
>> 1. Verify version string and build ID in "About Firefox..."
>>
> Ok. Mozilla/5.0 (X11; U; Linux i686; fi; rv:1.8.1b2) Gecko/2006082101
> Firefox/2.0b2
>
>> 2. Status of menu items and context menus, do they appear and are
>> translated properly?
>
> All ok.
>> 3. Key URLs are properly localized
>> 1. Default home page properly localized
>> 2. First run page
>> 3. Other new product pages.
>
> All URLs redirect apparently correctly.
Bah. Forgot the RSS feed. ATM redirecting to the (English) BBC feed. No
bug yet.
Ricardo Palomares Martinez
> Ricardo Palomares Martinez wrote:
>> Version string: Bon Echo versión 2.0b2
>> Build ID: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.8.1b2)
>> Gecko/20060829 BonEcho/2.0b2
>>
>> I suspect this is wrong (partly due to comments in bug 348082), but I
>> honestly don't know what I'm supposed to change. I've been reviewing
>> browser/branding/* and other-licenses/branding/firefox/* and I don't
>> see any difference between en-US and es-ES files.
>
> Have you downloaded your build from
> http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2.0b2-candidates/rc2/ ?
>
Yes, it was, thank you!
Version string: Firefox versión 2.0b2
Build ID: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.8.1b2)
Gecko/20060821 Firefox/2.0b2
Axel, I don't know if I'm supposed to re-test with this one-week old
version. It could have errors already solved in CVS. :-?
TIA
Robert Kaiser
> Axel, I don't know if I'm supposed to re-test with this one-week old
> version. It could have errors already solved in CVS. :-?
I think those are the versions supposed to be released as 2.0b2, current
CVS is already ahead of that release and on its way to rc1 while testing
of release builds continues (but take my comments with a grain of salt,
I'm not working on FF myself, as you might know).
Robert Kaiser
Axel Hecht
If the latest builds on ftp work, that's fine. We won't respin b2 for that.
Axel
Axel Hecht
No, this is supposed to be a category or page with extensions that help
or extend your experience with bookmarks. Shaver has something up on his
sleeves there.
>
>> 4. Search engines
>> 1. Verify the right ones are listed, logos are in good shape, try a
>> search in each one.
>
> I hope the right ones are listed. I'm not sure if we need to explain the
> removal of some which are in en-US but not in sl and the addition of a few
> others again in a new bug. The list is almost the same as in 1.5, except
> that:
> - Yahoo! has been left in, as it just seems easier that way
> - Slowwwenia has been removed, as they have complained about the search
> plugin in Firefox 1.5 and were very rude about it, so we assume they don't
> want a search plugin in future versions
>
Would you add that as a comment to bug 348104? That'd be pretty valuable
to have there.
>
>> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
>> 3. For others Google is first, Yahoo! is second (make sure that you
>> have bugs filed on exceptions for Yahoo!)
>
> Google is first, Yahoo! is second.
>
>> 5. Verify Help appears and is properly localized
>
> Help appears and is partially localised (do we need to localise it fully?).
>
>> 6. Ensure that dialogs for Extensions and Themes appear properly
>
> Seems OK.
>
>> 7. Verify that bookmarks display properly
>
> They do.
>
>> 8. Layouts for complex dialogs are correct. Try the
>> Preferences/Options tool and check the various tabs.
>
> Seems OK.
>
>
>
> Another thing: I was wondering about dictionaries on AMO: will we be able to
> provide a link to our dictionary somewhere, eg the localised Firefox
> Central? And also, will the English dictionary (preferably en-GB?) be
> available on the AMO site?
The link to download dictionaries will be available from the context
menu of text areas. That bug is fixed, though I don't know if it made
into B2.
If a en-GB dictionary will be available is pretty much up to the
maintainers of that dictionary.
Axel
Axel Hecht
I bet your testing is fair enough.
Axel
Axel Hecht
You want to use unique file names, as the build picks up en-US search
plugins of the same name favorably. For some, it's a feature, for some,
it's a bug ;-)
So, you want to create ebay-es.xml and yahoo-es.xml and reference those.
Axel
Axel Hecht
> Hi,
>
> we would like to get some feedback from all teams, to understand where
> each of several areas are in terms of completion. We will be able to use
> this information to help direct beta2 testing resources to the areas
> that are finished, and keep them away for areas where work is still in
> progress.
>
> parts of these are incomplete for Beta 2:
>
>
> translated properly?
>
> 1. Default home page properly localized
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> Are the URLs in the right format, do they resolve, are the redirects set
> up right?
>
A comment on the redirects, for B2, we won't attempt to set up the
redirects to localized content, we're just trying to not get any 404s.
I'm contacting infra on how to communicate the feed redirects, and how
to set up the domains for new locales.
For mozilla.com content, I'm leaving that up to Pascal, and add-ons to
Wil Clouser/shaver.
Axel
Damjan Georgievski
> parts of these are incomplete for Beta 2:
>
> 1. Verify version string and build ID in "About Firefox..."
Mozilla/5.0 (X11; U; Linux i686; mk; rv:1.8.1b2) Gecko/20060821
Firefox/2.0b2
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
ok
> 3. Key URLs are properly localized
> 1. Default home page properly localized
the google page? yes it's ok
> 2. First run page
not localized?
http://developer.mozilla.org/devnews/index.php/2006/07/12/firefox-2-beta-1-milestone-released/
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> Are the URLs in the right format, do they resolve, are the redirects set
> up right?
>
> 4. Search engines
> 1. Verify the right ones are listed, logos are in good shape, try a
> search in each one.
ok
> 3. For others Google is first, Yahoo! is second (make sure that you
> have bugs filed on exceptions for Yahoo!)
ok, google first
> 5. Verify Help appears and is properly localized
appears ok, we don't have it localized except the "Using the Help Window".
> 6. Ensure that dialogs for Extensions and Themes appear properly
seems ok, but clicking on the icons in the toolbar generates exceptions
(printed in the terminal):
[Exception... "Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsIPrefBranch.getComplexValue]" nsresult: "0x80004005
(NS_ERROR_FAILURE)" location: "JS frame ::
file:///home/gdamjan/firefox/components/nsURLFormatter.js ::
uf_formatURLPref :: line 129" data: no]
> 7. Verify that bookmarks display properly
bookmarks are ok
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
we spent some time before the b2 lock-down to make this pretty good.
It's still good.
--
damjan
Damjan Georgievski
>> parts of these are incomplete for Beta 2:
>>
>> 1. Verify version string and build ID in "About Firefox..."
>
> Mozilla/5.0 (X11; U; Linux i686; mk; rv:1.8.1b2) Gecko/20060821
> Firefox/2.0b2
BTW the file date of the build is 26.08.2006, why is the signature saying
20060821 ?
Also, the back and forward buttons don't look correct when hovered. Is this
a know problem with b2 or I am the only one seeing it?
--
damjan
Josesun
For zh-TW:
Axel Hecht 寫道：
> Please provide status for the following areas and let us know if any
> parts of these are incomplete for Beta 2:
>
> 1. Verify version string and build ID in "About Firefox..."
Mozilla/5.0 (Windows; U; Windows NT 5.1; zh-TW; rv:1.8.1b2)
Gecko/20060830 BonEcho/2.0b2
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
It's all right.
> 3. Key URLs are properly localized
> 1. Default home page properly localized
OK.
> 2. First run page
That page still in Beta 1.
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> Are the URLs in the right format, do they resolve, are the redirects set
> up right?
All get 404 error.
> 4. Search engines
> 1. Verify the right ones are listed, logos are in good shape, try a
> search in each one.
OK.
> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
> 3. For others Google is first, Yahoo! is second (make sure that you
> have bugs filed on exceptions for Yahoo!)
OK.Yahoo first, Google second.
> 5. Verify Help appears and is properly localized
OK
> 6. Ensure that dialogs for Extensions and Themes appear properly
OK
> 7. Verify that bookmarks display properly
OK
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
OK
Jose Sun
Magyarkúti Barna
> 1. Verify version string and build ID in "About Firefox..."
Looks OK
(Mozilla/5.0 (X11; U; Linux i686; hu; rv:1.8.1b1) Gecko/20060710
Firefox/2.0b1)
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
Absolutely fine.
> 3. Key URLs are properly localized
> 1. Default home page properly localized
Firefox Start, as it is in 1.5 (Hungarian version loads:
http://www.google.co.hu/firefox?client=firefox-a&rls=org.mozilla:hu:official)
> 2. First run page
Current English version appears, we will need to localize it.
> 3. Other new product pages.
* Will-be first run page (http://hu.www.mozilla.com/hu/firefox/2.0/firstrun)
redirects to http://www.mozilla.com/firefox/2.0/firstrun
* Will-be updated page (http://hu.www.mozilla.com/hu/firefox/2.0/whatsnew)
redirects to http://www.mozilla.com/firefox/2.0/whatsnew
*Getting started page (http://hu.www.mozilla.com/hu/firefox/central/)
redirects to http://www.mozilla.com/firefox/central/ - already have it
localized elsewhere
*Help and tutorials page (http://hu.www.mozilla.com/hu/firefox/help/)
redirects to http://www.mozilla.com/support/ - already localized for 1.5
*Customize Firefox page (http://hu.www.mozilla.com/hu/firefox/customize/)
redirects to https://addons.mozilla.org/ - have a Hungarian extension site,
should we somehow include that as well?
*Get involved page (http://hu.www.mozilla.com/hu/firefox/community/)
redirects to http://www.mozilla.org/contribute/ - but we already have it
localized at Mozilla Europe.
*About us page (http://hu.www.mozilla.com/hu/firefox/about/) redirects to
http://www.mozilla.com/about/ - but already have it localized at Mozilla
Europe
We intend to translate the above pages (some of them are already translated
but located elsewhere), so there is going to be a great mess here in the
future :)
> 4. Search engines
> 1. Verify the right ones are listed, logos are in good shape, try a
> search in each one.
All work fine.
> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
> 3. For others Google is first, Yahoo! is second (make sure that you
> have bugs filed on exceptions for Yahoo!)
OK, Google first.
> 5. Verify Help appears and is properly localized
We had help localized in 1.5, nothing appears in help windows with B2, we
want help localized in B2 as well.
> 6. Ensure that dialogs for Extensions and Themes appear properly
Yes, they do.
> 7. Verify that bookmarks display properly
Properly and localized.
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
All is fine.
> It is important for you to let us know what areas are completed and
> which ones are still in progress.
>
> Thanks
>
> Axel
--
Magyarkúti Barna
Get my PGP public key from
http://www.bke.hu/magyarkuti/barna/bmagyarkuti.asc
or key id 0672F1A0 from server hkp://wwwkeys.eu.pgp.net
Axel Hecht
http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages has details on that.
>
>> 4. Search engines
>
>> 1. Verify the right ones are listed, logos are in good shape, try a
>> search in each one.
> All work fine.
>
>> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
>> 3. For others Google is first, Yahoo! is second (make sure that you
>> have bugs filed on exceptions for Yahoo!)
> OK, Google first.
>
>> 5. Verify Help appears and is properly localized
> We had help localized in 1.5, nothing appears in help windows with B2, we
> want help localized in B2 as well.
https://bugzilla.mozilla.org/show_bug.cgi?id=344312 is the culprit.
Magyarkúti Barna
>Magyarkúti Barna wrote:
>> For Hungarian (HU)
>>
>>> 1. Verify version string and build ID in "About Firefox..."
>> Looks OK
>> (Mozilla/5.0 (X11; U; Linux i686; hu; rv:1.8.1b1) Gecko/20060710
>> Firefox/2.0b1)
Sorry, I mixed up my firefox versions and seem to have tested on B1 :(
Version string is (Mozilla/5.0 (X11; U; Linux i686; hu; rv:1.8.1b2)
Gecko/20060821 Firefox/2.0b2)
>>> 3. Other new product pages.
>> We intend to translate the above pages (some of them are already
>> translated but located elsewhere), so there is going to be a great mess
>> here in the future :)
>
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages has details on that.
Thanks for the advice
>>> 5. Verify Help appears and is properly localized
>> We had help localized in 1.5, nothing appears in help windows with B2, we
>> want help localized in B2 as well.
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=344312 is the culprit.
We have that fixed in B2 HU, help appears correctly.
To sum it up, everything works fine, but we have to work on the product
pages. Sorry for glitch.
--
Magyarkúti Barna
Hungarian Mozilla Project
Tim Riley
> Axel Hecht a écrit :
>> Please provide status for the following areas and let us know if any
>> parts of these are incomplete for Beta 2:
>
>> 1. Verify version string and build ID in "About Firefox..."
> Firefox/2.0b2
>
>> 2. Status of menu items and context menus, do they appear and are
>> translated properly?
>
>> 3. Key URLs are properly localized
> http://bonsai-l10n.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&subdir=l10n/fr/browser/profile&command=DIFF_FRAMESET&file=bookmarks.html&rev1=1.3.2.4&rev2=1.3.2.5&root=/l10n
>> 1. Default home page properly localized
> http://www.google.fr/firefox?client=firefox-a&rls=org.mozilla:fr:official
>> 2. First run page
> KEY is OK, Redirection not OK
> (http://www.mozilla.org/projects/firefox/2.0b2/firstrun/)
>
>> 3. Other new product pages. See:
>> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
>> Are the URLs in the right format, do they resolve, are the redirects
>> set up right?
> (http://www.mozilla.com/firefox/2.0/whatsnew) 404
> *Help and tutorials* : KEY is OK, Redirection not OK
> (http://www.mozilla.com/firefox/help/) 404
> *Customize* : KEY is OK, Redirection not OK
> (http://www.mozilla.com/firefox/customize/) 404
> *Get involved* : KEY is OK, redirection not OK
> (http://www.mozilla.com/firefox/community/) 404
> *About us* : KEY is OK, Redirection not OK
> (http://www.mozilla.com/firefox/about/) 404
>
>> 4. Search engines
>> 1. Verify the right ones are listed, logos are in good shape, try a
>> search in each one.
>
>> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
>
>> 3. For others Google is first, Yahoo! is second (make sure that you
>> have bugs filed on exceptions for Yahoo!)
> OK
>
> links from the TOC and pages correctly displayed.
> But:
> *** We are very concerned about the plan to put the help on the
> Internet. Will that happen? As you might know, we used entities from DTD
> in the help files to stay synced with the interface (bug 247595). If
> help will go on Internet for FF 2.0 : we need to test that as soon as
> possible.
> *** Also, help is not finished yet (in en-US) and we'd like to have soon
> the new screenshots images for help because of the new theme and because
> we need to localize them too for part of them.
>
>> 6. Ensure that dialogs for Extensions and Themes appear properly
>
>> 7. Verify that bookmarks display properly
>
>> 8. Layouts for complex dialogs are correct. Try the
>> Preferences/Options tool and check the various tabs.
>
> for all platforms and also between KDE and Gnome which seem to behave
> differently
>
> Last : we need to make a last review for the help files, maybe some
> rewording for the new terms or concepts that appeared in this version
> and looking for some possible remaining accesskeys conflicts.
>
> Regards
Thanks for the info Cedric. Did anyone get back to you about your
concerns with help?
--Tim
Axel Hecht
> Axel Hecht a écrit :
<...>
>
>> 5. Verify Help appears and is properly localized
> This was not the case on 2.0b2. This is now fixed on nightlies. All the
> links from the TOC and pages correctly displayed.
> But:
> *** We are very concerned about the plan to put the help on the
> Internet. Will that happen? As you might know, we used entities from DTD
> in the help files to stay synced with the interface (bug 247595). If
> help will go on Internet for FF 2.0 : we need to test that as soon as
> possible.
> *** Also, help is not finished yet (in en-US) and we'd like to have soon
> the new screenshots images for help because of the new theme and because
> we need to localize them too for part of them.
>
The plan of moving help to the web is still vague, but there. At least I
didn't hear it die. I'm not sure if we'll enable using chrome entities
in general, but we have that problem for the accesskey modifier already
anyway.
Axel
Cédric
>
> Thanks for the info Cedric. Did anyone get back to you about your
> concerns with help?
>
> --Tim
No, not yet.
For the help screenshot images, the ones that needed to be localized
have been removed, so no problem anymore about that.
I saw a few bugs about help (concerning the changes occurred in the
preferences windows) that are still pending :
At least bug 341899, bug 343857 and bug 344580 : these ones are
mandatory for FF 2.0 IMHO, and need to be resolved ASAP so that
localizers can localize the changes.
For the Help being hosted on Internet : I have no further information.
Regards
Tim Riley
> In article <UcmdnfotFMY4Xm_Z...@mozilla.org>, Axel Hecht wrote...
>
>> 1. Verify version string and build ID in "About Firefox..."
>
>
>> 2. Status of menu items and context menus, do they appear and are
>> translated properly?
>
>
>> 3. Key URLs are properly localized
>
>
>> 2. First run page
>
> http://www.mozilla.org/projects/firefox/2.0b2/firstrun/ is a 404
>
>> 3. Other new product pages. See:
>> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
>> Are the URLs in the right format, do they resolve, are the redirects set
>> up right?
>
> http://www.mozilla.org/projects/firefox/2.0b2/whatsnew/ is a 404
>
> Help -> Release Notes
> http://www.mozilla.org/projects/bonecho/releases/2.0b2.html is a 404
>
> Help -> Report Web Forgery
> http://sv-se.phish-report.mozilla.com/?hl=sv-SE&url=http%3A%2F%2Fwww.mozilla.org%2F
> redirects to
> http://www.mozilla.com/?hl=sv-SE&url=http%253A%252F%252Fwww.mozilla.org%252F
> which doesn't seem right.
>
>> 4. Search engines
>
> We use the same plugins as en-US.
>
>> 5. Verify Help appears and is properly localized
>
>
>> 6. Ensure that dialogs for Extensions and Themes appear properly
>
>
>> 7. Verify that bookmarks display properly
>
> http://sv-SE.add-ons.mozilla.com/sv-SE/firefox/bookmarks/
> redirects to
> https://addons.mozilla.org/
>
> Getting Started
> http://sv-SE.www.mozilla.com/sv-SE/firefox/central/
> redirects to
> http://www.mozilla.com/firefox/central/
>
> Latest Headlines
> http://sv-SE.fxfeeds.mozilla.com/sv-SE/firefox/headlines.xml
> fails to update live bookmark
>
> Help and Tutorials
> http://sv-SE.www.mozilla.com/sv-SE/firefox/help/
> redirects to
> http://www.mozilla.com/firefox/help/
> which is a 404
>
> Customize Firefox
> http://sv-SE.www.mozilla.com/sv-SE/firefox/customize/
> redirects to
> http://www.mozilla.com/firefox/customize/
> which is a 404
>
> Get Involved
> http://sv-SE.www.mozilla.com/sv-SE/firefox/community/
> redirects to
> http://www.mozilla.com/firefox/community/
> which is a 404
>
> About Us
> http://sv-SE.www.mozilla.com/sv-SE/firefox/about/
> redirects to
> http://www.mozilla.com/firefox/about/
> which is a 404
>
>> 8. Layouts for complex dialogs are correct. Try the
>> Preferences/Options tool and check the various tabs.
>
>
Thanks for the info Hasse! --Tim
Tim Riley
pi wrote:
> Axel Hecht wrote:
>> Hi,
>>
>> we would like to get some feedback from all teams, to understand where
>> each of several areas are in terms of completion. We will be able to use
>> this information to help direct beta2 testing resources to the areas
>> that are finished, and keep them away for areas where work is still in
>> progress.
>>
>> parts of these are incomplete for Beta 2:
>>
>
> BonEcho/2.0b2
>> 2. Status of menu items and context menus, do they appear and are
>> translated properly?
>
> Yes
>
>> 3. Key URLs are properly localized
>> 1. Default home page properly localized
>
>
>> 3. Other new product pages. See:
>> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
>> Are the URLs in the right format, do they resolve, are the redirects set
>> up right?
>
>
>> 4. Search engines
>> 1. Verify the right ones are listed, logos are in good shape, try a
>> search in each one.
>
>
>
>> 3. For others Google is first, Yahoo! is second (make sure that you
>> have bugs filed on exceptions for Yahoo!)
>
> OK
>
>
>> 6. Ensure that dialogs for Extensions and Themes appear properly
>
>> 7. Verify that bookmarks display properly
>
>
>> 8. Layouts for complex dialogs are correct. Try the
>> Preferences/Options tool and check the various tabs.
>
>> It is important for you to let us know what areas are completed and
>> which ones are still in progress.
>>
>> Thanks
>>
>> Axel
>
Tim Riley
> ਸੋਮਵਾਰ 28 ਅਗਸਤ 2006 15:58 ਨੂੰ, Axel Hecht ਨੇ ਲਿਖਿਆ:
>> Please provide status for the following areas and let us know if any
>> parts of these are incomplete for Beta 2:
>>
>> 1. Verify version string and build ID in "About Firefox..."
>>
> Firefox/2.0b2
>> 2. Status of menu items and context menus, do they appear and are
>> translated properly?
>>
>> 3. Key URLs are properly localized
>> 1. Default home page properly localized
>> 2. First run page
>> 3. Other new product pages. See:
>> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
>> Are the URLs in the right format, do they resolve, are the redirects set
>> up right?
>> 4. Search engines
>> 1. Verify the right ones are listed, logos are in good shape, try a
>> search in each one.
>> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
>> have bugs filed on exceptions for Yahoo!)
>>
>> 5. Verify Help appears and is properly localized
>> 6. Ensure that dialogs for Extensions and Themes appear properly
>> 7. Verify that bookmarks display properly
>> 8. Layouts for complex dialogs are correct. Try the
>> Preferences/Options tool and check the various tabs.
>>
>
> thanks
Thanks A S Alam! --Tim
Mad Maks
>> 2. First run page
> -http://www.mozilla.org/projects/firefox/2.0b2/firstrun/ redirect to
> http://developer.mozilla.org/devnews/index.php/2006/07/12/firefox-2-beta-1-milestone-released/
>
it is now redirected to
http://www.mozilla.org/projects/bonecho/index-2.0b2.html
Tim Riley
> Hello,
>
> here is Lithuanian (lt) Firefox 2 B2 localization status.
>
> > 1. Verify version string and build ID in "About Firefox..."
>
> Mozilla/5.0 (Windows; U; Windows NT 5.1; lt; rv:1.8.1b2) Gecko/20060821
>
>
> > 2. Status of menu items and context menus, do they appear and are
> > translated properly?
>
>
> > 3. Key URLs are properly localized
> > 1. Default home page properly localized
>
> redirected from http://lt.www.mozilla.com/lt/firefox/central/
>
> > 2. First run page
>
> Two tabs:
> Page in English:
> http://developer.mozilla.org/devnews/index.php/2006/07/12/firefox-2-beta-1-milestone-released/
>
> and Google Start page (new snippets need to be translated).
>
> > 3. Other new product pages. See:
> > http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> > Are the URLs in the right format, do they resolve, are the redirects set
> > up right?
>
> they are redirected to pages in English.
>
> > 4. Search engines
> > 1. Verify the right ones are listed, logos are in good shape, try a
> > search in each one.
>
>
> > 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
> > 3. For others Google is first, Yahoo! is second (make sure that you
> > have bugs filed on exceptions for Yahoo!)
>
>
> >
> > 5. Verify Help appears and is properly localized
>
>
> > 6. Ensure that dialogs for Extensions and Themes appear properly
>
>
> > 7. Verify that bookmarks display properly
>
> pages in English.
>
> News feed http://lt.fxfeeds.mozilla.com/lt/firefox/headlines.xml
> is redirected to BBC news in English.
> Could we set redirection to news in Lithhuanian, e.g. news feed,
> provided by Lithuanian
> national radio and television site http://www.lrt.lt/rss/all.php (this
> feed was approved and integrated
> in Fx 1.5.0.x official versions)? Should I file a bug on this?
>
> > 8. Layouts for complex dialogs are correct. Try the
> > Preferences/Options tool and check the various tabs.
>
>
> > It is important for you to let us know what areas are completed and
> > which ones are still in progress.
> >
>
> Tatjana
Tatjana-
Thanks Tatjana! Did you get an answer to you question about redirection
to news in Lithuanian?
--Tim
Tim Riley
> Michele Dal Corso ha scritto:
>>> 1. Verify version string and build ID in "About Firefox..."
>> BonEcho/2.0b2
> I'm sorry, the right string is:
> Mozilla/5.0 (X11; U; Linux i686; it; rv:1.8.1b2) Gecko/20060821
> Firefox/2.0b2
Thanks for all the info! --Tim
Tim Riley
> Axel Hecht yazmış:
>
>> 1. Verify version string and build ID in "About Firefox..."
>
> BonEcho/2.0b2
>
>> 2. Status of menu items and context menus, do they appear and are
>> translated properly?
>
>
>> 3. Key URLs are properly localized
>> 1. Default home page properly localized
>
>
>> 2. First run page
>
> Two tabs:
>
>
>
> and
>
> http://www.google.com.tr/firefox?client=firefox-a&rls=org.mozilla:tr:official
>
>> 3. Other new product pages. See:
>> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
>> Are the URLs in the right format, do they resolve, are the redirects
>> set up right?
>
>
>> 4. Search engines
>> 1. Verify the right ones are listed, logos are in good shape, try a
>> search in each one.
>> 3. For others Google is first, Yahoo! is second (make sure that you
>> have bugs filed on exceptions for Yahoo!)
>
>
>> 5. Verify Help appears and is properly localized
>
>
>> 6. Ensure that dialogs for Extensions and Themes appear properly
>
>
>> 7. Verify that bookmarks display properly
>
>
>> 8. Layouts for complex dialogs are correct. Try the
>> Preferences/Options tool and check the various tabs.
>
>
>
> Serkan
>
>
Thanks for the info Serkan!
Tim Riley
>> 1. Verify version string and build ID in "About Firefox..."
> Firefox/2.0b2
>>
>> 2. Status of menu items and context menus, do they appear and are
>> translated properly?
>
> Yes
>
>>
>> 1. Default home page properly localized
> Yes
>> 2. First run page
> -http://www.mozilla.org/projects/firefox/2.0b2/firstrun/ redirect to
> http://developer.mozilla.org/devnews/index.php/2006/07/12/firefox-2-beta-1-milestone-released/
>
>
> bookmarks.html is not updated yet (Bug #350569)
> the localized URL are redirect to the en-US version
>>
>> 4. Search engines
>> 1. Verify the right ones are listed, logos are in good shape, try a
>> search in each one.
>> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
>> 3. For others Google is first, Yahoo! is second (make sure that you
>> have bugs filed on exceptions for Yahoo!)
>>
>> 5. Verify Help appears and is properly localized
>
>> 6. Ensure that dialogs for Extensions and Themes appear properly
> -http://nl.add-ons.mozilla.com/nl/firefox/2.0b2/extensions/ redirect to
> https://addons.mozilla.org/extensions/
> -http://nl.add-ons.mozilla.com/nl/firefox/2.0b2/themes/ redirect to
> https://addons.mozilla.org/themes/
>
>> 7. Verify that bookmarks display properly
>> 8. Layouts for complex dialogs are correct. Try the
>> Preferences/Options tool and check the various tabs.
>>
Thankyou for the info! --Tim
Tim Riley
> Also, the default live bookmark feed leads to English BBC,
> we need it redirected to http://www.gazeta.pl/pub/rss/wiadomosci.xml
>
Marek-
I think the Livefeed issue is fixed as of August 30th. Thanks for all
the info for pl!
--Tim
Tim Riley
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> En/na Axel Hecht ha escrit:
>> Hi,
>>
>> we would like to get some feedback from all teams, to understand where
>> each of several areas are in terms of completion. We will be able to use
>> this information to help direct beta2 testing resources to the areas
>> that are finished, and keep them away for areas where work is still in
>> progress.
>>
>> parts of these are incomplete for Beta 2:
>>
>>
> BonEcho/2.0b2
>
>> 2. Status of menu items and context menus, do they appear and are
>> translated properly?
>>
>
>
>> 3. Key URLs are properly localized
>> 1. Default home page properly localized
>
> http://www.google.es/firefox?client=firefox-a&rls=org.mozilla:ca:official
> Note: bug 345479
>
>> 2. First run page
>
> Two tabs:
>
> http://developer.mozilla.org/devnews/index.php/2006/07/12/firefox-2-beta-1-milestone-released/
>
>
>> 3. Other new product pages. See:
>> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
>> Are the URLs in the right format, do they resolve, are the redirects set
>> up right?
>
> Latest News -> redirecting BBC feed
> Help and tutorials -> redirecting fine
> Customize -> redirecting fine
> Get involved -> redirecting fine
> About us -> redirecting fine
>
>
> Pages referred in wiki page as:
>
> First run -> redirect well, but no content:
> http://www.mozilla.com/firefox/2.0/firstrun
> What's new -> redirect well, but no content:
> http://www.mozilla.com/firefox/2.0/whatsnew
>
>> 4. Search engines
>> 1. Verify the right ones are listed, logos are in good shape, try a
>> search in each one.
>
>
>> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
>> 3. For others Google is first, Yahoo! is second (make sure that you
>> have bugs filed on exceptions for Yahoo!)
>
>
>> 5. Verify Help appears and is properly localized
>
>
>> 6. Ensure that dialogs for Extensions and Themes appear properly
>
>
>> 7. Verify that bookmarks display properly
>
>
>> 8. Layouts for complex dialogs are correct. Try the
>> Preferences/Options tool and check the various tabs.
>>
>
>
> I think that's all :)
>
> - --
> * Toni Hermoso Pulido
> - ------------------------------------------------------
> web: http://www.cau.cat
> email: ton...@softcatala.org
> gpg: B67B43DC
> planet: http://planeta.softcatala.org
> - ------------------------------------------------------
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFE9CC53O471rZ7Q9wRAiVDAJ9svl9seoroyEVJF+VLGAWU8smhSwCggxvp
> JwJhUDmudxLWK6C+cOOiT2w=
> =U7GI
> -----END PGP SIGNATURE-----
Thankyou Toni! --Tim
Tim Riley
> Seg, 2006-08-28 às 12:28 +0200, Axel Hecht escreveu:
>> Hi,
>>
>> we would like to get some feedback from all teams, to understand where
>> each of several areas are in terms of completion. We will be able to use
>> this information to help direct beta2 testing resources to the areas
>> that are finished, and keep them away for areas where work is still in
>> progress.
>>
>> Please provide status for the following areas and let us know if any
>> parts of these are incomplete for Beta 2:
>>
>> 1. Verify version string and build ID in "About Firefox..."
>>
> Firefox/2.0b2
>
>> 2. Status of menu items and context menus, do they appear and are
>> translated properly?
>>
>
>> 3. Key URLs are properly localized
>> 1. Default home page properly localized
>
>
>> 2. First run page
> http://developer.mozilla.org/devnews/index.php/2006/07/12/firefox-2-beta-1-milestone-released/ (not translated) and the start page.
>
>> 3. Other new product pages. See:
>> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
>> Are the URLs in the right format, do they resolve, are the redirects set
>> up right?
>>
> all the others on that page also give a 404.
>
>> 4. Search engines
>> 1. Verify the right ones are listed, logos are in good shape, try a
>> search in each one.
> on google and yahoo).
>
>> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
>> 3. For others Google is first, Yahoo! is second (make sure that you
>> have bugs filed on exceptions for Yahoo!)
>>
>
>> 6. Ensure that dialogs for Extensions and Themes appear properly
>
>> 7. Verify that bookmarks display properly
>
>> 8. Layouts for complex dialogs are correct. Try the
>> Preferences/Options tool and check the various tabs.
>>
>
>> It is important for you to let us know what areas are completed and
>> which ones are still in progress.
>>
> no strings in English, but our system has identified some
> inconsistencies in the translation (and we're also starting to check
> against the glossary we've been building). So that's where the work will
> go next. We hope to have that fixed by RC1.
>
> There's no one working on mozilla.com pages for pt-PT at the moment. We
> have some people working with Mozilla Europe. Is that enough? What
> should we do?
>
> Best regards,
> João Miguel Neves
João-
Did you get an answer to you question about translating the mozilla.com
pages?
Thanks for the info about your locale!
--Tim
Axel Hecht
I have said at a few places now that I'm still working on a process to
get those feed redirects collected and up.
And I still do.
Axel
Brian King
Axel Hecht wrote:
> Please provide status for the following areas and let us know if any
> parts of these are incomplete for Beta 2:
>
> 1. Verify version string and build ID in "About Firefox..."
Mozilla/5.0 (Windows; U; Windows NT 5.1; ga-IE; rv:1.8.1b2)
Gecko/20060830 BonEcho/2.0b2
Note it was build dated 2006-08-31 downloaded from:
http://ftp.eu.mozilla.org/pub/mozilla.org/firefox/tinderbox/latest-mozilla1.8-l10n/
Build dated 26th from following location are broken:
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2.0b2-candidates/rc2/
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
Yes.
> 3. Key URLs are properly localized
> 1. Default home page properly localized
OK
http://www.google.com/firefox?client=firefox-a&rls=org.mozilla:ga-IE:official
> 2. First run page
http://developer.mozilla.org/devnews/index.php/2006/07/12/firefox-2-beta-1-milestone-released/
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> Are the URLs in the right format, do they resolve, are the redirects set
> up right?
All of these have localized URLs, but just redirect to English pages.
Help and Tutorials : http://www.mozilla.com/support/
Customize Firefox : https://addons.mozilla.org/
Get Involved : http://www.mozilla.org/contribute/
About Us : http://www.mozilla.com/about/
> 4. Search engines
> 1. Verify the right ones are listed, logos are in good shape, try a
> search in each one.
> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
> 3. For others Google is first, Yahoo! is second (make sure that you
> have bugs filed on exceptions for Yahoo!)
All is in order, except Yahoo is missing. But I think that is being
taken care of in bug 348121 which got checkin approval.
> 5. Verify Help appears and is properly localized
No, but we never undertook this task.
> 6. Ensure that dialogs for Extensions and Themes appear properly
Yes.
> 7. Verify that bookmarks display properly
Yes.
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
In the Security tab (Slandail) in Options, the content is obscured a bit
on the right side. Everything else is fine.
> It is important for you to let us know what areas are completed and
> which ones are still in progress.
AFAIK, everything is completed, though Kevin will confirm.
--
Brian King
www.mozdev.org - free project hosting for the Mozilla community
Axel Hecht
>> 6. Ensure that dialogs for Extensions and Themes appear properly
> seems ok, but clicking on the icons in the toolbar generates exceptions
> (printed in the terminal):
>
> [Exception... "Component returned failure code: 0x80004005
> (NS_ERROR_FAILURE) [nsIPrefBranch.getComplexValue]" nsresult: "0x80004005
> (NS_ERROR_FAILURE)" location: "JS frame ::
> file:///home/gdamjan/firefox/components/nsURLFormatter.js ::
> uf_formatURLPref :: line 129" data: no]
>
Did anybody else see this? Might be worthwhile to file a bug.
Axel
Mad Maks
Natsagdorj Shagdar
> 1. Verify version string and build ID in "About Firefox..."
Mozilla/5.0 (Windows; U; Windows NT 5.1; mn; rv:1.8.1b2) Gecko/20060821 Firefox/2.0b2
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
OK
> 3. Key URLs are properly localized
> 1. Default home page properly localized
OK
> 2. First run page
Two tabs:
http://www.mozilla.org/projects/bonecho/index-2.0b2.html
and
http://www.google.com.tr/firefox?client=firefox-a&rls=org.mozilla:mn:official
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> Are the URLs in the right format, do they resolve, are the redirects set
> up right?
Getting Started :
Key URL is NOT OK http://mn-MN.www.mozilla.com/en-US/firefox/central/
> 4. Search engines
> 1. Verify the right ones are listed, logos are in good shape, try a
> search in each one.
OK
> 2. For ja, ja-JP, ko, zh-CN, and zh-TW: Yahoo! is first, Google 2nd
Not applicable
> 3. For others Google is first, Yahoo! is second (make sure that you
> have bugs filed on exceptions for Yahoo!)
OK
> 5. Verify Help appears and is properly localized
Help content doesn't appear.
> 6. Ensure that dialogs for Extensions and Themes appear properly
OK
> 7. Verify that bookmarks display properly
OK
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
Some dialog's size need to be resized (color, advanced dialogs in the Web contents tab)
Damjan Georgievski
>>> (NS_ERROR_FAILURE) [nsIPrefBranch.getComplexValue]" nsresult:
>>> "0x80004005
>>> (NS_ERROR_FAILURE)" location: "JS frame ::
>>> file:///home/gdamjan/firefox/components/nsURLFormatter.js ::
>>> uf_formatURLPref :: line 129" data: no]
>>>
>>
>> Did anybody else see this? Might be worthwhile to file a bug.
> I do not see this error in firefox 2.0b2 nl
Are you sure?
I just installed the Dutch 2.0b2 and I get the same exception on the
terminal.
As I said, even in the mk version, everything seems to work ok, but the
exception is there.
Or maybe it's something with my platform?!?
I'm using gtk+2-2.8.20, glib2-2.10.3, glibc-2.3.6, xorg-6.8.2 (Slackware
10.2, slightly updated).
--
damjan
Mad Maks
start Fx from within the teminal and you see the error there or in the
errorconsole? I will try to replicate your way.
greetings
Damjan Georgievski
> Damjan Georgievski wrote:
>>>>> [Exception... "Component returned failure code: 0x80004005
>>>>> (NS_ERROR_FAILURE) [nsIPrefBranch.getComplexValue]" nsresult:
>>>>> "0x80004005
>>>>> (NS_ERROR_FAILURE)" location: "JS frame ::
>>>>> file:///home/gdamjan/firefox/components/nsURLFormatter.js ::
>>>>> uf_formatURLPref :: line 129" data: no]
>>>>>
>>>> Did anybody else see this? Might be worthwhile to file a bug.
>>
>>> I do not see this error in firefox 2.0b2 nl
>>
>> Are you sure?
>> I just installed the Dutch 2.0b2 and I get the same exception on the
>> terminal.
>>
>> As I said, even in the mk version, everything seems to work ok, but the
>> exception is there.
>>
>> Or maybe it's something with my platform?!?
>> I'm using gtk+2-2.8.20, glib2-2.10.3, glibc-2.3.6, xorg-6.8.2 (Slackware
>> 10.2, slightly updated).
>>
> do you have any extension installed or do you use a clean profile?
I start with no profile at all
> you start Fx from within the teminal and you see the error there or in the
> errorconsole? I will try to replicate your way.
I start Firefox from xterm and see the errors on stdout.
Maybe this "screenshot" will make it clearer:
gdamjan@legolas:~$ rm -rf .mozilla/
gdamjan@legolas:~$ ./firefox-nl/firefox
[Exception... "Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsIPrefBranch.getComplexValue]" nsresult: "0x80004005
(NS_ERROR_FAILURE)" location: "JS frame ::
file:///home/gdamjan/firefox-nl/components/nsURLFormatter.js ::
uf_formatURLPref :: line 129" data: no]
[Exception... "Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsIPrefBranch.getComplexValue]" nsresult: "0x80004005
(NS_ERROR_FAILURE)" location: "JS frame ::
file:///home/gdamjan/firefox-nl/components/nsURLFormatter.js ::
uf_formatURLPref :: line 129" data: no]
[Exception... "Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsIPrefBranch.getComplexValue]" nsresult: "0x80004005
(NS_ERROR_FAILURE)" location: "JS frame ::
file:///home/gdamjan/firefox-nl/components/nsURLFormatter.js ::
uf_formatURLPref :: line 129" data: no]
[Exception... "Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsIPrefBranch.getComplexValue]" nsresult: "0x80004005
(NS_ERROR_FAILURE)" location: "JS frame ::
file:///home/gdamjan/firefox-nl/components/nsURLFormatter.js ::
uf_formatURLPref :: line 129" data: no]
--
damjan
Mad Maks
i don't see your error. i get a lot of other reports but non like yours:
timmaks@laptop:~/My Computer/testbuilds/firefox$ ./firefox
(Gecko:14577): Gdk-CRITICAL **: gdk_pixbuf_get_from_drawable: assertion
`gdk_window_is_viewable (src)' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels:
assertion `pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_bits_per_sample:
assertion`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion
`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion
`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride:
assertion `pixbuf != NULL' failed
(Gecko:14577): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT(object)' failed
(Gecko:14577): Gdk-CRITICAL **: gdk_pixbuf_get_from_drawable: assertion
`gdk_window_is_viewable (src)' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels:
assertion `pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_bits_per_sample:
assertion`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion
`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion
`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride:
assertion `pixbuf != NULL' failed
(Gecko:14577): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT(object)' failed
(Gecko:14577): Gdk-CRITICAL **: gdk_pixbuf_get_from_drawable: assertion
`gdk_window_is_viewable (src)' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels:
assertion `pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_bits_per_sample:
assertion`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion
`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion
`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride:
assertion `pixbuf != NULL' failed
(Gecko:14577): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT(object)' failed
(Gecko:14577): Gdk-CRITICAL **: gdk_pixbuf_get_from_drawable: assertion
`gdk_window_is_viewable (src)' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels:
assertion `pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_bits_per_sample:
assertion`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion
`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion
`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride:
assertion `pixbuf != NULL' failed
(Gecko:14577): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT(object)' failed
(Gecko:14577): Gdk-CRITICAL **: gdk_pixbuf_get_from_drawable: assertion
`gdk_window_is_viewable (src)' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels:
assertion `pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_bits_per_sample:
assertion`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion
`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion
`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride:
assertion `pixbuf != NULL' failed
(Gecko:14577): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT(object)' failed
(Gecko:14577): Gdk-CRITICAL **: gdk_pixbuf_get_from_drawable: assertion
`gdk_window_is_viewable (src)' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels:
assertion `pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_bits_per_sample:
assertion`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion
`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion
`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride:
assertion `pixbuf != NULL' failed
(Gecko:14577): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT(object)' failed
(Gecko:14577): Gdk-CRITICAL **: gdk_pixbuf_get_from_drawable: assertion
`gdk_window_is_viewable (src)' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels:
assertion `pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_bits_per_sample:
assertion`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion
`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion
`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride:
assertion `pixbuf != NULL' failed
(Gecko:14577): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT(object)' failed
(Gecko:14577): Gdk-CRITICAL **: gdk_pixbuf_get_from_drawable: assertion
`gdk_window_is_viewable (src)' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels:
assertion `pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_bits_per_sample:
assertion`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion
`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion
`pixbuf != NULL' failed
(Gecko:14577): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride:
assertion `pixbuf != NULL' failed
(Gecko:14577): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT(object)' failed
Axel Hecht
> Damjan Georgievski wrote:
>
>>>> Or maybe it's something with my platform?!?
>>>> I'm using gtk+2-2.8.20, glib2-2.10.3, glibc-2.3.6, xorg-6.8.2
>>>> (Slackware
>>>> 10.2, slightly updated).
>>>>
>>> do you have any extension installed or do you use a clean profile?
>>
>> I start with no profile at all
>>
>>> you start Fx from within the teminal and you see the error there or
>>> in the
>>> errorconsole? I will try to replicate your way.
>>
>> I start Firefox from xterm and see the errors on stdout.
>> Maybe this "screenshot" will make it clearer:
>>
I know that there were versions of the url formatter that had spurious
dump()s in them. I bet Damjan has dump switched on, Tim does not.
I'm CCed on bugs that should fix that stuff, and I would think that it
should be fixed on a nightly.
Axel
Mark Tyndall
[...]
> Please provide status for the following areas and let us know if any
> parts of these are incomplete for Beta 2:
Sorry about the delay, I was unplugged from the 'net last week (and took
this long to catch up).
> 1. Verify version string and build ID in "About Firefox..."
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.8.1b2)
Gecko/20060821 Firefox/2.0b2
> 2. Status of menu items and context menus, do they appear and are
> translated properly?
Yes
> 3. Key URLs are properly localized
> 1. Default home page properly localized
http://www.google.co.uk/firefox?client=firefox-a&rls=org.mozilla:en-GB:official
> 2. First run page
Two tabs, which are the above home page and
http://www.mozilla.org/projects/bonecho/index-2.0b2.html
> 3. Other new product pages. See:
> http://wiki.mozilla.org/Firefox2/In-Product_Web_Pages
> Are the URLs in the right format, do they resolve, are the redirects set
> up right?
URLs are correct; all redirect to the current en-US pages
> 4. Search engines
All correct and working.
> 5. Verify Help appears and is properly localized
It appears. Localisation is still to complete, but this is on my list.
> 6. Ensure that dialogs for Extensions and Themes appear properly
*cough* I think you mean Add-ons. Yes, it's here.
> 7. Verify that bookmarks display properly
Yes.
> 8. Layouts for complex dialogs are correct. Try the
> Preferences/Options tool and check the various tabs.
All fine.
regards,
Mark..
--
British English localisations of:
SeaMonkey <http://www.tyndall.org.uk/moz_en-gb.html>
Firefox <http://www.tyndall.org.uk/fb_en-gb.html>
Thunderbird <http://www.tyndall.org.uk/tb_en-gb.html>