MozillaWiki - User contributions [en]

L10n:Teams:ja

2017-06-29T13:12:27Z

Dynamis: team update

__NOTOC__

=== Japanese (ja,ja-JP-mac) ===
Team website:
* [http://www.mozilla.jp/community/localization.html Introduction to Japanese L10N Community]
* [https://github.com/mozilla-japan/translation/wiki Translation Wiki]

====Active team members====
{| border="1" class="wikitable"
|-
! Name
! Email
! Role
! Desktop OS
! Tablet OS
! Mobile OS
! Hg Access?
! SVN Access?
|-
|ABE Hiroki (hATrayflood)
|<h[DOT]rayflood[AT] gmail[DOT]com>
|browser leader, mail/toolkit peer
|
|
|Android, iOS
|[https://bugzilla.mozilla.org/show_bug.cgi?id=659534 HG]
|
|-
|Masahiko IMANAKA (mar or marsf)
|<chimantaea_mirabilis[AT] yahoo[DOT]co[DOT]jp>
|firefoxos and mail leader, browser/toolkit peer
|
|
|
|[https://bugzilla.mozilla.org/show_bug.cgi?id=401979 CVS/HG]
|[https://bugzilla.mozilla.org/show_bug.cgi?id=775901 SVN]
|-
|Kasaki Nagato
|<nagato[DOT]kasaki[AT] gmail[DOT]com>
|mobile leader
|
|
|iOS
|[https://bugzilla.mozilla.org/show_bug.cgi?id=696693 HG]
|
|-
|Kazuyuki SUZUKI
|<info[AT]kechol[DOT]net>
|firefox os and mobile peer
|
|
|iOS
|
|
|-
|Tomoya ASAI (dynamis)
|<dynamis[AT] mozilla-japan[DOT]org> (MDN/SUMO: <dynamis[AT] firehacks[DOT]org>, bugmail: <bugzilla[AT] firehacks[DOT]org>, [https://twitter.com/dynamitter @dynamitter], [http://www.facebook.com/dynamis facebook])
|ja locale reviewer
|Mac (Win on VMWare)
|Android, iOS
|Android, Firefox OS
|[https://bugzilla.mozilla.org/show_bug.cgi?id=264931 CVS/HG]
|[https://bugzilla.mozilla.org/show_bug.cgi?id=708537 SVN]
|-
|Mantaroh Yoshinaga
|<mantaroh[AT] mozilla-japan[DOT]org> (bugmail: <mantaroh[AT] mozilla-japan[DOT]org>)
|MDN Translator
|Linux (Windows VM)
|
|
|
|
|
|-
|Takeshi Hamasaki
|<hmatrjp[AT] users[DOT]sourceforge[DOT]jp>
|MDN Translator
|Linux
|
|
|
|
|-
| Kohei Yoshino
| kohei.yoshino@gmail.com
| Web localizer
| OS X (Windows & Linux VM)
| Android
| Android
| No
| [https://bugzilla.mozilla.org/show_bug.cgi?id=870284 SVN]
|}

Note: You can use l10n-qa[AT]mozilla-japan[DOT]org alias to contact the ja l10n leaders. Some of members those who only related to [http://www.mozilla.jp/community/translation.html translating documents] are not on the table above, yet.

====Localizers in training====

====Active projects====
<ul>
<li>Product L10n: 
[https://github.com/mozilla-japan/gecko-l10n gecko-l10n GitHub repo],
[https://github.com/mozilla-japan/gaia-l10n gaia-l10n GitHub repo]</li>
<li>Document Translation: 
[https://github.com/mozilla-japan/translation/issues Translation Request (GitHub issues)],
[https://github.com/mozilla-japan/translation/wiki Translation Wiki]</li>
<li>SUMO: 
[https://support.mozilla.org/ja/localization Mozilla Support - (ja) L10N Dashboard]</li>
<li>MDN: 
[https://dev.mozilla.jp/project/mdnja/ MDN 日本語版 | Mozilla Developer Street (modest)]</li>
<li>Website L10n: 
[https://localize.mozilla.org/ja/ Mozilla Verbatim - Japanese]</li>
<li>Webmaker: 
[https://www.transifex.com/projects/p/webmaker/language/ja/ Mozilla Webmaker | Transifex]</li>
<li>Bugzilla-ja: 
[http://bug-ja.org/ Bugzilla Users Group in JApan]</li>
</ul>

====L10n kit====
''(Please list here the tools your team uses, as well as links to your L10n assets (e.g., translation memories, termbases, style guides, etc.).)''
;Tools:
* [https://github.com/mozilla-japan/lot Localization Tools (lot) Script]

;Translation Memory:
Japanese team are not using Translation Memory so far.

;Glossary:
* [https://github.com/mozilla-japan/translation/wiki/Mozilla-L10N-Glossary Mozilla L10N Glossary]
* [https://github.com/mozilla-japan/translation/wiki/Firefox-OS-Glossary Firefox OS Glossary]

;Style Guide:
* [https://github.com/mozilla-japan/translation/wiki/L10N-Guideline L10n Guideline (Product)]
* [https://github.com/mozilla-japan/translation/wiki/Editorial-Guideline Editorial Guideline (Translation)]

====How to join this l10n team====
* Join our [https://groups.google.com/forum/#!forum/mozilla-translations-ja Mozilla Japanese Translation Google Group].
* Check our [https://github.com/mozilla-japan/gecko-l10n Github repo for Gecko product l10n].
* Check our [https://github.com/mozilla-japan/translation/issues Translation wishlist in the Github Issues].

===== Localizing SUpport.MOzilla.org (SUMO) =====
If you want to help localize http://support.mozilla.org/ja into your language, please do the following:
# [https://support.mozilla.org/users/authcontributor Create a SUMO account]
# If you can, [https://support.mozilla.org/groups/japanese-localization get in touch with the Group Leader(s) listed here via a Private Message]. If there is nobody listed there, please get in touch with [http://support.mozilla.org/user/vesper Michał / vesper].
# [https://support.mozilla.org/kb/localize-mozilla-support Read our universal l10n documentation here]. For language-specific documentation, please get in touch with your Group Leader(s).
# [https://support.mozilla.org/forums/l10n-forum/711082 Visit our forums and introduce yourself to the community]. We don’t bite, unless you’re made of cake ;-)
# You're ready to go! If you have any questions, ask them on the forums.


====Team communication====
;Mailing lists:
There are some ML related to L10N/Translation
* [https://groups.google.com/forum/#!forum/mozilla-translations-ja Mozilla Japanese Translation Google Group]
* QA contact of ja L10N is private mailing list of l10n leaders: l10n-qa[AT]mozilla-japan[DOT]org

;Related websites:
* [http://forums.firehacks.org/l10n/ Japanese Localization Forum]
* [https://dev.mozilla.jp/l10n/ L10n documents at modest site]
* [http://www.mozilla-japan.org/jp/l10n/ Project Web Page (almost obsolete)]
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&component=ja,%20ja-JP-mac%20/%20Japanese link to file bug]

;Hashtag in tweets
* someones use hashtags when they mention the topic related to mozilla in Japan: (please add other hashtags if you know)
#もじら, #mozjp...
* #もずでぶ is used for topics rather development related. If your tweet contain crossover L10N and development, of course you can use it, too.

<noinclude>[[category:L10n Teams|ja]]</noinclude>

L10n:Teams:ja

2016-08-15T02:05:44Z

Dynamis: add l10n-qa contact

__NOTOC__

=== Japanese (ja,ja-JP-mac) ===
Team website:
* [http://www.mozilla.jp/community/localization.html Introduction to Japanese L10N Community]
* [https://github.com/mozilla-japan/translation/wiki Translation Wiki]

====Active team members====
{| border="1" class="wikitable"
|-
! Name
! Email
! Role
! Desktop OS
! Tablet OS
! Mobile OS
! Hg Access?
! SVN Access?
|-
|ABE Hiroki (hATrayflood)
|<h[DOT]rayflood[AT] gmail[DOT]com>
|browser leader, mail/toolkit peer
|
|
|Android, iOS
|[https://bugzilla.mozilla.org/show_bug.cgi?id=659534 HG]
|
|-
|Masahiko IMANAKA (mar or marsf)
|<chimantaea_mirabilis[AT] yahoo[DOT]co[DOT]jp>
|firefoxos and mail leader, browser/toolkit peer
|
|
|
|[https://bugzilla.mozilla.org/show_bug.cgi?id=401979 CVS/HG]
|[https://bugzilla.mozilla.org/show_bug.cgi?id=775901 SVN]
|-
|Kasaki Nagato
|<nagato[DOT]kasaki[AT] gmail[DOT]com>
|mobile leader
|
|
|iOS
|[https://bugzilla.mozilla.org/show_bug.cgi?id=696693 HG]
|
|-
|Kazuyuki SUZUKI
|<info[AT]kechol[DOT]net>
|firefox os and mobile peer
|
|
|iOS
|
|
|-
|Noritada Shimizu
|<nshimizu[AT] mozilla-japan[DOT]org>
|web l10n leader (webmaster of mozilla.jp)
|Mac (Win on VMWare)
|
|iOS
|
|[https://bugzilla.mozilla.org/show_bug.cgi?id=843403 SVN]
|-
|Tomoya ASAI (dynamis)
|<dynamis[AT] mozilla-japan[DOT]org> (MDN/SUMO: <dynamis[AT] firehacks[DOT]org>, bugmail: <bugzilla[AT] firehacks[DOT]org>, [https://twitter.com/dynamitter @dynamitter], [http://www.facebook.com/dynamis facebook])
|ja locale reviewer
|Mac (Win on VMWare)
|Android, iOS
|Android, Firefox OS
|[https://bugzilla.mozilla.org/show_bug.cgi?id=264931 CVS/HG]
|[https://bugzilla.mozilla.org/show_bug.cgi?id=708537 SVN]
|-
|Mantaroh Yoshinaga
|<mantaroh[AT] mozilla-japan[DOT]org> (bugmail: <mantaroh[AT] mozilla-japan[DOT]org>)
|MDN Translator
|Linux (Windows VM)
|
|
|
|
|
|-
|Takeshi Hamasaki
|<hmatrjp[AT] users[DOT]sourceforge[DOT]jp>
|MDN Translator
|Linux
|
|
|
|
|-
| Kohei Yoshino
| kohei.yoshino@gmail.com
| Web localizer
| OS X (Windows & Linux VM)
| Android
| Android
| No
| [https://bugzilla.mozilla.org/show_bug.cgi?id=870284 SVN]
|}

Note: You can use l10n-qa[AT]mozilla-japan[DOT]org alias to contact the ja l10n leaders. Some of members those who only related to [http://www.mozilla.jp/community/translation.html translating documents] are not on the table above, yet.

====Localizers in training====

====Active projects====
<ul>
<li>Product L10n: 
[https://github.com/mozilla-japan/gecko-l10n gecko-l10n GitHub repo],
[https://github.com/mozilla-japan/gaia-l10n gaia-l10n GitHub repo]</li>
<li>Document Translation: 
[https://github.com/mozilla-japan/translation/issues Translation Request (GitHub issues)],
[https://github.com/mozilla-japan/translation/wiki Translation Wiki]</li>
<li>SUMO: 
[https://support.mozilla.org/ja/localization Mozilla Support - (ja) L10N Dashboard]</li>
<li>MDN: 
[https://dev.mozilla.jp/project/mdnja/ MDN 日本語版 | Mozilla Developer Street (modest)]</li>
<li>Website L10n: 
[https://localize.mozilla.org/ja/ Mozilla Verbatim - Japanese]</li>
<li>Webmaker: 
[https://www.transifex.com/projects/p/webmaker/language/ja/ Mozilla Webmaker | Transifex]</li>
<li>Bugzilla-ja: 
[http://bug-ja.org/ Bugzilla Users Group in JApan]</li>
</ul>

====L10n kit====
''(Please list here the tools your team uses, as well as links to your L10n assets (e.g., translation memories, termbases, style guides, etc.).)''
;Tools:
* [https://github.com/mozilla-japan/lot Localization Tools (lot) Script]

;Translation Memory:
Japanese team are not using Translation Memory so far.

;Glossary:
* [https://github.com/mozilla-japan/translation/wiki/Mozilla-L10N-Glossary Mozilla L10N Glossary]
* [https://github.com/mozilla-japan/translation/wiki/Firefox-OS-Glossary Firefox OS Glossary]

;Style Guide:
* [https://github.com/mozilla-japan/translation/wiki/L10N-Guideline L10n Guideline (Product)]
* [https://github.com/mozilla-japan/translation/wiki/Editorial-Guideline Editorial Guideline (Translation)]

====How to join this l10n team====
* Join our [https://groups.google.com/forum/#!forum/mozilla-translations-ja Mozilla Japanese Translation Google Group].
* Check our [https://github.com/mozilla-japan/gecko-l10n Github repo for Gecko product l10n].
* Check our [https://github.com/mozilla-japan/translation/issues Translation wishlist in the Github Issues].

===== Localizing SUpport.MOzilla.org (SUMO) =====
If you want to help localize http://support.mozilla.org/ja into your language, please do the following:
# [https://support.mozilla.org/users/authcontributor Create a SUMO account]
# If you can, [https://support.mozilla.org/groups/japanese-localization get in touch with the Group Leader(s) listed here via a Private Message]. If there is nobody listed there, please get in touch with [http://support.mozilla.org/user/vesper Michał / vesper].
# [https://support.mozilla.org/kb/localize-mozilla-support Read our universal l10n documentation here]. For language-specific documentation, please get in touch with your Group Leader(s).
# [https://support.mozilla.org/forums/l10n-forum/711082 Visit our forums and introduce yourself to the community]. We don’t bite, unless you’re made of cake ;-)
# You're ready to go! If you have any questions, ask them on the forums.


====Team communication====
;Mailing lists:
There are some ML related to L10N/Translation
* [https://groups.google.com/forum/#!forum/mozilla-translations-ja Mozilla Japanese Translation Google Group]
* QA contact of ja L10N is private mailing list of l10n leaders: l10n-qa[AT]mozilla-japan[DOT]org

;Related websites:
* [http://forums.firehacks.org/l10n/ Japanese Localization Forum]
* [https://dev.mozilla.jp/l10n/ L10n documents at modest site]
* [http://www.mozilla-japan.org/jp/l10n/ Project Web Page (almost obsolete)]
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&component=ja,%20ja-JP-mac%20/%20Japanese link to file bug]

;Hashtag in tweets
* someones use hashtags when they mention the topic related to mozilla in Japan: (please add other hashtags if you know)
#もじら, #mozjp...
* #もずでぶ is used for topics rather development related. If your tweet contain crossover L10N and development, of course you can use it, too.

<noinclude>[[category:L10n Teams|ja]]</noinclude>

L10n:Teams:ja

2016-06-30T02:58:13Z

Dynamis: write "how to join" section

__NOTOC__

=== Japanese (ja,ja-JP-mac) ===
Team website:
* [http://www.mozilla.jp/community/localization.html Introduction to Japanese L10N Community]
* [https://github.com/mozilla-japan/translation/wiki Translation Wiki]

====Active team members====
{| border="1" class="wikitable"
|-
! Name
! Email
! Role
! Desktop OS
! Tablet OS
! Mobile OS
! Hg Access?
! SVN Access?
|-
|ABE Hiroki (hATrayflood)
|<h[DOT]rayflood[AT] gmail[DOT]com>
|browser leader, mail/toolkit peer
|
|
|Android, iOS
|[https://bugzilla.mozilla.org/show_bug.cgi?id=659534 HG]
|
|-
|Masahiko IMANAKA (mar or marsf)
|<chimantaea_mirabilis[AT] yahoo[DOT]co[DOT]jp>
|firefoxos and mail leader, browser/toolkit peer
|
|
|
|[https://bugzilla.mozilla.org/show_bug.cgi?id=401979 CVS/HG]
|[https://bugzilla.mozilla.org/show_bug.cgi?id=775901 SVN]
|-
|Kasaki Nagato
|<nagato[DOT]kasaki[AT] gmail[DOT]com>
|mobile leader
|
|
|iOS
|[https://bugzilla.mozilla.org/show_bug.cgi?id=696693 HG]
|
|-
|Kazuyuki SUZUKI
|<info[AT]kechol[DOT]net>
|firefox os and mobile peer
|
|
|iOS
|
|
|-
|Noritada Shimizu
|<nshimizu[AT] mozilla-japan[DOT]org>
|web l10n leader (webmaster of mozilla.jp)
|Mac (Win on VMWare)
|
|iOS
|
|[https://bugzilla.mozilla.org/show_bug.cgi?id=843403 SVN]
|-
|Tomoya ASAI (dynamis)
|<dynamis[AT] mozilla-japan[DOT]org> (MDN/SUMO: <dynamis[AT] firehacks[DOT]org>, bugmail: <bugzilla[AT] firehacks[DOT]org>, [https://twitter.com/dynamitter @dynamitter], [http://www.facebook.com/dynamis facebook])
|ja locale reviewer
|Mac (Win on VMWare)
|Android, iOS
|Android, Firefox OS
|[https://bugzilla.mozilla.org/show_bug.cgi?id=264931 CVS/HG]
|[https://bugzilla.mozilla.org/show_bug.cgi?id=708537 SVN]
|-
|Mantaroh Yoshinaga
|<mantaroh[AT] mozilla-japan[DOT]org> (bugmail: <mantaroh[AT] mozilla-japan[DOT]org>)
|MDN Translator
|Linux (Windows VM)
|
|
|
|
|
|-
|Takeshi Hamasaki
|<hmatrjp[AT] users[DOT]sourceforge[DOT]jp>
|MDN Translator
|Linux
|
|
|
|
|}

(Some of members those who only related to [http://www.mozilla.jp/community/translation.html translating documents] are not on the table above, yet.)

====Localizers in training====

====Active projects====
<ul>
<li>Product L10n: 
[https://github.com/mozilla-japan/gecko-l10n gecko-l10n GitHub repo],
[https://github.com/mozilla-japan/gaia-l10n gaia-l10n GitHub repo]</li>
<li>Document Translation: 
[https://github.com/mozilla-japan/translation/issues Translation Request (GitHub issues)],
[https://github.com/mozilla-japan/translation/wiki Translation Wiki]</li>
<li>SUMO: 
[https://support.mozilla.org/ja/localization Mozilla Support - (ja) L10N Dashboard]</li>
<li>MDN: 
[https://dev.mozilla.jp/project/mdnja/ MDN 日本語版 | Mozilla Developer Street (modest)]</li>
<li>Website L10n: 
[https://localize.mozilla.org/ja/ Mozilla Verbatim - Japanese]</li>
<li>Webmaker: 
[https://www.transifex.com/projects/p/webmaker/language/ja/ Mozilla Webmaker | Transifex]</li>
<li>Bugzilla-ja: 
[http://bug-ja.org/ Bugzilla Users Group in JApan]</li>
</ul>

====L10n kit====
''(Please list here the tools your team uses, as well as links to your L10n assets (e.g., translation memories, termbases, style guides, etc.).)''
;Tools:
* [https://github.com/mozilla-japan/lot Localization Tools (lot) Script]

;Translation Memory:
Japanese team are not using Translation Memory so far.

;Glossary:
* [https://github.com/mozilla-japan/translation/wiki/Mozilla-L10N-Glossary Mozilla L10N Glossary]
* [https://github.com/mozilla-japan/translation/wiki/Firefox-OS-Glossary Firefox OS Glossary]

;Style Guide:
* [https://github.com/mozilla-japan/translation/wiki/L10N-Guideline L10n Guideline (Product)]
* [https://github.com/mozilla-japan/translation/wiki/Editorial-Guideline Editorial Guideline (Translation)]

====How to join this l10n team====
* Join our [https://groups.google.com/forum/#!forum/mozilla-translations-ja Mozilla Japanese Translation Google Group].
* Check our [https://github.com/mozilla-japan/gecko-l10n Github repo for Gecko product l10n].
* Check our [https://github.com/mozilla-japan/translation/issues Translation wishlist in the Github Issues].

===== Localizing SUpport.MOzilla.org (SUMO) =====
If you want to help localize http://support.mozilla.org/ja into your language, please do the following:
# [https://support.mozilla.org/users/authcontributor Create a SUMO account]
# If you can, [https://support.mozilla.org/groups/japanese-localization get in touch with the Group Leader(s) listed here via a Private Message]. If there is nobody listed there, please get in touch with [http://support.mozilla.org/user/vesper Michał / vesper].
# [https://support.mozilla.org/kb/localize-mozilla-support Read our universal l10n documentation here]. For language-specific documentation, please get in touch with your Group Leader(s).
# [https://support.mozilla.org/forums/l10n-forum/711082 Visit our forums and introduce yourself to the community]. We don’t bite, unless you’re made of cake ;-)
# You're ready to go! If you have any questions, ask them on the forums.


====Team communication====
;Mailing lists:
There are some ML related to L10N/Translation
* [https://groups.google.com/forum/#!forum/mozilla-translations-ja Mozilla Japanese Translation Google Group]
* QA contact of ja L10N is private mailing list of l10n leaders: l10n-qa[AT]mozilla-japan[DOT]org

;Related websites:
* [http://forums.firehacks.org/l10n/ Japanese Localization Forum]
* [https://dev.mozilla.jp/l10n/ L10n documents at modest site]
* [http://www.mozilla-japan.org/jp/l10n/ Project Web Page (almost obsolete)]
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&component=ja,%20ja-JP-mac%20/%20Japanese link to file bug]

;Hashtag in tweets
* someones use hashtags when they mention the topic related to mozilla in Japan: (please add other hashtags if you know)
#もじら, #mozjp...
* #もずでぶ is used for topics rather development related. If your tweet contain crossover L10N and development, of course you can use it, too.

<noinclude>[[category:L10n Teams|ja]]</noinclude>

L10n:Teams:ja

2016-06-30T02:54:33Z

Dynamis: some links addes to guildelines

__NOTOC__

=== Japanese (ja,ja-JP-mac) ===
Team website:
* [http://www.mozilla.jp/community/localization.html Introduction to Japanese L10N Community]
* [https://github.com/mozilla-japan/translation/wiki Translation Wiki]

====Active team members====
{| border="1" class="wikitable"
|-
! Name
! Email
! Role
! Desktop OS
! Tablet OS
! Mobile OS
! Hg Access?
! SVN Access?
|-
|ABE Hiroki (hATrayflood)
|<h[DOT]rayflood[AT] gmail[DOT]com>
|browser leader, mail/toolkit peer
|
|
|Android, iOS
|[https://bugzilla.mozilla.org/show_bug.cgi?id=659534 HG]
|
|-
|Masahiko IMANAKA (mar or marsf)
|<chimantaea_mirabilis[AT] yahoo[DOT]co[DOT]jp>
|firefoxos and mail leader, browser/toolkit peer
|
|
|
|[https://bugzilla.mozilla.org/show_bug.cgi?id=401979 CVS/HG]
|[https://bugzilla.mozilla.org/show_bug.cgi?id=775901 SVN]
|-
|Kasaki Nagato
|<nagato[DOT]kasaki[AT] gmail[DOT]com>
|mobile leader
|
|
|iOS
|[https://bugzilla.mozilla.org/show_bug.cgi?id=696693 HG]
|
|-
|Kazuyuki SUZUKI
|<info[AT]kechol[DOT]net>
|firefox os and mobile peer
|
|
|iOS
|
|
|-
|Noritada Shimizu
|<nshimizu[AT] mozilla-japan[DOT]org>
|web l10n leader (webmaster of mozilla.jp)
|Mac (Win on VMWare)
|
|iOS
|
|[https://bugzilla.mozilla.org/show_bug.cgi?id=843403 SVN]
|-
|Tomoya ASAI (dynamis)
|<dynamis[AT] mozilla-japan[DOT]org> (MDN/SUMO: <dynamis[AT] firehacks[DOT]org>, bugmail: <bugzilla[AT] firehacks[DOT]org>, [https://twitter.com/dynamitter @dynamitter], [http://www.facebook.com/dynamis facebook])
|ja locale reviewer
|Mac (Win on VMWare)
|Android, iOS
|Android, Firefox OS
|[https://bugzilla.mozilla.org/show_bug.cgi?id=264931 CVS/HG]
|[https://bugzilla.mozilla.org/show_bug.cgi?id=708537 SVN]
|-
|Mantaroh Yoshinaga
|<mantaroh[AT] mozilla-japan[DOT]org> (bugmail: <mantaroh[AT] mozilla-japan[DOT]org>)
|MDN Translator
|Linux (Windows VM)
|
|
|
|
|
|-
|Takeshi Hamasaki
|<hmatrjp[AT] users[DOT]sourceforge[DOT]jp>
|MDN Translator
|Linux
|
|
|
|
|}

(Some of members those who only related to [http://www.mozilla.jp/community/translation.html translating documents] are not on the table above, yet.)

====Localizers in training====

====Active projects====
<ul>
<li>Product L10n: 
[https://github.com/mozilla-japan/gecko-l10n gecko-l10n GitHub repo],
[https://github.com/mozilla-japan/gaia-l10n gaia-l10n GitHub repo]</li>
<li>Document Translation: 
[https://github.com/mozilla-japan/translation/issues Translation Request (GitHub issues)],
[https://github.com/mozilla-japan/translation/wiki Translation Wiki]</li>
<li>SUMO: 
[https://support.mozilla.org/ja/localization Mozilla Support - (ja) L10N Dashboard]</li>
<li>MDN: 
[https://dev.mozilla.jp/project/mdnja/ MDN 日本語版 | Mozilla Developer Street (modest)]</li>
<li>Website L10n: 
[https://localize.mozilla.org/ja/ Mozilla Verbatim - Japanese]</li>
<li>Webmaker: 
[https://www.transifex.com/projects/p/webmaker/language/ja/ Mozilla Webmaker | Transifex]</li>
<li>Bugzilla-ja: 
[http://bug-ja.org/ Bugzilla Users Group in JApan]</li>
</ul>

====L10n kit====
''(Please list here the tools your team uses, as well as links to your L10n assets (e.g., translation memories, termbases, style guides, etc.).)''
;Tools:
* [https://github.com/mozilla-japan/lot Localization Tools (lot) Script]

;Translation Memory:
Japanese team are not using Translation Memory so far.

;Glossary:
* [https://github.com/mozilla-japan/translation/wiki/Mozilla-L10N-Glossary Mozilla L10N Glossary]
* [https://github.com/mozilla-japan/translation/wiki/Firefox-OS-Glossary Firefox OS Glossary]

;Style Guide:
* [https://github.com/mozilla-japan/translation/wiki/L10N-Guideline L10n Guideline (Product)]
* [https://github.com/mozilla-japan/translation/wiki/Editorial-Guideline Editorial Guideline (Translation)]

====How to join this l10n team====
* Join L10N Mailing list. 

===== Localizing SUpport.MOzilla.org (SUMO) =====
If you want to help localize http://support.mozilla.org/ja into your language, please do the following:
# [https://support.mozilla.org/users/authcontributor Create a SUMO account]
# If you can, [https://support.mozilla.org/groups/japanese-localization get in touch with the Group Leader(s) listed here via a Private Message]. If there is nobody listed there, please get in touch with [http://support.mozilla.org/user/vesper Michał / vesper].
# [https://support.mozilla.org/kb/localize-mozilla-support Read our universal l10n documentation here]. For language-specific documentation, please get in touch with your Group Leader(s).
# [https://support.mozilla.org/forums/l10n-forum/711082 Visit our forums and introduce yourself to the community]. We don’t bite, unless you’re made of cake ;-)
# You're ready to go! If you have any questions, ask them on the forums.


====Team communication====
;Mailing lists:
There are some ML related to L10N/Translation
* [https://groups.google.com/forum/#!forum/mozilla-translations-ja Mozilla Japanese Translation Google Group]
* QA contact of ja L10N is private mailing list of l10n leaders: l10n-qa[AT]mozilla-japan[DOT]org

;Related websites:
* [http://forums.firehacks.org/l10n/ Japanese Localization Forum]
* [https://dev.mozilla.jp/l10n/ L10n documents at modest site]
* [http://www.mozilla-japan.org/jp/l10n/ Project Web Page (almost obsolete)]
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&component=ja,%20ja-JP-mac%20/%20Japanese link to file bug]

;Hashtag in tweets
* someones use hashtags when they mention the topic related to mozilla in Japan: (please add other hashtags if you know)
#もじら, #mozjp...
* #もずでぶ is used for topics rather development related. If your tweet contain crossover L10N and development, of course you can use it, too.

<noinclude>[[category:L10n Teams|ja]]</noinclude>

L10n:Teams:ja

2015-10-28T04:40:32Z

Dynamis: update my contact

__NOTOC__

=== Japanese (ja,ja-JP-mac) ===
Team website:
* [http://www.mozilla.jp/community/localization.html Introduction to Japanese L10N Community]

====Active team members====
{| border="1" class="wikitable"
|-
! Name
! Email
! Role
! Desktop OS
! Tablet OS
! Mobile OS
! Hg Access?
! SVN Access?
|-
|ABE Hiroki (hATrayflood)
|<h[DOT]rayflood[AT] gmail[DOT]com>
|browser leader, mail/toolkit peer
|
|
|Android, iOS
|[https://bugzilla.mozilla.org/show_bug.cgi?id=659534 HG]
|
|-
|Masahiko IMANAKA (mar or marsf)
|<chimantaea_mirabilis[AT] yahoo[DOT]co[DOT]jp>
|firefoxos and mail leader, browser/toolkit peer
|
|
|
|[https://bugzilla.mozilla.org/show_bug.cgi?id=401979 CVS/HG]
|[https://bugzilla.mozilla.org/show_bug.cgi?id=775901 SVN]
|-
|Kasaki Nagato
|<nagato[DOT]kasaki[AT] gmail[DOT]com>
|mobile leader
|
|
|iOS
|[https://bugzilla.mozilla.org/show_bug.cgi?id=696693 HG]
|
|-
|Kazuyuki SUZUKI
|<info[AT]kechol[DOT]net>
|firefox os and mobile peer
|
|
|iOS
|
|
|-
|Noritada Shimizu
|<nshimizu[AT] mozilla-japan[DOT]org>
|web l10n leader (webmaster of mozilla.jp)
|Mac (Win on VMWare)
|
|iOS
|
|[https://bugzilla.mozilla.org/show_bug.cgi?id=843403 SVN]
|-
|Tomoya ASAI (dynamis)
|<dynamis[AT] mozilla-japan[DOT]org> (MDN/SUMO: <dynamis[AT] firehacks[DOT]org>, bugmail: <bugzilla[AT] firehacks[DOT]org>, [https://twitter.com/dynamitter @dynamitter], [http://www.facebook.com/dynamis facebook])
|ja locale reviewer
|Mac (Win on VMWare)
|Android, iOS
|Android, Firefox OS
|[https://bugzilla.mozilla.org/show_bug.cgi?id=264931 CVS/HG]
|[https://bugzilla.mozilla.org/show_bug.cgi?id=708537 SVN]
|-
|Mantaroh Yoshinaga
|<mantaroh[AT] mozilla-japan[DOT]org> (bugmail: <mantaroh[AT] mozilla-japan[DOT]org>)
|MDN Translator
|Linux (Windows VM)
|
|
|
|
|}

(Some of members those who only related to [http://www.mozilla.jp/community/translation.html translating documents] are not on the table above, yet.)

====Localizers in training====

====Active projects====
<ul>
<li>Product L10n: 
[https://github.com/mozilla-japan/gecko-l10n gecko-l10n GitHub repo],
[https://github.com/mozilla-japan/gaia-l10n gaia-l10n GitHub repo]</li>
<li>Document Translation: 
[https://github.com/mozilla-japan/translation/issues Translation Request (GitHub issues)],
[https://github.com/mozilla-japan/translation/wiki Translation Wiki]</li>
<li>SUMO: 
[https://support.mozilla.org/ja/localization Mozilla Support - (ja) L10N Dashboard]</li>
<li>MDN: 
[https://dev.mozilla.jp/project/mdnja/ MDN 日本語版 | Mozilla Developer Street (modest)]</li>
<li>Website L10n: 
[https://localize.mozilla.org/ja/ Mozilla Verbatim - Japanese]</li>
<li>Webmaker: 
[https://www.transifex.com/projects/p/webmaker/language/ja/ Mozilla Webmaker | Transifex]</li>
<li>Bugzilla-ja: 
[http://bug-ja.org/ Bugzilla Users Group in JApan]</li>
</ul>

====L10n kit====
''(Please list here the tools your team uses, as well as links to your L10n assets (e.g., translation memories, termbases, style guides, etc.).)''
;Tools:
[https://github.com/mozilla-japan/lot Localization Tools (lot) Script]
;Translation Memory:
;Glossary:
[https://github.com/mozilla-japan/translation/wiki/Mozilla-L10N-Glossary Mozilla L10N Glossary]

[https://github.com/mozilla-japan/translation/wiki/Firefox-OS-Glossary Firefox OS Glossary]
;Style Guide:

====How to join this l10n team====
* Join L10N Mailing list. 

===== Localizing SUpport.MOzilla.org (SUMO) =====
If you want to help localize http://support.mozilla.org/ja into your language, please do the following:
# [https://support.mozilla.org/users/authcontributor Create a SUMO account]
# If you can, [https://support.mozilla.org/groups/japanese-localization get in touch with the Group Leader(s) listed here via a Private Message]. If there is nobody listed there, please get in touch with [http://support.mozilla.org/user/vesper Michał / vesper].
# [https://support.mozilla.org/kb/localize-mozilla-support Read our universal l10n documentation here]. For language-specific documentation, please get in touch with your Group Leader(s).
# [https://support.mozilla.org/forums/l10n-forum/711082 Visit our forums and introduce yourself to the community]. We don’t bite, unless you’re made of cake ;-)
# You're ready to go! If you have any questions, ask them on the forums.


====Team communication====
;Mailing lists:
There are some ML related to L10N/Translation
* [https://groups.google.com/forum/#!forum/mozilla-translations-ja Mozilla Japanese Translation Google Group]
* QA contact of ja L10N is private mailing list of l10n leaders: l10n-qa[AT]mozilla-japan[DOT]org

;Related websites:
* [http://forums.firehacks.org/l10n/ Japanese Localization Forum]
* [https://dev.mozilla.jp/l10n/ L10n documents at modest site]
* [http://www.mozilla-japan.org/jp/l10n/ Project Web Page (almost obsolete)]
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&component=ja,%20ja-JP-mac%20/%20Japanese link to file bug]

;Hashtag in tweets
* someones use hashtags when they mention the topic related to mozilla in Japan: (please add other hashtags if you know)
#もじら, #mozjp, #fxos...
* #もずでぶ is used for topics rather development related. If your tweet contain crossover L10N and development, of course you can use it, too.

<noinclude>[[category:L10n Teams|ja]]</noinclude>

L10n:Teams:ja

2015-08-27T06:01:31Z

Dynamis: /* Active team members */

__NOTOC__

=== Japanese (ja,ja-JP-mac) ===
Team website:
* [http://www.mozilla.jp/community/localization.html Introduction to Japanese L10N Community]

====Active team members====
{| border="1" class="wikitable"
|-
! Name
! Email
! Role
! Desktop OS
! Tablet OS
! Mobile OS
! Hg Access?
! SVN Access?
|-
|ABE Hiroki (hATrayflood)
|<h[DOT]rayflood[AT] gmail[DOT]com>
|browser leader, mail/toolkit peer
|
|
|Android, iOS
|[https://bugzilla.mozilla.org/show_bug.cgi?id=659534 HG]
|
|-
|Masahiko IMANAKA (mar or marsf)
|<chimantaea_mirabilis[AT] yahoo[DOT]co[DOT]jp>
|firefoxos and mail leader, browser/toolkit peer
|
|
|
|[https://bugzilla.mozilla.org/show_bug.cgi?id=401979 CVS/HG]
|[https://bugzilla.mozilla.org/show_bug.cgi?id=775901 SVN]
|-
|Kasaki Nagato
|<nagato[DOT]kasaki[AT] gmail[DOT]com>
|mobile leader
|
|
|iOS
|[https://bugzilla.mozilla.org/show_bug.cgi?id=696693 HG]
|
|-
|Kazuyuki SUZUKI
|<info[AT]kechol[DOT]net>
|firefox os and mobile peer
|
|
|iOS
|
|
|-
|Noritada Shimizu
|<nshimizu[AT] mozilla-japan[DOT]org>
|web l10n leader (webmaster of mozilla.jp)
|Mac (Win on VMWare)
|
|iOS
|
|[https://bugzilla.mozilla.org/show_bug.cgi?id=843403 SVN]
|-
|Tomoya ASAI (dynamis)
|<dynamis[AT] mozilla-japan[DOT]org> (bugmail: <bugzilla[AT] firehacks[DOT]org>, [https://twitter.com/dynamitter @dynamitter], [http://www.facebook.com/dynamis facebook])
|ja locale reviewer
|Mac (Win on VMWare)
|Android, iOS
|Android, Firefox OS
|[https://bugzilla.mozilla.org/show_bug.cgi?id=264931 CVS/HG]
|[https://bugzilla.mozilla.org/show_bug.cgi?id=708537 SVN]
|-
|Mantaroh Yoshinaga
|<mantaroh[AT] mozilla-japan[DOT]org> (bugmail: <mantaroh[AT] mozilla-japan[DOT]org>)
|MDN Translator
|Linux (Windows VM)
|
|
|
|
|}

(Some of members those who only related to [http://www.mozilla.jp/community/translation.html translating documents] are not on the table above, yet.)

====Localizers in training====

====Active projects====
<ul>
<li>Product L10n: 
[https://github.com/mozilla-japan/gecko-l10n gecko-l10n GitHub repo],
[https://github.com/mozilla-japan/gaia-l10n gaia-l10n GitHub repo]</li>
<li>Document Translation: 
[https://github.com/mozilla-japan/translation/issues Translation Request (GitHub issues)],
[https://github.com/mozilla-japan/translation/wiki Translation Wiki]</li>
<li>SUMO: 
[https://support.mozilla.org/ja/localization Mozilla Support - (ja) L10N Dashboard]</li>
<li>MDN: 
[https://dev.mozilla.jp/project/mdnja/ MDN 日本語版 | Mozilla Developer Street (modest)]</li>
<li>Website L10n: 
[https://localize.mozilla.org/ja/ Mozilla Verbatim - Japanese]</li>
<li>Webmaker: 
[https://www.transifex.com/projects/p/webmaker/language/ja/ Mozilla Webmaker | Transifex]</li>
<li>Bugzilla-ja: 
[http://bug-ja.org/ Bugzilla Users Group in JApan]</li>
</ul>

====L10n kit====
''(Please list here the tools your team uses, as well as links to your L10n assets (e.g., translation memories, termbases, style guides, etc.).)''
;Tools:
[https://github.com/mozilla-japan/lot Localization Tools (lot) Script]
;Translation Memory:
;Glossary:
[https://github.com/mozilla-japan/translation/wiki/Mozilla-L10N-Glossary Mozilla L10N Glossary]

[https://github.com/mozilla-japan/translation/wiki/Firefox-OS-Glossary Firefox OS Glossary]
;Style Guide:

====How to join this l10n team====
* Join L10N Mailing list. 

===== Localizing SUpport.MOzilla.org (SUMO) =====
If you want to help localize http://support.mozilla.org/ja into your language, please do the following:
# [https://support.mozilla.org/users/authcontributor Create a SUMO account]
# If you can, [https://support.mozilla.org/groups/japanese-localization get in touch with the Group Leader(s) listed here via a Private Message]. If there is nobody listed there, please get in touch with [http://support.mozilla.org/user/vesper Michał / vesper].
# [https://support.mozilla.org/kb/localize-mozilla-support Read our universal l10n documentation here]. For language-specific documentation, please get in touch with your Group Leader(s).
# [https://support.mozilla.org/forums/l10n-forum/711082 Visit our forums and introduce yourself to the community]. We don’t bite, unless you’re made of cake ;-)
# You're ready to go! If you have any questions, ask them on the forums.


====Team communication====
;Mailing lists:
There are some ML related to L10N/Translation
* [https://groups.google.com/forum/#!forum/mozilla-translations-ja Mozilla Japanese Translation Google Group]
* QA contact of ja L10N is private mailing list of l10n leaders: l10n-qa[AT]mozilla-japan[DOT]org

;Related websites:
* [http://forums.firehacks.org/l10n/ Japanese Localization Forum]
* [https://dev.mozilla.jp/l10n/ L10n documents at modest site]
* [http://www.mozilla-japan.org/jp/l10n/ Project Web Page (almost obsolete)]
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&component=ja,%20ja-JP-mac%20/%20Japanese link to file bug]

;Hashtag in tweets
* someones use hashtags when they mention the topic related to mozilla in Japan: (please add other hashtags if you know)
#もじら, #mozjp, #fxos...
* #もずでぶ is used for topics rather development related. If your tweet contain crossover L10N and development, of course you can use it, too.

<noinclude>[[category:L10n Teams|ja]]</noinclude>

L10n:Teams:ja

2015-07-28T02:37:03Z

Dynamis: update communication ML list

__NOTOC__

=== Japanese (ja,ja-JP-mac) ===
Team website:
* [http://www.mozilla.jp/community/localization.html Introduction to Japanese L10N Community]

====Active team members====
{| border="1" class="wikitable"
|-
! Name
! Email
! Role
! Desktop OS
! Tablet OS
! Mobile OS
! Hg Access?
! SVN Access?
|-
|ABE Hiroki (hATrayflood)
|<h[DOT]rayflood[AT] gmail[DOT]com>
|browser leader, mail/toolkit peer
|
|
|
|[https://bugzilla.mozilla.org/show_bug.cgi?id=659534 HG]
|
|-
|Masahiko IMANAKA (mar or marsf)
|<chimantaea_mirabilis[AT] yahoo[DOT]co[DOT]jp>
|firefoxos and mail leader, browser/toolkit peer
|
|
|
|[https://bugzilla.mozilla.org/show_bug.cgi?id=401979 CVS/HG]
|[https://bugzilla.mozilla.org/show_bug.cgi?id=775901 SVN]
|-
|Kasaki Nagato
|<nagato[DOT]kasaki[AT] gmail[DOT]com>
|mobile leader
|
|
|
|[https://bugzilla.mozilla.org/show_bug.cgi?id=696693 HG]
|
|-
|Kazuyuki SUZUKI
|<info[AT]kechol[DOT]net>
|firefox os and mobile peer
|
|
|
|
|
|-
|Noritada Shimizu
|<nshimizu[AT] mozilla-japan[DOT]org>
|web l10n leader (webmaster of mozilla.jp)
|
|
|
|
|[https://bugzilla.mozilla.org/show_bug.cgi?id=843403 SVN]
|-
|Tomoya ASAI (dynamis)
|<dynamis[AT] mozilla-japan[DOT]org> (bugmail: <bugzilla[AT] firehacks[DOT]org>, [https://twitter.com/dynamitter @dynamitter], [http://www.facebook.com/dynamis facebook])
|ja locale reviewer
|Mac (Win on VMWare)
|Android
|Android, Firefox OS
|[https://bugzilla.mozilla.org/show_bug.cgi?id=264931 CVS/HG]
|[https://bugzilla.mozilla.org/show_bug.cgi?id=708537 SVN]
|-
|Mantaroh Yoshinaga
|<mantaroh[AT] mozilla-japan[DOT]org> (bugmail: <mantaroh[AT] mozilla-japan[DOT]org>)
|MDN Translator
|Linux (Windows VM)
|
|
|
|
|}

(Some of members those who only related to [http://www.mozilla.jp/community/translation.html translating documents] are not on the table above, yet.)

====Localizers in training====

====Active projects====
<ul>
<li>Product L10n: 
[https://github.com/mozilla-japan/gecko-l10n gecko-l10n GitHub repo],
[https://github.com/mozilla-japan/gaia-l10n gaia-l10n GitHub repo]</li>
<li>Document Translation: 
[https://github.com/mozilla-japan/translation/issues Translation Request (GitHub issues)],
[https://github.com/mozilla-japan/translation/wiki Translation Wiki]</li>
<li>SUMO: 
[https://support.mozilla.org/ja/localization Mozilla Support - (ja) L10N Dashboard]</li>
<li>MDN: 
[https://dev.mozilla.jp/project/mdnja/ MDN 日本語版 | Mozilla Developer Street (modest)]</li>
<li>Website L10n: 
[https://localize.mozilla.org/ja/ Mozilla Verbatim - Japanese]</li>
<li>Webmaker: 
[https://www.transifex.com/projects/p/webmaker/language/ja/ Mozilla Webmaker | Transifex]</li>
<li>Bugzilla-ja: 
[http://bug-ja.org/ Bugzilla Users Group in JApan]</li>
</ul>

====L10n kit====
''(Please list here the tools your team uses, as well as links to your L10n assets (e.g., translation memories, termbases, style guides, etc.).)''
;Tools:
;Translation Memory:
;Glossary:
;Style Guide:

====How to join this l10n team====
* Join L10N Mailing list. 

===== Localizing SUpport.MOzilla.org (SUMO) =====
If you want to help localize http://support.mozilla.org/ja into your language, please do the following:
# [https://support.mozilla.org/users/authcontributor Create a SUMO account]
# If you can, [https://support.mozilla.org/groups/japanese-localization get in touch with the Group Leader(s) listed here via a Private Message]. If there is nobody listed there, please get in touch with [http://support.mozilla.org/user/vesper Michał / vesper].
# [https://support.mozilla.org/kb/localize-mozilla-support Read our universal l10n documentation here]. For language-specific documentation, please get in touch with your Group Leader(s).
# [https://support.mozilla.org/forums/l10n-forum/711082 Visit our forums and introduce yourself to the community]. We don’t bite, unless you’re made of cake ;-)
# You're ready to go! If you have any questions, ask them on the forums.


====Team communication====
;Mailing lists:
There are some ML related to L10N/Translation
* [https://groups.google.com/forum/#!forum/mozilla-translations-ja Mozilla Japanese Translation Google Group]
* QA contact of ja L10N is private mailing list of l10n leaders: l10n-qa[AT]mozilla-japan[DOT]org

;Related websites:
* [http://forums.firehacks.org/l10n/ Japanese Localization Forum]
* [https://dev.mozilla.jp/l10n/ L10n documents at modest site]
* [http://www.mozilla-japan.org/jp/l10n/ Project Web Page (almost obsolete)]
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&component=ja,%20ja-JP-mac%20/%20Japanese link to file bug]

;Hashtag in tweets
* someones use hashtags when they mention the topic related to mozilla in Japan: (please add other hashtags if you know)
#もじら, #mozjp, #fxos...
* #もずでぶ is used for topics rather development related. If your tweet contain crossover L10N and development, of course you can use it, too.

<noinclude>[[category:L10n Teams|ja]]</noinclude>

L10n:Teams:ja

2015-07-28T02:30:59Z

Dynamis: update project links

__NOTOC__

=== Japanese (ja,ja-JP-mac) ===
Team website:
* [http://www.mozilla.jp/community/localization.html Introduction to Japanese L10N Community]

====Active team members====
{| border="1" class="wikitable"
|-
! Name
! Email
! Role
! Desktop OS
! Tablet OS
! Mobile OS
! Hg Access?
! SVN Access?
|-
|ABE Hiroki (hATrayflood)
|<h[DOT]rayflood[AT] gmail[DOT]com>
|browser leader, mail/toolkit peer
|
|
|
|[https://bugzilla.mozilla.org/show_bug.cgi?id=659534 HG]
|
|-
|Masahiko IMANAKA (mar or marsf)
|<chimantaea_mirabilis[AT] yahoo[DOT]co[DOT]jp>
|firefoxos and mail leader, browser/toolkit peer
|
|
|
|[https://bugzilla.mozilla.org/show_bug.cgi?id=401979 CVS/HG]
|[https://bugzilla.mozilla.org/show_bug.cgi?id=775901 SVN]
|-
|Kasaki Nagato
|<nagato[DOT]kasaki[AT] gmail[DOT]com>
|mobile leader
|
|
|
|[https://bugzilla.mozilla.org/show_bug.cgi?id=696693 HG]
|
|-
|Kazuyuki SUZUKI
|<info[AT]kechol[DOT]net>
|firefox os and mobile peer
|
|
|
|
|
|-
|Noritada Shimizu
|<nshimizu[AT] mozilla-japan[DOT]org>
|web l10n leader (webmaster of mozilla.jp)
|
|
|
|
|[https://bugzilla.mozilla.org/show_bug.cgi?id=843403 SVN]
|-
|Tomoya ASAI (dynamis)
|<dynamis[AT] mozilla-japan[DOT]org> (bugmail: <bugzilla[AT] firehacks[DOT]org>, [https://twitter.com/dynamitter @dynamitter], [http://www.facebook.com/dynamis facebook])
|ja locale reviewer
|Mac (Win on VMWare)
|Android
|Android, Firefox OS
|[https://bugzilla.mozilla.org/show_bug.cgi?id=264931 CVS/HG]
|[https://bugzilla.mozilla.org/show_bug.cgi?id=708537 SVN]
|-
|Mantaroh Yoshinaga
|<mantaroh[AT] mozilla-japan[DOT]org> (bugmail: <mantaroh[AT] mozilla-japan[DOT]org>)
|MDN Translator
|Linux (Windows VM)
|
|
|
|
|}

(Some of members those who only related to [http://www.mozilla.jp/community/translation.html translating documents] are not on the table above, yet.)

====Localizers in training====

====Active projects====
<ul>
<li>Product L10n: 
[https://github.com/mozilla-japan/gecko-l10n gecko-l10n GitHub repo],
[https://github.com/mozilla-japan/gaia-l10n gaia-l10n GitHub repo]</li>
<li>Document Translation: 
[https://github.com/mozilla-japan/translation/issues Translation Request (GitHub issues)],
[https://github.com/mozilla-japan/translation/wiki Translation Wiki]</li>
<li>SUMO: 
[https://support.mozilla.org/ja/localization Mozilla Support - (ja) L10N Dashboard]</li>
<li>MDN: 
[https://dev.mozilla.jp/project/mdnja/ MDN 日本語版 | Mozilla Developer Street (modest)]</li>
<li>Website L10n: 
[https://localize.mozilla.org/ja/ Mozilla Verbatim - Japanese]</li>
<li>Webmaker: 
[https://www.transifex.com/projects/p/webmaker/language/ja/ Mozilla Webmaker | Transifex]</li>
<li>Bugzilla-ja: 
[http://bug-ja.org/ Bugzilla Users Group in JApan]</li>
</ul>

====L10n kit====
''(Please list here the tools your team uses, as well as links to your L10n assets (e.g., translation memories, termbases, style guides, etc.).)''
;Tools:
;Translation Memory:
;Glossary:
;Style Guide:

====How to join this l10n team====
* Join L10N Mailing list. 

===== Localizing SUpport.MOzilla.org (SUMO) =====
If you want to help localize http://support.mozilla.org/ja into your language, please do the following:
# [https://support.mozilla.org/users/authcontributor Create a SUMO account]
# If you can, [https://support.mozilla.org/groups/japanese-localization get in touch with the Group Leader(s) listed here via a Private Message]. If there is nobody listed there, please get in touch with [http://support.mozilla.org/user/vesper Michał / vesper].
# [https://support.mozilla.org/kb/localize-mozilla-support Read our universal l10n documentation here]. For language-specific documentation, please get in touch with your Group Leader(s).
# [https://support.mozilla.org/forums/l10n-forum/711082 Visit our forums and introduce yourself to the community]. We don’t bite, unless you’re made of cake ;-)
# You're ready to go! If you have any questions, ask them on the forums.


====Team communication====
;Mailing lists:
There are some ML related to L10N
* [https://lists.mozilla.org/listinfo/dev-mdc-ja Discussion mailing list for Mozilla Developer Center Japanese (ja)]
* [https://groups.google.com/forum/?hl=ja#!forum/seamonkey-ja SeaMonkey-ja (product specific)]
* Discussions about L10N sometimes take place among the members in Community ML, community[AT]mozilla-japan[DOT]org. (To be a member, you need to be approved by admin)

;Related websites:
* [http://forums.firehacks.org/l10n/ Japanese Localization Forum]
* [https://dev.mozilla.jp/l10n/ L10n documents at modest site]
* [http://www.mozilla-japan.org/jp/l10n/ Project Web Page (almost obsolete)]
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&component=ja,%20ja-JP-mac%20/%20Japanese link to file bug]

;Hashtag in tweets
* someones use hashtags when they mention the topic related to mozilla in Japan: (please add other hashtags if you know)
#もじら, #mozjp, #fxos...
* #もずでぶ is used for topics rather development related. If your tweet contain crossover L10N and development, of course you can use it, too.

<noinclude>[[category:L10n Teams|ja]]</noinclude>

L10n:Teams:ja

2014-10-14T06:26:57Z

Dynamis: /* Active team members */

L10n:Teams:ja

2014-04-25T01:51:56Z

Dynamis: /* Team communication */

L10n:Teams:ja

2014-04-23T06:59:04Z

Dynamis: /* Active team members */

L10n:Teams:ja

2014-04-23T06:58:27Z

Dynamis: /* Active team members */

B2G/Roadmap

2014-04-01T09:27:22Z

Dynamis: s/FireFox/Firefox/

This is an overview of the current Firefox OS product roadmap. '''Information on this page is subject to frequent updates and changes.'''

== Feature Complete Dates ==

'''FC''' means Feature Complete. At this date, a development package is made available to chipset and hardware manufacturers to stabilize the release for productization.

* '''FxOS 1.2''' Feature Complete date: September 15, 2013 [completed]
* '''FxOS 1.3''' Feature Complete date: December 9, 2013 [completed]
* '''FxOS 1.4''' Feature Complete date: April 25, 2014 [in progress]
* '''FxOS 2.0''' Feature Complete date: July 21, 2014 [planning]
* '''FxOS 2.1''' Feature Complete date: Oct 21, 2014 [planning]
* '''FxOS 2.2''' Feature Complete date: Jan 2, 2015 [TBD]

'''Disclaimer''': Future Feature Complete dates are subject to change, based on changes in commercialization and business demands.

The current planning is to continue with FxOS releases every 12 weeks, aligned with the Firefox/Gecko release trains. At any given time master is open for feature development and in parallel converging one release for productization.

== Feature Backlog ==

We maintain a public backlog [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AtVT90hlMtdSdEd4TVVjWXNfU3ctMlVhWFRrWkpweVE#gid=39] of features for Firefox OS. Our engineering community of Mozilla engineers, partner engineers and contributors pick and prioritize features from this backlog. To propose additions to the backlog, please contact ''ffos-product@mozilla.org''.

== Upcoming Releases ==

For each of our upcoming releases, we have defined a selection of focus areas which highlight expected product features and enhancements. The team is confident many of the features in these focus areas will make the feature complete dates for each respective release. However, it is possible that the set of features that land at the end of a release cycle can be impacted by market/partner demand.

See also [[Release Management/B2G Landing]]

== Key 2.0 Focus Areas ==

'''WebRTC'''
* Deploy user facing Loop (WebRTC real-time) service Meta {{Bug|971986}}
* User-facing app/integration for Mobile Meta {{Bug|972003}}
* Platform support Meta {{bug|750011}}

'''System Front-End'''
* Vertical Homescreen Enhancements Meta {{bug|989848}}
* Haida: Visual Refresh
** Visual changes will be managed by each of the functional teams below
* Sheets Performance
** Edge Gestures {{Bug|918792}}
** Edge Gesture Tutorial Outside of First Time Experience (FTE) {{bug|939174}}
** Add Edge Gestures to FTE tutorial {{bug|924624}}
*Haida: Work will begin on the following additional components. Inclusion in the release to be based on successful user testing.
** Rocketbar Meta {{bug|946452}}
** Browser Integration into System Meta {{Bug|945259}}
** Universal Search and Navigation Meta {{Bug|946452}}
** Updated Systems Tray and Notifications Meta {{Bug|959722}}
** Bookmark Migration from Browser to Homescreen {{Bug|945827}}
** Explanation of Bookmark Migration {{Bug|938279}}
** Settings Drawer {{Bug|924586}}
** Settings Drawer tutorial {{Bug|924626}}

'''Media'''
* Ringtone creation/management
** Ringtones: Create a ringtone from an audio file downloaded from the browser {{Bug|960333}}
** Ringtones: Assign new ringtones using songs in the Music app {{Bug|960329}}
** Ringtones: Crop an audio file when creating a ringtone {{Bug|960335}}
** Ringtones: Delete ringtones that I do not want anymore {{Bug|960331}}
** Ringtones: Add/replace 'FxOS signature’ ringtones to default set of ringtones Bug #TBD

'''Platform'''
* NFC use cases
** NFC: NFC sharing of contacts Meta {{Bug|894676}}
** NFC: NFC sharing of Image/video content {{Bug|894320}}
** NFC: NFC sharing (URL) {{Bug|894678}}
** NFC: Daemon modifications for supporting Tap2pay {{bug|989889}}

'''Services:'''
* Firefox Accounts
** Firefox Accounts on FxOS {{Bug|941723}}
* Find My Device
** Find My Device: Locate my Phone {{Bug|941268}}
** Find My Device: Lock-screen {{Bug|945889}}, {{Bug|948612}}
** Find My Device: Remote wipe {{Bug|941289}}
** Find My Device: Play a sound {{Bug|941280}}
** Find My Device: Location tracking {{Bug|941273}}
* FxA and Marketplace - subset of Meta {{Bug|941723}}

'''Productivity'''
* Visual Refresh
** OS Visual Refresh - subset of Meta {{Bug|930561}}
* Email Enhancements
** Outbox and Asynchronous Sending {{Bug|921050}}
** Address Auto Complete From Address Book {{bug|989809}}
** Quick-to-Top action {{bug|989810}}

'''System Platform'''
*Keyboard
** Text Selection {{Bug|921965}}
** Cut/Copy/Paste {{Bug|747798}}
* Lockscreen: Visual Refresh
** Lockscreen Visual Refresh {{Bug|950884}}

'''Communications'''
* Visual Refresh
** OS Visual Refresh - subset of Meta {{Bug|930561}}
* Dialer
** Call Log: Call directly from call log {{Bug|920011}}

'''Performance/Metrics'''
* Performance Phase 1
** Improve Home Screen swipe {{Bug|979396}}
** Improve APZC Kinetic scrolling {{Bug|962278}}
** Perceived performance improvements Meta {{Bug|989590}}
* Metrics phase 2 {{Bug|982663}}

=== Partner Contribution 2.0 Features ===
The list of features below are contributed by our ecosystem partners as well as the Mozilla community. Many of these features will land in the v2.0 release, however, for any features that don't make the feature landing date, they will land in our next release.

* System: Offline Error handling improvements Meta {{bug|930630}}
* Communications: Single Variant SIM Card Customization Improvements Meta {{bug|980301}}

== Past Releases + Complete Features ==

=== 1.4 Features ===

'''Dual Sim Dual Standby (DSDS)'''

* DSDS: Support delivery reports {{bug|919977}} [DONE]
* DSDS: Manage FDN list for both SIMs {{bug|921971}} [DONE]
* DSDS: STK menu and events management {{bug|934404}} [DONE]
* DSDS: Correct Subscription {{bug|975918}} [DONE]
* DSDS: On-the-fly SIM change when calling {{bug|946866}} [DONE]
* DSDS: Display receiving SIM on call screen {{bug|946874}} [DONE]
* DSDS: Call Log shows which SIM was involved in call {{bug|947131}} [DONE]
* DSDS: Send message via default SIM {{bug|947139}} [DONE]
* DSDS: Long tap to send message {{bug|947140}} [DONE]
* DSDS: Message notification informs of SIM {{bug|947180}} [DONE]
* DSDS: Calling from Contact Details {{bug|947186}} [DONE]
* DSDS: Long tap on contacts details to choose SIM {{bug|947189}} [DONE]
* DSDS: Show STK app icons {{bug|951599}} [DONE]
* DSDS: Settings: Edit PIN2 and PUK2 {{bug|947907}} [DONE]
* DSDS: Enter PIN and PUK for both SIMs {{bug|948575}} [DONE]
* DSDS: Edit PIN1 and PUK1 for both SIMs {{bug|948584}} [DONE]

'''LTE/CDMA/Networking Support'''
* LTE: LTE Support {{bug|951764}}, {{bug|952026}} [DONE]
* CDMA: Support 3-way conference calls {{bug|881174}} [DONE]
* IPv6 Support {{bug|957917}} [DONE]

'''Communications'''
* Messages: Support delivery reports {{bug|919977}} [DONE]

=== 1.4 Features - Partner Contribution ===
The list of features below were contributed by our ecosystem partners as well as the Mozilla community.

'''Communications (Dialer, SMS, Contacts)'''

* Support MMS message with Subject {{bug|885680}}, {{bug|885679}} [DONE]
* SMS Message Concatenation Bug # TBD [DONE]
* Prevent SMS wrong concatenation function {{bug|945089}}
* Recipient suggestion list improvement for SMS/MMS {{bug|959018}} [DONE], {{bug|963043}}
* Reading (Phonetic) field support {{bug|936386}}, {{bug|909224}}
* Sort and search by reading field {{bug|936386}}, {{bug|909224}}
* Japan disaster/emergency support {{bug|956220}} [DONE]
* Roaming of GSM/UMTS/(3GPP):text coding (UCS2/GSM7bit) Bug # TBD [DONE]
* Three-way calling (CDMA {{bug|881174}}) (GSM Bugs: {{bug|887680}}, {{bug|887686}}, {{bug|887764}} -- [DONE]
* Support deleting multiple contacts {{bug|956219}}
* Sending pre-defined message during call reject {{bug|959011}}
* Send MMS to Email {{bug|840515}}, {{bug|866938}}
'''Device, RIL, BT, LBS, etc..'''
* Tethering APN {{bug|961571}}, {{bug|960865}} [DONE]
* The Cell Broadcast Message is not saved in DB and is not managed by List {{bug|960498}}
* 369 Character Encoding Setting is not supported. S-JIS support for Message {{bug|958445}}
* System: Advanced Offline Error handling improvements Sub of meta{{bug|930630}}
* Support for Shift-JIS decoding of SMS in CDMA {{bug|958445}} -- [DONE]

'''Media (Camera, Music, Video, etc)'''
* Battery popup in video {{bug|959511}}
* Add Crop option when setting wallpaper from Gallery {{bug|883028}}
* Navigate using Prev and Next controls while playing a video {{bug|951025}}
* Selection of multiple images from Gallery to share via MMS {{bug|929027}}
* Support for more than 5 MP image size in gallery {{bug|956014}}
* Camera settings and configuration Meta{{bug|965438}}
* Camera: Add zoom functionality {{bug|933902}}
* Camera: Add face tracking capability {{bug|966828}}
* Camera: Support for continuous auto focus {{bug|966829}}
* Camera: Add touch focus to the camera {{bug|966830}}
* Camera: Add camera resolution to the camera settings {{bug|966831}}
* Camera: Add video resolution to camera settings {{bug|966832}}
* Camera: Add white balance support in camera {{bug|966834}}
* Camera: Add HDR to camera settings {{bug|966835}}
* Camera: Set ISO mode to auto {{bug|966836}}
* Camera: Add self-timer to camera settings {{bug|966837}}
* Camera: Flash mode options while recording video {{bug|966838}}
* Camera: Add frame grid to camera settings {{bug|966839}}
* Camera: Battery status while taking pictures or recording a video {{bug|966841}}

'''Productivity (Email, Calendar, Clock)'''
* Select ringtones from music for Clock app {{bug|959020}}
* Select multiple recipients for email {{bug |904635}}
* Multiple Contact Selection Screen for SMS, Email application {{bug|950644}}
* Can receive image, audio and video are supported. pdf and other types files are not supported {{bug|825318}}

=== 1.3 Features ===

* Browser: Removal of About page in Browser [https://bugzilla.mozilla.org/show_bug.cgi?id=903690 903690] -- [DONE]

* Device: Multiple Bluetooth file transfers [https://bugzilla.mozilla.org/show_bug.cgi?id=921085 921085] -- [DONE]
* Device BlueDroid porting [https://bugzilla.mozilla.org/show_bug.cgi?id=876583 876583] -- [DONE]

* Email: POP3 support [https://bugzilla.mozilla.org/show_bug.cgi?id=916080 916080], [https://bugzilla.mozilla.org/show_bug.cgi?id=916083 916083], [https://bugzilla.mozilla.org/show_bug.cgi?id=916088 916088] -- [DONE]

* Communications: MMS/SMS Enhancements {{bug|919966}}, {{bug|919995}} -- [DONE]
* Communications: Support MMS message with Subject {{bug|19966}} -- [DONE]
* Communications: Send MMS message to Email address {{bug|840515}} -- [DONE]
* Communications: Call Ended message {{bug|920414}} -- [DONE]
* Communications: DSDS Import contacts from each SIM at a time {{bug|923629}} -- [DONE]
* Communications: Datastore API Support {{bug|918827}} -- [DONE]
* Communications: Emergency Call {{bug|956220}} -- [DONE]
* Communications: Save message draft Meta{{bug|879143}} -- [DONE]
* Communications: Automatic switch SMS to MMS Send with Subject {{bug|885680}}, {{bug|885679}} -- [DONE]
* Communications: Forward Message feature is not supported {{bug|919995}} -- [DONE]
* Communications: FFOS Does not support the confirmation message popup when you change the PIN1 or unlock PIN1 {{bug|881957}} -- [DONE]
* Communications: Gallery Performance {{bug|889728}}, {{bug|841579}} -- [DONE]

* Graphics: Asynchronous Panning/Zooming in Apps and Web Content [https://bugzilla.mozilla.org/show_bug.cgi?id=909877 909877] -- [DONE]
* Graphics: WebGL improvements (gralloc) [https://bugzilla.mozilla.org/show_bug.cgi?id=883437 883437] -- [DONE]
* Graphics: Enable Azure content for b2g [https://bugzilla.mozilla.org/show_bug.cgi?id=914984 914984] -- [DONE]

* Media: Access to music controls in notifications tray [https://bugzilla.mozilla.org/show_bug.cgi?id=902981 902981] -- [DONE]
* Media: Access to music controls when screen is locked [https://bugzilla.mozilla.org/show_bug.cgi?id=891024 891024] -- [DONE]
* Media: Enable continuous autofocus on camera [https://bugzilla.mozilla.org/show_bug.cgi?id=925192 925192] -- [DONE]
* Media: Add flash capability to camera [https://bugzilla.mozilla.org/show_bug.cgi?id=925215 925215] -- [DONE]
* Media: Arrange content in the gallery app [https://bugzilla.mozilla.org/show_bug.cgi?id=925179 925179] -- [DONE]
* Media: Display file information for the content shown in the gallery app [https://bugzilla.mozilla.org/show_bug.cgi?id=925216 925216] -- [DONE]

* Multimedia Platform: Use speakerphone with FM radio app [https://bugzilla.mozilla.org/show_bug.cgi?id=863098 863098], [https://bugzilla.mozilla.org/show_bug.cgi?id=929960 929960], [https://bugzilla.mozilla.org/show_bug.cgi?id=854753 854753] -- [DONE]

* NFC: NFC Pairing [https://bugzilla.mozilla.org/show_bug.cgi?id=894672 894672] -- [DONE]
* NFC: Reading from NFC tags [https://bugzilla.mozilla.org/show_bug.cgi?id=894323 894323] -- [DONE]
* NFC: NFC API [https://bugzilla.mozilla.org/show_bug.cgi?id=894689 894689] -- [DONE]

* Performance: Performanc: Scrolling FPS, Latencies [https://bugzilla.mozilla.org/show_bug.cgi?id=915068 915068], [https://bugzilla.mozilla.org/show_bug.cgi?id=915064 915064] -- [DONE]

* RIL: EAP-SIM [https://bugzilla.mozilla.org/show_bug.cgi?id=920933 920933], [https://bugzilla.mozilla.org/show_bug.cgi?id=920936 920936], [https://bugzilla.mozilla.org/show_bug.cgi?id=920939 920939] -- [DONE]
* RIL:DSDS Settings [https://bugzilla.mozilla.org/show_bug.cgi?id=938422 938422], [https://bugzilla.mozilla.org/show_bug.cgi?id=927764 927764], [https://bugzilla.mozilla.org/show_bug.cgi?id=926347 926347],[https://bugzilla.mozilla.org/show_bug.cgi?id=926350 926350],[https://bugzilla.mozilla.org/show_bug.cgi?id=926352 926352],[https://bugzilla.mozilla.org/show_bug.cgi?id=926351 926351],[https://bugzilla.mozilla.org/show_bug.cgi?id=938440 938440],[https://bugzilla.mozilla.org/show_bug.cgi?id=921980 921980],[https://bugzilla.mozilla.org/show_bug.cgi?id=918558 918558], [https://bugzilla.mozilla.org/show_bug.cgi?id=923629 923629],[https://bugzilla.mozilla.org/show_bug.cgi?id=926342 926342] --[DONE]

* RTSP: Support rtsp streaming framework [https://bugzilla.mozilla.org/show_bug.cgi?id=831645 831645]-- [DONE]
* RTSP: Support RTP/RTCP via UDP/IP and RTSP via TCP/IP [https://bugzilla.mozilla.org/show_bug.cgi?id=940539 940539] -- [DONE]
* RTSP: "RTSP-Teardown” message [https://bugzilla.mozilla.org/show_bug.cgi?id=940544 940544] -- [DONE]
* RTSP: RTSP support for absolute and relative control URLs [https://bugzilla.mozilla.org/show_bug.cgi?id=940552 940552] -- [DONE]

* System: Engineering mode [https://bugzilla.mozilla.org/show_bug.cgi?id=925673 925673] -- [DONE]
* System: Haida: Replaceable Homescreen prototype [https://bugzilla.mozilla.org/show_bug.cgi?id=898330 898330] -- [DONE]

* Systems Front-End: Add Marketplace and Installed Apps to E.Me search results [https://bugzilla.mozilla.org/show_bug.cgi?id=881063 881063] --[DONE]

* System Platform: Keyboard visual update [https://bugzilla.mozilla.org/show_bug.cgi?id=929361 929361] -- [DONE]

* UX: UX: Visual refresh phase 1 '''Headers:''' [https://bugzilla.mozilla.org/show_bug.cgi?id=92529 92529], '''Status bar:''' [https://bugzilla.mozilla.org/show_bug.cgi?id=925930 925930] -- [DONE]

=== 1.2 Features ===

* Bluetooth: A2DP ([https://bugzilla.mozilla.org/show_bug.cgi?id=892162 892162]) -- [DONE]
* Bluetooth: AVRCP ([https://bugzilla.mozilla.org/show_bug.cgi?id=892164 892164], [https://bugzilla.mozilla.org/show_bug.cgi?id=892165 892165]) -- [DONE]

* Browser: Enhanced responsiveness/rendering ([https://bugzilla.mozilla.org/show_bug.cgi?id=894923 894923], [https://bugzilla.mozilla.org/show_bug.cgi?id=894939 894939], [https://bugzilla.mozilla.org/show_bug.cgi?id=894954 894954]) -- [DONE]

* Communication: Redial last number ([https://bugzilla.mozilla.org/show_bug.cgi?id=887488 887488], [https://bugzilla.mozilla.org/show_bug.cgi?id=887545 887545]) -- [DONE]
* Communication: Bluetooth contacts sharing ([https://bugzilla.mozilla.org/show_bug.cgi?id=887534 887534], [https://bugzilla.mozilla.org/show_bug.cgi?id=887488 887663]) -- [DONE]
* Communication: Contact export to USIM ([https://bugzilla.mozilla.org/show_bug.cgi?id=887673 887673]) -- [DONE]
* Communication: Export Contact to media card ([https://bugzilla.mozilla.org/show_bug.cgi?id=887776 887776]) -- [DONE]
* Communication: Fixed dialing number (FDN) support ([https://bugzilla.mozilla.org/show_bug.cgi?id=888902 888902], [https://bugzilla.mozilla.org/show_bug.cgi?id=888912 888912], [https://bugzilla.mozilla.org/show_bug.cgi?id=888919 888919]) -- [DONE]
* Communication: Conference calling ([https://bugzilla.mozilla.org/show_bug.cgi?id=887680 887680], [https://bugzilla.mozilla.org/show_bug.cgi?id=887686 887686], [https://bugzilla.mozilla.org/show_bug.cgi?id=887764 887764]) -- [DONE]
* Communication: Silent SMS ([https://bugzilla.mozilla.org/show_bug.cgi?id=816564 816564]) -- [DONE]
* Communication: Improvements to contact import ([https://bugzilla.mozilla.org/show_bug.cgi?id=887783 887783], [https://bugzilla.mozilla.org/show_bug.cgi?id=894851 894851]) -- [DONE]
* Communication: Improvements to incoming call design ([https://bugzilla.mozilla.org/show_bug.cgi?id=887802 887802]) -- [DONE]
* Communication: MMI code improvements (CLIP, CLIR, Call Barring, Call on Hold, Call waiting) ([https://bugzilla.mozilla.org/show_bug.cgi?id=891345 891345], [https://bugzilla.mozilla.org/show_bug.cgi?id=892498 892498], [https://bugzilla.mozilla.org/show_bug.cgi?id=894871 894871], [https://bugzilla.mozilla.org/show_bug.cgi?id=893727 893727], [https://bugzilla.mozilla.org/show_bug.cgi?id=833754 833754], [https://bugzilla.mozilla.org/show_bug.cgi?id=890831 890831], [https://bugzilla.mozilla.org/show_bug.cgi?id=890912 890912], [https://bugzilla.mozilla.org/show_bug.cgi?id=897441 897441]) -- [DONE]

* DNT: three-state setting ([https://bugzilla.mozilla.org/show_bug.cgi?id=900434 900434]) -- [DONE]

* Email: message body format improvements (bug TBD based on UX input) -- [DONE]

* Graphics/Audio: Microphone API ([https://bugzilla.mozilla.org/show_bug.cgi?id=894848 894848]) -- [DONE]

* Media: Music player status on homescreen ([https://bugzilla.mozilla.org/show_bug.cgi?id=891014 891014]) -- [DONE]
* Media: Speaker out for FM radio ([https://bugzilla.mozilla.org/show_bug.cgi?id=854753 854753]) -- [DONE]
* Media: Additional file info display in Video player ([https://bugzilla.mozilla.org/show_bug.cgi?id=902995 902995]) -- [DONE]

* Productivity: Email notifications ([https://bugzilla.mozilla.org/show_bug.cgi?id=892519 892519], [https://bugzilla.mozilla.org/show_bug.cgi?id=892521 892521], [https://bugzilla.mozilla.org/show_bug.cgi?id=892522 892522], [https://bugzilla.mozilla.org/show_bug.cgi?id=892523 892523]) -- [DONE]
* Productivity: Email sync internal settings ([https://bugzilla.mozilla.org/show_bug.cgi?id=892518 892518]) -- [DONE]
* Productivity: Email support for audio & video attachments ([https://bugzilla.mozilla.org/show_bug.cgi?id=838007 838007],[https://bugzilla.mozilla.org/show_bug.cgi?id=838008 838008]) -- [DONE]

* RIL: Basic CDMA support ([https://bugzilla.mozilla.org/show_bug.cgi?id=869778 869778], [https://bugzilla.mozilla.org/show_bug.cgi?id=874841 874841], [https://bugzilla.mozilla.org/show_bug.cgi?id=890325 890325], [https://bugzilla.mozilla.org/show_bug.cgi?id=890330 890330], [https://bugzilla.mozilla.org/show_bug.cgi?id=890807 890807], [https://bugzilla.mozilla.org/show_bug.cgi?id=890809 890809], [https://bugzilla.mozilla.org/show_bug.cgi?id=890814 890814], [https://bugzilla.mozilla.org/show_bug.cgi?id=890816 890816], [https://bugzilla.mozilla.org/show_bug.cgi?id=890819 890819], [https://bugzilla.mozilla.org/show_bug.cgi?id=890820 890820], [https://bugzilla.mozilla.org/show_bug.cgi?id=890822 890822], [https://bugzilla.mozilla.org/show_bug.cgi?id=890823 890823], [https://bugzilla.mozilla.org/show_bug.cgi?id=890825 890825], [https://bugzilla.mozilla.org/show_bug.cgi?id=890826 890826], [https://bugzilla.mozilla.org/show_bug.cgi?id=890827 890827], [https://bugzilla.mozilla.org/show_bug.cgi?id=890828 890828]) -- [DONE]
* RIL: OMA CP ([https://bugzilla.mozilla.org/show_bug.cgi?id=815554 815554]) -- [DONE]
* RIL: WAP Push ([https://bugzilla.mozilla.org/show_bug.cgi?id=891253 891253]) -- [DONE]
* RIL: SIMTK improvements

* Settings: CE: Audio volume warning ([https://bugzilla.mozilla.org/show_bug.cgi?id=891687 891687]) -- [DONE]
* Settings: Keyboard IME framework ([https://bugzilla.mozilla.org/show_bug.cgi?id=891678 891678]) -- [DONE]

* System: Multi-resolution support (WVGA, qHD) ([https://bugzilla.mozilla.org/show_bug.cgi?id=891685 891685]) -- [DONE]
* System: Customization management ([https://bugzilla.mozilla.org/show_bug.cgi?id=891723 891723], [https://bugzilla.mozilla.org/show_bug.cgi?id=891724 891724], [https://bugzilla.mozilla.org/show_bug.cgi?id=891725 891725], [https://bugzilla.mozilla.org/show_bug.cgi?id=892938 892938]) -- [DONE]
* System: Closing/replacing notifications ([https://bugzilla.mozilla.org/show_bug.cgi?id=892528 892528], [https://bugzilla.mozilla.org/show_bug.cgi?id=892530 892530]) -- [DONE]

* Wifi/hybrid aGPS positioning

MozCampAsia2012/Holding Firefox OS Hackathon

2012-10-26T10:57:13Z

Dynamis:

'''Holding Firefox OS Hackathon''':

'''Facilitator(s)''': [https://mozillians.org/en-US/tomoya Tomoya Asai]

'''Are you paid or volunteer staff?''': paid

'''Area of Contribution (Team Name)''': developer evangelism, technical marketing

'''How are you currently involved with the community?''': Managing developer community site in Japan, Holding Workshops, Leader of Japanese Localization, Finding and supporting contributers

'''Location of Work (where do you reside?)''': Tokyo

'''Talk Length (please choose between 30, 60, 90, 120 minutes)''': 30min. (or 60min)

'''Summary''': I'll talk what you need to prepare for Firefox OS Hackathon. I'll show short tutorial including some demos to show how easy to customize Firefox OS (it's the most easy OS to hack!). I'll share sample hacks, best practices and case studies from our Hackathon.

note: We'll hold Firefox OS Hackathon in Japan with Tizen community and web designer community on 11/03 (and once more before mozcamp?). To make more people think easy to hack Firefox OS, our main target audience are web designers, not experienced web developers.

'''How your session furthers the MozCamp [https://wiki.mozilla.org/MozCampAsia2012/Tracks Goals]''': being able to hold Firefox OS hackathon in your community. You can get more contributers and fans of our platform through hackathon you hold.

'''Expected Outcome or Deliverable''': More Firefox OS Hackathon in other Asian countries based on our case study.

'''Desired Audience Type or Skill-set''': web developer, developer community leader

'''Equipment Needs (Video projector already included)''': -

--------------------------------------------------------------------

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:

MozCampAsia2012/Holding Firefox OS Hackathon

2012-10-26T10:56:26Z

Dynamis:

'''Holding Firefox OS Hackathon''':

'''Facilitator(s)''': [https://mozillians.org/en-US/tomoya Tomoya Asai]

'''Are you paid or volunteer staff?''': paid

'''Area of Contribution (Team Name)''': developer evangelism, technical marketing

'''How are you currently involved with the community?''': Managing developer community site in Japan, Holding Workshops, Leader of Japanese Localization, Finding and supporting contributers

'''Location of Work (where do you reside?)''': Tokyo

'''Talk Length (please choose between 30, 60, 90, 120 minutes)''': 30min. (or 60min)

'''Summary''': I'll talk what you need to prepare for Firefox OS Hackathon. I'll show short tutorial including some demos to show how easy to customize Firefox OS (it's the most easy OS to hack!). I'll share sample hacks, best practice and case study from our Hackathon.

note: We'll hold Firefox OS Hackathon in Japan with Tizen community and web designer community on 11/03 (and once more before mozcamp?). To make more people think easy to hack Firefox OS, our main target audience are web designers, not experienced web developers.

'''How your session furthers the MozCamp [https://wiki.mozilla.org/MozCampAsia2012/Tracks Goals]''': being able to hold Firefox OS hackathon in your community. You can get more contributers and fans of our platform through hackathon you hold.

'''Expected Outcome or Deliverable''': More Firefox OS Hackathon in other Asian countries based on our case study.

'''Desired Audience Type or Skill-set''': web developer, developer community leader

'''Equipment Needs (Video projector already included)''': -

--------------------------------------------------------------------

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:

MozCampAsia2012/Holding Firefox OS Hackathon

2012-10-26T10:52:27Z

Dynamis:

'''Holding Firefox OS Hackathon''':

'''Facilitator(s)''': [https://mozillians.org/en-US/tomoya Tomoya Asai]

'''Are you paid or volunteer staff?''': paid

'''Area of Contribution (Team Name)''': developer evangelism, technical marketing

'''How are you currently involved with the community?''': Managing developer community site in Japan, Holding Workshops, Leader of Japanese Localization, Finding and supporting contributers

'''Location of Work (where do you reside?)''': Tokyo

'''Talk Length (please choose between 30, 60, 90, 120 minutes)''': 30min. (or 60min)

'''Summary''': I'll talk what you need to prepare for Firefox OS Hackathon. I'll show short tutorial including some demos to show how easy to customize Firefox OS (it's the most easy OS to hack!). I'll share sample hacks, best practice and case study from our Hackathon.

note: We'll hold Firefox OS Hackathon in Japan with Tizen community and web designer community on 11/03 (and once more?). To make more people think easy to hack Firefox OS, our main target audience are web designers, not experienced web developers.

'''How your session furthers the MozCamp [https://wiki.mozilla.org/MozCampAsia2012/Tracks Goals]''': being able to hold Firefox OS hackathon in your community. You can get more contributers and fans of our platform through hackathon you hold.

'''Expected Outcome or Deliverable''': More Firefox OS Hackathon in other Asian countries based on our case study.

'''Desired Audience Type or Skill-set''': web developer, developer community leader

'''Equipment Needs (Video projector already included)''': -

--------------------------------------------------------------------

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:

MozCampAsia2012/Holding Firefox OS Hackathon

2012-10-26T10:48:15Z

Dynamis:

'''Holding Firefox OS Hackathon''':

'''Facilitator(s)''': Tomoya Asai

'''Are you paid or volunteer staff?''': paid

'''Area of Contribution (Team Name)''': developer evangelism, technical marketing

'''How are you currently involved with the community?''': Managing developer community site in Japan, Holding Workshops, Leader of Japanese Localization, Finding and supporting contributers

'''Location of Work (where do you reside?)''': Tokyo

'''Talk Length (please choose between 30, 60, 90, 120 minutes)''': 30min. (or 60min)

'''Summary''': I'll talk what you need to prepare for Firefox OS Hackathon. I'll show short tutorial including some demos to show how easy to customize Firefox OS (it's the most easy OS to hack!). I'll share sample hacks, best practice and case study from our Hackathon.

note: We'll hold Firefox OS Hackathon in Japan with Tizen community and web designer community on 11/03 (and once more?). To make more people think easy to hack Firefox OS, our main target audience are web designers, not experienced web developers.

'''How your session furthers the MozCamp [https://wiki.mozilla.org/MozCampAsia2012/Tracks Goals]''': being able to hold Firefox OS hackathon in your community. You can get more contributers and fans of our platform through hackathon you hold.

'''Expected Outcome or Deliverable''': More Firefox OS Hackathon in other Asian countries based on our case study.

'''Desired Audience Type or Skill-set''': web developer, developer community leader

'''Equipment Needs (Video projector already included)''': -

--------------------------------------------------------------------

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:

MozCampAsia2012/Holding Firefox OS Hackathon

2012-10-26T10:47:43Z

Dynamis:

'''Holding Firefox OS Hackathon''':

'''Facilitator(s)''': Tomoya Asai

'''Are you paid or volunteer staff?''': paid

'''Area of Contribution (Team Name)''': developer evangelism, technical marketing

'''How are you currently involved with the community?''': Managing developer community site in Japan, Holding Workshops, Leader of Japanese Localization, Finding and supporting contributers

'''Location of Work (where do you reside?)''': Tokyo

'''Talk Length (please choose between 30, 60, 90, 120 minutes)''': 30min.

'''Summary''': I'll talk what you need to prepare for Firefox OS Hackathon. I'll show short tutorial including some demos to show how easy to customize Firefox OS (it's the most easy OS to hack!). I'll share sample hacks, best practice and case study from our Hackathon.

note: We'll hold Firefox OS Hackathon in Japan with Tizen community and web designer community on 11/03 (and once more?). To make more people think easy to hack Firefox OS, our main target audience are web designers, not experienced web developers.

'''How your session furthers the MozCamp [https://wiki.mozilla.org/MozCampAsia2012/Tracks Goals]''': being able to hold Firefox OS hackathon in your community. You can get more contributers and fans of our platform through hackathon you hold.

'''Expected Outcome or Deliverable''': More Firefox OS Hackathon in other Asian countries based on our case study.

'''Desired Audience Type or Skill-set''': web developer, developer community leader

'''Equipment Needs (Video projector already included)''': -

--------------------------------------------------------------------

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:

MozCampAsia2012/Holding Firefox OS Hackathon

2012-10-26T10:46:59Z

Dynamis:

'''Holding Firefox OS Hackathon''':

'''Facilitator(s)''': Tomoya Asai

'''Are you paid or volunteer staff?''': paid

'''Area of Contribution (Team Name)''': developer evangelism, technical marketing

'''How are you currently involved with the community?''': Managing developer community site in Japan, Holding Workshops, Leader of Japanese Localization, Finding and supporting contributers

'''Location of Work (where do you reside?)''': Tokyo

'''Talk Length (please choose between 30, 60, 90, 120 minutes)''': 30min.

'''Summary''': I'll talk what you need to prepare for Firefox OS Hackathon. I'll show short tutorial including some demos to show how easy to customize Firefox OS (it's the most easy OS to hack!). I'll share sample hacks, best practice and case study from our Hackathon.

note: We'll hold Firefox OS Hackathon in Japan on 11/03 (and once more?). To make more people think easy to hack Firefox OS, our main target audience are web designers, not experienced web developers.

'''How your session furthers the MozCamp [https://wiki.mozilla.org/MozCampAsia2012/Tracks Goals]''': being able to hold Firefox OS hackathon in your community. You can get more contributers and fans of our platform through hackathon you hold.

'''Expected Outcome or Deliverable''': More Firefox OS Hackathon in other Asian countries based on our case study.

'''Desired Audience Type or Skill-set''': web developer, developer community leader

'''Equipment Needs (Video projector already included)''': -

--------------------------------------------------------------------

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:

MozCampAsia2012/Schedule/appsandb2g

2012-10-26T10:43:21Z

Dynamis: /* Proposed Sessions */

[[Category:MozCampAsia2012]]
==Proposed Sessions==

* [[MozCampAsia2012/r2d2b2g_ftw| R2D2B2G FTW]] - Jeff Griffiths
* [[MozCampAsia2012/firefoxos_apps_technical| Technical Resources for Firefox OS and Marketplace (Apps)]] - Desigan Chinniah
* [[MozCampAsia2012/ZeroToApp]] From Zero to App - An Open Web Apps Adventure! - Potch
* [https://wiki.mozilla.org/MozCampAsia2012/Schedule/FirefoxOsLaunch Firefox OS launch]
* [[MozCampAsia2012/insight_gaia|Insight Gaia]] - Tim Chien, Evelyn Hung
* [[MozCampAsia2012/Security_in_Firefox_OS|Security in Firefox OS]] - Paul Theriault
* [[MozCampAsia2012/Marketing my amazing apps|What Apps Should I Build for the FireFox Marketplace and How Can I Best Market Them?]] - Diana Livits
* [[MozCampAsia2012/Functional_testing_B2G_apps|Functional/Introduction to automated testing B2G apps using Marionette]] - Zac Campbell
* [[MozCampAsia2012/I_Reject_Because_I_Care|I Reject Because I Care: Resetting expectations of the app review process]] - Lisa Brewster
* [[MozCampAsia2012/How_to_build_quality_open_web_apps|How to build quality web apps]] - David Burns
* [[MozCampAsia2012/How_to_User_Test_Your_App|How to User Test Your App]] - Jennifer Morrow
* <s>[[MozCampAsia2012/B2G_Localization|B2G Localization]] - Stas Malolepszy</s> (merged into [[ MozCampAsia2012/l10n_sprint|Localization sprint for b2g]])
* [[MozCampAsia2012/Firefox_OS_Support_Article_Sprint|Firefox OS Support Article Sprint]] - Michael Verdi & David Tenser
* [[MozCampAsia2012/Anatomy_of_an_App|Anatomy of an Open Web App--and How to Create Your Own Today ]] - r1cky and tofumatt
* [[MozCampAsia2012/mozilla_indonesia_community_local_app|Firefox OS Local App To Support Mozilla Indonesia Community ]] - Finan Akbar & Jemmy
* [[ MozCampAsia2012/Flicks_2013_Firefox_OS|Our global short film contest for Firefox OS - Firefox Flicks 2013]] - Tobias Leingruber
* [[ MozCampAsia2012/l10n_sprint|Localization sprint for b2g]] - Dwayne Bailey
* [[MozCampAsia2012/firefoxOS_brand_workshop|Firefox OS Brand Workshop]] - Greg Jost
* [[MozCampAsia2012/ShippingFirefoxOS|Shipping Firefox OS, and How You Can Help]] - Dietrich Ayala
* [[MozCampAsia2012/FirefoxOS-hacking-lounge|Firefox OS hacking lounge]] - William Reynolds
* [[MozCampAsia2012/apps-hacking-lounge|Apps Hacking Lounge]] - Amy Tsay
* [[MozCampAsia2012/apps-show-and-tell|Apps Show & Tell]] - Amy Tsay
* [[MozCampAsia2012/apps_dissected|Apps Dissected - APIs as Awesome Sauce!]] - Harald Kirschner
* [[MozCampAsia2012/Holding_Firefox_OS_Hackathon|Holding Firefox OS Hackathon]] - Tomoya Asai

MozCampAsia2012/Holding Firefox OS Hackathon

2012-10-26T10:41:30Z

Dynamis: create the proposal page

'''Holding Firefox OS Hackathon''':

'''Facilitator(s)''': Tomoya Asai

'''Are you paid or volunteer staff?''': paid

'''Area of Contribution (Team Name)''': developer evangelism, technical marketing

'''How are you currently involved with the community?''': Managing developer community site in Japan, Holding Workshops, Leader of Japanese Localization, Finding and supporting contributers

'''Location of Work (where do you reside?)''': Tokyo

'''Talk Length (please choose between 30, 60, 90, 120 minutes)''': 30min.

'''Summary''': I'll talk what you need to prepare for Firefox OS Hackathon. I'll show short tutorial including some demos to show how easy to customize Firefox OS (it's the most easy OS to hack!). I'll share sample hacks, best practice and case study from our Hackathon.

note: We'll hold Firefox OS Hackathon in Japan on 11/03. To make more people think easy to hack Firefox OS, our main target audience are web designers, not experienced web developers.

'''How your session furthers the MozCamp [https://wiki.mozilla.org/MozCampAsia2012/Tracks Goals]''': being able to hold Firefox OS hackathon in your community. You can get more contributers and fans of our platform through hackathon you hold.

'''Expected Outcome or Deliverable''': More Firefox OS Hackathon in other Asian countries based on our case study.

'''Desired Audience Type or Skill-set''': web developer, developer community leader

'''Equipment Needs (Video projector already included)''': -

--------------------------------------------------------------------

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:

L10n:Teams:ja

2012-05-23T19:13:42Z

Dynamis: /* Japanese (ja,ja-JP-mac) */

=== Japanese (ja,ja-JP-mac) ===
[https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&component=ja,%20ja-JP-mac%20/%20Japanese file bug]

* [http://forums.firehacks.org/l10n/ Japanese Localization Forum]
* [https://dev.mozilla.jp/l10n/ L10n documents at modest site]
* [http://www.mozilla-japan.org/jp/l10n/ Project Web Page (almost obsolate)]

; browser leader, mail/toolkit peer : ABE Hiroki (hATrayflood) (hATrayflood) <h[DOT]rayflood[AT]gmail[DOT]com>- [https://bugzilla.mozilla.org/show_bug.cgi?id=659534 HG access: YES]
; mail leader, browser/toolkit peer : Masahiko IMANAKA (mar or marsf) <chimantaea_mirabilis[AT]yahoo[DOT]co[DOT]jp> - [https://bugzilla.mozilla.org/show_bug.cgi?id=401979 CVS/HG access: YES]
; mobile leader : Kasaki Nagato <nagato[DOT]kasaki[AT]gmail[DOT]com>- [https://bugzilla.mozilla.org/show_bug.cgi?id=696693 HG access: YES]

; ja locale reviewer: Tomoya ASAI (dynamis) <dynamis[AT]mozilla-japan[DOT]org> (bugmail: <bugzilla[AT]firehacks[DOT]org>, [https://twitter.com/dynamitter @dynamitter], [http://www.facebook.com/dynamis facebook]) - [https://bugzilla.mozilla.org/show_bug.cgi?id=264931 CVS/HG access: YES]

; peer : Atsushi SAKAI <dev-null[AT]hotmail[DOT]co[DOT]jp> - [https://bugzilla.mozilla.org/show_bug.cgi?id=401978 CVS/HG access: YES]
; peer : KOZAWA Hidehiro <kozawa[AT]mozilla[DOT]gr[DOT]jp> - [https://bugzilla.mozilla.org/show_bug.cgi?id=282337 CVS access: YES]

<noinclude>[[category:L10n Teams|ja]]</noinclude>

L10n:Teams:ja

2012-05-23T19:12:24Z

Dynamis: /* Japanese (ja,ja-JP-mac) */

=== Japanese (ja,ja-JP-mac) ===
[https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&component=ja,%20ja-JP-mac%20/%20Japanese file bug]

* [http://forums.firehacks.org/l10n/ Japanese Localization Forum]
* [https://dev.mozilla.jp/l10n/ L10n documents at modest site]
* [http://www.mozilla-japan.org/jp/l10n/ Project Web Page (almost obsolate)]

; browser leader, mail/toolkit peer : ABE Hiroki (hATrayflood) (hATrayflood) <h[DOT]rayflood[AT]gmail[DOT]com>- [https://bugzilla.mozilla.org/show_bug.cgi?id=659534 HG access: YES]
; mail leader, browser/toolkit peer : Masahiko IMANAKA (mar or marsf) <chimantaea_mirabilis[AT]yahoo[DOT]co[DOT]jp> - [https://bugzilla.mozilla.org/show_bug.cgi?id=401979 CVS/HG access: YES]
; mobile leader : Kasaki Nagato <nagato[DOT]kasaki[AT]gmail[DOT]com>- [https://bugzilla.mozilla.org/show_bug.cgi?id=696693 HG access: YES]

; ja locale reviewer: Tomoya ASAI (dynamis) <dynamis[AT]mozilla-japan[DOT]org> (bugmail: <bugzilla[AT]firehacks[DOT]org>, [https://twitter.com/dynamitter @dynamitter], [http://www.facebook.com/dynamis facebook]) - [https://bugzilla.mozilla.org/show_bug.cgi?id=264931 CVS access: YES]

; peer : Atsushi SAKAI <dev-null[AT]hotmail[DOT]co[DOT]jp> - [https://bugzilla.mozilla.org/show_bug.cgi?id=401978 CVS/HG access: YES]
; peer : KOZAWA Hidehiro <kozawa[AT]mozilla[DOT]gr[DOT]jp> - [https://bugzilla.mozilla.org/show_bug.cgi?id=282337 CVS access: YES]

<noinclude>[[category:L10n Teams|ja]]</noinclude>

L10n:Teams:ja

2012-05-07T08:48:43Z

Dynamis: /* Japanese (ja,ja-JP-mac) */

=== Japanese (ja,ja-JP-mac) ===
[https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&component=ja,%20ja-JP-mac%20/%20Japanese file bug]

* [http://forums.firehacks.org/l10n/ Japanese Localization Forum]
* [https://dev.mozilla.jp/l10n/ L10n documents at modest site]
* [http://www.mozilla-japan.org/jp/l10n/ Project Web Page (almost obsolate)]

; browser leader, mail/toolkit peer : ABE Hiroki (hATrayflood) (hATrayflood) <h[DOT]rayflood[AT]gmail[DOT]com>- [https://bugzilla.mozilla.org/show_bug.cgi?id=659534 HG access: YES]
; mail leader, browser/toolkit peer : Masahiko IMANAKA (mar or marsf) <chimantaea_mirabilis[AT]yahoo[DOT]co[DOT]jp> - [https://bugzilla.mozilla.org/show_bug.cgi?id=401979 CVS/HG access: YES]
; mobile leader : Kasaki Nagato <nagato[DOT]kasaki[AT]gmail[DOT]com>- [https://bugzilla.mozilla.org/show_bug.cgi?id=696693 HG access: YES]

; ja locale reviewer: Tomoya ASAI (dynamis) <dynamis[AT]mozilla-japan[DOT]org> (bugmail: <bugzilla@firehacks.org>) - [https://bugzilla.mozilla.org/show_bug.cgi?id=264931 CVS access: YES]

; peer : Atsushi SAKAI <dev-null[AT]hotmail[DOT]co[DOT]jp> - [https://bugzilla.mozilla.org/show_bug.cgi?id=401978 CVS/HG access: YES]
; peer : KOZAWA Hidehiro <kozawa[AT]mozilla[DOT]gr[DOT]jp> - [https://bugzilla.mozilla.org/show_bug.cgi?id=282337 CVS access: YES]

<noinclude>[[category:L10n Teams|ja]]</noinclude>

Websites/Domain List/http

2012-04-18T09:15:39Z

Dynamis: adding some domains for mozilla japan

* abp.mozilla-hispano.org
* accessfirefox.org
* addon.mozilla.org
* addons.allizom.org
* addons-cdn.mozilla.net
* addons-dev.allizom.org
* addons-dev-cdn.allizom.org
* addons-dev-proxy.allizom.org
* add-ons.mozilla.com
* addons.mozilla.com
* addons.mozilla.jp
* addons.mozilla.org
* addons-nl.stage.mozilla.com
* addons-origin.allizom.org
* addons-stage.allizom.org
* addons-stage-proxy.allizom.org
* addons.update.mozilla.org
* addons-updater.allizom.org
* affiliates-admin.mozilla.org
* affiliates.allizom.org
* affiliates-cdn.allizom.org
* affiliates-cdn.mozilla.org
* affiliates-dev.allizom.org
* affiliates.mozilla.org
* africa.mozilla.org
* air.allizom.org
* air-dev.allizom.org
* air.mozilla.com
* air.mozilla.org
* allizom.org
* ams.mozilla.com
* ankeena.mozilla.org
* apps.allizom.org
* apps-dev.allizom.org
* apps.mozillalabs.com
* appstatus.mozilla.com
* appstore.mozillalabs.com
* arabicmozilla.org
* archive.mozilla.org
* archive.quality.mozilla.org
* archive-sfx.spreadfirefox.com
* arecibo1.dmz.phx1.mozilla.com
* arecibo1.dmz.sjc1.mozilla.com
* arecibo.mozilla.org
* arecibo-phx.mozilla.org
* arecibo-sjc.mozilla.org
* arewefastyet.com
* arewefirstyet.com
* arewefunyet.com
* arewemobileyet.com
* areweprettyyet.com
* areweslimyet.com
* arewesmallyet.com
* ar.start3.mozilla.com
* artzilla.org
* ar.www.mozilla.com
* asia.mozilla.org
* aurora.mozilla.org
* aus01.zlb.phx.mozilla.net
* aus02.zlb.phx.mozilla.net
* aus03.zlb.phx.mozilla.net
* aus2.mozilla.org
* aus2.mozilla.osuosl.org
* aus2-staging.mozilla.org
* aus2-static.mozilla.org
* aus2-test.mozilla.org
* aus3.mozilla.org
* aus4-dev.allizom.org
* aus.mozilla.org
* aus.mozilla.osuosl.org
* auth.services.mozilla.com
* authstage.mozilla.com
* aviary.pl
* banners.mozilla-europe.org
* basket-dev.allizom.org
* basket.mozilla.com
* bb.mozillazine-tr.org
* bespin.mozilla.com
* bespin.mozillalabs.com
* bespin.mozilla.org
* bespinplugins.mozillalabs.com
* beta.mozilla.org
* bg.www.mozilla.com
* bg.www.mozillamessaging.com
* bgzilla.org
* blocker-reports.brasstacks.mozilla.com
* blog.allizom.org
* blog-dev.allizom.org
* blog.frenchmozilla.fr
* blog.getfirebug.allizom.org
* blog.getfirebug.com
* blog.getfirebug-dev.allizom.org
* blog.lizardwrangler.com
* blog-lizardwrangler-dev.allizom.org
* blog.local.getfirebug.com
* blog.mozilla.com
* blog.mozilladanmark.dk
* blog.mozillafoundation.org
* blog.mozillaonline.com
* blog.mozilla.org
* blog.php5stage.mozilla.com
* blogs.mozilla.com
* blogs.mozilla-europe.org
* blogs.mozilla-japan.org
* blogs.mozillamessaging.com
* boardwiki.mozilla.org
* bonjourmozilla.fr
* bonsai.mozilla.org
* bonsai-www.mozilla.org
* bounceradmin.mozilla.com
* brasstacks.mozilla.com
* browserchoice.mozilla.com
* browserchoice-mpt.mozilla.com
* browserchoice.stage.mozilla.com
* browserid.org
* browserquest.mozilla.org
* bugs.mozilla.org
* bugzilla-cluster.mozilla.org
* bugzilla-eu.mozilla.org
* bugzilla.mozilla.org
* bugzilla.mozilla.osuosl.org
* bugzilla.org
* builder-addons.allizom.org
* builder-addons-dev.allizom.org
* builder.addons.mozilla.org
* builder-addons-next.allizom.org
* builder.mozillalabs.com
* build-graphs.mozilla.org
* build.mozillamessaging.com
* butterapp.com
* byob.mozilla.com
* byob.mozilla.org
* bzr.mozilla.org
* caminobrowser.jp
* caminobrowser.org
* camp-firefox.de
* careers.mozilla.com
* careers.mozilla.org
* caseconductor.allizom.org
* ca.www.mozilla.com
* ccm.mozillaes.org
* chat.mozillamessaging.com
* chat-support.mozilla.com
* chat.support.mozilla.com
* chilemoz.org
* china-start.mozilla.net
* ci.mozilla.org
* college.mozilla.com
* college.stage.mozilla.com
* community-store.authstage.mozilla.com
* communitystore.mozilla.org
* confluence1.webapp.phx1.mozilla.com
* confluence1.webapp.sjc1.mozilla.com
* contribute.mozilla.org
* crash-analysis.mozilla.com
* crash-reports.allizom.org
* crash-reports.mozilla.com
* crash-stacks.mozilla.com
* crash-stats.allizom.org
* crashstats.mozilla.com
* crash-stats.mozilla.com
* crash-stats.mozilla.org
* creative.mozilla.com
* creative.mozilla.org
* cs.start3.mozilla.com
* cs.www.mozilla.com
* czilla.cz
* da.add-ons.mozilla.com
* da.trunk.mozillamessaging.com
* da.www.mozilla.com
* de.add-ons.mozilla.com
* demoparty.mozillalabs.com
* demos.allizom.org
* demos-dev.allizom.org
* demos.hacks.mozilla.org
* demos.mozilla.org
* design-challenge.mozilla.com
* design-challenge.mozillalabs.com
* design-challenge.mozilla.org
* designchallenges.org
* despot.mozilla.org
* de.start2.mozilla.com
* de.start3.mozilla.com
* detodosparatodos.org
* devedge-temp.mozilla.org
* developer-admin.mozilla.org
* developer.mozilla.com
* developer.mozilla.org
* developer.mozilla.osuosl.org
* developer-stage9.mozilla.org
* developer-test.mozilla.org
* devmo.dekiwiki.mozilla.org
* devmo.developer.mozilla.org
* dev.mozilla.jp
* de.www.mozilla.com
* de.www.mozillamessaging.com
* directory.mozilla.org
* discovershiretoko.org
* dm-cms02.nslb.sj.mozilla.com
* dm-download02.mozilla.org
* dm-download-lb.mozilla.org
* dm-ftp01.mozilla.org
* dnt.mozilla.org
* docs.services.mozilla.com
* doctor.mozilla.com
* doctor.mozilla.org
* donate.mozilla.org
* do-not-add.mozilla.org
* download-cdnetworks.mozilla.net
* downloadcounter.sj.mozilla.com
* download-eu.mozilla.org
* downloadmap.mozilla.org
* download.mozilla.org
* download-speed-test.mozilla.net
* download-stats.mozilla.com
* downloadstats.mozilla.com
* downloadstats.mozilla.org
* dromaeo.com
* drumbeat.org
* dxr.lanedo.com
* dxr.mozilla.org
* dyna-crashreports.nslb.sj.mozilla.com
* ecmascript.org
* education.mozilla.org
* eklentiler.mozillazine-tr.org
* el.start3.mozilla.com
* el.www.mozilla.com
* en-gb.google.mozilla.com
* en-gb.start2.mozilla.com
* en-gb.start3.mozilla.com
* en-gb.start.mozilla.com
* en-gb.www.mozilla.com
* en-gb.www.mozillamessaging.com
* en-us.add-ons.mozilla.com
* en-us.fxfeeds.mozilla.com
* en-us.google.mozilla.com
* en-us.malware-error.mozilla.com
* en-us.start2.mozilla.com
* en-us.start3.mozilla.com
* en-us.start.mozilla.com
* en-us.www.mozilla.com
* en-us.www.mozillamessaging.com
* en.www.mozilla.com
* es-ar.start3.mozilla.com
* es-ar.www.mozilla.com
* es-cl.www.mozilla.com
* es-es.start2.mozilla.com
* es-es.start3.mozilla.com
* es-es.www.mozilla.com
* es-es.www.mozillamessaging.com
* etherpad.mozilla.com
* etherpad.mozilla.org
* et.start3.mozilla.com
* europe.mozilla.org
* euro-surveys.php5stage.mozilla.com
* evangelism.dekiwiki.mozilla.org
* eyeballs.mozilla.org
* events.mozilla-europe.org
* extendfirefox.com
* extensions.mozilla.org
* extranet.mozilla.org
* f1.mozillamessaging.com
* facebook.addons.mozilla.org
* fastestfirefox.com
* fastestfirefox.mozilla.com
* fa.www.mozilla.com
* fa.www-trunk.stage.mozilla.com
* feedback.mozillalabs.com
* feedback.mozilla.org
* feedhouse.mozillazine.org
* feeds.mozilla.com
* feeds.mozilla-hispano.org
* feeds.mozilla.org
* feeds.spreadfirefox.com
* festival.mozilla.org
* filer.mozilladanmark.dk
* firefoxccstudio.org
* firefox.cl
* firefox.co.il
* firefox.com.cn
* firefox.com
* firefoxfestival.com
* firefoxflicks.com
* firefoxflicks.mozilla.org
* firefox.hu
* firefoxlive.mozilla.org
* firefox.no
* firefoxnote.jp
* firefox.org.il
* firefoxparty.authstage.mozilla.com
* firefoxtshirt.mozilla.org
* firefoxtweetmachine.com
* fi.start3.mozilla.com
* fi.www.mozilla.com
* foxkeh.jp
* foxkeh.com
* foxkeh.net
* foxkeh.org
* fortunes.frenchmozilla.fr
* fortunes.frenchmozilla.org
* forum.addons.mozilla.org
* forum.mozilladanmark.dk
* forum.mozillazine-tr.org
* forums.addons.mozilla.org
* forums.mozilla.org
* forums.mozillazine.jp
* forums.mozillazine.org
* forums-test.mozillazine.org
* foundationwiki.mozilla.org
* foxkeh.com
* fr.add-ons.mozilla.com
* frenchmozilla.fr
* frenchmozilla.net
* frenchmozilla.org
* fr.fxfeeds.mozilla.com
* fr.start2.mozilla.com
* fr.start3.mozilla.com
* fr.www.mozilla.com
* fr.www.mozillamessaging.com
* fxfeeds.mozilla.com
* fxfeeds.mozilla-japan.org
* fxfeeds.mozilla.org
* fxfeeds.mozilla.osuosl.org
* fxfeeds.mozillazine.org
* gaming.mozillalabs.com
* ganglia.mozilla.org
* geckozone.org
* getfirebug.allizom.org
* getfirebug.com
* getfirebug-dev.allizom.org
* getfirefox.com
* getfirefox.jp
* getpersonas-cdn.mozilla.net
* getpersonas.com
* getthunderbird.com
* getthunderbird.jp
* g-fox.cn
* gfx.tw
* gitmirror.mozilla.org
* glowfx4.mozilla.com
* glowfx4.mozilla.org
* glow.mozilla.com
* glow.mozilla.org
* graphite1.dmz.phx1.mozilla.com
* graphite1.dmz.sjc1.mozilla.com
* graphite.mozilla.org
* graphite-phx.mozilla.org
* graphite-sjc.mozilla.org
* graphs.allizom.org
* graphs.mozilla.org
* graphs-new.mozilla.org
* graphs-stage2.mozilla.org
* graphs-stagedb.allizom.org
* graphs-testdb.allizom.org
* gslb-stage.mozilla-europe.org
* gs.mozillamessaging.com
* guides.mozilla.org
* gu-in.www-trunk.stage.mozilla.com
* hackasaurus.org
* hacks.mozilla.org
* handler-test.mozilla.org
* hardhat.mozilla.net
* heatmap.mozillalabs.com
* hendrix.mozilla.org
* hg.ecmascript.org
* hg.frenchmozilla.fr
* hg.mozilla-hispano.org
* hg.mozilla.org
* hgpvt.mozilla.org
* hg_trunk.frenchmozilla.fr
* hu.start3.mozilla.com
* hu.www.mozilla.com
* identity.mozilla.com
* id.www.mozilla.com
* images.spreadfirefox.com
* input.allizom.org
* input-dev.allizom.org
* input.firefox.com
* input.mozilla.com
* input.mozilla.org
* interforest.org
* interns.mozilla.com
* intlstore.mozilla.org
* intranet.mozilla.org
* inventory-django.mozilla.org
* inventory.mozilla.org
* inventory.phx1.mozilla.com
* ipv6.mozilla.com
* ipv6.mozilla.org
* irc.mozilla.org
* ispdb.mozillamessaging.com
* it.add-ons.mozilla.com
* it.fxfeeds.mozilla.com
* itisatrap.allizom.org
* itisatrap-dev.allizom.org
* it.start2.mozilla.com
* it.start3.mozilla.com
* it.start.mozilla.com
* it.www.mozilla.com
* ja-jp-mac.start.mozilla.com
* ja-jpm.start.mozilla.com
* ja.start2.mozilla.com
* ja.start3.mozilla.com
* ja.start.mozilla.com
* jenkins1.dmz.phx1.mozilla.com
* jetpackgallery.mozillalabs.com
* jetpack.mozillalabs.com
* jetpack.stage.mozilla.com
* join.mozilla.org
* jp-nii01.mozilla.org
* jp-nii02.mozilla.org
* kb.mozillazine.org
* kildare.stage.mozilla.com
* ko.add-ons.mozilla.com
* ko.start.mozilla.com
* krakenbenchmark.mozilla.com
* krakenbenchmark.mozilla.org
* kubla.mozilla.com
* kubla.mozillaonline.com
* kuma-stage.mozilla.org
* l10n-dev.allizom.org
* l10n.mozilla.org
* l10n-stage-sj.mozilla.org
* labs.mozilla.com
* labs.mozilla.org
* labs.stage.mozilla.com
* landfill.addons.allizom.org
* landfill.bugzilla.org
* landfill.mozilla.org
* latam.mozilla.org
* ldap.mozilla.org
* learningfreedomandtheweb.org
* library.mozilla.org
* lists.mozilla-europe.org
* lists.mozilla.org
* litmus.mozilla.org
* live.mozillamessaging.com
* livingdocs.org
* localize.mozilla.org
* longimanus.requin.jmsp.net
* lt.fxfeeds.mozilla.com
* lvscluster.mozilla.org
* lxr.mozilla.org
* m.addons.mozilla.org
* mail.mozillaes.net
* mail.mozilla.org
* malware-error.mozilla.com
* malware-report.mozilla.com
* mana.allizom.org
* mana.mozilla.org
* marketplace.mozilla.org
* markup.mozilla.org
* master.support.mozilla.com
* messaging.php5stage.mozilla.com
* metrics-collector.mozilla.com
* metrics-collector.php5stage.mozilla.com
* metrics.mozilla.com
* m.firefox.com
* mhafai.com
* m.input.allizom.org
* m.input-dev.allizom.org
* m.input.mozilla.com
* mobile.support.mozilla.com
* moff.mozilla.com
* moz10.mozilla.org
* mozbrowser.nl
* mozcom-cdn.mozilla.net
* mozdev.org
* mozilla24.com
* mozilla24.jp
* mozilla-algeria.org
* mozilla.am
* mozilla-antarctica.org
* mozilla-ar.org
* mozilla.ba
* mozilla-belgium.org
* mozillabolivia.org
* mozillabrasil.org.br
* mozillacamp.org
* mozilla.cat
* mozillacolombia.org
* mozilla.com.cn
* mozilla.com
* mozilla.cz
* mozilladanmark.dk
* mozilla.de
* mozillademos.org
* mozillaecuador.org
* mozilla-eg.org
* mozillaes.net
* mozillaes.org
* mozilla-europe.org
* mozillaeurope.org
* mozillafestival.org
* mozillafoundation.org
* mozilla.fsf.hu
* mozilla-ghana.org
* mozilla.gr.jp
* mozilla-hispano.org
* mozilla-hr.org
* mozillaignite.org
* mozillaindia.org
* mozillaireland.org
* mozillaitalia.it
* mozilla-japan.org
* mozilla.jp
* mozilla-kenya.org
* mozilla-kosovo.org
* mozillalabs.com
* mozillalinks.org
* mozilla.lk
* mozilla.lt
* mozilla.ma
* mozillamemory.org
* mozillamessaging.com
* mozilla-mexico.org
* mozilla.mk
* mozilla.net
* mozilla-nl.org
* mozillaonline.com
* mozillaonline.stage.mozilla.com
* mozillaonline-trunk.stage.mozilla.com
* mozillaopennews.org
* mozilla.org
* mozilla.org.il
* mozilla.org.tr
* mozilla.org.ua
* mozilla.org.uk
* mozilla.or.kr
* mozillaparaguay.org
* mozillaparty-archive.mozilla.com
* mozilla.pe
* mozillaphilippines.org
* mozillapl.org
* mozillapopcorn.org
* mozilla.pt
* mozilla.ro
* mozilla-russia.org
* mozilla-senegal.org
* mozillaservice.org
* mozilla.si
* mozilla.sk
* mozilla-srbija.org
* mozilla.status.net
* mozilla-tunisia.org
* mozilla-uk.org
* mozilla-uruguay.org
* mozillavenezuela.org
* mozilla.web.id
* mozillazine-fr.org
* mozillazine.hu
* mozillazine.jp
* mozillazine.org
* mozillazine-tr.org
* mozillians.allizom.org
* mozillians-dev.allizom.org
* mozillians.org
* mozilla-mexico.net
* mozillaitalia.org
* mozmill-archive.brasstacks.mozilla.com
* mozmill-crowd.brasstacks.mozilla.com
* mozmill-release.brasstacks.mozilla.com
* mozsecworld.allizom.org
* mozsecworld-dev.allizom.org
* moztw.org
* mpl.mozilla.org
* mrepo.3ti.be
* mrepo.localdomain
* mware.socorro.stage.webapp.sjc1.mozilla.com
* mxr.mozilla.org
* myapps.mozillalabs.com
* mzl.la
* narro-dev.allizom.org
* nb-no.www.mozilla.com
* newsfx.spreadfirefox.com
* nightly.mozilla.org
* nl.start3.mozilla.com
* nl.www.mozilla.com
* noc.mozillamessaging.com
* noise.addons.mozilla.org
* old.drumbeat.org
* onebillionplusyou.com
* onemozilla.org
* openbadges.org
* opentimetable.jp
* opentochoice.org
* operationfx.authstage.mozilla.com
* ostats.mozilla.com
* outage-org.nslb.sj.mozilla.com
* outages.mozilla.com
* outgoing.mozilla.org
* pastebin.mozilla.org
* pastebin-stage.mozilla.org
* people.mozilla.com
* people.mozilla.org
* personas.stage.mozilla.com
* pfs2.mozilla.org
* pfs2.stage.mozilla.com
* pfs.mozilla.org
* pfs.stage.mozilla.com
* phish-error.mozilla.com
* phish-report.mozilla.com
* phonebook.mozilla.org
* pj-mirror01.mozilla.org
* places-stats.mozilla.com
* planet.bugzilla.org
* planet.drumbeat.org
* planet.firefox.com
* planet.mozilla.de
* planet.mozillamessaging.com
* planet.mozillaonline.com
* planet.mozilla.org
* planet.mozillazine.org
* planet.universalsubtitles.org
* planet.webmademovies.org
* pl.start2.mozilla.com
* pl.start3.mozilla.com
* plugins.mozilla.org
* pl.www.mozilla.com
* popcornjs.org
* popcornmaker.mozilla.org
* pp-proxy02.phx.mozilla.net
* preview.addons.mozilla.org
* preview.apps.mozilla.org
* prism.mozilla.com
* prism.mozillalabs.com
* proyectonave.es
* pt-br.start3.mozilla.com
* pt-br.www.mozilla.com
* pt-br.www-trunk.stage.mozilla.com
* pto-dev.allizom.org
* pto.mozilla.org
* pt-pt.start3.mozilla.com
* pt-pt.www.mozilla.com
* publicsuffix.org
* pulse.mozilla.org
* pv-mirror01.mozilla.org
* quality.allizom.org
* quality-dev.allizom.org
* quality.mozilla.org
* razem.mozilla.org
* recluse.mozilla.org
* releases.mozilla.com
* releases.mozillaonline.com
* releases.mozilla.org
* reporter.mozilla.org
* reporter-test.mozilla.org
* reps.mozilla.org
* rockyourfirefox.com
* ro.www.mozilla.com
* rsvp.authstage.mozilla.com
* rsvp.mozilla.com
* rt1.dmz.sjc1.mozilla.com
* ru.start3.mozilla.com
* ru.www.mozilla.com
* s3.mozillamessaging.com
* seamonkey-project.org
* seamonkeyproject.org
* securityquiz.facebook.mozilla.com
* securitywiki.mozilla.org
* services.addons.mozilla.org
* services.mozilla.com:443
* services.mozilla.com
* services.stage.mozilla.com
* serviceweek.mozilla.org
* sfxdown.mozilla.com
* sfx-images.mozilla.org
* sheriff.allizom.org
* sheriff-dev.allizom.org
* sheriff.mozilla.org
* sheriffs.mozilla.org
* sjc.mozilla.com
* sk.www.mozilla.com
* snippetsadm.internal.phx1.mozilla.com
* snippets.mozilla.com
* snippet-stats.mozilla.org
* socorro-mware-zlb.webapp.phx1.mozilla.com
* soiree.mozilla-europe.org
* sorbzilla.de
* spark.mozilla.org
* spreadfirefox.com
* spreadfirefox.jp
* spreadthunderbird.com
* spreadthunderbird.org
* stage.mozilla.com
* stage.mozillamessaging.com
* start.mozilla.org
* static.addons.mozilla.net
* static.developer-stage9.mozilla.net
* static.kuma-stage.mozilla.net
* static.mozilla.com
* stats-proxy.php5stage.mozilla.com
* status.mozilla.com
* store.mozilla.com
* store.mozilla.org
* studentreps.mozilla.org
* studentreps.stage.mozilla.com
* sub1.test1.bugzilla.mozilla.org
* sub1.test2.bugzilla.mozilla.org
* sub2.test1.bugzilla.mozilla.org
* summit.mozilla.org
* sumo-cdn.3crowd.mozilla.net
* sumo-cdn.mozilla.net
* support.allizom.org
* support-dev.allizom.org
* support.live.mozillamessaging.com
* support.mozilla.com
* support.mozillamessaging.com
* support.mozilla.org
* support-release.allizom.org
* support-stage.mozilla.com
* support-stage.mozilla.org
* support-stage-new.mozilla.com
* support-stage-new.mozilla.org
* support-trunk.php5stage.mozilla.com
* survey.mozilla.com
* survey.php5stage.mozilla.com
* surveys.mozilla-europe.org
* surveys.mozilla.org
* survey.stage.mozilla.com
* svn.mozilla.org
* sv-se.start3.mozilla.com
* sv-se.www.mozilla.com
* symbols.mozilla.org
* talkback.mozilla.org
* talkback-public.mozilla.org
* talkback-reports.mozilla.org
* tbpl-dev.allizom.org
* tbpl.mozilla.org
* tcm.oddsites.net
* test1.bugzilla.mozilla.org
* test2.bugzilla.mozilla.org
* testpilot.mozillalabs.com
* testswarm.com
* theband.mozillalabs.com
* themes.mozilla.org
* thetree.mozilla.org
* th.start3.mozilla.com
* thunderbird-mail.de
* th.www.mozilla.com
* ticker.mozilla.org
* tinderbox.mozilla.org
* tomoshibi.mozilla.jp
* tools.mozilla.com
* tree.mozilla.org
* tr.start3.mozilla.com
* trunk.mozillamessaging.com
* trunk.stage.mozilla.com
* trunk.support.mozilla.org
* tr.www.mozilla.com
* tr.www.mozillamessaging.com
* twittercollage.allizom.org
* twittercollage.mozilla.org
* twitterparty.mozilla.org
* ubiquity.mozilla.com
* update.mozilla.org
* updater.allizom.org
* updates.mozilla.org
* userpanel.mozilla.com
* userpanel.stage.mozilla.com
* ux.firefox.com
* v6wiki.mozilla.org
* versioncheck.addons.mozilla.org
* videos-cdn.mozilla.net
* videos.mozilla.org
* videos-origin.mozilla.org
* video.spreadfirefox.com
* videotest.spreadfirefox.com
* viewvc.svn.mozilla.org
* virtual-bzorg.mozilla.org
* virtualpark.mozilla.org
* virtual-reporter.mozilla.org
* virtual-sfx.mozilla.org
* virtual-store.mozilla.org
* virtual-survey.mozilla.com
* webfwd.org
* webifyme.allizom.org
* webifyme-dev.allizom.org
* webifyme.org
* weblogs.mozillazine.org
* webmademovies.org
* website-archive.mozilla.org
* websitearchive.mozilla.org
* website-beta.bugzilla.org
* website-beta.mozilla.org
* webtools.mozilla.org
* weeklyupdates.mozillacloud.org
* wiki.frenchmozilla.fr
* wiki.mozilladanmark.dk
* wiki.mozilla-japan.org
* wiki.mozilla.org
* womoz.org
* worldfirefoxday.stage.mozilla.com
* www.mozilla.jp
* www-archive.mozilla.org
* www-dev.allizom.org
* www-fx4.mozilla.com
* www-mozilla-com.glb.mozilla.com
* www-stage.mozilla.com
* www-stage.mozillafoundation.org
* www-stage.mozilla.org
* www-stage-old.mozilla.com
* www-stage.seamonkey-project.org
* www-stage.seamonkeyproject.org
* www-trunk.stage.mozilla.com
* xulfr.org
* zhcn.start3.mozilla.com
* zh-cn.www.mozilla.com
* zh-tw.add-ons.mozilla.com
* zh-tw.www.mozilla.com
* zh-tw.www.mozillamessaging.com

Talk:Mobile/Platforms/Android

2012-01-30T03:43:40Z

Dynamis: requesting to add link to single locale build

Tried Fennec. Using Sprint EVO 4G with 2.1(update1) Android system.
Found some items:

Keyboard-- backspace does not work.

Went to yahoo homepage -
Looked good, but top header links did not work.

Like the bookmark setup.

Took me a while to figure out I could push MENU to goto previous page.

Was surprised DL was only 11Mb.

Uninstalled it and will try again later...
Be nice to have Firefox on phone..

== Xperia X10 ==

the xperia x10 does have the ARMv7 CPU needed but lacks the 2.0+ OS

will be getting the update 2nd half of October

Ihave moved it to compatible devices albeit with a note that OS is not there yet

-PiLoT-

== Samsung Galaxy S II ==

Tested Firefox Mobile 4.0.1. Everything works like a charm.

-jooliaan

== Why ARMv7? ==

First of all I must say I am not that familiar with the ARM CPUs but I mus say I was somewhat surprised that my phone - which runs Android 2.2 quite smoothly - cannot run firefox.

Problem is that teh processor is "just" an ARMv5 ... seems I am out of luck with firefox.

== Samsung Galaxy GIO S5660M Armv6 ==

Another phone to add to the unsupported list because of ArmV6 CPU :(

I was going to add it to the page, but edit's are disabled.

== ASUS Transformer EEE Pad ==

Should be added to the list of supported products.

== supported and not supported devices ==

just tried and found that LG Optimus Chic E720 and Jpad WM8650 (or called as Wondermate WM8650) is not compatible with firefox mobile and should be added to not support list while Archos 32 internet tablets able to run firefox normally and should eb added to support list.

== ZTE Skate / Orange Monte Carlo ==

This is another ARMv6 mobile.

== Link to single locale l10n build ==

NativeUI Fennec will have single UI locale build, not only multi-locale build but current page don't have link to the FTP dir. Please include link to:

http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-aurora-android-l10n/

AsiaCamp 2011/Schedule/Skills Development and Community Growth Track/mascots

2011-11-22T01:17:57Z

Dynamis: /* Build Mascot with Community Power */

== Build Mascot with Community Power ==

'''Summary:''' Now we have Foxkeh, Foxmosa, G-Fox, and KUMI in Asia regions, it's interesting that we use mascot much more then other areas. In this section, we are going to share the experience on mascot planning, include the reason to create a mascot, how we create it, current status, how it benefit the community, and issues we are facing.

* '''Speaker''':
** Po-chiang Chao aka. BobChao (MozTW)
** Viking Karwur (Mozilla Indonesia)
** Jack Guo (MozillaOnline)
** Tomoya Asai aka. dynamis (Mozilla Japan)
* '''Time:'''
* '''Duration:''' 45 minutes
* '''Slide / URLs (will provide after the talk)''':
** [http://www.slideshare.net/dynamis/promoting-firefox-with-foxkeh Promoting Firefox with Foxkeh]
* '''Equipment needs (video projector already included):''' Just projector.

== Note, Photo... ==

* Please take note on MoPad: https://etherpad.mozilla.org/asiacamp-mascot
* tagging things as "#mozcamp #mascot"

== Feel free to submit a question for the speaker below ==
(add your question here)

L10n:Teams:ja

2011-06-10T10:56:08Z

Dynamis: /* Japanese (ja,ja-JP-mac) */

=== Japanese (ja,ja-JP-mac) ===
[https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&component=ja,%20ja-JP-mac%20/%20Japanese file bug]

[http://forums.firehacks.org/l10n/ forum] [https://dev.mozilla.jp/l10n/ documents] [http://www.mozilla-japan.org/jp/l10n/ web page (almost obsolate)]
; browser/mail/toolkit/mobile/minimo owner: Tomoya ASAI (aka dynamis) <dynamis[AT]mozilla-japan[DOT]org> (bugmail: <bugzilla@firehacks.org>) - [https://bugzilla.mozilla.org/show_bug.cgi?id=264931 CVS access: YES]
; browser/mail/toolkit main peer : Atsushi SAKAI <dev-null[AT]hotmail[DOT]co[DOT]jp> - [https://bugzilla.mozilla.org/show_bug.cgi?id=401978 CVS/HG access: YES]
; mail leader, browser/toolkit peer : Masahiko IMANAKA (aka mar) <chimantaea_mirabilis[AT]yahoo[DOT]co[DOT]jp> - [https://bugzilla.mozilla.org/show_bug.cgi?id=401979 CVS/HG access: YES]
; browser leader, mail/toolkit peer : ABE Hiroki (aka hATrayflood) (hATrayflood) <h[DOT]rayflood[AT]gmail[DOT]com>- [https://bugzilla.mozilla.org/show_bug.cgi?id=659534 HG access: YES]
; browser/mail/toolkit peer : KOZAWA Hidehiro <kozawa[AT]mozilla[DOT]gr[DOT]jp> - [https://bugzilla.mozilla.org/show_bug.cgi?id=282337 CVS access: YES]

<noinclude>[[category:L10n Teams|ja]]</noinclude>

Websites/Mozilla.org/Archive/Parks/Tumucumaque/L10n

2011-03-02T06:52:37Z

Dynamis:

This page is '''Keywords translation table''' of '''Virtual Park Tumucumaque demo'''. [http://virtualpark.mozilla.org Virtual Park] will find these keywords within tweets to show creatures. 

 

http://virtualpark.mozilla.org/docs/about/images/tweetanimal.en.png 

 

Please translate creature names into your language. If your locale is not in the list, just add it. Any language translation is welcome!

In case there are multiple translations in your language, just input them as comma "," separated list. Words with spaces will be treated as single sequence of words.

Daisuke is watching change of this page and include your translation into the Virtual Park demo system (until the end of March). 

Please read this page for more info about the Virtual Park: [http://virtualpark.mozilla.org/docs/about/ http://virtualpark.mozilla.org/docs/about/]

*creature
**en: creature
**ja: 生物,動植物
**pt: criatura
**zh-tw: 生物,動植物
**fr: créature
**es: criatura
**ru: создание
**pl: stworzenia
**eo: kreaĵo, kreitaĵo, estaĵo, ekzistaĵo
**ro: vietate
**de: Geschöpf

*plant
**en: plant
**ja: 植物
**pt: planta
**zh-tw: 植物
**fr: plante
**es: planta
**ru: растение
**pl: rośliny
**eo: kreskaĵo, planto, vegetaĵo
**ro: plantă
**de: Pflanze

*tree
**en: tree,wood
**ja: 木,き,キ,森,林
**pt: árvore
**zh-tw: 樹,樹木
**fr: arbre
**es: árbol
**ru: дерево
**pl: drzewo
**eo: arbo
**ro: arbore
**de: Baum,Wald

*flower
**en: flower
**ja: はな,花,ハナ
**pt: flor
**zh-tw: 花
**fr: fleur
**es: flor
**ru: цветок
**pl: kwiat
**eo: floro
**ro: floare
**de: Blume

*animal
**en: animal
**ja: 動物
**pt: animal
**zh-tw: 動物
**fr: animal
**es: animal
**ru: животное
**pl: zwierzęta
**eo: besto, animalo
**ro: animal
**de: Tier

*reptilia
**en: reptilia
**ja: 爬虫類
**pt: reptil
**zh-tw: 爬蟲類
**fr: reptiles
**es: reptil
**ru: пресмыкающееся
**pl: gady
**eo: rampulo, reptilio, rampaĵo
**ro: reptilă
**de: Reptil

*lizard
**en: lizard
**ja: とかげ,トカゲ
**pt: lagarto
**zh-tw: 蜥蜴
**fr: lézard
**es: lagarto
**ru: ящерица
**pl: jaszczurka
**eo: lacerto
**ro: șopârlă
**de: Echse

*gecko
**en: gecko
**ja: やもり,ヤモリ
**pt: lagartixa,osga
**zh-tw: 壁虎,守宮
**fr: gecko
**es: lagartija
**ru: геккон
**pl: gekon
**eo: geko
**ro: șopârlă,mică,gecko
**de: Gecko

*amphibia
**en: amphibia
**ja: 両生類
**pt: anfíbio
**zh-tw: 兩棲類
**fr: amphibien
**es: anfibio
**ru: земноводное
**pl: płazy
**eo: amfibio
**ro: amfibie
**de: Amphibie

*frog
**en: frog
**ja: かえる,カエル,蛙
**pt: sapo,rã
**zh-tw: 蛙,青蛙
**fr: grenouille
**es: sapo
**ru: лягушка
**pl: żaba
**eo: rano
**ro: broască
**de: Frosch

*bird
**en: bird
**ja: 鳥類,鳥,とり,トリ
**pt: pássaro
**zh-tw: 鳥,小鳥
**fr: oiseau
**es: ave
**ru: птица
**pl: ptaki
**eo: birdo
**ro: pasăre
**de: Vogel

*hawk
**en: hawk eagle
**ja: わし,ワシ,鷲,たか,タカ,鷹
**pt: águia,falcão
**zh-tw: 鷹,老鷹
**fr: faucon
**es: halcón
**ru: ястреб,орёл
**pl: jastrząb
**eo: akcipitro,falko,aglo
**ro: șoim
**de: Habicht,Adler

*macaw
**en: macaw
**ja: インコ,オウム
**pt: arara,papagaio
**zh-tw: 金剛鸚鵡
**fr: ara
**es: guacamayo
**ru: ара
**pl: ary
**eo: arao
**ro: papagal Ara Macao,
**de: Ara

*mammal
**en: mammal
**ja: 哺乳類
**pt: mamífero
**zh-tw: 哺乳類
**fr: mammifère
**es: mamífero
**ru: млекопитающее
**pl: ssaki
**eo: mamulo
**ro: mamifer
**de: Säugetier

*anteater
**en: anteater
**ja: アリクイ,食蟻獣,蟻食
**pt: papa-formigas
**zh-tw: 食蟻獸
**fr: fourmilier
**es: oso,hormiguero
**ru: муравьед
**pl: mrówkojad
**eo: formikomanĝulo,formikmanĝulo,formik-manĝulo
**ro: furnicar
**de: Ameisenbär

*monkey
**en: monkey
**ja: 猿,さる,サル
**pt: macaco,chimpanzé
**zh-tw: 猴子,猴
**fr: singe
**es: mono
**ru: обезьяна
**pl: małpa
**eo: simio
**ro: maimuță
**de: Affe

*cat
**en: cat
**ja: ねこ,ネコ,猫
**pt: gato
**zh-tw: 貓
**fr: chat
**es: gato
**ru: кошка
**pl: kot
**eo: kato
**ro: pisică
**de: Katze

*dog
**en: dog
**ja: いぬ,イヌ,犬
**pt: cão
**zh-tw: 狗,犬
**fr: chien
**es: perro
**ru: собака
**pl: pies
**eo: hundo
**ro: câine
**de: Hund

*ColeodactylusNatalensis
**en: natal-pigmy-gecko
**ja:
**pt:
**zh-tw: 巴西侏儒守宮
**fr: coleodactylus natalensis,
**es: lagartija pigmea de Natal,
**ru: вкладнопалый геккон,
**pl: gekon-amazoński
**eo:
**ro: șopârlă gecko foarte mică,

*TurnipTailedGecko
**en: turnip-tailed-gecko
**ja:
**pt:
**zh-tw:
**fr: thécadactyle à queue épineuse,
**es: lagartija cola de nabo,
**ru: реп-хвостатый геккон
**pl: turnip-tailed-gekon,
**eo:
**ro: șopârlă gecko cu coadă ruptă,

*CeratophrysCornuta
**en: amazonian-horned-frog, surinam-horned-frog
**ja: アマゾンツノガエル
**pt:
**zh-tw: 亞馬遜角蛙,蘇利南角蛙,霸王角蛙
**fr: grenouille cornue,
**es: rana cornuda de Surinam,
**ru: суринамская рогатая лягушка,
**pl: amazońska-rogata-żaba, surinamska-rogata-żaba
**eo:
**ro: broască cu coarne Surinam,

*DendrobatesTinctorius
**en: dyeing-poison-dart-frog
**ja: アイゾメヤドクガエル
**pt:
**zh-tw: 箭毒蛙
**fr: dendrobate à tapirer,
**es: rana dardo,
**ru: древолаз пятнистый,
**pl: drzewołaz-malarski,
**eo:
**ro: broască rapidă pictată otrăvitoare,

*PseudisParadoxa
**en: paradoxical-frog
**ja:
**pt:
**zh-tw: 奇異多指節蛙,奇異多指節蟾,萎縮蛙
**fr: grenouille paradoxale,
**es: rana patito ,
**ru: парадоксальная лягушка,
**pl: dziwaczka-arlekin ,
**eo:
**ro: pseudo-broască,
**de:

*HarpiaHarpyja
**en: harpy-eagle
**ja: オウギワシ
**pt:
**zh-tw: 角雕,哈比鷹
**fr: harpie féroce,
**es: harpía
**ru: большая гарпия,
**pl: harpia-wielka ,
**eo: Amerika harpio,
**ro: acvilă Harpia (coronată) americană,

*AnodorhynchusHyacinthinus
**en: black-macaw, blue-macaw, hyacinth-macaw
**ja: スミレコンゴウインコ
**pt:
**zh-tw: 紫藍金剛鸚鵡
**fr: ara hyacinthe,
**es: guacamayo azul,
**ru: гиацинтовый ара,
**pl: ara-hiacyntowa,
**eo:
**ro: papagal macao zambilă (albastru),

*AraArarauna
**en: blue-and-yellow-macaw, blue-and-gold-macaw
**ja: ルリコンゴウインコ
**pt: arara
**zh-tw: 藍黃金剛鸚鵡
**fr: ara bleu et or,
**es: guacamayo azul y amarillo,
**ru: сине-жёлтый ара,
**pl: ara-żółtoniebieska,
**eo:
**ro: papagal Ara Macao albastru-galben,

*AraChloroptera
**en: green-winged-macaw
**ja: ベニコンゴウインコ
**pt:
**zh-tw: 綠翅金剛鸚鵡
**fr: ara chloroptère,
**es: guacamayo rojo,
**ru: зеленокрылый ара,
**pl: ara-zielonoskrzydła,
**eo:
**ro: papagal Ara Macao verde-roșu(aripi-verzi),

*MyrmecophagaTridactyla
**en: giant-ant-eater, giant-anteater
**ja: オオアリクイ
**pt:
**zh-tw: 大食蟻獸
**fr: fourmilier géant,
**es: oso hormiguero gigante,
**ru: гигантский муравьед,
**pl: mrówkojad-wielki,
**eo: granda formik-manĝulo, granda formikmanĝulo, granda formikomanĝulo, formik-urso, formikurso, formikourso
**ro: furnicar gigant,

*CebusApella
**en: tufted-capuchin, brown-capuchin
**ja: フサオマキザル
**pt:
**zh-tw: 褐捲尾猴
**fr: capucin à poitrine jaune,
**es: mono maicero,
**ru: бурый капуцин,
**pl: kapucynka-czubata,
**eo: vango-hara kapuceno, vangohara kapuceno, vanghara kapuceno, vang-hara kapuceno 
**ro: maimuță capucin cu smocuri,

*LagothrixLagotricha
**en: brown-woollymonkey, common-woolly-monkey, humboldt's-woolly-monkey
**ja: コモンウーリーモンキー, フンボルトウーリーモンキー
**pt:
**zh-tw: 褐毛猴
**fr: lagotriche gris,
**es: mono lanudo común,
**ru: шерстистая обезьяна,
**pl: małpa-wełnista,
**eo: 
**ro: maimuță lânoasă maro,
**de:

*PitheciaPithecia
**en: white-faced-saki
**ja: シロガオサキ
**pt:
**zh-tw: 白面僧面猴, 南美白臉猴, 白臉猴, 白面粗尾猿
**fr: saki à face blanche,
**es: sakí cariblanco,
**ru: саки бледноголовый,
**pl: saki-białolica,
**eo:
**ro: maimuță Saki față-galbenă,

*FelisPardalis
**en: ocelot
**ja: オセロット
**pt:
**zh-tw: 虎貓
**fr: ocelot
**es: ocelote
**ru: оцелот
**pl: ocelot
**eo:  
**ro: ocelot

*LeopardusTigrinus
**en: oncilla
**ja: ジャガーネコ
**pt:
**zh-tw: 小斑虎貓
**fr: oncille
**es: leopardo
**ru: онцилла
**pl: leopard
**eo: nana tigro-kato, 
**ro: leopard

*PantheraOnca
**en: jaguar
**ja: ジャガー
**pt:
**zh-tw: 美洲豹
**fr: jaguar
**es: jaguar
**ru: ягуар
**pl: jaguar
**eo: jaguaro
**ro: jaguar
**de:

*PumaYaguarondi
**en: jaguarundi
**ja: ジャガランディ
**pt:
**zh-tw: 美洲山貓, 細腰貓
**fr: jaguarondi
**es: puma
**ru: ягуарунди
**pl: puma
**eo:
**ro: puma

*SpeothosVenaticus
**en: bush-dog
**ja: ヤブイヌ
**pt:
**zh-tw: 叢林犬, 藪犬
**fr: chien des buissons,
**es: perro venadero,
**ru: кустарниковая собака,
**pl: pies-leśny
**eo: speoto, arbaro-hundo, arbarhundo, arbarohundo, mustelvulpo
**ro: câine de preerie,
**de: 

*aqua
**en: aqua, water, river, pond
**ja: みず, ミズ, 水, かわ, カワ, 川, いけ, イケ, 池, 瀧, 滝, たき, タキ,
**pt: água, rio, lagoa, lago
**zh-tw: 水, 湖, 河, 溪, 池塘, 江, 海, 川, 溝, 圳
**fr: eau, rivière, étang, mare, lac, fleuve, torrent
**es: aqua, agua, río, lago
**ru: вода, вода, река, пруд
**pl: woda, rzeka, staw
**eo: akvo, akvujo, rivero, lago, lageto
**ro: apă, apă, râu, lac, fluviu
**de: Wasser, Wasser, Fluss, Teich

Websites/Mozilla.org/Archive/Parks/Tumucumaque/L10n

2011-03-02T06:50:59Z

Dynamis:

This page is '''Keywords translation table''' of '''Virtual Park Tumucumaque demo'''. [http://virtualpark.mozilla.org Virtual Park] will find these keywords within tweets to show creatures. 

 

http://virtualpark.mozilla.org/docs/about/images/tweetanimal.en.png 

 

Please translate creature names into your language. If your locale is not in the list, just add it. Any language translation is welcome!

In case there are multiple translations in your language, just input them as comma "," separated list. Words with spaces will be treated as single sequence of words.

Daisuke is watching change of this page and include your translation into the Virtual Park demo system (until the end of March). 

Please read this page for more info about the Virtual Park: [http://virtualpark.mozilla.org/docs/about/ http://virtualpark.mozilla.org/docs/about/]

*creature
**en: creature
**ja: 生物,動植物
**pt: criatura
**zh-tw: 生物,動植物
**fr: créature
**es: criatura
**ru: создание
**pl: stworzenia
**eo: kreaĵo, kreitaĵo, estaĵo, ekzistaĵo
**ro: vietate
**de: Geschöpf

*plant
**en: plant
**ja: 植物
**pt: planta
**zh-tw: 植物
**fr: plante
**es: planta
**ru: растение
**pl: rośliny
**eo: kreskaĵo, planto, vegetaĵo
**ro: plantă
**de: Pflanze

*tree
**en: tree,wood
**ja: 木,き,キ,森,林
**pt: árvore
**zh-tw: 樹,樹木
**fr: arbre
**es: árbol
**ru: дерево
**pl: drzewo
**eo: arbo
**ro: arbore
**de: Baum,Wald

*flower
**en: flower
**ja: はな,花,ハナ
**pt: flor
**zh-tw: 花
**fr: fleur
**es: flor
**ru: цветок
**pl: kwiat
**eo: floro
**ro: floare
**de: Blume

*animal
**en: animal
**ja: 動物
**pt: animal
**zh-tw: 動物
**fr: animal
**es: animal
**ru: животное
**pl: zwierzęta
**eo: besto, animalo
**ro: animal
**de: Tier

*reptilia
**en: reptilia
**ja: 爬虫類
**pt: reptil
**zh-tw: 爬蟲類
**fr: reptiles
**es: reptil
**ru: пресмыкающееся
**pl: gady
**eo: rampulo, reptilio, rampaĵo
**ro: reptilă
**de: Reptil

*lizard
**en: lizard
**ja: とかげ,トカゲ
**pt: lagarto
**zh-tw: 蜥蜴
**fr: lézard
**es: lagarto
**ru: ящерица
**pl: jaszczurka
**eo: lacerto
**ro: șopârlă
**de: Echse

*gecko
**en: gecko
**ja: やもり,ヤモリ
**pt: lagartixa,osga
**zh-tw: 壁虎,守宮
**fr: gecko
**es: lagartija
**ru: геккон
**pl: gekon
**eo: geko
**ro: șopârlă,mică,gecko
**de: Gecko

*amphibia
**en: amphibia
**ja: 両生類
**pt: anfíbio
**zh-tw: 兩棲類
**fr: amphibien
**es: anfibio
**ru: земноводное
**pl: płazy
**eo: amfibio
**ro: amfibie
**de: Amphibie

*frog
**en: frog
**ja: かえる,カエル,蛙
**pt: sapo,rã
**zh-tw: 蛙,青蛙
**fr: grenouille
**es: sapo
**ru: лягушка
**pl: żaba
**eo: rano
**ro: broască
**de: Frosch

*bird
**en: bird
**ja: 鳥類,鳥,とり,トリ
**pt: pássaro
**zh-tw: 鳥,小鳥
**fr: oiseau
**es: ave
**ru: птица
**pl: ptaki
**eo: birdo
**ro: pasăre
**de: Vogel

*hawk
**en: hawk eagle
**ja: わし,ワシ,鷲,たか,タカ,鷹
**pt: águia,falcão
**zh-tw: 鷹,老鷹
**fr: faucon
**es: halcón
**ru: ястреб,орёл
**pl: jastrząb
**eo: akcipitro,falko,aglo
**ro: șoim
**de: Habicht,Adler

*macaw
**en: macaw
**ja: インコ,オウム
**pt: arara,papagaio
**zh-tw: 金剛鸚鵡
**fr: ara
**es: guacamayo
**ru: ара
**pl: ary
**eo: arao
**ro: papagal Ara Macao,
**de: Ara

*mammal
**en: mammal
**ja: 哺乳類
**pt: mamífero
**zh-tw: 哺乳類
**fr: mammifère
**es: mamífero
**ru: млекопитающее
**pl: ssaki
**eo: mamulo
**ro: mamifer
**de: Säugetier

*anteater
**en: anteater
**ja: アリクイ,食蟻獣,蟻食
**pt: papa-formigas
**zh-tw: 食蟻獸
**fr: fourmilier
**es: oso,hormiguero
**ru: муравьед
**pl: mrówkojad
**eo: formikomanĝulo,formikmanĝulo,formik-manĝulo
**ro: furnicar
**de: Ameisenbär

*monkey
**en: monkey
**ja: 猿,さる,サル
**pt: macaco,chimpanzé
**zh-tw: 猴子,猴
**fr: singe
**es: mono
**ru: обезьяна
**pl: małpa
**eo: simio
**ro: maimuță
**de: Affe

*cat
**en: cat
**ja: ねこ,ネコ,猫
**pt: gato
**zh-tw: 貓
**fr: chat
**es: gato
**ru: кошка
**pl: kot
**eo: kato
**ro: pisică
**de: Katze

*dog
**en: dog
**ja: いぬ,イヌ,犬
**pt: cão
**zh-tw: 狗,犬
**fr: chien
**es: perro
**ru: собака
**pl: pies
**eo: hundo
**ro: câine
**de: Hund

*ColeodactylusNatalensis
**en: natal-pigmy-gecko
**ja:
**pt:
**zh-tw: 巴西侏儒守宮
**fr: coleodactylus natalensis,
**es: lagartija pigmea de Natal,
**ru: вкладнопалый геккон,
**pl: gekon-amazoński
**eo:
**ro: șopârlă gecko foarte mică,

*TurnipTailedGecko
**en: turnip-tailed-gecko
**ja:
**pt:
**zh-tw:
**fr: thécadactyle à queue épineuse,
**es: lagartija cola de nabo,
**ru: реп-хвостатый геккон
**pl: turnip-tailed-gekon,
**eo:
**ro: șopârlă gecko cu coadă ruptă,

*CeratophrysCornuta
**en: amazonian-horned-frog, surinam-horned-frog
**ja: アマゾンツノガエル
**pt:
**zh-tw: 亞馬遜角蛙,蘇利南角蛙,霸王角蛙
**fr: grenouille cornue,
**es: rana cornuda de Surinam,
**ru: суринамская рогатая лягушка,
**pl: amazońska-rogata-żaba, surinamska-rogata-żaba
**eo:
**ro: broască cu coarne Surinam,

*DendrobatesTinctorius
**en: dyeing-poison-dart-frog
**ja: アイゾメヤドクガエル
**pt:
**zh-tw: 箭毒蛙
**fr: dendrobate à tapirer,
**es: rana dardo,
**ru: древолаз пятнистый,
**pl: drzewołaz-malarski,
**eo:
**ro: broască rapidă pictată otrăvitoare,

*PseudisParadoxa
**en: paradoxical-frog
**ja:
**pt:
**zh-tw: 奇異多指節蛙,奇異多指節蟾,萎縮蛙
**fr: grenouille paradoxale,
**es: rana patito ,
**ru: парадоксальная лягушка,
**pl: dziwaczka-arlekin ,
**eo:
**ro: pseudo-broască,
**de:

*HarpiaHarpyja
**en: harpy-eagle
**ja: オウギワシ
**pt:
**zh-tw: 角雕,哈比鷹
**fr: harpie féroce,
**es: harpía
**ru: большая гарпия,
**pl: harpia-wielka ,
**eo: Amerika harpio,
**ro: acvilă Harpia (coronată) americană,

*AnodorhynchusHyacinthinus
**en: black-macaw, blue-macaw, hyacinth-macaw
**ja: スミレコンゴウインコ
**pt:
**zh-tw: 紫藍金剛鸚鵡
**fr: ara hyacinthe,
**es: guacamayo azul,
**ru: гиацинтовый ара,
**pl: ara-hiacyntowa,
**eo:
**ro: papagal macao zambilă (albastru),

*AraArarauna
**en: blue-and-yellow-macaw, blue-and-gold-macaw
**ja: ルリコンゴウインコ
**pt: arara
**zh-tw: 藍黃金剛鸚鵡
**fr: ara bleu et or,
**es: guacamayo azul y amarillo,
**ru: сине-жёлтый ара,
**pl: ara-żółtoniebieska,
**eo:
**ro: papagal Ara Macao albastru-galben,

*AraChloroptera
**en: green-winged-macaw
**ja: ベニコンゴウインコ
**pt:
**zh-tw: 綠翅金剛鸚鵡
**fr: ara chloroptère,
**es: guacamayo rojo,
**ru: зеленокрылый ара,
**pl: ara-zielonoskrzydła,
**eo:
**ro: papagal Ara Macao verde-roșu(aripi-verzi),

*MyrmecophagaTridactyla
**en: giant-ant-eater, giant-anteater
**ja: オオアリクイ
**pt:
**zh-tw: 大食蟻獸
**fr: fourmilier géant,
**es: oso hormiguero gigante,
**ru: гигантский муравьед,
**pl: mrówkojad-wielki,
**eo: granda formik-manĝulo, granda formikmanĝulo, granda formikomanĝulo, formik-urso, formikurso, formikourso
**ro: furnicar gigant,

*CebusApella
**en: tufted-capuchin, brown-capuchin
**ja: フサオマキザル
**pt:
**zh-tw: 褐捲尾猴
**fr: capucin à poitrine jaune,
**es: mono maicero,
**ru: бурый капуцин,
**pl: kapucynka-czubata,
**eo: vango-hara kapuceno, vangohara kapuceno, vanghara kapuceno, vang-hara kapuceno 
**ro: maimuță capucin cu smocuri,

*LagothrixLagotricha
**en: brown-woollymonkey, common-woolly-monkey, humboldt's-woolly-monkey
**ja: コモンウーリーモンキー, フンボルトウーリーモンキー
**pt:
**zh-tw: 褐毛猴
**fr: lagotriche gris,
**es: mono lanudo común,
**ru: шерстистая обезьяна,
**pl: małpa-wełnista,
**eo: 
**ro: maimuță lânoasă maro,
**de:

*PitheciaPithecia
**en: white-faced-saki
**ja: シロガオサキ
**pt:
**zh-tw: 白面僧面猴, 南美白臉猴, 白臉猴, 白面粗尾猿
**fr: saki à face blanche,
**es: sakí cariblanco,
**ru: саки бледноголовый,
**pl: saki-białolica,
**eo:
**ro: maimuță Saki față-galbenă,

*FelisPardalis
**en: ocelot
**ja: オセロット
**pt:
**zh-tw: 虎貓
**fr: ocelot
**es: ocelote
**ru: оцелот
**pl: ocelot
**eo:  
**ro: ocelot

*LeopardusTigrinus
**en: oncilla
**ja: ジャガーネコ
**pt:
**zh-tw: 小斑虎貓
**fr: oncille
**es: leopardo
**ru: онцилла
**pl: leopard
**eo: nana tigro-kato, 
**ro: leopard

*PantheraOnca
**en: jaguar
**ja: ジャガー
**pt:
**zh-tw: 美洲豹
**fr: jaguar
**es: jaguar
**ru: ягуар
**pl: jaguar
**eo: jaguaro
**ro: jaguar
**de:

*PumaYaguarondi
**en: jaguarundi
**ja: ジャガランディ
**pt:
**zh-tw: 美洲山貓, 細腰貓
**fr: jaguarondi
**es: puma
**ru: ягуарунди
**pl: puma
**eo:
**ro: puma

*SpeothosVenaticus
**en: bush-dog
**ja: ヤブイヌ
**pt:
**zh-tw: 叢林犬, 藪犬
**fr: chien des buissons,
**es: perro venadero,
**ru: кустарниковая собака,
**pl: pies-leśny
**eo: speoto, arbaro-hundo, arbarhundo, arbarohundo, mustelvulpo
**ro: câine de preerie,
**de: 

*aqua
**en: aqua, water, river, pond
**ja: みず, ミズ, 水, かわ, カワ, 川, いけ, イケ, 池, 瀧, 滝, たき, タキ,
**pt: água, rio, lagoa, lago
**zh-tw: 水, 湖, 河, 溪, 池塘, 江, 海, 川, 溝, 圳
**fr: eau, rivière, étang, mare, lac, fleuve, torrent
**es: aqua, agua, río, lago
**ru: вода, вода, река, пруд
**pl: woda, rzeka, staw
**eo: akvo, akvujo, rivero, lago, lageto
**ro: apă, apă, râu, lac, fluviu
**de: Wasser, Wasser, Fluss, Teich

Websites/Mozilla.org/Archive/Parks/Tumucumaque/L10n

2011-03-01T05:44:27Z

Dynamis:

This page is Keywords translation table of Virtual Park Tumucumaque demo. [http://virtualpark.mozilla.org/ Virtual Park] will find these keywords within tweets to show creatures.

http://virtualpark.mozilla.org/docs/about/images/tweetanimal.en.png

Please translate creature names into your language. If your locale is not in the list, just add it. Any language translation is welcome!
Daisuke is watching change of this page and include your translation into the Virtual Park demo system (until the end of March).

Please read this page for more info about the Virtual Park: http://virtualpark.mozilla.org/docs/about/

*creature
**en: creature
**ja: 生物動植物
**pt:

*plant
**en: plant
**ja: 植物
**pt:

*tree
**en: tree wood
**ja: 木きキ森林
**pt: árvore

*flower
**en: flower
**ja: はな花ハナ
**pt: flor

*animal
**en: animal
**ja: 動物
**pt:

*reptilia
**en: reptilia
**ja: 爬虫類
**pt:

*lizard
**en: lizard
**ja: とかげトカゲ
**pt: lagarto lagartixa

*gecko
**en: gecko
**ja: やもりヤモリ
**pt:

*amphibia
**en: amphibia
**ja: 両生類
**pt:

*frog
**en: frog
**ja: かえるカエル蛙
**pt: sapo

*bird
**en: bird
**ja: 鳥類鳥とりトリ
**pt:

*hawk
**en: hawk eagle
**ja: わしワシ鷲たかタカ鷹
**pt: águia

*macaw
**en: macaw
**ja: インコオウム
**pt:

*mammal
**en: mammal
**ja: 哺乳類
**pt:

*anteater
**en: anteater
**ja: アリクイ食蟻獣蟻食
**pt:

*monkey
**en: monkey
**ja: 猿さるサル
**pt:

*cat
**en: cat
**ja: ねこネコ猫
**pt:

*dog
**en: dog
**ja: いぬイヌ犬
**pt:

*ColeodactylusNatalensis
**en: natal-pigmy-gecko
**ja:
**pt:

*TurnipTailedGecko
**en: turnip-tailed-gecko
**ja:
**pt:

*CeratophrysCornuta
**en: amazonian-horned-frog surinam-horned-frog
**ja: アマゾンツノガエル
**pt:

*DendrobatesTinctorius
**en: dyeing-poison-dart-frog
**ja: アイゾメヤドクガエル
**pt:

*PseudisParadoxa
**en: paradoxical-frog
**ja:
**pt:

*HarpiaHarpyja
**en: harpy-eagle
**ja: オウギワシ
**pt:

*AnodorhynchusHyacinthinus
**en: black-macaw blue-macaw hyacinth-macaw
**ja: スミレコンゴウインコ
**pt:

*AraArarauna
**en: blue-and-yellow-macaw blue-and-gold-macaw
**ja: ルリコンゴウインコ
**pt:

*AraChloroptera
**en: green-winged-macaw
**ja: ベニコンゴウインコ
**pt:

*MyrmecophagaTridactyla
**en: giant-ant-eater giant-anteater
**ja: オオアリクイ
**pt:

*CebusApella
**en: tufted-capuchin brown-capuchin
**ja: フサオマキザル
**pt:

*LagothrixLagotricha
**en: brown-woollymonkey common-woolly-monkey humboldt's-woolly-monkey
**ja: コモンウーリーモンキーフンボルトウーリーモンキー
**pt:

*PitheciaPithecia
**en: white-faced-saki
**ja: シロガオサキ
**pt:

*FelisPardalis
**en: ocelot
**ja: オセロット
**pt:

*LeopardusTigrinus
**en: oncilla
**ja: ジャガーネコ
**pt:

*PantheraOnca
**en: jaguar
**ja: ジャガー
**pt:

*PumaYaguarondi
**en: jaguarundi
**ja: ジャガランディ
**pt:

*SpeothosVenaticus
**en: bush-dog
**ja: ヤブイヌ
**pt:

*aqua
**en: aqua water river pond
**ja: みずミズ水かわカワ川いけイケ池瀧滝たきタキ
**pt: água rio lagoa

Websites/Mozilla.org/Archive/Parks/Tumucumaque/L10n

2011-02-28T02:33:17Z

Dynamis:

This page is Keywords table of Virtual Park demo. Virtual park will search these keywords within tweets to show creatures.

Please input creature names in your language. Daisuke is watching change of this page and include your translation into the Virtual Park demo system (until the end of March).

about Virtual Park demo:
http://virtualpark.mozilla.org/docs/about/

* creature
**en: creature
**ja: 生物動植物
**pt:

* plant
**en: plant
**ja: 植物
**pt:

* tree
**en: tree wood
**ja: 木きキ森林
**pt: árvore

* flower
**en: flower
**ja: はな花ハナ
**pt: flor

* animal
**en: animal
**ja: 動物
**pt:

* reptilia
**en: reptilia
**ja: 爬虫類
**pt:

* lizard
**en: lizard
**ja: とかげトカゲ
**pt: lagarto lagartixa

* gecko
**en: gecko
**ja: やもりヤモリ
**pt:

* amphibia
**en: amphibia
**ja: 両生類
**pt:

* frog
**en: frog
**ja: かえるカエル蛙
**pt: sapo

* bird
**en: bird
**ja: 鳥類鳥とりトリ
**pt:

* hawk
**en: hawk eagle
**ja: わしワシ鷲たかタカ鷹
**pt: águia

* macaw
**en: macaw
**ja: インコオウム
**pt:

* mammal
**en: mammal
**ja: 哺乳類
**pt:

* anteater
**en: anteater
**ja: アリクイ食蟻獣蟻食
**pt:

* monkey
**en: monkey
**ja: 猿さるサル
**pt:

* cat
**en: cat
**ja: ねこネコ猫
**pt:

* dog
**en: dog
**ja: いぬイヌ犬
**pt:

* ColeodactylusNatalensis
**en: natal-pigmy-gecko
**ja:
**pt:

* TurnipTailedGecko
**en: turnip-tailed-gecko
**ja:
**pt:

* CeratophrysCornuta
**en: amazonian-horned-frog surinam-horned-frog
**ja: アマゾンツノガエル
**pt:

* DendrobatesTinctorius
**en: dyeing-poison-dart-frog
**ja: アイゾメヤドクガエル
**pt:

* PseudisParadoxa
**en: paradoxical-frog
**ja:
**pt:

* HarpiaHarpyja
**en: harpy-eagle
**ja: オウギワシ
**pt:

* AnodorhynchusHyacinthinus
**en: black-macaw blue-macaw hyacinth-macaw
**ja: スミレコンゴウインコ
**pt:

* AraArarauna
**en: blue-and-yellow-macaw blue-and-gold-macaw
**ja: ルリコンゴウインコ
**pt:

* AraChloroptera
**en: green-winged-macaw
**ja: ベニコンゴウインコ
**pt:

* MyrmecophagaTridactyla
**en: giant-ant-eater giant-anteater
**ja: オオアリクイ
**pt:

* CebusApella
**en: tufted-capuchin brown-capuchin
**ja: フサオマキザル
**pt:

* LagothrixLagotricha
**en: brown-woollymonkey common-woolly-monkey humboldt's-woolly-monkey
**ja: コモンウーリーモンキーフンボルトウーリーモンキー
**pt:

* PitheciaPithecia
**en: white-faced-saki
**ja: シロガオサキ
**pt:

* FelisPardalis
**en: ocelot
**ja: オセロット
**pt:

* LeopardusTigrinus
**en: oncilla
**ja: ジャガーネコ
**pt:

* PantheraOnca
**en: jaguar
**ja: ジャガー
**pt:

* PumaYaguarondi
**en: jaguarundi
**ja: ジャガランディ
**pt:

* SpeothosVenaticus
**en: bush-dog
**ja: ヤブイヌ
**pt:

* aqua
**en: aqua water river pond
**ja: みず水かわ川いけ池
**pt: água rio lagoa

Websites/Mozilla.org/Archive/Parks/Tumucumaque/L10n

2011-02-28T02:30:35Z

Dynamis:

This page is Keywords table of Virtual Park demo. Virtual park will search these keywords within tweets to show creatures.

Please input creature names in your language. Daisuke is watching change of this page and include your translation into the Virtual Park demo system.
# until the end of March

about Virtual Park demo:
http://virtualpark.mozilla.org/docs/about/

* creature
**en: creature
**ja: 生物動植物
**pt:

* plant
**en: plant
**ja: 植物
**pt:

* tree
**en: tree wood
**ja: 木きキ森林
**pt: árvore

* flower
**en: flower
**ja: はな花ハナ
**pt: flor

* animal
**en: animal
**ja: 動物
**pt:

* reptilia
**en: reptilia
**ja: 爬虫類
**pt:

* lizard
**en: lizard
**ja: とかげトカゲ
**pt: lagarto lagartixa

* gecko
**en: gecko
**ja: やもりヤモリ
**pt:

* amphibia
**en: amphibia
**ja: 両生類
**pt:

* frog
**en: frog
**ja: かえるカエル蛙
**pt: sapo

* bird
**en: bird
**ja: 鳥類鳥とりトリ
**pt:

* hawk
**en: hawk eagle
**ja: わしワシ鷲たかタカ鷹
**pt: águia

* macaw
**en: macaw
**ja: インコオウム
**pt:

* mammal
**en: mammal
**ja: 哺乳類
**pt:

* anteater
**en: anteater
**ja: アリクイ食蟻獣蟻食
**pt:

* monkey
**en: monkey
**ja: 猿さるサル
**pt:

* cat
**en: cat
**ja: ねこネコ猫
**pt:

* dog
**en: dog
**ja: いぬイヌ犬
**pt:

* ColeodactylusNatalensis
**en: natal-pigmy-gecko
**ja:
**pt:

* TurnipTailedGecko
**en: turnip-tailed-gecko
**ja:
**pt:

* CeratophrysCornuta
**en: amazonian-horned-frog surinam-horned-frog
**ja: アマゾンツノガエル
**pt:

* DendrobatesTinctorius
**en: dyeing-poison-dart-frog
**ja: アイゾメヤドクガエル
**pt:

* PseudisParadoxa
**en: paradoxical-frog
**ja:
**pt:

* HarpiaHarpyja
**en: harpy-eagle
**ja: オウギワシ
**pt:

* AnodorhynchusHyacinthinus
**en: black-macaw blue-macaw hyacinth-macaw
**ja: スミレコンゴウインコ
**pt:

* AraArarauna
**en: blue-and-yellow-macaw blue-and-gold-macaw
**ja: ルリコンゴウインコ
**pt:

* AraChloroptera
**en: green-winged-macaw
**ja: ベニコンゴウインコ
**pt:

* MyrmecophagaTridactyla
**en: giant-ant-eater giant-anteater
**ja: オオアリクイ
**pt:

* CebusApella
**en: tufted-capuchin brown-capuchin
**ja: フサオマキザル
**pt:

* LagothrixLagotricha
**en: brown-woollymonkey common-woolly-monkey humboldt's-woolly-monkey
**ja: コモンウーリーモンキーフンボルトウーリーモンキー
**pt:

* PitheciaPithecia
**en: white-faced-saki
**ja: シロガオサキ
**pt:

* FelisPardalis
**en: ocelot
**ja: オセロット
**pt:

* LeopardusTigrinus
**en: oncilla
**ja: ジャガーネコ
**pt:

* PantheraOnca
**en: jaguar
**ja: ジャガー
**pt:

* PumaYaguarondi
**en: jaguarundi
**ja: ジャガランディ
**pt:

* SpeothosVenaticus
**en: bush-dog
**ja: ヤブイヌ
**pt:

* aqua
**en: aqua water river pond
**ja: みず水かわ川いけ池
**pt: água rio lagoa

Mobile/Build/Windows Mobile DevSpecificInfo

2009-05-29T16:09:17Z

Dynamis: /* HTC Touch Pro */

=Device Specific Debugging Information=

This page should contain information about specific devices and bugs which have shown themselves on those devices.

This page is NOT in any way a replacement for Bugzilla - it is only a cache of information in a readily accessible form.

If you are debugging on a particular device, please feel free to update the information on that device. However, do not remove other people's comments on a device - only add the information that you do (or do not) see that same issue.

==HTC Touch Pro==

This device is our current reference platform for developing XULRunner and Fennec Mobile Browser for Windows Mobile.

This device was chosen for it's large RAM and storage availability, as well as its good resolution, touch screen, and expansion card.

This device gets the most testing, and should need the least amount of information cached on this page.

note: Model numbers are [http://www.nttdocomo.co.jp/product/foma/pro/ht01a/ HT-01A] for NTT docomo, [http://mb.softbank.jp/mb/product/X/x05ht/ X05HT] for Softbank and [http://www.kddi.com/business/keitai_denwa/lineup/e30ht/ E30HT] for au in Japan.

==HTC Orbit (XDA)==

This is a Windows Mobile 5.0 Professional Device, code named HTC Artimis. This device has a Microsoft Windows Mobile 5.0 for Pocket PC Phone Edition (Magneto) AKU 3.0.0 OS, running on a Texas Instruments OMAP 850 CPU which executes ARMv5TEJ code at 201 MHz. This device has 128 MB ROM and 64 MByte RAM.

One user reports that this device will launch XULRunner, but he never sees any windows -- even when using the simple mybrowser application.

==Samsung i900 Omnia==

This is a Microsoft Windows Mobile 6.1 Professional device running on a 624MHz Marvell PXA312 processor. It has 128 MB RAM and 256 MB ROM.

Fennec just crashes with the following error log:

EvntType: WinCE501bException
AppName : xulrunner.exe
AppVer : 5.2.0.0
AppStamp: 49921b5a
ModName : xul.dll
ModVer : 5.0.0.0
ModStamp: 49921b28
Offset : 00189d8c
OwnName : xulrunner.exe
OwnVer : 5.2.0.0
OwnStamp: 49921b5a

The complete device and error logs are uploaded here[https://wiki.mozilla.org/images/9/9b/SamsungOmnia_Kdmp.zip].

==LG Incite CT810==

This is a Windows Mobile 6.1 Professional device with a 528MHz processor. It has 128 MB RAM and 256 MB ROM.

Fennec takes a very long time to load, but does so eventually, but it is very unpredictable. After loading, it tends to be very slow and lags often. With the latest builds, the virtual keyboard does work, and it is possible to type in an address. Google loads in about 3 minutes on a 3G connection. Page is vibrant and well painted, but lag is still an issue. I have not been able to actually type in a search however, as it crashes before I am able to. At some times, these crashes will crash the whole phone.

==WILLCOM 03==

This device is Windows Mobile 6.1 Classic Japanese device with 520MHz processor and 128MB RAM and 256 MB ROM.

[http://www.sharp.co.jp/ws/020sh/spec/index.html product spec page]

We test with TrueType fonts and settings to use it for content/chrome to show multi-byte chars.

Fennec alpha 1 takes about 30 secs to start and takes about 5~10 sec to load simple page like google search results.
Sunspider result was [http://people.mozilla.com/~dynamis/fennec/screenshots/wince/alpha1/sunspider%20result%20virtical.png 87183ms total] (ref. 132869 sec at iPhone 3G)

You can see more and more [http://people.mozilla.com/~dynamis/fennec/screenshots/wince/alpha1/ screenshots by dynamis].

==Toshiba dynapocket==

This is the most powerful device in the world so far.

This device is Windows Mobile 6.1 Professional device with 4.1-inch WVGA touchscreen and Qualcomm’s 1GHz Snapdragon QSD2850 processor.

[http://www.toshiba.co.jp/product/etsg/cmt/docomo/t-01a/t-01a_menu.htm product page], [http://www.markstechnologynews.com/2009/02/toshiba-tg01-41-inch-touchscreen.html english news], and [http://t-01a.windows-keitai.com/?T-01A%2F%E5%8B%95%E7%94%BB%E3%81%A7%E3%81%BF%E3%82%8B%2F%E6%B5%B7%E5%A4%96%E3%82%B5%E3%82%A4%E3%83%88%E3%81%A7%E3%81%AE%E3%83%AC%E3%83%93%E3%83%A5%E3%83%BC demo movie]

Model number is T-01A for NTT docomo in Japan.

Mobile/Build/Windows Mobile DevSpecificInfo

2009-05-29T07:29:13Z

Dynamis: /* WILLCOM 03 */

=Device Specific Debugging Information=

This page should contain information about specific devices and bugs which have shown themselves on those devices.

This page is NOT in any way a replacement for Bugzilla - it is only a cache of information in a readily accessible form.

If you are debugging on a particular device, please feel free to update the information on that device. However, do not remove other people's comments on a device - only add the information that you do (or do not) see that same issue.

==HTC Touch Pro==

This device is our current reference platform for developing XULRunner and Fennec Mobile Browser for Windows Mobile.

This device was chosen for it's large RAM and storage availability, as well as its good resolution, touch screen, and expansion card.

This device gets the most testing, and should need the least amount of information cached on this page.

note: Model numbers are X05HT for Softbank and E30HT for au in Japan.

==HTC Orbit (XDA)==

This is a Windows Mobile 5.0 Professional Device, code named HTC Artimis. This device has a Microsoft Windows Mobile 5.0 for Pocket PC Phone Edition (Magneto) AKU 3.0.0 OS, running on a Texas Instruments OMAP 850 CPU which executes ARMv5TEJ code at 201 MHz. This device has 128 MB ROM and 64 MByte RAM.

One user reports that this device will launch XULRunner, but he never sees any windows -- even when using the simple mybrowser application.

==Samsung i900 Omnia==

This is a Microsoft Windows Mobile 6.1 Professional device running on a 624MHz Marvell PXA312 processor. It has 128 MB RAM and 256 MB ROM.

Fennec just crashes with the following error log:

EvntType: WinCE501bException
AppName : xulrunner.exe
AppVer : 5.2.0.0
AppStamp: 49921b5a
ModName : xul.dll
ModVer : 5.0.0.0
ModStamp: 49921b28
Offset : 00189d8c
OwnName : xulrunner.exe
OwnVer : 5.2.0.0
OwnStamp: 49921b5a

The complete device and error logs are uploaded here[https://wiki.mozilla.org/images/9/9b/SamsungOmnia_Kdmp.zip].

==LG Incite CT810==

This is a Windows Mobile 6.1 Professional device with a 528MHz processor. It has 128 MB RAM and 256 MB ROM.

Fennec takes a very long time to load, but does so eventually, but it is very unpredictable. After loading, it tends to be very slow and lags often. With the latest builds, the virtual keyboard does work, and it is possible to type in an address. Google loads in about 3 minutes on a 3G connection. Page is vibrant and well painted, but lag is still an issue. I have not been able to actually type in a search however, as it crashes before I am able to. At some times, these crashes will crash the whole phone.

==WILLCOM 03==

This device is Windows Mobile 6.1 Classic Japanese device with 520MHz processor and 128MB RAM and 256 MB ROM.

[http://www.sharp.co.jp/ws/020sh/spec/index.html product spec page]

We test with TrueType fonts and settings to use it for content/chrome to show multi-byte chars.

Fennec alpha 1 takes about 30 secs to start and takes about 5~10 sec to load simple page like google search results.
Sunspider result was [http://people.mozilla.com/~dynamis/fennec/screenshots/wince/alpha1/sunspider%20result%20virtical.png 87183ms total] (ref. 132869 sec at iPhone 3G)

You can see more and more [http://people.mozilla.com/~dynamis/fennec/screenshots/wince/alpha1/ screenshots by dynamis].

==Toshiba dynapocket==

This is the most powerful device in the world so far.

This device is Windows Mobile 6.1 Professional device with 4.1-inch WVGA touchscreen and Qualcomm’s 1GHz Snapdragon QSD2850 processor.

[http://www.toshiba.co.jp/product/etsg/cmt/docomo/t-01a/t-01a_menu.htm product page], [http://www.markstechnologynews.com/2009/02/toshiba-tg01-41-inch-touchscreen.html english news], and [http://t-01a.windows-keitai.com/?T-01A%2F%E5%8B%95%E7%94%BB%E3%81%A7%E3%81%BF%E3%82%8B%2F%E6%B5%B7%E5%A4%96%E3%82%B5%E3%82%A4%E3%83%88%E3%81%A7%E3%81%AE%E3%83%AC%E3%83%93%E3%83%A5%E3%83%BC demo movie]

Model number is T-01A for NTT docomo in Japan.

Mobile/Build/Windows Mobile DevSpecificInfo

2009-05-29T07:21:22Z

Dynamis: /* Toshiba dynapocket */

=Device Specific Debugging Information=

This page should contain information about specific devices and bugs which have shown themselves on those devices.

This page is NOT in any way a replacement for Bugzilla - it is only a cache of information in a readily accessible form.

If you are debugging on a particular device, please feel free to update the information on that device. However, do not remove other people's comments on a device - only add the information that you do (or do not) see that same issue.

==HTC Touch Pro==

This device is our current reference platform for developing XULRunner and Fennec Mobile Browser for Windows Mobile.

This device was chosen for it's large RAM and storage availability, as well as its good resolution, touch screen, and expansion card.

This device gets the most testing, and should need the least amount of information cached on this page.

note: Model numbers are X05HT for Softbank and E30HT for au in Japan.

==HTC Orbit (XDA)==

This is a Windows Mobile 5.0 Professional Device, code named HTC Artimis. This device has a Microsoft Windows Mobile 5.0 for Pocket PC Phone Edition (Magneto) AKU 3.0.0 OS, running on a Texas Instruments OMAP 850 CPU which executes ARMv5TEJ code at 201 MHz. This device has 128 MB ROM and 64 MByte RAM.

One user reports that this device will launch XULRunner, but he never sees any windows -- even when using the simple mybrowser application.

==Samsung i900 Omnia==

This is a Microsoft Windows Mobile 6.1 Professional device running on a 624MHz Marvell PXA312 processor. It has 128 MB RAM and 256 MB ROM.

Fennec just crashes with the following error log:

EvntType: WinCE501bException
AppName : xulrunner.exe
AppVer : 5.2.0.0
AppStamp: 49921b5a
ModName : xul.dll
ModVer : 5.0.0.0
ModStamp: 49921b28
Offset : 00189d8c
OwnName : xulrunner.exe
OwnVer : 5.2.0.0
OwnStamp: 49921b5a

The complete device and error logs are uploaded here[https://wiki.mozilla.org/images/9/9b/SamsungOmnia_Kdmp.zip].

==LG Incite CT810==

This is a Windows Mobile 6.1 Professional device with a 528MHz processor. It has 128 MB RAM and 256 MB ROM.

Fennec takes a very long time to load, but does so eventually, but it is very unpredictable. After loading, it tends to be very slow and lags often. With the latest builds, the virtual keyboard does work, and it is possible to type in an address. Google loads in about 3 minutes on a 3G connection. Page is vibrant and well painted, but lag is still an issue. I have not been able to actually type in a search however, as it crashes before I am able to. At some times, these crashes will crash the whole phone.

==WILLCOM 03==

This device is Windows Mobile 6.1 Classic Japanese device with 520MHz processor and 128MB RAM and 256 MB ROM.

http://www.sharp.co.jp/ws/020sh/spec/index.html

We test with TrueType fonts and settings to use it for content/chrome to show multi-byte chars.

Fennec alpha 1 takes about 30 secs to start and takes about 5~10 sec to load simple page like google search results.
Sunspider result: [[http://people.mozilla.com/~dynamis/fennec/screenshots/wince/alpha1/sunspider%20result%20virtical.png 87183ms total]]

You can see more and more screenshots here;
http://people.mozilla.com/~dynamis/fennec/screenshots/wince/alpha1/

==Toshiba dynapocket==

This is the most powerful device in the world so far.

This device is Windows Mobile 6.1 Professional device with 4.1-inch WVGA touchscreen and Qualcomm’s 1GHz Snapdragon QSD2850 processor.

[http://www.toshiba.co.jp/product/etsg/cmt/docomo/t-01a/t-01a_menu.htm product page], [http://www.markstechnologynews.com/2009/02/toshiba-tg01-41-inch-touchscreen.html english news], and [http://t-01a.windows-keitai.com/?T-01A%2F%E5%8B%95%E7%94%BB%E3%81%A7%E3%81%BF%E3%82%8B%2F%E6%B5%B7%E5%A4%96%E3%82%B5%E3%82%A4%E3%83%88%E3%81%A7%E3%81%AE%E3%83%AC%E3%83%93%E3%83%A5%E3%83%BC demo movie]

Model number is T-01A for NTT docomo in Japan.

Mobile/Build/Windows Mobile DevSpecificInfo

2009-05-29T07:17:38Z

Dynamis:

=Device Specific Debugging Information=

This page should contain information about specific devices and bugs which have shown themselves on those devices.

This page is NOT in any way a replacement for Bugzilla - it is only a cache of information in a readily accessible form.

If you are debugging on a particular device, please feel free to update the information on that device. However, do not remove other people's comments on a device - only add the information that you do (or do not) see that same issue.

==HTC Touch Pro==

This device is our current reference platform for developing XULRunner and Fennec Mobile Browser for Windows Mobile.

This device was chosen for it's large RAM and storage availability, as well as its good resolution, touch screen, and expansion card.

This device gets the most testing, and should need the least amount of information cached on this page.

note: Model numbers are X05HT for Softbank and E30HT for au in Japan.

==HTC Orbit (XDA)==

This is a Windows Mobile 5.0 Professional Device, code named HTC Artimis. This device has a Microsoft Windows Mobile 5.0 for Pocket PC Phone Edition (Magneto) AKU 3.0.0 OS, running on a Texas Instruments OMAP 850 CPU which executes ARMv5TEJ code at 201 MHz. This device has 128 MB ROM and 64 MByte RAM.

One user reports that this device will launch XULRunner, but he never sees any windows -- even when using the simple mybrowser application.

==Samsung i900 Omnia==

This is a Microsoft Windows Mobile 6.1 Professional device running on a 624MHz Marvell PXA312 processor. It has 128 MB RAM and 256 MB ROM.

Fennec just crashes with the following error log:

EvntType: WinCE501bException
AppName : xulrunner.exe
AppVer : 5.2.0.0
AppStamp: 49921b5a
ModName : xul.dll
ModVer : 5.0.0.0
ModStamp: 49921b28
Offset : 00189d8c
OwnName : xulrunner.exe
OwnVer : 5.2.0.0
OwnStamp: 49921b5a

The complete device and error logs are uploaded here[https://wiki.mozilla.org/images/9/9b/SamsungOmnia_Kdmp.zip].

==LG Incite CT810==

This is a Windows Mobile 6.1 Professional device with a 528MHz processor. It has 128 MB RAM and 256 MB ROM.

Fennec takes a very long time to load, but does so eventually, but it is very unpredictable. After loading, it tends to be very slow and lags often. With the latest builds, the virtual keyboard does work, and it is possible to type in an address. Google loads in about 3 minutes on a 3G connection. Page is vibrant and well painted, but lag is still an issue. I have not been able to actually type in a search however, as it crashes before I am able to. At some times, these crashes will crash the whole phone.

==WILLCOM 03==

This device is Windows Mobile 6.1 Classic Japanese device with 520MHz processor and 128MB RAM and 256 MB ROM.

http://www.sharp.co.jp/ws/020sh/spec/index.html

We test with TrueType fonts and settings to use it for content/chrome to show multi-byte chars.

Fennec alpha 1 takes about 30 secs to start and takes about 5~10 sec to load simple page like google search results.
Sunspider result: [[http://people.mozilla.com/~dynamis/fennec/screenshots/wince/alpha1/sunspider%20result%20virtical.png 87183ms total]]

You can see more and more screenshots here;
http://people.mozilla.com/~dynamis/fennec/screenshots/wince/alpha1/

==Toshiba dynapocket==

This is the most powerful device in the world so far.

This device is Windows Mobile 6.1 Professional device with 4.1-inch WVGA touchscreen and Qualcomm’s 1GHz Snapdragon QSD2850 processor.

http://www.toshiba.co.jp/product/etsg/cmt/docomo/t-01a/t-01a_menu.htm
http://www.markstechnologynews.com/2009/02/toshiba-tg01-41-inch-touchscreen.html
http://t-01a.windows-keitai.com/?T-01A%2F%E5%8B%95%E7%94%BB%E3%81%A7%E3%81%BF%E3%82%8B%2F%E6%B5%B7%E5%A4%96%E3%82%B5%E3%82%A4%E3%83%88%E3%81%A7%E3%81%AE%E3%83%AC%E3%83%93%E3%83%A5%E3%83%BC

Model number is T-01A for NTT docomo in Japan.

Evangelism/WebsiteCompatibilityInternational

2009-03-06T08:20:15Z

Dynamis: /* Feedback */

International Web Site Compatibility and Tech Evangelism

= Goal =

To improve Firefox website compatibility and the use of open standards outside
of the US and Europe.

= Strategy =

Take the data that's being collected in reporter and use it as a lever to improve website compatibility for Firefox and open standards-based development. Invite local volunteers to use reports for their countries as a way to help websites in those countries improve compatibility. Give them the tools to be able to work together on these problems. Inform our localization contacts of this as a resource and offer them help in building communities around testing and compatibility.

= Stakeholders for Feedback =

* justin
* sethb
* asa
* chofmann
* robert accettura
* kenk
* morgamic
* beltzner
* arun
* jay
* jane
* gen, dynamis, kohei
* li, jack
* djst
* (india?)

= Overall Plan =

== Stage One ==

* <strike>Open up communications for the Evangelism team. Start using the external mailing list on a regular basis including posting plans such as this one. Have an open irc channel for people who want to join up with us (#devrel.) </strike>
* <strike>Talk with Ken to identify key data elements, output and key metrics that can help us drive change.</strike>
* <strike>Scope out changes to reporter to support per-country information.</strike> (Turns out reporter already records locale information.)
* Scope out changes to Firefox to support voluntary per-country information to improve fidelity.
* Scope out changes to support geoip support so we can get country information.

== Stage Two ==

* Look at the current reporter database to see if there are any changes required to improve scaling with today's data
* Set up a dashboard of reports that include:
** Number of daily reports (total)
** Number of daily reports (per-browser)
** Per-country reports (total)
** Per-country reports vs. local market share
** Top 10 sites per country (zeitgeist-style)
* Expose this information to the public to help drive awareness and value of the data.

== Stage Three ==

* From first set of data and scoping from stage one, execute on changes to Firefox to improve data fidelity.
* Involve support in this process to see if there are things that can improve end user support.

== Stage Four ==

* Start inviting localizers to start listing places that they know about.
* Set up a wiki place for this stuff to live on developer.mozilla.org including per-country pages.
* Look at setting up per-country mailing lists for evangelism or ways we can manage that through the wiki. (What does localization do?)
* Identify leads in every country to lead efforts.
* Identify and localize docs required to launch a larger effort in identified countries.
* Identify a set of docs that local people can use to describe tech evangelism issues.

== Stage Five ==

* From local communities see if there are "expert tools" (add-ons) that we can create that will allow those communities to do focused testing.

== Stage Six ==

* Look at outreach through PR and Marketing in various countries once we have data on particular countries and a local community to handle questions, community development and press.

= Metrics =

== How many leaders we have in various countries and if they are able to run an effective program for local website compatibility? ==

This is more about local leadership than anything else. Are we giving them good materials? Are we giving them good data they can work against?

== Number of compatibility problems reported per-country? ==

We can compare reporting information with top-site information on a per country basis to determine how deep into various countries we're getting and how compatible we are with top content in any particular geography.

== Market share results? ==

Does increased compatibility turn into increased market share in a particular market? Does building a local team to handle compatibility also drive awareness, PR and market share as a result of word of mouth work?

== Does this give us more tools for end-user support around the world? ==

It turns out that we can use this data to help end users solve support problems at both an aggregate level but also at a local "I'm having problems with this website" level. We also might be able to use this data directly in Firefox to display reported problems to users with a particular site if and when they use the broken site reporter tool.

= WebDev Work Items =

* Update schema to include most recent version information for reports
** might be saved in the database already when reported by the client but not exposed in the interface
* Schema analysis to support l10n
** The data is currently storing locale information
** Would be good to gather geoip information since locale doesn't reflect country
** Not sure if the description is unicode-safe
* Rewriting reporter templates to support gettext in static files
* Schema changes if needed, including modifying service and front-end to work with new schema
* Database optimization and performance tuning as needed
* Front-end scaling (yslow scores) and visual refresh
* Load testing, QA, and Unit Tests

= Firefox Work Items =

* Iterate to see when people are using Report Broken Website when they shouldn't be or what it's teaching us about how people are using the browser.
* Work with metrics, webdev + evangelism to see if the form in the browser should be updated.
* Take part in metrics design to understand if changes are helping users or not.

= Community Building Exercises =

* Can run a simple testing day to report broken web sites for a release and/or a beta. Could use that data in conjunction with the RRRT to see if things pop up as important around the world.
* Can offer an extension that offers more capabilities for local power testers. For example, could keep a list of urls that we generate from the top 1000 sites for a particular country and have you be "responsible" for testing those sites and reporting problems. Reports from those people would include more information about possible solutions.
* Good way for localizers to get involved and build larger communities of their own.
* Need to have a site for particular country people to get organized and involved. (Or let them develop them on their own in the MCS model or use local social networking sites? They very a _lot_ per-country.)
* Recognize "power testers" on a testing site per-country as special for the work that they do. "tested 100 sites", etc.
* Offer the ability via an extension to have a list of urls and sites you need to test on your corporate intranet.

= Observations and Ideas =

* There might be more than one type of user using this - end users vs. technical users vs. testers. Do those individual users have different needs when reporting broken web sites?
* Lots of reports do include "I tested this in another browser and it does work" - might want to make that an easy to use checkbox in the interface for reporting a broken web site.
* The most reported site in the US was google. Lots of people are reporting that the safe browsing screen is "broken". Interesting, that.
* Locale has very little to do with actual country. Would be good to use geoip information and/or ask in the interface for country information to improve fidelity. Need to be clear in privacy on this.
* Allow web sites to get an RSS feed for reports about their site. Get them involved directly.
** Also could do something like "live feed for top 100 sites in the US" for testing team and RRRT

= Feedback =
* Consider more '''direct''' outreach campaigns from the start of Stage 1. There is likely a web developer audience in non-US/European locales that need to join our campaign from step one. (sethb)
* Stage 4 asks to reach out to localizers. Consider expanding this to all constituents relevant in local markets. This includes localizers, campus reps, fans of Firefox, conference organizers, known web developer or other industry contacts, government contacts, etc. (sethb)
** Would love help on figuring out how to do these two. I would like it, too, assuming we're committed to doing this but I don't have a sense of how to do it. Looking for advice and help. (blizzard)
* Consider a tool a bit more dynamic than a wiki to capture websites that need evangelizing. Perhaps a simple web app with a database collecting information and then a great way to display it. Would this be hard? Don't know... (sethb)
** The reporter site can do this and won't be a wiki. It's entirely data driven. Here's an example of a report for www.google.com for one day: http://tinyurl.com/c3rz4s
* Should look into combining information with herdict: http://futureoftheinternet.org/herdict-launch - lots of good visualization and data ideas here. (blizzard)
* As for Reporter addons, people think that their report will be checked and used by Mozilla. They don't know how to search the database. They also don't know they can see the reports on http://reporter.mozilla.org/. This is because reporter UI don't tell "you can see your report here" nor "you can search reports here". I think if reporter include such a information (link to search interface or metrics), locale web evangelism community will know about it and start using it. That is, if we want to develop local evangelist team, we should update reporter UI to make people know how to see the reports. (dynamis)
** of course, we should prepare introduction page for search page, top 10 sites (per locale), and other metrics and should link to the page from reporter addons UI. (dynamis)
* As for type of the problem, in Japan (and I believe in China, Korea etc too) mojibake (garbage text) is the most famous broken case (caused by lack or miss of charset in the content type header). I thinks it's nice to add mojibake in the type list in the reporter (at least for multibyte locales). (dynamis)
* Some problems are caused by addons and reporter should also include installed addons list (not only build config). (dynamis)

Evangelism/WebsiteCompatibilityInternational

2009-03-06T08:15:45Z

Dynamis: /* Feedback */

Evangelism/WebsiteCompatibilityInternational

2009-03-06T08:07:04Z

Dynamis: /* Feedback */

International Web Site Compatibility and Tech Evangelism

= Goal =

To improve Firefox website compatibility and the use of open standards outside
of the US and Europe.

= Strategy =

Take the data that's being collected in reporter and use it as a lever to improve website compatibility for Firefox and open standards-based development. Invite local volunteers to use reports for their countries as a way to help websites in those countries improve compatibility. Give them the tools to be able to work together on these problems. Inform our localization contacts of this as a resource and offer them help in building communities around testing and compatibility.

= Stakeholders for Feedback =

* justin
* sethb
* asa
* chofmann
* robert accettura
* kenk
* morgamic
* beltzner
* arun
* jay
* jane
* gen, dynamis, kohei
* li, jack
* djst
* (india?)

= Overall Plan =

== Stage One ==

* <strike>Open up communications for the Evangelism team. Start using the external mailing list on a regular basis including posting plans such as this one. Have an open irc channel for people who want to join up with us (#devrel.) </strike>
* <strike>Talk with Ken to identify key data elements, output and key metrics that can help us drive change.</strike>
* <strike>Scope out changes to reporter to support per-country information.</strike> (Turns out reporter already records locale information.)
* Scope out changes to Firefox to support voluntary per-country information to improve fidelity.
* Scope out changes to support geoip support so we can get country information.

== Stage Two ==

* Look at the current reporter database to see if there are any changes required to improve scaling with today's data
* Set up a dashboard of reports that include:
** Number of daily reports (total)
** Number of daily reports (per-browser)
** Per-country reports (total)
** Per-country reports vs. local market share
** Top 10 sites per country (zeitgeist-style)
* Expose this information to the public to help drive awareness and value of the data.

== Stage Three ==

* From first set of data and scoping from stage one, execute on changes to Firefox to improve data fidelity.
* Involve support in this process to see if there are things that can improve end user support.

== Stage Four ==

* Start inviting localizers to start listing places that they know about.
* Set up a wiki place for this stuff to live on developer.mozilla.org including per-country pages.
* Look at setting up per-country mailing lists for evangelism or ways we can manage that through the wiki. (What does localization do?)
* Identify leads in every country to lead efforts.
* Identify and localize docs required to launch a larger effort in identified countries.
* Identify a set of docs that local people can use to describe tech evangelism issues.

== Stage Five ==

* From local communities see if there are "expert tools" (add-ons) that we can create that will allow those communities to do focused testing.

== Stage Six ==

* Look at outreach through PR and Marketing in various countries once we have data on particular countries and a local community to handle questions, community development and press.

= Metrics =

== How many leaders we have in various countries and if they are able to run an effective program for local website compatibility? ==

This is more about local leadership than anything else. Are we giving them good materials? Are we giving them good data they can work against?

== Number of compatibility problems reported per-country? ==

We can compare reporting information with top-site information on a per country basis to determine how deep into various countries we're getting and how compatible we are with top content in any particular geography.

== Market share results? ==

Does increased compatibility turn into increased market share in a particular market? Does building a local team to handle compatibility also drive awareness, PR and market share as a result of word of mouth work?

== Does this give us more tools for end-user support around the world? ==

It turns out that we can use this data to help end users solve support problems at both an aggregate level but also at a local "I'm having problems with this website" level. We also might be able to use this data directly in Firefox to display reported problems to users with a particular site if and when they use the broken site reporter tool.

= WebDev Work Items =

* Update schema to include most recent version information for reports
** might be saved in the database already when reported by the client but not exposed in the interface
* Schema analysis to support l10n
** The data is currently storing locale information
** Would be good to gather geoip information since locale doesn't reflect country
** Not sure if the description is unicode-safe
* Rewriting reporter templates to support gettext in static files
* Schema changes if needed, including modifying service and front-end to work with new schema
* Database optimization and performance tuning as needed
* Front-end scaling (yslow scores) and visual refresh
* Load testing, QA, and Unit Tests

= Firefox Work Items =

* Iterate to see when people are using Report Broken Website when they shouldn't be or what it's teaching us about how people are using the browser.
* Work with metrics, webdev + evangelism to see if the form in the browser should be updated.
* Take part in metrics design to understand if changes are helping users or not.

= Community Building Exercises =

* Can run a simple testing day to report broken web sites for a release and/or a beta. Could use that data in conjunction with the RRRT to see if things pop up as important around the world.
* Can offer an extension that offers more capabilities for local power testers. For example, could keep a list of urls that we generate from the top 1000 sites for a particular country and have you be "responsible" for testing those sites and reporting problems. Reports from those people would include more information about possible solutions.
* Good way for localizers to get involved and build larger communities of their own.
* Need to have a site for particular country people to get organized and involved. (Or let them develop them on their own in the MCS model or use local social networking sites? They very a _lot_ per-country.)
* Recognize "power testers" on a testing site per-country as special for the work that they do. "tested 100 sites", etc.
* Offer the ability via an extension to have a list of urls and sites you need to test on your corporate intranet.

= Observations and Ideas =

* There might be more than one type of user using this - end users vs. technical users vs. testers. Do those individual users have different needs when reporting broken web sites?
* Lots of reports do include "I tested this in another browser and it does work" - might want to make that an easy to use checkbox in the interface for reporting a broken web site.
* The most reported site in the US was google. Lots of people are reporting that the safe browsing screen is "broken". Interesting, that.
* Locale has very little to do with actual country. Would be good to use geoip information and/or ask in the interface for country information to improve fidelity. Need to be clear in privacy on this.
* Allow web sites to get an RSS feed for reports about their site. Get them involved directly.
** Also could do something like "live feed for top 100 sites in the US" for testing team and RRRT

= Feedback =
* Consider more '''direct''' outreach campaigns from the start of Stage 1. There is likely a web developer audience in non-US/European locales that need to join our campaign from step one. (sethb)
* Stage 4 asks to reach out to localizers. Consider expanding this to all constituents relevant in local markets. This includes localizers, campus reps, fans of Firefox, conference organizers, known web developer or other industry contacts, government contacts, etc. (sethb)
** Would love help on figuring out how to do these two. I would like it, too, assuming we're committed to doing this but I don't have a sense of how to do it. Looking for advice and help. (blizzard)
* Consider a tool a bit more dynamic than a wiki to capture websites that need evangelizing. Perhaps a simple web app with a database collecting information and then a great way to display it. Would this be hard? Don't know... (sethb)
** The reporter site can do this and won't be a wiki. It's entirely data driven. Here's an example of a report for www.google.com for one day: http://tinyurl.com/c3rz4s
* Should look into combining information with herdict: http://futureoftheinternet.org/herdict-launch - lots of good visualization and data ideas here. (blizzard)
* As for Reporter addons, people think that their report will be checked and used my Mozilla. They don't know how to search the database. They also don't know they can see the reports on http://reporter.mozilla.org/. This is because reporter UI don't tell "you can see your report here" nor "you can search reports here". I think if reporter include such a information (link to search interface or metrics), locale web evangelism community will know about it and start using it. That is, if we want to develop local evangelist team, we should update reporter UI to make people know how to see the reports. (dynamis)
** of course, we should prepare introduction page for search page, top 10 sites (per locale), and other metrics and should link to the page from reporter addons UI. (dynamis)
* As for type of the problem, in Japan (and I believe in China, Korea etc too) mojibake (garbage text) is the most famous broken case (caused by lack or miss of charset in the content type header). I thinks it's nice to add mojibake in the type list in the reporter (at least for multibyte locales). (dynamis)

Evangelism/WebsiteCompatibilityInternational

2009-03-06T07:58:00Z

Dynamis: /* Feedback */

International Web Site Compatibility and Tech Evangelism

= Goal =

To improve Firefox website compatibility and the use of open standards outside
of the US and Europe.

= Strategy =

Take the data that's being collected in reporter and use it as a lever to improve website compatibility for Firefox and open standards-based development. Invite local volunteers to use reports for their countries as a way to help websites in those countries improve compatibility. Give them the tools to be able to work together on these problems. Inform our localization contacts of this as a resource and offer them help in building communities around testing and compatibility.

= Stakeholders for Feedback =

* justin
* sethb
* asa
* chofmann
* robert accettura
* kenk
* morgamic
* beltzner
* arun
* jay
* jane
* gen, dynamis, kohei
* li, jack
* djst
* (india?)

= Overall Plan =

== Stage One ==

* <strike>Open up communications for the Evangelism team. Start using the external mailing list on a regular basis including posting plans such as this one. Have an open irc channel for people who want to join up with us (#devrel.) </strike>
* <strike>Talk with Ken to identify key data elements, output and key metrics that can help us drive change.</strike>
* <strike>Scope out changes to reporter to support per-country information.</strike> (Turns out reporter already records locale information.)
* Scope out changes to Firefox to support voluntary per-country information to improve fidelity.
* Scope out changes to support geoip support so we can get country information.

== Stage Two ==

* Look at the current reporter database to see if there are any changes required to improve scaling with today's data
* Set up a dashboard of reports that include:
** Number of daily reports (total)
** Number of daily reports (per-browser)
** Per-country reports (total)
** Per-country reports vs. local market share
** Top 10 sites per country (zeitgeist-style)
* Expose this information to the public to help drive awareness and value of the data.

== Stage Three ==

* From first set of data and scoping from stage one, execute on changes to Firefox to improve data fidelity.
* Involve support in this process to see if there are things that can improve end user support.

== Stage Four ==

* Start inviting localizers to start listing places that they know about.
* Set up a wiki place for this stuff to live on developer.mozilla.org including per-country pages.
* Look at setting up per-country mailing lists for evangelism or ways we can manage that through the wiki. (What does localization do?)
* Identify leads in every country to lead efforts.
* Identify and localize docs required to launch a larger effort in identified countries.
* Identify a set of docs that local people can use to describe tech evangelism issues.

== Stage Five ==

* From local communities see if there are "expert tools" (add-ons) that we can create that will allow those communities to do focused testing.

== Stage Six ==

* Look at outreach through PR and Marketing in various countries once we have data on particular countries and a local community to handle questions, community development and press.

= Metrics =

== How many leaders we have in various countries and if they are able to run an effective program for local website compatibility? ==

This is more about local leadership than anything else. Are we giving them good materials? Are we giving them good data they can work against?

== Number of compatibility problems reported per-country? ==

We can compare reporting information with top-site information on a per country basis to determine how deep into various countries we're getting and how compatible we are with top content in any particular geography.

== Market share results? ==

Does increased compatibility turn into increased market share in a particular market? Does building a local team to handle compatibility also drive awareness, PR and market share as a result of word of mouth work?

== Does this give us more tools for end-user support around the world? ==

It turns out that we can use this data to help end users solve support problems at both an aggregate level but also at a local "I'm having problems with this website" level. We also might be able to use this data directly in Firefox to display reported problems to users with a particular site if and when they use the broken site reporter tool.

= WebDev Work Items =

* Update schema to include most recent version information for reports
** might be saved in the database already when reported by the client but not exposed in the interface
* Schema analysis to support l10n
** The data is currently storing locale information
** Would be good to gather geoip information since locale doesn't reflect country
** Not sure if the description is unicode-safe
* Rewriting reporter templates to support gettext in static files
* Schema changes if needed, including modifying service and front-end to work with new schema
* Database optimization and performance tuning as needed
* Front-end scaling (yslow scores) and visual refresh
* Load testing, QA, and Unit Tests

= Firefox Work Items =

* Iterate to see when people are using Report Broken Website when they shouldn't be or what it's teaching us about how people are using the browser.
* Work with metrics, webdev + evangelism to see if the form in the browser should be updated.
* Take part in metrics design to understand if changes are helping users or not.

= Community Building Exercises =

* Can run a simple testing day to report broken web sites for a release and/or a beta. Could use that data in conjunction with the RRRT to see if things pop up as important around the world.
* Can offer an extension that offers more capabilities for local power testers. For example, could keep a list of urls that we generate from the top 1000 sites for a particular country and have you be "responsible" for testing those sites and reporting problems. Reports from those people would include more information about possible solutions.
* Good way for localizers to get involved and build larger communities of their own.
* Need to have a site for particular country people to get organized and involved. (Or let them develop them on their own in the MCS model or use local social networking sites? They very a _lot_ per-country.)
* Recognize "power testers" on a testing site per-country as special for the work that they do. "tested 100 sites", etc.
* Offer the ability via an extension to have a list of urls and sites you need to test on your corporate intranet.

= Observations and Ideas =

* There might be more than one type of user using this - end users vs. technical users vs. testers. Do those individual users have different needs when reporting broken web sites?
* Lots of reports do include "I tested this in another browser and it does work" - might want to make that an easy to use checkbox in the interface for reporting a broken web site.
* The most reported site in the US was google. Lots of people are reporting that the safe browsing screen is "broken". Interesting, that.
* Locale has very little to do with actual country. Would be good to use geoip information and/or ask in the interface for country information to improve fidelity. Need to be clear in privacy on this.
* Allow web sites to get an RSS feed for reports about their site. Get them involved directly.
** Also could do something like "live feed for top 100 sites in the US" for testing team and RRRT

= Feedback =
* Consider more '''direct''' outreach campaigns from the start of Stage 1. There is likely a web developer audience in non-US/European locales that need to join our campaign from step one. (sethb)
* Stage 4 asks to reach out to localizers. Consider expanding this to all constituents relevant in local markets. This includes localizers, campus reps, fans of Firefox, conference organizers, known web developer or other industry contacts, government contacts, etc. (sethb)
** Would love help on figuring out how to do these two. I would like it, too, assuming we're committed to doing this but I don't have a sense of how to do it. Looking for advice and help. (blizzard)
* Consider a tool a bit more dynamic than a wiki to capture websites that need evangelizing. Perhaps a simple web app with a database collecting information and then a great way to display it. Would this be hard? Don't know... (sethb)
** The reporter site can do this and won't be a wiki. It's entirely data driven. Here's an example of a report for www.google.com for one day: http://tinyurl.com/c3rz4s
* Should look into combining information with herdict: http://futureoftheinternet.org/herdict-launch - lots of good visualization and data ideas here. (blizzard)
* As for Reporter addons, people think that their report will be checked and used my Mozilla. They don't know how to search the database. They also don't know they can see the reports on http://reporter.mozilla.org/. This is because reporter UI don't tell "you can see your report here" nor "you can search reports here". I think if reporter include such a information (link to search interface or metrics), locale web evangelism community will know about it and start using it. That is, if we want to develop local evangelist team, we should update reporter UI to make people know how to see the reports. (dynamis)

Labs/Ubiquity/i18n

2009-02-27T06:23:30Z

Dynamis:

= Participation =

* [http://groups.google.com/group/ubiquity-i18n ubiquity-i18n Google Group/mailing list] - for the discussion of internationalization and localization issues
* [irc://irc.mozilla.org/ubiquity #ubiquity irc.mozilla.org] - Live internet relay chat discussion.
* [[User:Mitcho/ResearchTopics|Research topics]] - future research and blog topics in the Ubiquity + i18n realm. Feel free to blog on or discuss these and other topics!
* [https://ubiquity.mozilla.com/trac/report/1 Issue Tracker] - Used to report/discuss bugs and submit patches for Ubiquity.

= Meetings =
* [https://wiki.mozilla.org/Labs/Ubiquity/Meetings Meeting notes & times]

= Resources =

== Proposals ==

* [http://mitcho.com/blog/projects/how-natural-should-a-natural-interface-be/ Towards a "natural syntax"]
* [http://jonoscript.wordpress.com/2009/01/24/overlord-verbs-a-proposal/ Overlord verbs]
* [http://mitcho.com/blog/projects/writing-commands-with-semantic-roles/ Writing commands with semantic roles]

== Notes ==

* [http://jonoscript.wordpress.com/2008/07/21/language-based-interfaces-part-1-the-problem/ Language-based interfaces part 1: the problem]
* [http://jonoscript.wordpress.com/2008/07/26/why-verbs/ Why verbs?]
* [http://jonoscript.wordpress.com/2008/10/01/%E3%83%90%E3%83%93%E3%83%AB%E3%81%AE%E5%A1%94/ Jono on the current Japanese parser]

== Documentation ==

* [[Labs/Ubiquity/Parser_Documentation|Parser documentation]]
* [[Labs/Ubiquity/Ubiquity_0.1_Localization_Tutorial|Localization (writing your own parser) tutorial]]

== Particular language focus/proposals ==

* [http://mitcho.com/blog/projects/ubiquity-in-firefox-japanese/ Ubiquity in Firefox: Focus on Japanese]

Mobile/Build/Windows Mobile Build Instructions

2009-01-09T02:23:27Z

Dynamis: /* Debugging Fennec */

Windows Mobile Build Instructions

= work in progress - things are changing as we speak, er.. as you read this =

==Overview==
This page describes the commands for building the latest version of the Windows Mobile XULRunner application using either Visual Studio 2005 or Visual Studio 2008 and the MozillaBuild environment.

'''These instructions are changing frequently.''' The Windows Mobile build of XULRunner and Mobile Fennec is undergoing major improvements and bug fixes. Do not be surprised if your attempt to build and/or run do not immediately work.

People focused on the Windows Mobile build are currently using the [irc://irc.mozilla.org/#wince #wince channel] to communicate about Windows Mobile build-specific issues.

'''Did we mention that things are changing frequently?'''

===Big Picture===
Here is a big-picture view of the steps needed to prepare a new PC for debugging the Windows Mobile Fennec and/or a Windows Mobile ZULRunner application.

* '''One-Time Setup''', including:
** Install Visual Studio 2008 Professional (VS9) or Visual Studio 2005 Professional (VS8)
** Install Windows Mobile 6 Professional SDK
** Install Windows Mobile 6.1 Localized Emulator Images
** Install Mozilla Build Tools
** [Optional] Download and Install Latest Mercurial

* '''Prepare To Build'''
** Download (or update) Sources and Patch Queue
** Download and/or Create Your MOZCONFIG File

* '''Build'''

* '''Debugging'''
** Prepare for Debugging
** Start Debugging

Still interested? OK, let's get started.

==One-Time Setup==

You will only have to do this setup once.

Only Visual Studio 2005 (also known as Visual Studio 8, or VS8) and Visual Studio 2008 (also known as Visual Studio 9, or VS9) are currently supported.

Visual Studio 2008 Express Edition does NOT work for building, because the Windows Mobile SDK Installer will not successfully complete with only Visual Studio 2008 Express installed.

You will need to install your Visual Studio version before continuing with these instructions.

Follow the [http://developer.mozilla.org/en/docs/Windows_Build_Prerequisites#MozillaBuild instructions here] to setup a windows development environment.

Because the Windows Mobile build uses a patch queue, you must [http://hgbook.red-bean.com/hgbookch12.html#x16-26700012 turn on the mercurial queues extension].

Then you need to [http://www.microsoft.com/downloads/details.aspx?familyid=06111A3A-A651-4745-88EF-3D48091A390B&displaylang=en install] the Windows Mobile 6 Professional SDK (WM6 Pro SDK). To resolve dependencies in the installation of the Windows Mobile 6 Professional SDK, you might need to install some extra software. In this case, the WM6 Pro SDK Installation program will tell you what software you need to install.

You will also need to download and install the [http://www.microsoft.com/downloads/details.aspx?familyid=3D6F581E-C093-4B15-AB0C-A2CE5BFFDB47&displaylang=en Windows Mobile 6.1 Professional Localized Emulator Images].

===WM6.1 Emulator Images IMPORTANT NOTE===
(by wolfe in [irc://irc.mozilla.org/%23wince #wince IRC])

You NEED to install the WM6.1 Emulator Images, because Microsoft fixed something in between 6.0 and 6.1 - so now the specification of memory size via the Emulator Options dialog box works.

You will need to increase the amount of memory available in your chosen 6.1 Emulator (BEFORE you run the chosen 6.1 Emulator for the first time). Otherwise you'll receive "(e)", or "not enough storage is available to complete this operation".

You can increase the amount of memory in your emulator by using the VS8 tools menu, options dialog box.

Find the device tools | devices section, select your desired emulator, click on the properties... button, then press the Emulator Options... button

Once you are looking at the Emulator Options dialog box, check the Specify RAM Size check box - and enter in 256 - the acceptable range for this number is from 1 to 256.

BUT - BUT - BUT - The Emulator built into Visual Studio 2005 / VS8 does not work for mapping a local directory on your PC into the Emulator's \Storage Card (or \Storage Card2).

I have been told that the WM6.1 Emulator Images install fixes BOTH VS8's and VS9's mapping of a local directory into your Emulator as a Shared Directory.

SO - If you want to debug via Emulator, you NEED the Windows Mobile 6.1 Emulator Images.

If you use VS9, you need a minimum of the Visual Studio 2008 Professional version, because the VS9 Express version does not allow the WinMobile 6 SDKs to be installed.

Bottom Line - use VS8 Pro or VS9 Pro AND WM6.1 Emulator Images.

==Prepare To Build==

These directions assume you have created a '''c:\mozilla-build''' directory,
created by downloading and installing the
[[http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-1.3.exe Windows Mozilla Build Setup version 1.3]].

===Mercurial Version In Mozilla-Build version 1.3===
NOTE: As of 20-Nov-2008, Mozilla Build Setup version 1.3 includes a slightly stale
version of Mercurial (version 1.0.1+20080525). The latest Mercurial has a version
number of 1.1+20081203.
The latest Mercurial is downloadable directly from [http://www.selenic.com/mercurial/wiki/index.cgi/Download Selenic's Web Site].

In order to use the latest Mercurial, you have two basic choices:

(1) Remove the c:/mozilla-build/hg directory, and replace it with the contents of
C:/Program Files/Mercurial after you have installed the latest download from Selenic.

(2) Go into c:/mozilla-build/msys/etc/profiles.d/profile-extrapaths.sh and modify
the /c/mozilla-build/hg directory to say /c/Program Files/Mercurial

You can try updating to the latest version of Mercurial if you have troubles with hg.exe

===Downloading The Sources And Patch Queue===

Run the batch file '''C:\mozilla-build\start-msvc8.bat''' (or '''C:\mozilla-build\start-msvc9.bat''')
NOTE: This will setup and open a MingW32 command prompt.
All further commands are to be run inside MingW32.

$ '''cd /c/hg # assuming you've created /c/hg/ for your mozilla source tree'''

$ '''hg clone http://hg.mozilla.org/mozilla-central'''

$ '''cd mozilla-central'''

$ '''export topsrcdir=`pwd` # $topsrcdir becomes the path to mozilla-central/

$ '''hg clone http://hg.mozilla.org/mobile-browser mobile'''

$ '''wget http://people.mozilla.org/~blassey/mozconfig'''

$ '''cd .hg'''

$ '''hg clone http://hg.mozilla.org/users/blassey_mozilla.com/wince-patches patches'''

$ '''cd ..'''

$ '''export PATH="$PATH:$topsrcdir/build/wince/tools/bin"'''

====CRUD - The Clone of Mozilla-Central Freezes====

Several people have reported that the cloning of mozilla-central as described above freezes and does not complete.

If your clone of mozilla-central is taking more than an hour to complete, you may be in this same situation. Basically, this can be caused by a number of different situations:
* The Mozilla hg repository is overloaded,
* The Internet Connection you have is very slow and times out
* The Internet Connection you have drops enough packets that HG gets confused

As a point of reference, John Wolfe has a very fast RCN cable modem connection at home. However, he found out a while ago that RCN considers a 7% data loss to be within acceptable limits for customer service. 7% Data Loss (tested via pinging from an internal-to-RCN server to John Wolfe's cable modem) means that 7 out of every 100 packets gets ''lost''' within the RCN internal network.

This means that when RCN gets busy (nights and weekends, for instance), it is almost guaranteed that John Wolfe will not be able to do a full HG clone operation on the mozilla-central repository.

Here is what you can do to get around HG freezing when cloning mozilla-central:

# Download a [http://haqq.ws/mozilla/mc.bundle.2008_11_26 recent HG bundle]
(made on 26-Nov-08 after a new clone operation on mozilla-central)

# Create a new, empty mozilla-central repository:
$ '''cd /c/hg'''
$ '''hg init mozilla-central'''

# Un-bundle the real mozilla-central changes to that repository:
$ '''cd mozilla-central;'''
$ '''hg unbundle /path/to/mozilla-central.bundle/tip.tar.bz2'''

# Tell mercurial where you normally want to pull from by copying the
following content into your mozilla-central/.hg/hgrc file:

[paths]
default = http://hg.mozilla.org/mozilla-central/

# Pull any changes that happened since the bundle was created:
$ '''hg pull'''

# Update your working directory to the latest change:
$ '''hg update'''

NOTE: You will want to do two seperate operations for pulling then updating, as some versions of HG have a bug in their ''hg pull -u'' command. I forget exactly what the bug is - but the work-around is to do these two seperate operations.

Thanks go out to Benjamin Smedbergs for this solution - [http://benjamin.smedbergs.us/blog/2008-06-05/getting-mozilla-central-with-limited-bandwidth/ Original Blog Posting Here]

===Updating The Sources And Patch Queue===

Run the batch file '''C:\mozilla-build\start-msvc8.bat''' (or '''C:\mozilla-build\start-msvc9.bat''')
NOTE: This will setup and open a MingW32 command prompt.
All further commands are to be run inside MingW32.
This assumes you have a c:\hg\mozilla-central directory

$ '''cd /c/hg/mozilla-central'''

$ '''hg qpop -a'''

$ '''hg pull;hg update;'''

$ '''cd mobile'''

$ '''hg pull;hg update;'''

$ '''cd ../.hg/patches'''

$ '''hg pull;hg update;'''

$ '''cd ../..'''

===Setting Up Your MOZCONFIG File===

Building options are controlled by mozconfig, a master file within your top source directory (in our case, /c/hg/mozilla-central/mozconfig).

You need to create a MOZCONFIG file, since one is not included in the source code repositories. There are four options for Windows Mobile 6 development:

(1) Visual Studio 9 Debug Build
(2) Visual Studio 9 Release Build
(3) Visual Studio 8 Debug Build
(4) Visual Studio 8 Release Build

====VS9 Debug Build MOZCONFIG====
'''Here is our current VS9 mozconfig for building a Debug XULRunner and Fennec for WinMobile:'''

''# Options for client.mk.''
''mk_add_options MOZ_BUILD_PROJECTS="xulrunner mobile"''

''# Options for VS8 verses VS9 / Debug verses Release''
''# Debug/Non-Opt = ~28 MByte XUL.dll''
''# Debug/Opt = ~20 MByte XUL.dll''
''# Release/Opt = ~12 MByte XUL.dll''
''ac_add_options --enable-debug''
''#ac_add_options --disable-optimize''
''mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/objdir-wm6-dbg''
''MIDL=/c/Program\ Files/Microsoft\ Visual\ Studio\ 9/VC/ce/bin/x86_arm/midl.exe''

''# mobile options''
''ac_add_app_options mobile --enable-application=mobile''
''ac_add_app_options mobile --with-libxul-sdk=../xulrunner/dist''

''# Disabling tests due to bug 454881''
''ac_add_options --disable-tests''

''#WINCE specific options''
''ac_add_options --disable-javaxpcom''
''ac_add_options --disable-plugins''
''ac_add_options --disable-accessibility''
''ac_add_options --disable-printing''
''ac_add_options --disable-oji''
''ac_add_options --disable-vista-sdk-requirements''
''ac_add_options --disable-updater''
''ac_add_options --disable-installer''
''ac_add_options --disable-xpinstall''
''ac_add_options --enable-image-decoders="png gif jpeg"''
''ac_add_options --disable-dbm''

''CROSS_COMPILE=1''
''CC=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''CXX=$topsrcdir/build/wince/tools/bin/arm-wince-gcc ''
''CPP=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''LD=$topsrcdir/build/wince/tools/bin/arm-wince-link''
''AR=$topsrcdir/build/wince/tools/bin/arm-wince-lib''
''AS=$topsrcdir/build/wince/tools/bin/arm-wince-as''
''RC=$topsrcdir/build/wince/tools/bin/arm-wince-res''

''mk_add_options AR=@TOPSRCDIR@/build/wince/tools/bin/arm-wince-lib''

''ac_add_options --target=arm-wince''
''ac_add_options --enable-win32-target=WINCE''
''ac_add_options --enable-default-toolkit=cairo-windows''

''ac_add_options --with-wince-sdk="c:/program files/windows mobile 6 sdk/pocketpc/include/armv4i"''

====VS9 Release Build MOZCONFIG====

'''Here is our current VS9 mozconfig for building a non-debug XULRunner for WinMobile:'''

''# Options for client.mk.''
''mk_add_options MOZ_BUILD_PROJECTS="xulrunner"''

''# Options for VS8 verses VS9 / Debug verses Release''
''# Debug/Non-Opt = ~28 MByte XUL.dll''
''# Debug/Opt = ~20 MByte XUL.dll''
''# Release/Opt = ~12 MByte XUL.dll''
''#ac_add_options --enable-debug''
''ac_add_options --enable-optimize''
''mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/objdir-wm6-rel''
''MIDL=/c/Program\ Files/Microsoft\ Visual\ Studio\ 9/VC/ce/bin/x86_arm/midl.exe''

''# Disabling tests due to bug 454881''
''ac_add_options --disable-tests''

''#WINCE specific options''
''ac_add_options --disable-javaxpcom''
''ac_add_options --disable-plugins''
''ac_add_options --disable-accessibility''
''ac_add_options --disable-printing''
''ac_add_options --disable-oji''
''ac_add_options --disable-vista-sdk-requirements''
''ac_add_options --disable-updater''
''ac_add_options --disable-installer''
''ac_add_options --disable-xpinstall''
''ac_add_options --enable-image-decoders="png gif jpeg"''
''ac_add_options --disable-dbm''

''CROSS_COMPILE=1''
''CC=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''CXX=$topsrcdir/build/wince/tools/bin/arm-wince-gcc ''
''CPP=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''LD=$topsrcdir/build/wince/tools/bin/arm-wince-link''
''AR=$topsrcdir/build/wince/tools/bin/arm-wince-lib''
''AS=$topsrcdir/build/wince/tools/bin/arm-wince-as''
''RC=$topsrcdir/build/wince/tools/bin/arm-wince-res''

''mk_add_options AR=@TOPSRCDIR@/build/wince/tools/bin/arm-wince-lib''

''ac_add_options --target=arm-wince''
''ac_add_options --enable-win32-target=WINCE''
''ac_add_options --enable-default-toolkit=cairo-windows''

''ac_add_options --with-wince-sdk="c:/program files/windows mobile 6 sdk/pocketpc/include/armv4i"''

====VS8 Debug Build MOZCONFIG====

'''Here is our current VS8 mozconfig for building a Debug XULRunner and Fennec for WinMobile:'''

''# Options for client.mk.''
''mk_add_options MOZ_BUILD_PROJECTS="xulrunner mobile"''
''mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/objdir-wm6-dbg''

''# Options for VS8 verses VS9 / Debug verses Release''
''# Debug/Non-Opt = ~28 MByte XUL.dll''
''# Debug/Opt = ~20 MByte XUL.dll''
''# Release/Opt = ~12 MByte XUL.dll''
''ac_add_options --enable-debug''
''#ac_add_options --enable-optimize''
''mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/objdir-wm6-dbg-vs8''
''MIDL=/c/Program\ Files/Microsoft\ Visual\ Studio\ 8/VC/ce/bin/x86_arm/midl.exe''

''# mobile options''
''ac_add_app_options mobile --enable-application=mobile''
''ac_add_app_options mobile --with-libxul-sdk=../xulrunner/dist''

''# Disabling tests due to bug 454881''
''ac_add_options --disable-tests''

''#WINCE specific options''
''ac_add_options --disable-javaxpcom''
''ac_add_options --disable-plugins''
''ac_add_options --disable-accessibility''
''ac_add_options --disable-printing''
''ac_add_options --disable-oji''
''ac_add_options --disable-vista-sdk-requirements''
''ac_add_options --disable-updater''
''ac_add_options --disable-installer''
''ac_add_options --disable-xpinstall''
''ac_add_options --enable-image-decoders="png gif jpeg"''
''ac_add_options --disable-dbm''

''CROSS_COMPILE=1''
''CC=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''CXX=$topsrcdir/build/wince/tools/bin/arm-wince-gcc ''
''CPP=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''LD=$topsrcdir/build/wince/tools/bin/arm-wince-link''
''AR=$topsrcdir/build/wince/tools/bin/arm-wince-lib''
''AS=$topsrcdir/build/wince/tools/bin/arm-wince-as''
''RC=$topsrcdir/build/wince/tools/bin/arm-wince-res''

''MIDL=/c/Program\ Files/Microsoft\ Visual\ Studio\ 8/VC/ce/bin/x86_arm/midl.exe''

''mk_add_options AR=@TOPSRCDIR@/build/wince/tools/bin/arm-wince-lib''

''ac_add_options --target=arm-wince''
''ac_add_options --enable-win32-target=WINCE''
''ac_add_options --enable-default-toolkit=cairo-windows''

''ac_add_options --with-wince-sdk="c:/program files/windows mobile 6 sdk/pocketpc/include/armv4i"''

====VS8 Release Build MOZCONFIG====

'''Here is our current VS8 mozconfig for building a non-debug XULRunner for WinMobile:'''

''# Options for client.mk.''
''mk_add_options MOZ_BUILD_PROJECTS="xulrunner"''

''# Options for VS8 verses VS9 / Debug verses Release''
''# Debug/Non-Opt = ~28 MByte XUL.dll''
''# Debug/Opt = ~20 MByte XUL.dll''
''# Release/Opt = ~12 MByte XUL.dll''
''#ac_add_options --enable-debug''
''ac_add_options --enable-optimize''
''mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/objdir-wm6-rel-vs8''
''MIDL=/c/Program\ Files/Microsoft\ Visual\ Studio\ 8/VC/ce/bin/x86_arm/midl.exe''

''# Disabling tests due to bug 454881''
''ac_add_options --disable-tests''

''#WINCE specific options''
''ac_add_options --disable-javaxpcom''
''ac_add_options --disable-plugins''
''ac_add_options --disable-accessibility''
''ac_add_options --disable-printing''
''ac_add_options --disable-oji''
''ac_add_options --disable-vista-sdk-requirements''
''ac_add_options --disable-updater''
''ac_add_options --disable-installer''
''ac_add_options --disable-xpinstall''
''ac_add_options --enable-image-decoders="png gif jpeg"''
''ac_add_options --disable-dbm''

''CROSS_COMPILE=1''
''CC=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''CXX=$topsrcdir/build/wince/tools/bin/arm-wince-gcc ''
''CPP=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''LD=$topsrcdir/build/wince/tools/bin/arm-wince-link''
''AR=$topsrcdir/build/wince/tools/bin/arm-wince-lib''
''AS=$topsrcdir/build/wince/tools/bin/arm-wince-as''
''RC=$topsrcdir/build/wince/tools/bin/arm-wince-res''

''mk_add_options AR=@TOPSRCDIR@/build/wince/tools/bin/arm-wince-lib''

''ac_add_options --target=arm-wince''
''ac_add_options --enable-win32-target=WINCE''
''ac_add_options --enable-default-toolkit=cairo-windows''

''ac_add_options --with-wince-sdk="c:/program files/windows mobile 6 sdk/pocketpc/include/armv4i"''

==Build==

Now you can build xulrunner (and the mobile fennec code) using these commands:

$ '''cd /c/hg/mozilla-central'''

$ '''hg qpush -a'''

$ '''make -f client.mk build'''

===Copy MOZCE_SHUNT.DLL To BIN===
For Visual Studio 2005 (VS8), you can find the shunt DLL at:
/c/hg/mozilla-central/build/wince/shunt/build/vs8/mozce_shunt.dll

For Visual Studio 2008 (VS9), you can find the shunt DLL at:
/c/hg/mozilla-central/build/wince/shunt/build/vs9/mozce_shunt.dll

To debug fennec using VS8/9, you will have to copy mozce_shunt.dll into:
''$OBJDIR''\mobile\dist\bin\xulrunner
so that the .dll file is in the ''same directory'' as where xulrunner.exe is in.

Otherwise, you will receive a
:''Could not find 'XULRunner' (or one of its components). Make sure that the path and filename are correct and that all the required libraries are available.''
or
:''The file 'xulrunner' cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. If the problem persists, try reinstalling or restoring this file.''
error dialog if you try to run XULRunner.exe from a File Explorer.

The VS8 IDE will say that it is ''Unable to start program '\Storage Card\bin\xulrunner.exe'. An error occurred that usually indicates a corrupt installation (code 0x8007007e). If the problem persists, repair your Visual Studio installation via 'Add or Remove Programs' in Control Panel.''

Both of these rather cryptic messages try to tell you that an executable file (EXE or DLL) depends upon a DLL, and that DLL could not be found.

==Debugging==

===Debugging Fennec===
There is a bug in the way that Windows CE searches for executable files that means WinMobile can not search correctly for DLLs desired by xulrunner when launched by fennec.

There are three work-arounds to this problem, and you can select which work-around appeals to you the most:

(1) Copy all xulrunner files to the same directory as the fennec executable (NOTE: You should copy all files including subdirectories of xulrunner but some files like chrome/en-US.jar are already exists in the fennec directory. You should rename and edit them properly)

(2) Create shortcut of xulrunner "fennec.lnk" containing:
: 67#"\Storage Card\bin\xulrunner\xulrunner.exe" -app ..\application.ini
Of course you should chnage path according to your install path. NOTE: First number '67' is the bytes of following command line.

(3) Copy all xulrunner files to the \Windows directory on your device (NOTE: does not work unless your Windows Mobile device has a LOT of space - i.e. HTC Touch Diamond, GTC Touch Pro, others with > 192 MByte)

(4) Change your Registry's OEM Search Path string to add your xulrunner's bin directory. Further information for this option is available
[[http://msdn.microsoft.com/en-us/library/bb202759.aspx via Microsoft DevNetwork]]. Note that you will have to reboot your WinMobile device for a changed OEM Search Path to take effect.

===Visual Studio 2005 / Visual Studio 8 Debugging===
Visual Studio 2005 (VS8) has the following issues when debugging:

* VS8 is available for free from Microsoft, with is a great thing for part-time hackers.

* You can compile xulrunner and fennec, then copy the executables to a device and try running the executables.

* The main people working on WinMobile are using VS9 for compiling and debugging.

* VS8 Emulator's shared-directory driver does not work properly. If you try to use the Emulator supplied with VS8, you will receive LOTS of random errors and faults. You might be able to eventually get a good run of the xulrunner application, but you will also get very frustrated at the same time.

* To run / debug within a VS9 Emulator, you NEED to download and install the [[http://www.microsoft.com/downloads/details.aspx?familyid=3D6F581E-C093-4B15-AB0C-A2CE5BFFDB47&displaylang=en Microsoft Windows Mobile 6.1 Emulator Images]]

* Installing Windows Mobile 6.1 Professional Localized Emulator Images fixes the issue with Emulator Shared Directory use, allowing you to point your Emulator at your BIN directory for running your executables without needing to copy the executables.

* The WinMobile 6.1 Emulator Images installation also fixes a bug with setting the amount of memory within an Emulator Image.

===Visual Studio 2008 / Visual Studio 9 Debugging===
Visual Studio 2008 (VS9) has the following issues when debugging:

* If the Mozilla WinCE Shunt Library fails compiling with an error message about a missing CeGetCanonicalPathName() function, you will need to select the "Windows Mobile 6 Professional" platform in the VS9 IDE platform selection drop-down list box. On a brand-newly cloned source tree, VS9 selects a platform of Windows Mobile 2003.

* To run / debug within a VS9 Emulator, you NEED to download and install the [[http://www.microsoft.com/downloads/details.aspx?familyid=3D6F581E-C093-4B15-AB0C-A2CE5BFFDB47&displaylang=en Microsoft Windows Mobile 6.1 Emulator Images]]

* The WinMobile 6.1 Emulator Images installation updates the VS9 Emulator, fixing a bug with setting the amount of memory within an Emulator Image.

* The main people working on WinMobile use VS9 to run / debug in the emulator / debug on-device.

===Emulator Images===
To run / debug xulrunner and fennec, you will need to increase the amount of memory available to the WinMobile 6.1 Emulator Image in which you are running.

To increase the amount of memory available to your Windows Mobile 6.1 Localized Emulator Image, do the following within VS9:
* Pull down the Tools menu
* Select the Options... menu item
* Find the Device Tools section in the list on the left hand side
* Find and select the Devices sub-section
* Find and select the desired Emulator Image
* Press the Properties... button
* Press the Emulator Options... button
* Check the Specify RAM Size checkbox
* Enter a number greater than 192 (and less than or equal to 256) into the edit box.
* Press OK to close the Emulator Properties dialog box
* Press OK to close the Emulator Image dialog box
* Press OK to close the Options dialog box

* When you start up your Emulator Image, verify that you have the RAM you specified in the Emulator Properties dialog box.

* If your Emulator Image does not have the RAM you specified, you may need to make a new copy of the Emulator in order to correctly specify the RAM size available to your Emulator Image.

===On-Device Debugging===
Some devices ship with security settings turned on. All devices need to have development certificates loaded onto them before debugging.

====Putting Development Certificates On Your Device====
To set the development certificates into your device, copy the file ''C:\Program Files\Windows Mobile 6 SDK\Tools\Security\SDK Development Certificates\Certs.cab'' onto your device. Locate and run this CAB file using the device's File Explorer. Once this CAB file has been installed into your device, the device will be able to run all of the Visual Studio devlopment tools.

====Enabling RAPI Commands On Your Device====
To allow all RAPI (Remote API function calls from the desktop to your tethered, or connected, device) function calls to succeed, you may need to run a command from a DOS box on your PC. Run these commands once your device has the development certificates installed and you have your device connected to your PC:

C:\> '''cd "C:\Program Files\Windows Mobile 6 SDK\Tools\Smartphone\RapiSecurity"'''

C:\> '''RapiConfig.exe /P /M RapiAllowed.xml'''

Instead of running the RapiConfig.exe program, you can copy a Certificate Provisioning File (.CPF) to your device, and run the .CPF file just like you ran the Certs.cab file. Copy the file ''C:\Program Files\Windows Mobile 6 SDK\Tools\Smartphone\RapiSecurity\RapiAllow.cpf'' file onto your device. Locate and run this .CPF file using the device's File Explorer.

====Security Powertoy====
Microsoft provides a Security Powertoy application which allows mere mortals to manipulate the security settings on a device from a semi-friendly GUI.

WARNING: The Security Powertoy has the ability to completely mess up your device. Use this tool with extreme caution.

To use the Security Powertoy, run the "C:\Program Files\Windows Mobile 6 SDK\Tools\Security\Security Powertoy\SecCfgMgr.msi" installer. Once the installer has finished, there will be a shortcut created in your PC's Start Menu named "Security Configuration Manager".

====Putting XULRunner on a Device====
Thanks to Tim Zander for pointing out that no one ever explains how to get XULRunner onto a device.

NOTE: DO NOT FORGET to copy a mozce_shunt.dll executable from the TOPSRCDIR/build/wince/shunt/build/vs8 or TOPSRCDIR/build/wince/shunt/build/vs9 directory into the OBJDIR/dist/bin directory BEFORE copying the whole directory onto a external card or directly onto your device.

You currently (as of 10-Dec-2008) have two options for getting XULRunner on to a device:

(1) If your device takes a plug-in expansion card, copy the OBJDIR/dist/bin
directory on to a expansion card from your PC, then place that expansion
card into your device.

(2) If your device has a LOT of internal storage (i.e., the HTC Touch Diamond
has 4GBytes of internal storage), then you can teather your device to
your PC, and use ActiveSync's File Explorer to copy the OBJDIR/dist/bin
directory onto your device.

On my PC, the OBJDIR/dist/bin directory is located at c:\hg\mozilla-central\objdir-wm6-dbg\xulrunner\dist\bin, and is approximately 32 MBytes large.

Once you have the executables on your device, you can launch the executables via:

(A) The Visual Studio IDE (for debugging)
(B) Via RAPI remote execute command
(C) Via File Explorer on the device
(D) Via specially-created shortcut

====Creating Shortcut for XULRunner====
You can make a shortcut link to execute the command you want under Windows Mobile / WinCE. Here is how:

A Shortcut Link File is a text file with an extension .LNK with one line in a very particular format:

NN#THE_COMMAND_LINE_GOES_HERE

Where:

NN: Number of characters in the whole command line

THE_COMMAND_LINE_GOES_HERE: The actual command you would execute
(as if you were running in a DOS box on WinXP)

Some things to watch out for:

(1) It is a LOT safer to use a full path to your executable

(2) If the full path to your executable contains any spaces, you
HAVE to wrap the full path to your executable with double-quotes

(3) Any space not wrapped inside a double-quote will signal the OS that
an argument has ended and another argument is beginning

(4) If your arguments have spaces in them, again wrap the whole single
argument in double-quotes

Here is an example:

64#"\Program Files\MyDir\MyExe.exe" "First Argument" SecondArgument

There is also an app that you can use called [http://www.freewareppc.com/utilities/shortcutcreator.shtml ''Shortcut Creator''].

Place your newly created shortcut in \Windows\Start Menu\Programs (or one of its sub-folders). You MAY want to place your shortcut in the \Windows\Start Menu\Programs\Games folder, because WinMobile 6 does not automatically update the Start Menu's contents until its next reboot. However, each sub-directory of the Start menu is re-evaluated every time you open the corresponding folder in the Start menu.

===Setting Up MyBrowser===

A simple XULRunner application, MyBrowser, is used to test the XULRunner code.

[http://benjamin.smedbergs.us/xulrunner/mybrowser-0.2.2.xulapp Download the MyBrowser Application using this link.]

The XULApp file is a ZIP file with a number of files and directories. Further explanation of XULRunner and the XULApp format can be found [http://developer.mozilla.org/en/docs/Getting_started_with_XULRunner here.]

'''rename mybrowser-0.2.2.xulapp mybrowser-0.2.2.xulapp.zip'''

Unzip mybrowser-0.2.2.xulapp.zip into its own subdirectory,
while preserving it's ZIP file directory structure.

'''rename mybrowser-0.2.2.xulapp mybrowser'''

'''Edit mybrowser\application.ini''' file, replacing:
'''MaxVersion=1.8.0.*'''
with:
'''MaxVersion=1.9.*.*'''

'''copy -r mybrowser c:\mozilla\unicode\objdir-wm6-debug\dist\bin'''

===Setting Up Debugging of MyBrowser===

You can debug the MyBrowser XULapp from within Visual Studio by using the WinCE shunt Visual Studio Project, and adjusting the deployment device and executable to be run.

1. Open Visual Studio 2005 (Visual Studio 8) Integrated Development Environment (IDE)

2. Open the solution c:\mozilla\unicode\build\wince\shunt\build\vs8\mozce_shunt_static.sln

3. In the Solution Explorer, '''right mouse click on the mozce_shunt_static project'''

4. Select the '''Properties''' pop-up menu item

5. Under the configuration properties, highlight the '''Deployment''' section

6. Make the selected '''Deployment Device''' be '''"Windows Mobile 6 Standard Emulator"'''

7. Press the '''Apply''' button if necessary to save your new selection

8. Under the configuration properties, highlight the '''Debugging''' section

9. For '''Remote Executable''', enter '''\Storage Card\bin\xulrunner.exe'''

10. For '''Command Arguments''', enter '''-app mybrowser\application.ini'''

11. Press the '''Apply''' button if necessary to save your new selection

12. Close the Project Properties dialog box

===Actual Debugging===

You are now ready to begin debugging your XULRunner build.

1. From the Visual Studio 2005 '''Build''' menu, select the '''Deploy Solution''' menu item

2. Wait for your chosen Emulator to start

3. In the Emulator's '''File''' menu, select the '''Configure...''' menu item

4. Press the '''...''' button for the Shared Folder edit box

5. Select the '''c:\mozilla\unicode\objdir-wm6-debug\dist''' directory

6. Close the Emulator Properties dialog box by pressing the '''OK''' key

7. In the Visual Studio 2005's '''Debug''' menu, select the '''Start Debugging''' menu item

You should now see the Visual Studio begin a debugging session of XULRunner loading the MyBrowser XULApp.

==Other Tips==

'''1. Color scheme for MingW32 Command Line Prompt'''

I hated the default color scheme for the command prompt under MingW32 - so I changed it. Find the file c:\mozilla-build\msys\etc\profile, and edit the lines (toward the bottom) which export PS1, and make them say:

export PS1='\[\033]0;$MSYSTEM:\w\007
\033[34m\]\u@\h \[\033[31m\w\033[0m\]
$ '

This changed the directory color to something I could actually see against a white background.

'''3. Further Setting Up MingW32 Path'''

I get annoyed with continually adding the path to the Mercurial HG.EXE, as well as continually adding the path to the build's wince tools directory.

So I created a c:\mozilla-build\msys\etc\profile.d\profile-setup-hg.sh file, containing:

#!/bin/sh

export PATH="$PATH:/c/progra~1/Mercurial"

# This is an addition to get the shim cross-compile build tools into
# our path. - jvw 24-Apr-08
export PATH="$PATH:/c/hg/mozilla-central/build/wince/tools/bin"

This sets up my HG.EXE path, as well as the path to my WinCE build tools (arm-wince-as.exe, arm-wince-gcc.exe, arm-wince-lib.exe, and arm-wince-link.exe)

Mobile/Build/Windows Mobile Build Instructions

2009-01-09T02:06:28Z

Dynamis: /* Copy MOZCE_SHUNT.DLL To BIN */

Windows Mobile Build Instructions

= work in progress - things are changing as we speak, er.. as you read this =

==Overview==
This page describes the commands for building the latest version of the Windows Mobile XULRunner application using either Visual Studio 2005 or Visual Studio 2008 and the MozillaBuild environment.

'''These instructions are changing frequently.''' The Windows Mobile build of XULRunner and Mobile Fennec is undergoing major improvements and bug fixes. Do not be surprised if your attempt to build and/or run do not immediately work.

People focused on the Windows Mobile build are currently using the [irc://irc.mozilla.org/#wince #wince channel] to communicate about Windows Mobile build-specific issues.

'''Did we mention that things are changing frequently?'''

===Big Picture===
Here is a big-picture view of the steps needed to prepare a new PC for debugging the Windows Mobile Fennec and/or a Windows Mobile ZULRunner application.

* '''One-Time Setup''', including:
** Install Visual Studio 2008 Professional (VS9) or Visual Studio 2005 Professional (VS8)
** Install Windows Mobile 6 Professional SDK
** Install Windows Mobile 6.1 Localized Emulator Images
** Install Mozilla Build Tools
** [Optional] Download and Install Latest Mercurial

* '''Prepare To Build'''
** Download (or update) Sources and Patch Queue
** Download and/or Create Your MOZCONFIG File

* '''Build'''

* '''Debugging'''
** Prepare for Debugging
** Start Debugging

Still interested? OK, let's get started.

==One-Time Setup==

You will only have to do this setup once.

Only Visual Studio 2005 (also known as Visual Studio 8, or VS8) and Visual Studio 2008 (also known as Visual Studio 9, or VS9) are currently supported.

Visual Studio 2008 Express Edition does NOT work for building, because the Windows Mobile SDK Installer will not successfully complete with only Visual Studio 2008 Express installed.

You will need to install your Visual Studio version before continuing with these instructions.

Follow the [http://developer.mozilla.org/en/docs/Windows_Build_Prerequisites#MozillaBuild instructions here] to setup a windows development environment.

Because the Windows Mobile build uses a patch queue, you must [http://hgbook.red-bean.com/hgbookch12.html#x16-26700012 turn on the mercurial queues extension].

Then you need to [http://www.microsoft.com/downloads/details.aspx?familyid=06111A3A-A651-4745-88EF-3D48091A390B&displaylang=en install] the Windows Mobile 6 Professional SDK (WM6 Pro SDK). To resolve dependencies in the installation of the Windows Mobile 6 Professional SDK, you might need to install some extra software. In this case, the WM6 Pro SDK Installation program will tell you what software you need to install.

You will also need to download and install the [http://www.microsoft.com/downloads/details.aspx?familyid=3D6F581E-C093-4B15-AB0C-A2CE5BFFDB47&displaylang=en Windows Mobile 6.1 Professional Localized Emulator Images].

===WM6.1 Emulator Images IMPORTANT NOTE===
(by wolfe in [irc://irc.mozilla.org/%23wince #wince IRC])

You NEED to install the WM6.1 Emulator Images, because Microsoft fixed something in between 6.0 and 6.1 - so now the specification of memory size via the Emulator Options dialog box works.

You will need to increase the amount of memory available in your chosen 6.1 Emulator (BEFORE you run the chosen 6.1 Emulator for the first time). Otherwise you'll receive "(e)", or "not enough storage is available to complete this operation".

You can increase the amount of memory in your emulator by using the VS8 tools menu, options dialog box.

Find the device tools | devices section, select your desired emulator, click on the properties... button, then press the Emulator Options... button

Once you are looking at the Emulator Options dialog box, check the Specify RAM Size check box - and enter in 256 - the acceptable range for this number is from 1 to 256.

BUT - BUT - BUT - The Emulator built into Visual Studio 2005 / VS8 does not work for mapping a local directory on your PC into the Emulator's \Storage Card (or \Storage Card2).

I have been told that the WM6.1 Emulator Images install fixes BOTH VS8's and VS9's mapping of a local directory into your Emulator as a Shared Directory.

SO - If you want to debug via Emulator, you NEED the Windows Mobile 6.1 Emulator Images.

If you use VS9, you need a minimum of the Visual Studio 2008 Professional version, because the VS9 Express version does not allow the WinMobile 6 SDKs to be installed.

Bottom Line - use VS8 Pro or VS9 Pro AND WM6.1 Emulator Images.

==Prepare To Build==

These directions assume you have created a '''c:\mozilla-build''' directory,
created by downloading and installing the
[[http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-1.3.exe Windows Mozilla Build Setup version 1.3]].

===Mercurial Version In Mozilla-Build version 1.3===
NOTE: As of 20-Nov-2008, Mozilla Build Setup version 1.3 includes a slightly stale
version of Mercurial (version 1.0.1+20080525). The latest Mercurial has a version
number of 1.1+20081203.
The latest Mercurial is downloadable directly from [http://www.selenic.com/mercurial/wiki/index.cgi/Download Selenic's Web Site].

In order to use the latest Mercurial, you have two basic choices:

(1) Remove the c:/mozilla-build/hg directory, and replace it with the contents of
C:/Program Files/Mercurial after you have installed the latest download from Selenic.

(2) Go into c:/mozilla-build/msys/etc/profiles.d/profile-extrapaths.sh and modify
the /c/mozilla-build/hg directory to say /c/Program Files/Mercurial

You can try updating to the latest version of Mercurial if you have troubles with hg.exe

===Downloading The Sources And Patch Queue===

Run the batch file '''C:\mozilla-build\start-msvc8.bat''' (or '''C:\mozilla-build\start-msvc9.bat''')
NOTE: This will setup and open a MingW32 command prompt.
All further commands are to be run inside MingW32.

$ '''cd /c/hg # assuming you've created /c/hg/ for your mozilla source tree'''

$ '''hg clone http://hg.mozilla.org/mozilla-central'''

$ '''cd mozilla-central'''

$ '''export topsrcdir=`pwd` # $topsrcdir becomes the path to mozilla-central/

$ '''hg clone http://hg.mozilla.org/mobile-browser mobile'''

$ '''wget http://people.mozilla.org/~blassey/mozconfig'''

$ '''cd .hg'''

$ '''hg clone http://hg.mozilla.org/users/blassey_mozilla.com/wince-patches patches'''

$ '''cd ..'''

$ '''export PATH="$PATH:$topsrcdir/build/wince/tools/bin"'''

====CRUD - The Clone of Mozilla-Central Freezes====

Several people have reported that the cloning of mozilla-central as described above freezes and does not complete.

If your clone of mozilla-central is taking more than an hour to complete, you may be in this same situation. Basically, this can be caused by a number of different situations:
* The Mozilla hg repository is overloaded,
* The Internet Connection you have is very slow and times out
* The Internet Connection you have drops enough packets that HG gets confused

As a point of reference, John Wolfe has a very fast RCN cable modem connection at home. However, he found out a while ago that RCN considers a 7% data loss to be within acceptable limits for customer service. 7% Data Loss (tested via pinging from an internal-to-RCN server to John Wolfe's cable modem) means that 7 out of every 100 packets gets ''lost''' within the RCN internal network.

This means that when RCN gets busy (nights and weekends, for instance), it is almost guaranteed that John Wolfe will not be able to do a full HG clone operation on the mozilla-central repository.

Here is what you can do to get around HG freezing when cloning mozilla-central:

# Download a [http://haqq.ws/mozilla/mc.bundle.2008_11_26 recent HG bundle]
(made on 26-Nov-08 after a new clone operation on mozilla-central)

# Create a new, empty mozilla-central repository:
$ '''cd /c/hg'''
$ '''hg init mozilla-central'''

# Un-bundle the real mozilla-central changes to that repository:
$ '''cd mozilla-central;'''
$ '''hg unbundle /path/to/mozilla-central.bundle/tip.tar.bz2'''

# Tell mercurial where you normally want to pull from by copying the
following content into your mozilla-central/.hg/hgrc file:

[paths]
default = http://hg.mozilla.org/mozilla-central/

# Pull any changes that happened since the bundle was created:
$ '''hg pull'''

# Update your working directory to the latest change:
$ '''hg update'''

NOTE: You will want to do two seperate operations for pulling then updating, as some versions of HG have a bug in their ''hg pull -u'' command. I forget exactly what the bug is - but the work-around is to do these two seperate operations.

Thanks go out to Benjamin Smedbergs for this solution - [http://benjamin.smedbergs.us/blog/2008-06-05/getting-mozilla-central-with-limited-bandwidth/ Original Blog Posting Here]

===Updating The Sources And Patch Queue===

Run the batch file '''C:\mozilla-build\start-msvc8.bat''' (or '''C:\mozilla-build\start-msvc9.bat''')
NOTE: This will setup and open a MingW32 command prompt.
All further commands are to be run inside MingW32.
This assumes you have a c:\hg\mozilla-central directory

$ '''cd /c/hg/mozilla-central'''

$ '''hg qpop -a'''

$ '''hg pull;hg update;'''

$ '''cd mobile'''

$ '''hg pull;hg update;'''

$ '''cd ../.hg/patches'''

$ '''hg pull;hg update;'''

$ '''cd ../..'''

===Setting Up Your MOZCONFIG File===

Building options are controlled by mozconfig, a master file within your top source directory (in our case, /c/hg/mozilla-central/mozconfig).

You need to create a MOZCONFIG file, since one is not included in the source code repositories. There are four options for Windows Mobile 6 development:

(1) Visual Studio 9 Debug Build
(2) Visual Studio 9 Release Build
(3) Visual Studio 8 Debug Build
(4) Visual Studio 8 Release Build

====VS9 Debug Build MOZCONFIG====
'''Here is our current VS9 mozconfig for building a Debug XULRunner and Fennec for WinMobile:'''

''# Options for client.mk.''
''mk_add_options MOZ_BUILD_PROJECTS="xulrunner mobile"''

''# Options for VS8 verses VS9 / Debug verses Release''
''# Debug/Non-Opt = ~28 MByte XUL.dll''
''# Debug/Opt = ~20 MByte XUL.dll''
''# Release/Opt = ~12 MByte XUL.dll''
''ac_add_options --enable-debug''
''#ac_add_options --disable-optimize''
''mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/objdir-wm6-dbg''
''MIDL=/c/Program\ Files/Microsoft\ Visual\ Studio\ 9/VC/ce/bin/x86_arm/midl.exe''

''# mobile options''
''ac_add_app_options mobile --enable-application=mobile''
''ac_add_app_options mobile --with-libxul-sdk=../xulrunner/dist''

''# Disabling tests due to bug 454881''
''ac_add_options --disable-tests''

''#WINCE specific options''
''ac_add_options --disable-javaxpcom''
''ac_add_options --disable-plugins''
''ac_add_options --disable-accessibility''
''ac_add_options --disable-printing''
''ac_add_options --disable-oji''
''ac_add_options --disable-vista-sdk-requirements''
''ac_add_options --disable-updater''
''ac_add_options --disable-installer''
''ac_add_options --disable-xpinstall''
''ac_add_options --enable-image-decoders="png gif jpeg"''
''ac_add_options --disable-dbm''

''CROSS_COMPILE=1''
''CC=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''CXX=$topsrcdir/build/wince/tools/bin/arm-wince-gcc ''
''CPP=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''LD=$topsrcdir/build/wince/tools/bin/arm-wince-link''
''AR=$topsrcdir/build/wince/tools/bin/arm-wince-lib''
''AS=$topsrcdir/build/wince/tools/bin/arm-wince-as''
''RC=$topsrcdir/build/wince/tools/bin/arm-wince-res''

''mk_add_options AR=@TOPSRCDIR@/build/wince/tools/bin/arm-wince-lib''

''ac_add_options --target=arm-wince''
''ac_add_options --enable-win32-target=WINCE''
''ac_add_options --enable-default-toolkit=cairo-windows''

''ac_add_options --with-wince-sdk="c:/program files/windows mobile 6 sdk/pocketpc/include/armv4i"''

====VS9 Release Build MOZCONFIG====

'''Here is our current VS9 mozconfig for building a non-debug XULRunner for WinMobile:'''

''# Options for client.mk.''
''mk_add_options MOZ_BUILD_PROJECTS="xulrunner"''

''# Options for VS8 verses VS9 / Debug verses Release''
''# Debug/Non-Opt = ~28 MByte XUL.dll''
''# Debug/Opt = ~20 MByte XUL.dll''
''# Release/Opt = ~12 MByte XUL.dll''
''#ac_add_options --enable-debug''
''ac_add_options --enable-optimize''
''mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/objdir-wm6-rel''
''MIDL=/c/Program\ Files/Microsoft\ Visual\ Studio\ 9/VC/ce/bin/x86_arm/midl.exe''

''# Disabling tests due to bug 454881''
''ac_add_options --disable-tests''

''#WINCE specific options''
''ac_add_options --disable-javaxpcom''
''ac_add_options --disable-plugins''
''ac_add_options --disable-accessibility''
''ac_add_options --disable-printing''
''ac_add_options --disable-oji''
''ac_add_options --disable-vista-sdk-requirements''
''ac_add_options --disable-updater''
''ac_add_options --disable-installer''
''ac_add_options --disable-xpinstall''
''ac_add_options --enable-image-decoders="png gif jpeg"''
''ac_add_options --disable-dbm''

''CROSS_COMPILE=1''
''CC=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''CXX=$topsrcdir/build/wince/tools/bin/arm-wince-gcc ''
''CPP=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''LD=$topsrcdir/build/wince/tools/bin/arm-wince-link''
''AR=$topsrcdir/build/wince/tools/bin/arm-wince-lib''
''AS=$topsrcdir/build/wince/tools/bin/arm-wince-as''
''RC=$topsrcdir/build/wince/tools/bin/arm-wince-res''

''mk_add_options AR=@TOPSRCDIR@/build/wince/tools/bin/arm-wince-lib''

''ac_add_options --target=arm-wince''
''ac_add_options --enable-win32-target=WINCE''
''ac_add_options --enable-default-toolkit=cairo-windows''

''ac_add_options --with-wince-sdk="c:/program files/windows mobile 6 sdk/pocketpc/include/armv4i"''

====VS8 Debug Build MOZCONFIG====

'''Here is our current VS8 mozconfig for building a Debug XULRunner and Fennec for WinMobile:'''

''# Options for client.mk.''
''mk_add_options MOZ_BUILD_PROJECTS="xulrunner mobile"''
''mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/objdir-wm6-dbg''

''# Options for VS8 verses VS9 / Debug verses Release''
''# Debug/Non-Opt = ~28 MByte XUL.dll''
''# Debug/Opt = ~20 MByte XUL.dll''
''# Release/Opt = ~12 MByte XUL.dll''
''ac_add_options --enable-debug''
''#ac_add_options --enable-optimize''
''mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/objdir-wm6-dbg-vs8''
''MIDL=/c/Program\ Files/Microsoft\ Visual\ Studio\ 8/VC/ce/bin/x86_arm/midl.exe''

''# mobile options''
''ac_add_app_options mobile --enable-application=mobile''
''ac_add_app_options mobile --with-libxul-sdk=../xulrunner/dist''

''# Disabling tests due to bug 454881''
''ac_add_options --disable-tests''

''#WINCE specific options''
''ac_add_options --disable-javaxpcom''
''ac_add_options --disable-plugins''
''ac_add_options --disable-accessibility''
''ac_add_options --disable-printing''
''ac_add_options --disable-oji''
''ac_add_options --disable-vista-sdk-requirements''
''ac_add_options --disable-updater''
''ac_add_options --disable-installer''
''ac_add_options --disable-xpinstall''
''ac_add_options --enable-image-decoders="png gif jpeg"''
''ac_add_options --disable-dbm''

''CROSS_COMPILE=1''
''CC=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''CXX=$topsrcdir/build/wince/tools/bin/arm-wince-gcc ''
''CPP=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''LD=$topsrcdir/build/wince/tools/bin/arm-wince-link''
''AR=$topsrcdir/build/wince/tools/bin/arm-wince-lib''
''AS=$topsrcdir/build/wince/tools/bin/arm-wince-as''
''RC=$topsrcdir/build/wince/tools/bin/arm-wince-res''

''MIDL=/c/Program\ Files/Microsoft\ Visual\ Studio\ 8/VC/ce/bin/x86_arm/midl.exe''

''mk_add_options AR=@TOPSRCDIR@/build/wince/tools/bin/arm-wince-lib''

''ac_add_options --target=arm-wince''
''ac_add_options --enable-win32-target=WINCE''
''ac_add_options --enable-default-toolkit=cairo-windows''

''ac_add_options --with-wince-sdk="c:/program files/windows mobile 6 sdk/pocketpc/include/armv4i"''

====VS8 Release Build MOZCONFIG====

'''Here is our current VS8 mozconfig for building a non-debug XULRunner for WinMobile:'''

''# Options for client.mk.''
''mk_add_options MOZ_BUILD_PROJECTS="xulrunner"''

''# Options for VS8 verses VS9 / Debug verses Release''
''# Debug/Non-Opt = ~28 MByte XUL.dll''
''# Debug/Opt = ~20 MByte XUL.dll''
''# Release/Opt = ~12 MByte XUL.dll''
''#ac_add_options --enable-debug''
''ac_add_options --enable-optimize''
''mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/objdir-wm6-rel-vs8''
''MIDL=/c/Program\ Files/Microsoft\ Visual\ Studio\ 8/VC/ce/bin/x86_arm/midl.exe''

''# Disabling tests due to bug 454881''
''ac_add_options --disable-tests''

''#WINCE specific options''
''ac_add_options --disable-javaxpcom''
''ac_add_options --disable-plugins''
''ac_add_options --disable-accessibility''
''ac_add_options --disable-printing''
''ac_add_options --disable-oji''
''ac_add_options --disable-vista-sdk-requirements''
''ac_add_options --disable-updater''
''ac_add_options --disable-installer''
''ac_add_options --disable-xpinstall''
''ac_add_options --enable-image-decoders="png gif jpeg"''
''ac_add_options --disable-dbm''

''CROSS_COMPILE=1''
''CC=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''CXX=$topsrcdir/build/wince/tools/bin/arm-wince-gcc ''
''CPP=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''LD=$topsrcdir/build/wince/tools/bin/arm-wince-link''
''AR=$topsrcdir/build/wince/tools/bin/arm-wince-lib''
''AS=$topsrcdir/build/wince/tools/bin/arm-wince-as''
''RC=$topsrcdir/build/wince/tools/bin/arm-wince-res''

''mk_add_options AR=@TOPSRCDIR@/build/wince/tools/bin/arm-wince-lib''

''ac_add_options --target=arm-wince''
''ac_add_options --enable-win32-target=WINCE''
''ac_add_options --enable-default-toolkit=cairo-windows''

''ac_add_options --with-wince-sdk="c:/program files/windows mobile 6 sdk/pocketpc/include/armv4i"''

==Build==

Now you can build xulrunner (and the mobile fennec code) using these commands:

$ '''cd /c/hg/mozilla-central'''

$ '''hg qpush -a'''

$ '''make -f client.mk build'''

===Copy MOZCE_SHUNT.DLL To BIN===
For Visual Studio 2005 (VS8), you can find the shunt DLL at:
/c/hg/mozilla-central/build/wince/shunt/build/vs8/mozce_shunt.dll

For Visual Studio 2008 (VS9), you can find the shunt DLL at:
/c/hg/mozilla-central/build/wince/shunt/build/vs9/mozce_shunt.dll

To debug fennec using VS8/9, you will have to copy mozce_shunt.dll into:
''$OBJDIR''\mobile\dist\bin\xulrunner
so that the .dll file is in the ''same directory'' as where xulrunner.exe is in.

Otherwise, you will receive a
:''Could not find 'XULRunner' (or one of its components). Make sure that the path and filename are correct and that all the required libraries are available.''
or
:''The file 'xulrunner' cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. If the problem persists, try reinstalling or restoring this file.''
error dialog if you try to run XULRunner.exe from a File Explorer.

The VS8 IDE will say that it is ''Unable to start program '\Storage Card\bin\xulrunner.exe'. An error occurred that usually indicates a corrupt installation (code 0x8007007e). If the problem persists, repair your Visual Studio installation via 'Add or Remove Programs' in Control Panel.''

Both of these rather cryptic messages try to tell you that an executable file (EXE or DLL) depends upon a DLL, and that DLL could not be found.

==Debugging==

===Debugging Fennec===
There is a bug in the way that Windows CE searches for executable files that means WinMobile can not search correctly for DLLs desired by xulrunner when launched by fennec.

There are three work-arounds to this problem, and you can select which work-around appeals to you the most:

(1) Copy all xulrunner files to the same directory as the fennec executable

(2) Copy all xulrunner files to the \Windows directory on your device (NOTE: does not work unless your Windows Mobile device has a LOT of space - i.e. HTC Touch Diamond, GTC Touch Pro, others with > 192 MByte)

(3) Change your Registry's OEM Search Path string to add your xulrunner's bin directory. Further information for this option is available
[[http://msdn.microsoft.com/en-us/library/bb202759.aspx via Microsoft DevNetwork]]. Note that you will have to reboot your WinMobile device for a changed OEM Search Path to take effect.

===Visual Studio 2005 / Visual Studio 8 Debugging===
Visual Studio 2005 (VS8) has the following issues when debugging:

* VS8 is available for free from Microsoft, with is a great thing for part-time hackers.

* You can compile xulrunner and fennec, then copy the executables to a device and try running the executables.

* The main people working on WinMobile are using VS9 for compiling and debugging.

* VS8 Emulator's shared-directory driver does not work properly. If you try to use the Emulator supplied with VS8, you will receive LOTS of random errors and faults. You might be able to eventually get a good run of the xulrunner application, but you will also get very frustrated at the same time.

* To run / debug within a VS9 Emulator, you NEED to download and install the [[http://www.microsoft.com/downloads/details.aspx?familyid=3D6F581E-C093-4B15-AB0C-A2CE5BFFDB47&displaylang=en Microsoft Windows Mobile 6.1 Emulator Images]]

* Installing Windows Mobile 6.1 Professional Localized Emulator Images fixes the issue with Emulator Shared Directory use, allowing you to point your Emulator at your BIN directory for running your executables without needing to copy the executables.

* The WinMobile 6.1 Emulator Images installation also fixes a bug with setting the amount of memory within an Emulator Image.

===Visual Studio 2008 / Visual Studio 9 Debugging===
Visual Studio 2008 (VS9) has the following issues when debugging:

* If the Mozilla WinCE Shunt Library fails compiling with an error message about a missing CeGetCanonicalPathName() function, you will need to select the "Windows Mobile 6 Professional" platform in the VS9 IDE platform selection drop-down list box. On a brand-newly cloned source tree, VS9 selects a platform of Windows Mobile 2003.

* To run / debug within a VS9 Emulator, you NEED to download and install the [[http://www.microsoft.com/downloads/details.aspx?familyid=3D6F581E-C093-4B15-AB0C-A2CE5BFFDB47&displaylang=en Microsoft Windows Mobile 6.1 Emulator Images]]

* The WinMobile 6.1 Emulator Images installation updates the VS9 Emulator, fixing a bug with setting the amount of memory within an Emulator Image.

* The main people working on WinMobile use VS9 to run / debug in the emulator / debug on-device.

===Emulator Images===
To run / debug xulrunner and fennec, you will need to increase the amount of memory available to the WinMobile 6.1 Emulator Image in which you are running.

To increase the amount of memory available to your Windows Mobile 6.1 Localized Emulator Image, do the following within VS9:
* Pull down the Tools menu
* Select the Options... menu item
* Find the Device Tools section in the list on the left hand side
* Find and select the Devices sub-section
* Find and select the desired Emulator Image
* Press the Properties... button
* Press the Emulator Options... button
* Check the Specify RAM Size checkbox
* Enter a number greater than 192 (and less than or equal to 256) into the edit box.
* Press OK to close the Emulator Properties dialog box
* Press OK to close the Emulator Image dialog box
* Press OK to close the Options dialog box

* When you start up your Emulator Image, verify that you have the RAM you specified in the Emulator Properties dialog box.

* If your Emulator Image does not have the RAM you specified, you may need to make a new copy of the Emulator in order to correctly specify the RAM size available to your Emulator Image.

===On-Device Debugging===
Some devices ship with security settings turned on. All devices need to have development certificates loaded onto them before debugging.

====Putting Development Certificates On Your Device====
To set the development certificates into your device, copy the file ''C:\Program Files\Windows Mobile 6 SDK\Tools\Security\SDK Development Certificates\Certs.cab'' onto your device. Locate and run this CAB file using the device's File Explorer. Once this CAB file has been installed into your device, the device will be able to run all of the Visual Studio devlopment tools.

====Enabling RAPI Commands On Your Device====
To allow all RAPI (Remote API function calls from the desktop to your tethered, or connected, device) function calls to succeed, you may need to run a command from a DOS box on your PC. Run these commands once your device has the development certificates installed and you have your device connected to your PC:

C:\> '''cd "C:\Program Files\Windows Mobile 6 SDK\Tools\Smartphone\RapiSecurity"'''

C:\> '''RapiConfig.exe /P /M RapiAllowed.xml'''

Instead of running the RapiConfig.exe program, you can copy a Certificate Provisioning File (.CPF) to your device, and run the .CPF file just like you ran the Certs.cab file. Copy the file ''C:\Program Files\Windows Mobile 6 SDK\Tools\Smartphone\RapiSecurity\RapiAllow.cpf'' file onto your device. Locate and run this .CPF file using the device's File Explorer.

====Security Powertoy====
Microsoft provides a Security Powertoy application which allows mere mortals to manipulate the security settings on a device from a semi-friendly GUI.

WARNING: The Security Powertoy has the ability to completely mess up your device. Use this tool with extreme caution.

To use the Security Powertoy, run the "C:\Program Files\Windows Mobile 6 SDK\Tools\Security\Security Powertoy\SecCfgMgr.msi" installer. Once the installer has finished, there will be a shortcut created in your PC's Start Menu named "Security Configuration Manager".

====Putting XULRunner on a Device====
Thanks to Tim Zander for pointing out that no one ever explains how to get XULRunner onto a device.

NOTE: DO NOT FORGET to copy a mozce_shunt.dll executable from the TOPSRCDIR/build/wince/shunt/build/vs8 or TOPSRCDIR/build/wince/shunt/build/vs9 directory into the OBJDIR/dist/bin directory BEFORE copying the whole directory onto a external card or directly onto your device.

You currently (as of 10-Dec-2008) have two options for getting XULRunner on to a device:

(1) If your device takes a plug-in expansion card, copy the OBJDIR/dist/bin
directory on to a expansion card from your PC, then place that expansion
card into your device.

(2) If your device has a LOT of internal storage (i.e., the HTC Touch Diamond
has 4GBytes of internal storage), then you can teather your device to
your PC, and use ActiveSync's File Explorer to copy the OBJDIR/dist/bin
directory onto your device.

On my PC, the OBJDIR/dist/bin directory is located at c:\hg\mozilla-central\objdir-wm6-dbg\xulrunner\dist\bin, and is approximately 32 MBytes large.

Once you have the executables on your device, you can launch the executables via:

(A) The Visual Studio IDE (for debugging)
(B) Via RAPI remote execute command
(C) Via File Explorer on the device
(D) Via specially-created shortcut

====Creating Shortcut for XULRunner====
You can make a shortcut link to execute the command you want under Windows Mobile / WinCE. Here is how:

A Shortcut Link File is a text file with an extension .LNK with one line in a very particular format:

NN#THE_COMMAND_LINE_GOES_HERE

Where:

NN: Number of characters in the whole command line

THE_COMMAND_LINE_GOES_HERE: The actual command you would execute
(as if you were running in a DOS box on WinXP)

Some things to watch out for:

(1) It is a LOT safer to use a full path to your executable

(2) If the full path to your executable contains any spaces, you
HAVE to wrap the full path to your executable with double-quotes

(3) Any space not wrapped inside a double-quote will signal the OS that
an argument has ended and another argument is beginning

(4) If your arguments have spaces in them, again wrap the whole single
argument in double-quotes

Here is an example:

64#"\Program Files\MyDir\MyExe.exe" "First Argument" SecondArgument

There is also an app that you can use called [http://www.freewareppc.com/utilities/shortcutcreator.shtml ''Shortcut Creator''].

Place your newly created shortcut in \Windows\Start Menu\Programs (or one of its sub-folders). You MAY want to place your shortcut in the \Windows\Start Menu\Programs\Games folder, because WinMobile 6 does not automatically update the Start Menu's contents until its next reboot. However, each sub-directory of the Start menu is re-evaluated every time you open the corresponding folder in the Start menu.

===Setting Up MyBrowser===

A simple XULRunner application, MyBrowser, is used to test the XULRunner code.

[http://benjamin.smedbergs.us/xulrunner/mybrowser-0.2.2.xulapp Download the MyBrowser Application using this link.]

The XULApp file is a ZIP file with a number of files and directories. Further explanation of XULRunner and the XULApp format can be found [http://developer.mozilla.org/en/docs/Getting_started_with_XULRunner here.]

'''rename mybrowser-0.2.2.xulapp mybrowser-0.2.2.xulapp.zip'''

Unzip mybrowser-0.2.2.xulapp.zip into its own subdirectory,
while preserving it's ZIP file directory structure.

'''rename mybrowser-0.2.2.xulapp mybrowser'''

'''Edit mybrowser\application.ini''' file, replacing:
'''MaxVersion=1.8.0.*'''
with:
'''MaxVersion=1.9.*.*'''

'''copy -r mybrowser c:\mozilla\unicode\objdir-wm6-debug\dist\bin'''

===Setting Up Debugging of MyBrowser===

You can debug the MyBrowser XULapp from within Visual Studio by using the WinCE shunt Visual Studio Project, and adjusting the deployment device and executable to be run.

1. Open Visual Studio 2005 (Visual Studio 8) Integrated Development Environment (IDE)

2. Open the solution c:\mozilla\unicode\build\wince\shunt\build\vs8\mozce_shunt_static.sln

3. In the Solution Explorer, '''right mouse click on the mozce_shunt_static project'''

4. Select the '''Properties''' pop-up menu item

5. Under the configuration properties, highlight the '''Deployment''' section

6. Make the selected '''Deployment Device''' be '''"Windows Mobile 6 Standard Emulator"'''

7. Press the '''Apply''' button if necessary to save your new selection

8. Under the configuration properties, highlight the '''Debugging''' section

9. For '''Remote Executable''', enter '''\Storage Card\bin\xulrunner.exe'''

10. For '''Command Arguments''', enter '''-app mybrowser\application.ini'''

11. Press the '''Apply''' button if necessary to save your new selection

12. Close the Project Properties dialog box

===Actual Debugging===

You are now ready to begin debugging your XULRunner build.

1. From the Visual Studio 2005 '''Build''' menu, select the '''Deploy Solution''' menu item

2. Wait for your chosen Emulator to start

3. In the Emulator's '''File''' menu, select the '''Configure...''' menu item

4. Press the '''...''' button for the Shared Folder edit box

5. Select the '''c:\mozilla\unicode\objdir-wm6-debug\dist''' directory

6. Close the Emulator Properties dialog box by pressing the '''OK''' key

7. In the Visual Studio 2005's '''Debug''' menu, select the '''Start Debugging''' menu item

You should now see the Visual Studio begin a debugging session of XULRunner loading the MyBrowser XULApp.

==Other Tips==

'''1. Color scheme for MingW32 Command Line Prompt'''

I hated the default color scheme for the command prompt under MingW32 - so I changed it. Find the file c:\mozilla-build\msys\etc\profile, and edit the lines (toward the bottom) which export PS1, and make them say:

export PS1='\[\033]0;$MSYSTEM:\w\007
\033[34m\]\u@\h \[\033[31m\w\033[0m\]
$ '

This changed the directory color to something I could actually see against a white background.

'''3. Further Setting Up MingW32 Path'''

I get annoyed with continually adding the path to the Mercurial HG.EXE, as well as continually adding the path to the build's wince tools directory.

So I created a c:\mozilla-build\msys\etc\profile.d\profile-setup-hg.sh file, containing:

#!/bin/sh

export PATH="$PATH:/c/progra~1/Mercurial"

# This is an addition to get the shim cross-compile build tools into
# our path. - jvw 24-Apr-08
export PATH="$PATH:/c/hg/mozilla-central/build/wince/tools/bin"

This sets up my HG.EXE path, as well as the path to my WinCE build tools (arm-wince-as.exe, arm-wince-gcc.exe, arm-wince-lib.exe, and arm-wince-link.exe)

Mobile/Build/Windows Mobile Build Instructions

2009-01-05T13:02:47Z

Dynamis: /* Updating The Sources And Patch Queue */

Windows Mobile Build Instructions

= work in progress - things are changing as we speak, er.. as you read this =

==Overview==
This page describes the commands for building the latest version of the Windows Mobile XULRunner application using either Visual Studio 2005 or Visual Studio 2008 and the MozillaBuild environment.

'''These instructions are changing frequently.''' The Windows Mobile build of XULRunner and Mobile Fennec is undergoing major improvements and bug fixes. Do not be surprised if your attempt to build and/or run do not immediately work.

People focused on the Windows Mobile build are currently using the [irc://irc.mozilla.org/#wince #wince channel] to communicate about Windows Mobile build-specific issues.

'''Did we mention that things are changing frequently?'''

===Big Picture===
Here is a big-picture view of the steps needed to prepare a new PC for debugging the Windows Mobile Fennec and/or a Windows Mobile ZULRunner application.

* '''One-Time Setup''', including:
** Install Visual Studio 2008 Professional (VS9) or Visual Studio 2005 Professional (VS8)
** Install Windows Mobile 6 Professional SDK
** Install Windows Mobile 6.1 Localized Emulator Images
** Install Mozilla Build Tools
** [Optional] Download and Install Latest Mercurial

* '''Prepare To Build'''
** Download (or update) Sources and Patch Queue
** Download and/or Create Your MOZCONFIG File

* '''Build'''

* '''Debugging'''
** Prepare for Debugging
** Start Debugging

Still interested? OK, let's get started.

==One-Time Setup==

You will only have to do this setup once.

Only Visual Studio 2005 (also known as Visual Studio 8, or VS8) and Visual Studio 2008 (also known as Visual Studio 9, or VS9) are currently supported.

Visual Studio 2008 Express Edition does NOT work for building, because the Windows Mobile SDK Installer will not successfully complete with only Visual Studio 2008 Express installed.

You will need to install your Visual Studio version before continuing with these instructions.

Follow the [http://developer.mozilla.org/en/docs/Windows_Build_Prerequisites#MozillaBuild instructions here] to setup a windows development environment.

Because the Windows Mobile build uses a patch queue, you must [http://hgbook.red-bean.com/hgbookch12.html#x16-26700012 turn on the mercurial queues extension].

Then you need to [http://www.microsoft.com/downloads/details.aspx?familyid=06111A3A-A651-4745-88EF-3D48091A390B&displaylang=en install] the Windows Mobile 6 Professional SDK (WM6 Pro SDK). To resolve dependencies in the installation of the Windows Mobile 6 Professional SDK, you might need to install some extra software. In this case, the WM6 Pro SDK Installation program will tell you what software you need to install.

You will also need to download and install the [http://www.microsoft.com/downloads/details.aspx?familyid=3D6F581E-C093-4B15-AB0C-A2CE5BFFDB47&displaylang=en Windows Mobile 6.1 Professional Localized Emulator Images].

===WM6.1 Emulator Images IMPORTANT NOTE===
(by wolfe in [irc://irc.mozilla.org/%23wince #wince IRC])

You NEED to install the WM6.1 Emulator Images, because Microsoft fixed something in between 6.0 and 6.1 - so now the specification of memory size via the Emulator Options dialog box works.

You will need to increase the amount of memory available in your chosen 6.1 Emulator (BEFORE you run the chosen 6.1 Emulator for the first time). Otherwise you'll receive "(e)", or "not enough storage is available to complete this operation".

You can increase the amount of memory in your emulator by using the VS8 tools menu, options dialog box.

Find the device tools | devices section, select your desired emulator, click on the properties... button, then press the Emulator Options... button

Once you are looking at the Emulator Options dialog box, check the Specify RAM Size check box - and enter in 256 - the acceptable range for this number is from 1 to 256.

BUT - BUT - BUT - The Emulator built into Visual Studio 2005 / VS8 does not work for mapping a local directory on your PC into the Emulator's \Storage Card (or \Storage Card2).

I have been told that the WM6.1 Emulator Images install fixes BOTH VS8's and VS9's mapping of a local directory into your Emulator as a Shared Directory.

SO - If you want to debug via Emulator, you NEED the Windows Mobile 6.1 Emulator Images.

If you use VS9, you need a minimum of the Visual Studio 2008 Professional version, because the VS9 Express version does not allow the WinMobile 6 SDKs to be installed.

Bottom Line - use VS8 Pro or VS9 Pro AND WM6.1 Emulator Images.

==Prepare To Build==

These directions assume you have created a '''c:\mozilla-build''' directory,
created by downloading and installing the
[[http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-1.3.exe Windows Mozilla Build Setup version 1.3]].

===Mercurial Version In Mozilla-Build version 1.3===
NOTE: As of 20-Nov-2008, Mozilla Build Setup version 1.3 includes a slightly stale
version of Mercurial (version 1.0.1+20080525). The latest Mercurial has a version
number of 1.1+20081203.
The latest Mercurial is downloadable directly from [http://www.selenic.com/mercurial/wiki/index.cgi/Download Selenic's Web Site].

In order to use the latest Mercurial, you have two basic choices:

(1) Remove the c:/mozilla-build/hg directory, and replace it with the contents of
C:/Program Files/Mercurial after you have installed the latest download from Selenic.

(2) Go into c:/mozilla-build/msys/etc/profiles.d/profile-extrapaths.sh and modify
the /c/mozilla-build/hg directory to say /c/Program Files/Mercurial

You can try updating to the latest version of Mercurial if you have troubles with hg.exe

===Downloading The Sources And Patch Queue===

Run the batch file '''C:\mozilla-build\start-msvc8.bat''' (or '''C:\mozilla-build\start-msvc9.bat''')
NOTE: This will setup and open a MingW32 command prompt.
All further commands are to be run inside MingW32.

$ '''cd /c/hg # assuming you've created /c/hg/ for your mozilla source tree'''

$ '''hg clone http://hg.mozilla.org/mozilla-central'''

$ '''cd mozilla-central'''

$ '''export topsrcdir=`pwd` # $topsrcdir becomes the path to mozilla-central/

$ '''hg clone http://hg.mozilla.org/mobile-browser mobile'''

$ '''wget http://people.mozilla.org/~blassey/mozconfig'''

$ '''cd .hg'''

$ '''hg clone http://hg.mozilla.org/users/blassey_mozilla.com/wince-patches patches'''

$ '''cd ..'''

$ '''export PATH="$PATH:$topsrcdir/build/wince/tools/bin"'''

====CRUD - The Clone of Mozilla-Central Freezes====

Several people have reported that the cloning of mozilla-central as described above freezes and does not complete.

If your clone of mozilla-central is taking more than an hour to complete, you may be in this same situation. Basically, this can be caused by a number of different situations:
* The Mozilla hg repository is overloaded,
* The Internet Connection you have is very slow and times out
* The Internet Connection you have drops enough packets that HG gets confused

As a point of reference, John Wolfe has a very fast RCN cable modem connection at home. However, he found out a while ago that RCN considers a 7% data loss to be within acceptable limits for customer service. 7% Data Loss (tested via pinging from an internal-to-RCN server to John Wolfe's cable modem) means that 7 out of every 100 packets gets ''lost''' within the RCN internal network.

This means that when RCN gets busy (nights and weekends, for instance), it is almost guaranteed that John Wolfe will not be able to do a full HG clone operation on the mozilla-central repository.

Here is what you can do to get around HG freezing when cloning mozilla-central:

# Download a [http://haqq.ws/mozilla/mc.bundle.2008_11_26 recent HG bundle]
(made on 26-Nov-08 after a new clone operation on mozilla-central)

# Create a new, empty mozilla-central repository:
$ '''cd /c/hg'''
$ '''hg init mozilla-central'''

# Un-bundle the real mozilla-central changes to that repository:
$ '''cd mozilla-central;'''
$ '''hg unbundle /path/to/mozilla-central.bundle/tip.tar.bz2'''

# Tell mercurial where you normally want to pull from by copying the
following content into your mozilla-central/.hg/hgrc file:

[paths]
default = http://hg.mozilla.org/mozilla-central/

# Pull any changes that happened since the bundle was created:
$ '''hg pull'''

# Update your working directory to the latest change:
$ '''hg update'''

NOTE: You will want to do two seperate operations for pulling then updating, as some versions of HG have a bug in their ''hg pull -u'' command. I forget exactly what the bug is - but the work-around is to do these two seperate operations.

Thanks go out to Benjamin Smedbergs for this solution - [http://benjamin.smedbergs.us/blog/2008-06-05/getting-mozilla-central-with-limited-bandwidth/ Original Blog Posting Here]

===Updating The Sources And Patch Queue===

Run the batch file '''C:\mozilla-build\start-msvc8.bat''' (or '''C:\mozilla-build\start-msvc9.bat''')
NOTE: This will setup and open a MingW32 command prompt.
All further commands are to be run inside MingW32.
This assumes you have a c:\hg\mozilla-central directory

$ '''cd /c/hg/mozilla-central'''

$ '''hg qpop -a'''

$ '''hg pull;hg update;'''

$ '''cd mobile'''

$ '''hg pull;hg update;'''

$ '''cd ../.hg/patches'''

$ '''hg pull;hg update;'''

$ '''cd ../..'''

===Setting Up Your MOZCONFIG File===

Building options are controlled by mozconfig, a master file within your top source directory (in our case, /c/hg/mozilla-central/mozconfig).

You need to create a MOZCONFIG file, since one is not included in the source code repositories. There are four options for Windows Mobile 6 development:

(1) Visual Studio 9 Debug Build
(2) Visual Studio 9 Release Build
(3) Visual Studio 8 Debug Build
(4) Visual Studio 8 Release Build

====VS9 Debug Build MOZCONFIG====
'''Here is our current VS9 mozconfig for building a Debug XULRunner and Fennec for WinMobile:'''

''# Options for client.mk.''
''mk_add_options MOZ_BUILD_PROJECTS="xulrunner mobile"''

''# Options for VS8 verses VS9 / Debug verses Release''
''# Debug/Non-Opt = ~28 MByte XUL.dll''
''# Debug/Opt = ~20 MByte XUL.dll''
''# Release/Opt = ~12 MByte XUL.dll''
''ac_add_options --enable-debug''
''#ac_add_options --disable-optimize''
''mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/objdir-wm6-dbg''
''MIDL=/c/Program\ Files/Microsoft\ Visual\ Studio\ 9/VC/ce/bin/x86_arm/midl.exe''

''# mobile options''
''ac_add_app_options mobile --enable-application=mobile''
''ac_add_app_options mobile --with-libxul-sdk=../xulrunner/dist''

''# Disabling tests due to bug 454881''
''ac_add_options --disable-tests''

''#WINCE specific options''
''ac_add_options --disable-javaxpcom''
''ac_add_options --disable-plugins''
''ac_add_options --disable-accessibility''
''ac_add_options --disable-printing''
''ac_add_options --disable-oji''
''ac_add_options --disable-vista-sdk-requirements''
''ac_add_options --disable-updater''
''ac_add_options --disable-installer''
''ac_add_options --disable-xpinstall''
''ac_add_options --enable-image-decoders="png gif jpeg"''
''ac_add_options --disable-dbm''

''CROSS_COMPILE=1''
''CC=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''CXX=$topsrcdir/build/wince/tools/bin/arm-wince-gcc ''
''CPP=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''LD=$topsrcdir/build/wince/tools/bin/arm-wince-link''
''AR=$topsrcdir/build/wince/tools/bin/arm-wince-lib''
''AS=$topsrcdir/build/wince/tools/bin/arm-wince-as''
''RC=$topsrcdir/build/wince/tools/bin/arm-wince-res''

''mk_add_options AR=@TOPSRCDIR@/build/wince/tools/bin/arm-wince-lib''

''ac_add_options --target=arm-wince''
''ac_add_options --enable-win32-target=WINCE''
''ac_add_options --enable-default-toolkit=cairo-windows''

''ac_add_options --with-wince-sdk="c:/program files/windows mobile 6 sdk/pocketpc/include/armv4i"''

====VS9 Release Build MOZCONFIG====

'''Here is our current VS9 mozconfig for building a non-debug XULRunner for WinMobile:'''

''# Options for client.mk.''
''mk_add_options MOZ_BUILD_PROJECTS="xulrunner"''

''# Options for VS8 verses VS9 / Debug verses Release''
''# Debug/Non-Opt = ~28 MByte XUL.dll''
''# Debug/Opt = ~20 MByte XUL.dll''
''# Release/Opt = ~12 MByte XUL.dll''
''#ac_add_options --enable-debug''
''ac_add_options --enable-optimize''
''mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/objdir-wm6-rel''
''MIDL=/c/Program\ Files/Microsoft\ Visual\ Studio\ 9/VC/ce/bin/x86_arm/midl.exe''

''# Disabling tests due to bug 454881''
''ac_add_options --disable-tests''

''#WINCE specific options''
''ac_add_options --disable-javaxpcom''
''ac_add_options --disable-plugins''
''ac_add_options --disable-accessibility''
''ac_add_options --disable-printing''
''ac_add_options --disable-oji''
''ac_add_options --disable-vista-sdk-requirements''
''ac_add_options --disable-updater''
''ac_add_options --disable-installer''
''ac_add_options --disable-xpinstall''
''ac_add_options --enable-image-decoders="png gif jpeg"''
''ac_add_options --disable-dbm''

''CROSS_COMPILE=1''
''CC=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''CXX=$topsrcdir/build/wince/tools/bin/arm-wince-gcc ''
''CPP=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''LD=$topsrcdir/build/wince/tools/bin/arm-wince-link''
''AR=$topsrcdir/build/wince/tools/bin/arm-wince-lib''
''AS=$topsrcdir/build/wince/tools/bin/arm-wince-as''
''RC=$topsrcdir/build/wince/tools/bin/arm-wince-res''

''mk_add_options AR=@TOPSRCDIR@/build/wince/tools/bin/arm-wince-lib''

''ac_add_options --target=arm-wince''
''ac_add_options --enable-win32-target=WINCE''
''ac_add_options --enable-default-toolkit=cairo-windows''

''ac_add_options --with-wince-sdk="c:/program files/windows mobile 6 sdk/pocketpc/include/armv4i"''

====VS8 Debug Build MOZCONFIG====

'''Here is our current VS8 mozconfig for building a Debug XULRunner and Fennec for WinMobile:'''

''# Options for client.mk.''
''mk_add_options MOZ_BUILD_PROJECTS="xulrunner mobile"''
''mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/objdir-wm6-dbg''

''# Options for VS8 verses VS9 / Debug verses Release''
''# Debug/Non-Opt = ~28 MByte XUL.dll''
''# Debug/Opt = ~20 MByte XUL.dll''
''# Release/Opt = ~12 MByte XUL.dll''
''ac_add_options --enable-debug''
''#ac_add_options --enable-optimize''
''mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/objdir-wm6-dbg-vs8''
''MIDL=/c/Program\ Files/Microsoft\ Visual\ Studio\ 8/VC/ce/bin/x86_arm/midl.exe''

''# mobile options''
''ac_add_app_options mobile --enable-application=mobile''
''ac_add_app_options mobile --with-libxul-sdk=../xulrunner/dist''

''# Disabling tests due to bug 454881''
''ac_add_options --disable-tests''

''#WINCE specific options''
''ac_add_options --disable-javaxpcom''
''ac_add_options --disable-plugins''
''ac_add_options --disable-accessibility''
''ac_add_options --disable-printing''
''ac_add_options --disable-oji''
''ac_add_options --disable-vista-sdk-requirements''
''ac_add_options --disable-updater''
''ac_add_options --disable-installer''
''ac_add_options --disable-xpinstall''
''ac_add_options --enable-image-decoders="png gif jpeg"''
''ac_add_options --disable-dbm''

''CROSS_COMPILE=1''
''CC=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''CXX=$topsrcdir/build/wince/tools/bin/arm-wince-gcc ''
''CPP=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''LD=$topsrcdir/build/wince/tools/bin/arm-wince-link''
''AR=$topsrcdir/build/wince/tools/bin/arm-wince-lib''
''AS=$topsrcdir/build/wince/tools/bin/arm-wince-as''
''RC=$topsrcdir/build/wince/tools/bin/arm-wince-res''

''MIDL=/c/Program\ Files/Microsoft\ Visual\ Studio\ 8/VC/ce/bin/x86_arm/midl.exe''

''mk_add_options AR=@TOPSRCDIR@/build/wince/tools/bin/arm-wince-lib''

''ac_add_options --target=arm-wince''
''ac_add_options --enable-win32-target=WINCE''
''ac_add_options --enable-default-toolkit=cairo-windows''

''ac_add_options --with-wince-sdk="c:/program files/windows mobile 6 sdk/pocketpc/include/armv4i"''

====VS8 Release Build MOZCONFIG====

'''Here is our current VS8 mozconfig for building a non-debug XULRunner for WinMobile:'''

''# Options for client.mk.''
''mk_add_options MOZ_BUILD_PROJECTS="xulrunner"''

''# Options for VS8 verses VS9 / Debug verses Release''
''# Debug/Non-Opt = ~28 MByte XUL.dll''
''# Debug/Opt = ~20 MByte XUL.dll''
''# Release/Opt = ~12 MByte XUL.dll''
''#ac_add_options --enable-debug''
''ac_add_options --enable-optimize''
''mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/objdir-wm6-rel-vs8''
''MIDL=/c/Program\ Files/Microsoft\ Visual\ Studio\ 8/VC/ce/bin/x86_arm/midl.exe''

''# Disabling tests due to bug 454881''
''ac_add_options --disable-tests''

''#WINCE specific options''
''ac_add_options --disable-javaxpcom''
''ac_add_options --disable-plugins''
''ac_add_options --disable-accessibility''
''ac_add_options --disable-printing''
''ac_add_options --disable-oji''
''ac_add_options --disable-vista-sdk-requirements''
''ac_add_options --disable-updater''
''ac_add_options --disable-installer''
''ac_add_options --disable-xpinstall''
''ac_add_options --enable-image-decoders="png gif jpeg"''
''ac_add_options --disable-dbm''

''CROSS_COMPILE=1''
''CC=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''CXX=$topsrcdir/build/wince/tools/bin/arm-wince-gcc ''
''CPP=$topsrcdir/build/wince/tools/bin/arm-wince-gcc''
''LD=$topsrcdir/build/wince/tools/bin/arm-wince-link''
''AR=$topsrcdir/build/wince/tools/bin/arm-wince-lib''
''AS=$topsrcdir/build/wince/tools/bin/arm-wince-as''
''RC=$topsrcdir/build/wince/tools/bin/arm-wince-res''

''mk_add_options AR=@TOPSRCDIR@/build/wince/tools/bin/arm-wince-lib''

''ac_add_options --target=arm-wince''
''ac_add_options --enable-win32-target=WINCE''
''ac_add_options --enable-default-toolkit=cairo-windows''

''ac_add_options --with-wince-sdk="c:/program files/windows mobile 6 sdk/pocketpc/include/armv4i"''

==Build==

Now you can build xulrunner (and the mobile fennec code) using these commands:

$ '''cd /c/hg/mozilla-central'''

$ '''hg qpush -a'''

$ '''make -f client.mk build'''

===Copy MOZCE_SHUNT.DLL To BIN===
For Visual Studio 2005 (VS8), you can find the shunt DLL at:
/c/hg/mozilla-central/build/wince/shunt/build/vs8/mozce_shunt.dll

For Visual Studio 2008 (VS9), you can find the shunt DLL at:
/c/hg/mozilla-central/build/wince/shunt/build/vs9/mozce_shunt.dll

To debug fennec using VS8/9, you will have to copy mozce_shunt.dll into:
''$OBJDIR''\mobile\dist\bin\xulrunner
so that the .dll file is in the ''same directory'' as where xulrunner.exe is in.

Otherwise, you will receive a ''Could not find 'XULRunner' (or one of its components). Make sure that the path and filename are correct and that all the required libraries are available.'' error dialog if you try to run XULRunner.exe from a File Explorer.

The VS8 IDE will say that it is ''Unable to start program '\Storage Card\bin\xulrunner.exe'. An error occurred that usually indicates a corrupt installation (code 0x8007007e). If the problem persists, repair your Visual Studio installation via 'Add or Remove Programs' in Control Panel.''

Both of these rather cryptic messages try to tell you that an executable file (EXE or DLL) depends upon a DLL, and that DLL could not be found.

==Debugging==

===Debugging Fennec===
There is a bug in the way that Windows CE searches for executable files that means WinMobile can not search correctly for DLLs desired by xulrunner when launched by fennec.

There are three work-arounds to this problem, and you can select which work-around appeals to you the most:

(1) Copy all xulrunner files to the same directory as the fennec executable

(2) Copy all xulrunner files to the \Windows directory on your device (NOTE: does not work unless your Windows Mobile device has a LOT of space - i.e. HTC Touch Diamond, GTC Touch Pro, others with > 192 MByte)

(3) Change your Registry's OEM Search Path string to add your xulrunner's bin directory. Further information for this option is available
[[http://msdn.microsoft.com/en-us/library/bb202759.aspx via Microsoft DevNetwork]]. Note that you will have to reboot your WinMobile device for a changed OEM Search Path to take effect.

===Visual Studio 2005 / Visual Studio 8 Debugging===
Visual Studio 2005 (VS8) has the following issues when debugging:

* VS8 is available for free from Microsoft, with is a great thing for part-time hackers.

* You can compile xulrunner and fennec, then copy the executables to a device and try running the executables.

* The main people working on WinMobile are using VS9 for compiling and debugging.

* VS8 Emulator's shared-directory driver does not work properly. If you try to use the Emulator supplied with VS8, you will receive LOTS of random errors and faults. You might be able to eventually get a good run of the xulrunner application, but you will also get very frustrated at the same time.

* To run / debug within a VS9 Emulator, you NEED to download and install the [[http://www.microsoft.com/downloads/details.aspx?familyid=3D6F581E-C093-4B15-AB0C-A2CE5BFFDB47&displaylang=en Microsoft Windows Mobile 6.1 Emulator Images]]

* Installing Windows Mobile 6.1 Professional Localized Emulator Images fixes the issue with Emulator Shared Directory use, allowing you to point your Emulator at your BIN directory for running your executables without needing to copy the executables.

* The WinMobile 6.1 Emulator Images installation also fixes a bug with setting the amount of memory within an Emulator Image.

===Visual Studio 2008 / Visual Studio 9 Debugging===
Visual Studio 2008 (VS9) has the following issues when debugging:

* If the Mozilla WinCE Shunt Library fails compiling with an error message about a missing CeGetCanonicalPathName() function, you will need to select the "Windows Mobile 6 Professional" platform in the VS9 IDE platform selection drop-down list box. On a brand-newly cloned source tree, VS9 selects a platform of Windows Mobile 2003.

* To run / debug within a VS9 Emulator, you NEED to download and install the [[http://www.microsoft.com/downloads/details.aspx?familyid=3D6F581E-C093-4B15-AB0C-A2CE5BFFDB47&displaylang=en Microsoft Windows Mobile 6.1 Emulator Images]]

* The WinMobile 6.1 Emulator Images installation updates the VS9 Emulator, fixing a bug with setting the amount of memory within an Emulator Image.

* The main people working on WinMobile use VS9 to run / debug in the emulator / debug on-device.

===Emulator Images===
To run / debug xulrunner and fennec, you will need to increase the amount of memory available to the WinMobile 6.1 Emulator Image in which you are running.

To increase the amount of memory available to your Windows Mobile 6.1 Localized Emulator Image, do the following within VS9:
* Pull down the Tools menu
* Select the Options... menu item
* Find the Device Tools section in the list on the left hand side
* Find and select the Devices sub-section
* Find and select the desired Emulator Image
* Press the Properties... button
* Press the Emulator Options... button
* Check the Specify RAM Size checkbox
* Enter a number greater than 192 (and less than or equal to 256) into the edit box.
* Press OK to close the Emulator Properties dialog box
* Press OK to close the Emulator Image dialog box
* Press OK to close the Options dialog box

* When you start up your Emulator Image, verify that you have the RAM you specified in the Emulator Properties dialog box.

* If your Emulator Image does not have the RAM you specified, you may need to make a new copy of the Emulator in order to correctly specify the RAM size available to your Emulator Image.

===On-Device Debugging===
Some devices ship with security settings turned on. All devices need to have development certificates loaded onto them before debugging.

====Putting Development Certificates On Your Device====
To set the development certificates into your device, copy the file ''C:\Program Files\Windows Mobile 6 SDK\Tools\Security\SDK Development Certificates\Certs.cab'' onto your device. Locate and run this CAB file using the device's File Explorer. Once this CAB file has been installed into your device, the device will be able to run all of the Visual Studio devlopment tools.

====Enabling RAPI Commands On Your Device====
To allow all RAPI (Remote API function calls from the desktop to your tethered, or connected, device) function calls to succeed, you may need to run a command from a DOS box on your PC. Run these commands once your device has the development certificates installed and you have your device connected to your PC:

C:\> '''cd "C:\Program Files\Windows Mobile 6 SDK\Tools\Smartphone\RapiSecurity"'''

C:\> '''RapiConfig.exe /P /M RapiAllowed.xml'''

Instead of running the RapiConfig.exe program, you can copy a Certificate Provisioning File (.CPF) to your device, and run the .CPF file just like you ran the Certs.cab file. Copy the file ''C:\Program Files\Windows Mobile 6 SDK\Tools\Smartphone\RapiSecurity\RapiAllow.cpf'' file onto your device. Locate and run this .CPF file using the device's File Explorer.

====Security Powertoy====
Microsoft provides a Security Powertoy application which allows mere mortals to manipulate the security settings on a device from a semi-friendly GUI.

WARNING: The Security Powertoy has the ability to completely mess up your device. Use this tool with extreme caution.

To use the Security Powertoy, run the "C:\Program Files\Windows Mobile 6 SDK\Tools\Security\Security Powertoy\SecCfgMgr.msi" installer. Once the installer has finished, there will be a shortcut created in your PC's Start Menu named "Security Configuration Manager".

====Putting XULRunner on a Device====
Thanks to Tim Zander for pointing out that no one ever explains how to get XULRunner onto a device.

NOTE: DO NOT FORGET to copy a mozce_shunt.dll executable from the TOPSRCDIR/build/wince/shunt/build/vs8 or TOPSRCDIR/build/wince/shunt/build/vs9 directory into the OBJDIR/dist/bin directory BEFORE copying the whole directory onto a external card or directly onto your device.

You currently (as of 10-Dec-2008) have two options for getting XULRunner on to a device:

(1) If your device takes a plug-in expansion card, copy the OBJDIR/dist/bin
directory on to a expansion card from your PC, then place that expansion
card into your device.

(2) If your device has a LOT of internal storage (i.e., the HTC Touch Diamond
has 4GBytes of internal storage), then you can teather your device to
your PC, and use ActiveSync's File Explorer to copy the OBJDIR/dist/bin
directory onto your device.

On my PC, the OBJDIR/dist/bin directory is located at c:\hg\mozilla-central\objdir-wm6-dbg\xulrunner\dist\bin, and is approximately 32 MBytes large.

Once you have the executables on your device, you can launch the executables via:

(A) The Visual Studio IDE (for debugging)
(B) Via RAPI remote execute command
(C) Via File Explorer on the device
(D) Via specially-created shortcut

====Creating Shortcut for XULRunner====
You can make a shortcut link to execute the command you want under Windows Mobile / WinCE. Here is how:

A Shortcut Link File is a text file with an extension .LNK with one line in a very particular format:

NN#THE_COMMAND_LINE_GOES_HERE

Where:

NN: Number of characters in the whole command line

THE_COMMAND_LINE_GOES_HERE: The actual command you would execute
(as if you were running in a DOS box on WinXP)

Some things to watch out for:

(1) It is a LOT safer to use a full path to your executable

(2) If the full path to your executable contains any spaces, you
HAVE to wrap the full path to your executable with double-quotes

(3) Any space not wrapped inside a double-quote will signal the OS that
an argument has ended and another argument is beginning

(4) If your arguments have spaces in them, again wrap the whole single
argument in double-quotes

Here is an example:

64#"\Program Files\MyDir\MyExe.exe" "First Argument" SecondArgument

There is also an app that you can use called [http://www.freewareppc.com/utilities/shortcutcreator.shtml ''Shortcut Creator''].

Place your newly created shortcut in \Windows\Start Menu\Programs (or one of its sub-folders). You MAY want to place your shortcut in the \Windows\Start Menu\Programs\Games folder, because WinMobile 6 does not automatically update the Start Menu's contents until its next reboot. However, each sub-directory of the Start menu is re-evaluated every time you open the corresponding folder in the Start menu.

===Setting Up MyBrowser===

A simple XULRunner application, MyBrowser, is used to test the XULRunner code.

[http://benjamin.smedbergs.us/xulrunner/mybrowser-0.2.2.xulapp Download the MyBrowser Application using this link.]

The XULApp file is a ZIP file with a number of files and directories. Further explanation of XULRunner and the XULApp format can be found [http://developer.mozilla.org/en/docs/Getting_started_with_XULRunner here.]

'''rename mybrowser-0.2.2.xulapp mybrowser-0.2.2.xulapp.zip'''

Unzip mybrowser-0.2.2.xulapp.zip into its own subdirectory,
while preserving it's ZIP file directory structure.

'''rename mybrowser-0.2.2.xulapp mybrowser'''

'''Edit mybrowser\application.ini''' file, replacing:
'''MaxVersion=1.8.0.*'''
with:
'''MaxVersion=1.9.*.*'''

'''copy -r mybrowser c:\mozilla\unicode\objdir-wm6-debug\dist\bin'''

===Setting Up Debugging of MyBrowser===

You can debug the MyBrowser XULapp from within Visual Studio by using the WinCE shunt Visual Studio Project, and adjusting the deployment device and executable to be run.

1. Open Visual Studio 2005 (Visual Studio 8) Integrated Development Environment (IDE)

2. Open the solution c:\mozilla\unicode\build\wince\shunt\build\vs8\mozce_shunt_static.sln

3. In the Solution Explorer, '''right mouse click on the mozce_shunt_static project'''

4. Select the '''Properties''' pop-up menu item

5. Under the configuration properties, highlight the '''Deployment''' section

6. Make the selected '''Deployment Device''' be '''"Windows Mobile 6 Standard Emulator"'''

7. Press the '''Apply''' button if necessary to save your new selection

8. Under the configuration properties, highlight the '''Debugging''' section

9. For '''Remote Executable''', enter '''\Storage Card\bin\xulrunner.exe'''

10. For '''Command Arguments''', enter '''-app mybrowser\application.ini'''

11. Press the '''Apply''' button if necessary to save your new selection

12. Close the Project Properties dialog box

===Actual Debugging===

You are now ready to begin debugging your XULRunner build.

1. From the Visual Studio 2005 '''Build''' menu, select the '''Deploy Solution''' menu item

2. Wait for your chosen Emulator to start

3. In the Emulator's '''File''' menu, select the '''Configure...''' menu item

4. Press the '''...''' button for the Shared Folder edit box

5. Select the '''c:\mozilla\unicode\objdir-wm6-debug\dist''' directory

6. Close the Emulator Properties dialog box by pressing the '''OK''' key

7. In the Visual Studio 2005's '''Debug''' menu, select the '''Start Debugging''' menu item

You should now see the Visual Studio begin a debugging session of XULRunner loading the MyBrowser XULApp.

==Other Tips==

'''1. Color scheme for MingW32 Command Line Prompt'''

I hated the default color scheme for the command prompt under MingW32 - so I changed it. Find the file c:\mozilla-build\msys\etc\profile, and edit the lines (toward the bottom) which export PS1, and make them say:

export PS1='\[\033]0;$MSYSTEM:\w\007
\033[34m\]\u@\h \[\033[31m\w\033[0m\]
$ '

This changed the directory color to something I could actually see against a white background.

'''3. Further Setting Up MingW32 Path'''

I get annoyed with continually adding the path to the Mercurial HG.EXE, as well as continually adding the path to the build's wince tools directory.

So I created a c:\mozilla-build\msys\etc\profile.d\profile-setup-hg.sh file, containing:

#!/bin/sh

export PATH="$PATH:/c/progra~1/Mercurial"

# This is an addition to get the shim cross-compile build tools into
# our path. - jvw 24-Apr-08
export PATH="$PATH:/c/hg/mozilla-central/build/wince/tools/bin"

This sets up my HG.EXE path, as well as the path to my WinCE build tools (arm-wince-as.exe, arm-wince-gcc.exe, arm-wince-lib.exe, and arm-wince-link.exe)

Mobile/Background

2008-12-25T02:57:11Z

Dynamis:

* Mike Schroepfer: [http://blog.mozilla.com/schrep/2007/10/09/mozilla-and-mobile/ Mozilla and Mobile] (October 9, 2007) Mike talks about why it's important that we get into Mobile, and some of our early first steps.
* Jay Sullivan: [http://dailythemes.wordpress.com/2007/10/30/how-open-is-the-mobile-web/ How open is the mobile Web?] [http://dailythemes.wordpress.com/2007/10/31/from-the-mobile-web-to-the-web-on-mobile/ From the “mobile Web” to “the Web” on mobile] [http://dailythemes.wordpress.com/2007/11/01/mobile-and-the-mozilla-manifesto/ Mobile and the Mozilla manifesto] Jay walks us through some more thinking about how we're going to approach mobile, what Mozilla's mission means in the context of mobile devices and how the world has moved from just having a mobile web to a single web.
* Christian Sejersen: [http://www.christiansejersen.com/blog/2007/11/20/mobile-goals/ Mobile Goals] Christian is leading the team work on Mobile and talks very specifically about first steps. Devices we're starting with, who will be doing the work and what our first steps with the code will be.

Support/In-product

2008-06-05T03:42:52Z

Dynamis:

This page is used to keep track of the locales that have been imported to SUMO so far, to make sure we don't do an import twice (and thus overwriting the previous one).

'''Note: This page is a work in progress. If you see incorrect information, please fix them or notify me at djst at mozilla dot org. Thanks!'''

{| class="fullwidth-table" border="1" cellpadding="0" cellspacing="0"
! Locale
! Content imported
! Localizer contacted
! Localizer responded
! Fx2 content up-to-date
! Will update for Fx3
! Fx3 update status
! SUMO Locale reviewers
! Locale contacts
|- style="background:white; color:black"
| '''en-US''' [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&categId=17&lang=en]
| '''X'''
| '''X'''
| '''X'''
| '''X'''
| '''X'''
| Ready to be localized!
| cilias, np
| [mailto:sumo-at-cilias.com]
|- style="background:white; color:black"
| ca [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=ca&categId=17]
| X
| X
| X
| X
| X
| Not started
| toniher, e_gamonal
| [mailto:toniher-at-softcatala.org Toni Hermoso Pulido]
|- style="background:white; color:black"
| cs [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=cs&categId=17]
| X
| X
| X
| X
|
|
|
|
|- style="background:white; color:black"
| de [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=de&categId=17]
| X
| X
| X
| X
| X
|
| a.topal
| Abdulkadir Topal
|- style="background:white; color:black"
| el [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=el&categId=17]
| X
| X
| X
| X
| X
|
|
| [mailto:pkst-at-gmx.net Kostas Papadimas]
|- style="background:white; color:black"
| es [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=es&categId=17]
| X
| X
| X
|
| X
| starting may 19
| willyaranda, mpoli, deimidis, pgulijczuk
| [mailto:willyaranda-at-gmail.com Guillermo López - willyaranda], [mailto:enzomatrix-at-gmail.com Marcelo Poli]
|- style="background:white; color:black"
| eu [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=eu&categId=17]
| X
| X
| X
| X
| depends on time
| Not started
| Julen
| [mailto:julenx-at-gmail.com Julen]
|- style="background:white; color:black"
| fa [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=fa&categId=17]
| X
| X
| X
| Not localized
| x
| Not started
|
| [mailto:ehsan.akhgari-at-gmail.com Ehsan Akhgari], [mailto:behnam-at-zwnj.org Behnam Esfahbod], [mailto:mana.ghavifekr-at-gmail.com Mana Ghavifekr]
|- style="background:white; color:black"
| fi [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=fi&categId=17]
| X
| X
| X
| X
| X
| done
| villep, aksu
| [mailto:ville.pohjanheimo-at-iki.fi Ville Pohjanheimo]
|- style="background:white; color:black"
| fr [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=fr&categId=17]
| X
| X
| X
|
| ?
|
| Diti, omnisilver (approver)
| [mailto:postmaster-at-foxtwo.info Diti]
|- style="background:white; color:black"
| fy-NL [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=fy-NL&categId=17]
| X
| X
| X
| X
| X
|
| Fjoerfoks
| [mailto:fryskefirefox-at-gmail.com]
|- style="background:white; color:black"
| gu-IN [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=gu-IN&categId=17]
| X
| X
|
|
|
|
|
|
|- style="background:white; color:black"
| he [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=he&categId=17]
| X
| X
|
|
|
|
|
|
|- style="background:white; color:black"
| hu [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=hu&categId=17]
| X
| X
| X
|
| X
| In progress
| timar, kkemenczy
| [mailto:timar-at-fsf.hu Andras Timar]
|- style="background:white; color:black"
| it [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=it&categId=17]
| X
| X
| X
| X
| X
| In progress
| flod, underpass
| [mailto:francesco.lodolo-at-mozillaitalia.org Francesco Lodolo]
|- style="background:white; color:black"
| ja [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=ja&categId=17]
| X
| X
| X
| X
| X
| (almost) done
| marsf (main), a, cai, kozawa, mnakano
| [mailto:dynamis-at-mozilla-japan-dot-org dynamis]
|- style="background:white; color:black"
| ko [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=ko&categId=17]
| X
| X
| X
|
|
|
|
|
|- style="background:white; color:black"
| lt [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=lt&categId=17]
| X
| X
| X
| X
| X
| In progress
| tatjanaj, Gintautas
| [mailto:tatjanaj-at-julius.ktl.mii.lt Tatjana Jevsikova]
|- style="background:white; color:black"
| mk [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=mk&categId=17]
|
| X
| X
|
|
|
| novica
|
|- style="background:white; color:black"
| mn [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=mn&categId=17]
| X
| X
| X
| X
| X
| Starting on May 16
| nagi
| [mailto:natsagdorj-at-t-online.de nagi]
|- style="background:white; color:black"
| nb-NO [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=nb-NO&categId=17]
| X
| X
| X
|
| X
|
| hmork
| [mailto:havard.mork@gmail.com Håvard Mork]
|- style="background:white; color:black"
| nl [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=nl&categId=17]
| X
| X
|
|
|
|
|
|
|- style="background:white; color:black"
| nn-NO [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=nn-NO&categId=17]
| X
| X
|
|
|
|
| bjornivar
| [mailto:bjorn.svindseth-at-online.no Bjorn Ivar Svindseth]
|- style="background:white; color:black"
| pa-IN [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=pa-IN&categId=17]
| X
| X
| X
|
| X
|
|
| [mailto:apbrar-at-gmail.com A S Brar]
|- style="background:white; color:black"
| pl [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=pl&categId=17]
| X
| X
| X
|
| ?
|
| GmbH
| [mailto:gmbh-at-mozillapl.org Marek Wawoczny]
|- style="background:white; color:black"
| pt-BR [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=pt-BR&categId=17]
| X
| X
| X
| X
| X
|
| fernandopsilveira
| [mailto:fernandopsilveira-at-yahoo.com.br Fernando Silveira] [mailto:mgalli-at-mgalli.com Marcio Galli (review assist)]
|- style="background:white; color:black"
| pt-PT [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=pt-PT&categId=17]
| X
| X
| X
| X
| X
| In progress
| cesperanc@
| [mailto:cesperanc-at-gmail.com Cláudio Esperança]
|- style="background:white; color:black"
| ro [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=ro&categId=17]
| X
| X
| X
|
| X
| starting may 19
| alexxed, irina
| [mailto:alexxed-at-gmail.com] [mailto:irinamimoza-at-yahoo.com]
|- style="background:white; color:black"
| ru [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=ru&categId=17]
| X
| X
| X
|
| X
|
| unghost, PiVV
| [mailto:unghost-at-mozilla-russia.org Alexander L. Slovesnik]
|- style="background:white; color:black"
| rw [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=rw&categId=17]
| X
| X
|
|
|
|
|
|
|- style="background:white; color:black"
| sk [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=sk&categId=17]
| X
| X
| X
| X
| X
| done
| wladow, SlovakSoft
| [mailto:valastiak-at-mozilla.sk Vlado Valaštiak]
|- style="background:white; color:black"
| sl [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=sl&categId=17]
| X
| X
|
|
|
|
|
|
|- style="background:white; color:black"
| sq [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=sq&categId=17]
| X
| X
| X
|
| X
|
| Besnik
| [mailto:besnik-at-programeshqip.org Besnik Bleta]
|- style="background:white; color:black"
| sv-SE [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=sv-SE&categId=17]
| X
| X
| X
| X
| ?
|
| Hasse
| [mailto:hasse-at-jasajudeju.se Hasse Wallanger]
|- style="background:white; color:black"
| tr [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=tr&categId=17]
| X
| X
| X
|
| Probably not
|
| asteko
| [mailto:aserkant-at-linux-sevenler.org]
|- style="background:white; color:black"
| uk [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=uk&categId=17]
| X
| X
| X
| X
| X
| In progress
| tymofiy
| [mailto:tim.babych-at-gmail.com Timothy Babych]
|- style="background:white; color:black"
| zh-CN [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=zh-CN&categId=17]
| X
| X
| X
|
| X
|
| holywen
| [mailto:shaohua.wen@gmail.com 文少华]
|- style="background:white; color:black"
| zh-TW [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=zh-TW&categId=17]
| X
| X
| X
|
| X
|
| josesun,Bobchao
| [mailto:josesun@gmail.com Jose Sun]
|}

Support/In-product

2008-06-05T03:40:57Z

Dynamis:

This page is used to keep track of the locales that have been imported to SUMO so far, to make sure we don't do an import twice (and thus overwriting the previous one).

'''Note: This page is a work in progress. If you see incorrect information, please fix them or notify me at djst at mozilla dot org. Thanks!'''

{| class="fullwidth-table" border="1" cellpadding="0" cellspacing="0"
! Locale
! Content imported
! Localizer contacted
! Localizer responded
! Fx2 content up-to-date
! Will update for Fx3
! Fx3 update status
! SUMO Locale reviewers
! Locale contacts
|- style="background:white; color:black"
| '''en-US''' [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&categId=17&lang=en]
| '''X'''
| '''X'''
| '''X'''
| '''X'''
| '''X'''
| Ready to be localized!
| cilias, np
| [mailto:sumo-at-cilias.com]
|- style="background:white; color:black"
| ca [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=ca&categId=17]
| X
| X
| X
| X
| X
| Not started
| toniher, e_gamonal
| [mailto:toniher-at-softcatala.org Toni Hermoso Pulido]
|- style="background:white; color:black"
| cs [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=cs&categId=17]
| X
| X
| X
| X
|
|
|
|
|- style="background:white; color:black"
| de [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=de&categId=17]
| X
| X
| X
| X
| X
|
| a.topal
| Abdulkadir Topal
|- style="background:white; color:black"
| el [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=el&categId=17]
| X
| X
| X
| X
| X
|
|
| [mailto:pkst-at-gmx.net Kostas Papadimas]
|- style="background:white; color:black"
| es [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=es&categId=17]
| X
| X
| X
|
| X
| starting may 19
| willyaranda, mpoli, deimidis, pgulijczuk
| [mailto:willyaranda-at-gmail.com Guillermo López - willyaranda], [mailto:enzomatrix-at-gmail.com Marcelo Poli]
|- style="background:white; color:black"
| eu [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=eu&categId=17]
| X
| X
| X
| X
| depends on time
| Not started
| Julen
| [mailto:julenx-at-gmail.com Julen]
|- style="background:white; color:black"
| fa [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=fa&categId=17]
| X
| X
| X
| Not localized
| x
| Not started
|
| [mailto:ehsan.akhgari-at-gmail.com Ehsan Akhgari], [mailto:behnam-at-zwnj.org Behnam Esfahbod], [mailto:mana.ghavifekr-at-gmail.com Mana Ghavifekr]
|- style="background:white; color:black"
| fi [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=fi&categId=17]
| X
| X
| X
| X
| X
| done
| villep, aksu
| [mailto:ville.pohjanheimo-at-iki.fi Ville Pohjanheimo]
|- style="background:white; color:black"
| fr [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=fr&categId=17]
| X
| X
| X
|
| ?
|
| Diti, omnisilver (approver)
| [mailto:postmaster-at-foxtwo.info Diti]
|- style="background:white; color:black"
| fy-NL [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=fy-NL&categId=17]
| X
| X
| X
| X
| X
|
| Fjoerfoks
| [mailto:fryskefirefox-at-gmail.com]
|- style="background:white; color:black"
| gu-IN [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=gu-IN&categId=17]
| X
| X
|
|
|
|
|
|
|- style="background:white; color:black"
| he [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=he&categId=17]
| X
| X
|
|
|
|
|
|
|- style="background:white; color:black"
| hu [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=hu&categId=17]
| X
| X
| X
|
| X
| In progress
| timar, kkemenczy
| [mailto:timar-at-fsf.hu Andras Timar]
|- style="background:white; color:black"
| it [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=it&categId=17]
| X
| X
| X
| X
| X
| In progress
| flod, underpass
| [mailto:francesco.lodolo-at-mozillaitalia.org Francesco Lodolo]
|- style="background:white; color:black"
| ja [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=ja&categId=17]
| X
| X
| X
| X
| X
| (almost) done
| marsf (main), a
| [mailto:dynamis-at-mozilla-japan-dot-org dynamis]
|- style="background:white; color:black"
| ko [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=ko&categId=17]
| X
| X
| X
|
|
|
|
|
|- style="background:white; color:black"
| lt [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=lt&categId=17]
| X
| X
| X
| X
| X
| In progress
| tatjanaj, Gintautas
| [mailto:tatjanaj-at-julius.ktl.mii.lt Tatjana Jevsikova]
|- style="background:white; color:black"
| mk [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=mk&categId=17]
|
| X
| X
|
|
|
| novica
|
|- style="background:white; color:black"
| mn [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=mn&categId=17]
| X
| X
| X
| X
| X
| Starting on May 16
| nagi
| [mailto:natsagdorj-at-t-online.de nagi]
|- style="background:white; color:black"
| nb-NO [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=nb-NO&categId=17]
| X
| X
| X
|
| X
|
| hmork
| [mailto:havard.mork@gmail.com Håvard Mork]
|- style="background:white; color:black"
| nl [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=nl&categId=17]
| X
| X
|
|
|
|
|
|
|- style="background:white; color:black"
| nn-NO [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=nn-NO&categId=17]
| X
| X
|
|
|
|
| bjornivar
| [mailto:bjorn.svindseth-at-online.no Bjorn Ivar Svindseth]
|- style="background:white; color:black"
| pa-IN [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=pa-IN&categId=17]
| X
| X
| X
|
| X
|
|
| [mailto:apbrar-at-gmail.com A S Brar]
|- style="background:white; color:black"
| pl [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=pl&categId=17]
| X
| X
| X
|
| ?
|
| GmbH
| [mailto:gmbh-at-mozillapl.org Marek Wawoczny]
|- style="background:white; color:black"
| pt-BR [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=pt-BR&categId=17]
| X
| X
| X
| X
| X
|
| fernandopsilveira
| [mailto:fernandopsilveira-at-yahoo.com.br Fernando Silveira] [mailto:mgalli-at-mgalli.com Marcio Galli (review assist)]
|- style="background:white; color:black"
| pt-PT [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=pt-PT&categId=17]
| X
| X
| X
| X
| X
| In progress
| cesperanc@
| [mailto:cesperanc-at-gmail.com Cláudio Esperança]
|- style="background:white; color:black"
| ro [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=ro&categId=17]
| X
| X
| X
|
| X
| starting may 19
| alexxed, irina
| [mailto:alexxed-at-gmail.com] [mailto:irinamimoza-at-yahoo.com]
|- style="background:white; color:black"
| ru [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=ru&categId=17]
| X
| X
| X
|
| X
|
| unghost, PiVV
| [mailto:unghost-at-mozilla-russia.org Alexander L. Slovesnik]
|- style="background:white; color:black"
| rw [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=rw&categId=17]
| X
| X
|
|
|
|
|
|
|- style="background:white; color:black"
| sk [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=sk&categId=17]
| X
| X
| X
| X
| X
| done
| wladow, SlovakSoft
| [mailto:valastiak-at-mozilla.sk Vlado Valaštiak]
|- style="background:white; color:black"
| sl [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=sl&categId=17]
| X
| X
|
|
|
|
|
|
|- style="background:white; color:black"
| sq [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=sq&categId=17]
| X
| X
| X
|
| X
|
| Besnik
| [mailto:besnik-at-programeshqip.org Besnik Bleta]
|- style="background:white; color:black"
| sv-SE [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=sv-SE&categId=17]
| X
| X
| X
| X
| ?
|
| Hasse
| [mailto:hasse-at-jasajudeju.se Hasse Wallanger]
|- style="background:white; color:black"
| tr [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=tr&categId=17]
| X
| X
| X
|
| Probably not
|
| asteko
| [mailto:aserkant-at-linux-sevenler.org]
|- style="background:white; color:black"
| uk [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=uk&categId=17]
| X
| X
| X
| X
| X
| In progress
| tymofiy
| [mailto:tim.babych-at-gmail.com Timothy Babych]
|- style="background:white; color:black"
| zh-CN [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=zh-CN&categId=17]
| X
| X
| X
|
| X
|
| holywen
| [mailto:shaohua.wen@gmail.com 文少华]
|- style="background:white; color:black"
| zh-TW [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=zh-TW&categId=17]
| X
| X
| X
|
| X
|
| josesun,Bobchao
| [mailto:josesun@gmail.com Jose Sun]
|}

Support/UIl10n

2008-05-23T19:40:56Z

Dynamis:

# Download the file http://svn.mozilla.org/projects/sumo/trunk/language_files/%LOCALE%/language.php (replace %LOCALE% with your locale string) and open it in a text editor of your choice
# '''Don't translate all strings in the file!! :)''' Search for the line including "### start of untranslated words" and start from there. Be sure to remove the // at the end of each line you're translating.
#Save and e-mail the file back to me (djst at mozilla dot com) and I'll upload it on the server so we can try it out.

:::Note: You can check syntax of the language.php file with php command: 
::::php -l language.php

Support/In-product

2008-05-16T09:25:20Z

Dynamis:

This page is used to keep track of the locales that have been imported to SUMO so far, to make sure we don't do an import twice (and thus overwriting the previous one).

'''Note: This page is a work in progress. If you see incorrect information, please fix them or notify me at djst at mozilla dot org. Thanks!'''

{| class="fullwidth-table" border="1" cellpadding="0" cellspacing="0"
! Locale
! Content imported
! Localizer contacted
! Localizer responded
! Fx2 content up-to-date
! Will update for Fx3
! Fx3 update status
! SUMO Locale reviewers
! Locale contacts
|- style="background:white; color:black"
| '''en-US''' [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&categId=17&lang=en]
| '''X'''
| '''X'''
| '''X'''
| '''X'''
| '''X'''
| Ready to be localized!
| cilias, np
| [mailto:sumo-at-cilias.com]
|- style="background:white; color:black"
| ca [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=ca&categId=17]
| X
| X
| X
| X
| X
| Not started
| toniher
| [mailto:toniher-at-softcatala.org Toni Hermoso Pulido]
|- style="background:white; color:black"
| cs [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=cs&categId=17]
| X
| X
| X
| X
|
|
|
|
|- style="background:white; color:black"
| de [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=de&categId=17]
| X
| X
| X
| X
| X
|
| a.topal
| Abdulkadir Topal
|- style="background:white; color:black"
| el [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=el&categId=17]
| X
| X
| X
| X
| X
|
|
| [mailto:pkst-at-gmx.net Kostas Papadimas]
|- style="background:white; color:black"
| es [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=es&categId=17]
| X
| X
| X
|
| X
| starting may 19
| willyaranda, mpoli, deimidis, pgulijczuk
| [mailto:willyaranda-at-gmail.com Guillermo López - willyaranda], [mailto:enzomatrix-at-gmail.com Marcelo Poli]
|- style="background:white; color:black"
| eu [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=eu&categId=17]
| X
| X
| X
| X
| depends on time
|
| Julen
| [mailto:julenx-at-gmail.com Julen]
|- style="background:white; color:black"
| fa [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=fa&categId=17]
| X
| X
| X
| Not localized
| x
| Not started
|
| [mailto:ehsan.akhgari-at-gmail.com Ehsan Akhgari], [mailto:behnam-at-zwnj.org Behnam Esfahbod], [mailto:mana.ghavifekr-at-gmail.com Mana Ghavifekr]
|- style="background:white; color:black"
| fi [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=fi&categId=17]
| X
| X
| X
| X
| X
|
| villep, aksu
| [mailto:ville.pohjanheimo-at-iki.fi Ville Pohjanheimo]
|- style="background:white; color:black"
| fr [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=fr&categId=17]
| X
| X
| X
|
| ?
|
| Diti, omnisilver (approver)
| [mailto:postmaster-at-foxtwo.info Diti]
|- style="background:white; color:black"
| fy-NL [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=fy-NL&categId=17]
| X
| X
| X
| X
| X
|
| Fjoerfoks
| [mailto:fryskefirefox-at-gmail.com]
|- style="background:white; color:black"
| gu-IN [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=gu-IN&categId=17]
| X
| X
|
|
|
|
|
|
|- style="background:white; color:black"
| he [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=he&categId=17]
| X
| X
|
|
|
|
|
|
|- style="background:white; color:black"
| hu [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=hu&categId=17]
| X
| X
| X
|
| X
|
|
| [mailto:timar-at-fsf.hu Andras Timar]
|- style="background:white; color:black"
| it [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=it&categId=17]
| X
| X
| X
| X
| X
| In progress
| flod, underpass
| [mailto:francesco.lodolo-at-mozillaitalia.org Francesco Lodolo]
|- style="background:white; color:black"
| ja [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=ja&categId=17]
| X
| X
| X
| X
| X
| In progress
| marsf (main), a
| [mailto:dynamis-at-mozilla-japan-dot-org dynamis]
|- style="background:white; color:black"
| ko [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=ko&categId=17]
| X
| X
| X
|
|
|
|
|
|- style="background:white; color:black"
| lt [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=lt&categId=17]
| X
| X
| X
| X
| X
| In progress
| tatjanaj, Gintautas
| [mailto:tatjanaj-at-julius.ktl.mii.lt Tatjana Jevsikova]
|- style="background:white; color:black"
| mk [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=mk&categId=17]
|
| X
| X
|
|
|
|
|
|- style="background:white; color:black"
| mn [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=mn&categId=17]
| X
| X
|
|
|
|
|
|
|- style="background:white; color:black"
| nb-NO [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=nb-NO&categId=17]
| X
| X
| X
|
| X
|
| hmork
| [mailto:havard.mork@gmail.com Håvard Mork]
|- style="background:white; color:black"
| nl [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=nl&categId=17]
| X
| X
|
|
|
|
|
|
|- style="background:white; color:black"
| nn-NO [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=nn-NO&categId=17]
| X
| X
|
|
|
|
| bjornivar
| [mailto:bjorn.svindseth-at-online.no Bjorn Ivar Svindseth]
|- style="background:white; color:black"
| pa-IN [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=pa-IN&categId=17]
| X
| X
| X
|
| X
|
|
| [mailto:apbrar-at-gmail.com A S Brar]
|- style="background:white; color:black"
| pl [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=pl&categId=17]
| X
| X
| X
|
| ?
|
| GmbH
| [mailto:gmbh-at-mozillapl.org Marek Wawoczny]
|- style="background:white; color:black"
| pt-BR [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=pt-BR&categId=17]
| X
| X
| X
| X
| X
|
| fernandopsilveira
| [mailto:fernandopsilveira-at-yahoo.com.br Fernando Silveira] [mailto:mgalli-at-mgalli.com Marcio Galli (review assist)]
|- style="background:white; color:black"
| pt-PT [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=pt-PT&categId=17]
| X
| X
| X
| X
| X
|
| cesperanc@
| [mailto:cesperanc-at-gmail.com Cláudio Esperança]
|- style="background:white; color:black"
| ro [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=ro&categId=17]
| X
| X
| X
|
| X
| starting may 19
| alexxed, irina
| [mailto:alexxed-at-gmail.com] [mailto:irinamimoza-at-yahoo.com]
|- style="background:white; color:black"
| ru [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=ru&categId=17]
| X
| X
| X
|
| X
|
| unghost, PiVV
| [mailto:unghost-at-mozilla-russia.org Alexander L. Slovesnik]
|- style="background:white; color:black"
| rw [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=rw&categId=17]
| X
| X
|
|
|
|
|
|
|- style="background:white; color:black"
| sk [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=sk&categId=17]
| X
| X
| X
| X
| X
| done
| wladow, SlovakSoft
| [mailto:valastiak-at-mozilla.sk Vlado Valaštiak]
|- style="background:white; color:black"
| sl [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=sl&categId=17]
| X
| X
|
|
|
|
|
|
|- style="background:white; color:black"
| sq [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=sq&categId=17]
| X
| X
| X
|
| X
|
| Besnik
| [mailto:besnik-at-programeshqip.org Besnik Bleta]
|- style="background:white; color:black"
| sv-SE [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=sv-SE&categId=17]
| X
| X
| X
| X
| ?
|
| Hasse
| [mailto:hasse-at-jasajudeju.se Hasse Wallanger]
|- style="background:white; color:black"
| tr [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=tr&categId=17]
| X
| X
| X
|
| Probably not
|
| asteko
| [mailto:aserkant-at-linux-sevenler.org]
|- style="background:white; color:black"
| uk [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=uk&categId=17]
| X
| X
| X
| X
| X
|
| tymofiy
| [mailto:tim.babych-at-gmail.com Timothy Babych]
|- style="background:white; color:black"
| zh-CN [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=zh-CN&categId=17]
| X
| X
| X
|
| X
|
| holywen
| [mailto:shaohua.wen@gmail.com 文少华]
|- style="background:white; color:black"
| zh-TW [http://support.mozilla.com/tiki-listpages.php?maxRecords=15&lang=zh-TW&categId=17]
| X
| X
| X
|
| X
|
| josesun
| [mailto:josesun@gmail.com Jose Sun]
|}