Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
upcoming webapp runtime landing with locale-specific strings
13 views
Skip to first unread message
Myk Melez
Apr 16, 2012, 4:00:55 PM4/16/12
to Mozilla l10n
Localizers!
In the very near future, I'm going to land a changeset to
mozilla-central that adds a "webapp runtime" to Firefox. The runtime is
an executable and XUL application for running webapps in their own
processes (somewhat similar to the old Prism project). It will ship with
Firefox 14, which merges from central to aurora next week.
Although the runtime has very little application chrome, it does provide
some functionality, like standard OS menus/menuitems, that contains
locale-specific strings. The changeset puts these strings into
webapp.dtd and webapp.properties files in the
browser/locales/en-US/webapprt/ directory.
(In the long run, I'd like them to live in the webapprt/locales/en-US/
directory, inside the same top-level webapprt/ directory as the rest of
the runtime's files, but I understand that this will require significant
work on l10n repackaging, so I'm not putting them there for now.)
If you'd like a sneak peek at the files before I land them, check them
out in the GitHub repository where we have been developing the feature:
https://github.com/michaelrhanson/mozilla-central/blob/master/browser/locales/en-US/webapprt/webapp.dtd
https://github.com/michaelrhanson/mozilla-central/blob/master/browser/locales/en-US/webapprt/webapp.properties
Regards,
-myk
In the very near future, I'm going to land a changeset to
mozilla-central that adds a "webapp runtime" to Firefox. The runtime is
an executable and XUL application for running webapps in their own
processes (somewhat similar to the old Prism project). It will ship with
Firefox 14, which merges from central to aurora next week.
Although the runtime has very little application chrome, it does provide
some functionality, like standard OS menus/menuitems, that contains
locale-specific strings. The changeset puts these strings into
webapp.dtd and webapp.properties files in the
browser/locales/en-US/webapprt/ directory.
(In the long run, I'd like them to live in the webapprt/locales/en-US/
directory, inside the same top-level webapprt/ directory as the rest of
the runtime's files, but I understand that this will require significant
work on l10n repackaging, so I'm not putting them there for now.)
If you'd like a sneak peek at the files before I land them, check them
out in the GitHub repository where we have been developing the feature:
https://github.com/michaelrhanson/mozilla-central/blob/master/browser/locales/en-US/webapprt/webapp.dtd
https://github.com/michaelrhanson/mozilla-central/blob/master/browser/locales/en-US/webapprt/webapp.properties
Regards,
-myk
Axel Hecht
Apr 16, 2012, 4:42:27 PM4/16/12
to
If you wanted to move the files to webapprt, you'd have to add webapprt
to browser/locales/l10n.ini, add webapprt to the directories to repack
in libs-%, and have a Makefile.in in webapprt/locales very much like the
one in dom/locales.
Axel
Hasse
Apr 21, 2012, 3:00:46 AM4/21/12
to
In article <mailman.21643.13346...@lists.mozilla.org>,
Myk Melez wrote...
> Although the runtime has very little application chrome, it does provide
> some functionality, like standard OS menus/menuitems, that contains
> locale-specific strings. The changeset puts these strings into
> webapp.dtd and webapp.properties files in the
> browser/locales/en-US/webapprt/ directory.
>
> (In the long run, I'd like them to live in the webapprt/locales/en-US/
> directory, inside the same top-level webapprt/ directory as the rest of
> the runtime's files, but I understand that this will require significant
> work on l10n repackaging, so I'm not putting them there for now.)
What about webapprt/locales/en-US/webapp-uninstaller/webapp-
uninstaller.properties? Should we not localize that file?
--
Hasse
sv-SE l10n team
Myk Melez wrote...
> Although the runtime has very little application chrome, it does provide
> some functionality, like standard OS menus/menuitems, that contains
> locale-specific strings. The changeset puts these strings into
> webapp.dtd and webapp.properties files in the
> browser/locales/en-US/webapprt/ directory.
>
> (In the long run, I'd like them to live in the webapprt/locales/en-US/
> directory, inside the same top-level webapprt/ directory as the rest of
> the runtime's files, but I understand that this will require significant
> work on l10n repackaging, so I'm not putting them there for now.)
uninstaller.properties? Should we not localize that file?
--
Hasse
sv-SE l10n team
Hasse
Apr 21, 2012, 12:16:17 PM4/21/12
to
In article <MPG.29fc7983e...@news.mozilla.org>, Hasse
wrote...
> What about webapprt/locales/en-US/webapp-uninstaller/webapp-
> uninstaller.properties? Should we not localize that file?
I guess we should, since building with --enable-ui-locale=ab-CD is
broken without that file.
wrote...
> What about webapprt/locales/en-US/webapp-uninstaller/webapp-
> uninstaller.properties? Should we not localize that file?
broken without that file.
Myk Melez
Apr 21, 2012, 12:32:08 PM4/21/12
to Hasse, dev-...@lists.mozilla.org, Tim Abraldes
possible to localize without having to update the l10n build
infrastructure. I filed bug 747645 on that:
https://bugzilla.mozilla.org/show_bug.cgi?id=747645
-myk
0 new messages