One question.
AFAIK NativeUI is currently only for smart phone, not for tablet.
Then can we use different labels like this?
mobile/android - short label for smart phone (small screen)
mobile/xul is - longer label for tablet (large screen)
I believe smart phone and tablet should have different text labels since
it's screen size and UI are different.
If we'll still continue to release XUL version for smart phone, we
should keep labels short (too short and difficult to understand).
If we no more use mobile/xul for smart phone, we can use longer (and
easy to understand) text labels in mobile/xul for tablet UI.
(11/12/22 23:28), Staś Małolepszy wrote:
> Hi all,
>
> The scoop: the files in mobile/ need to move around. You can use
> a script to do it yourself or file a bug to have us help you out.
>
> As you probably know, a lot of time and effort has been invested into
> porting Firefox Mobile's interface to the native Java UI. The goal is
> to reduce the startup time and the responsiveness of the browser.
>
> We will be using the same file formats of the localization files for
> the native Android builds as we are right now for the XUL builds, i.e.
> DTD and .properties.
>
> Instead of a single mobile/ directory, there will be mobile/android
> and mobile/xul. Additionally, the files that are shared between the
> two builds, like search engines, bookmarks and region.properties will
> stay in mobile/. See bug 708015 [1] for details.
>
> In the end, you will end up with the following directory layout inside
> mobile/:
>
> mobile/android
> mobile/android/base (copied from embedding/android)
> mobile/chrome (for region.properties)
> mobile/overrides
> mobile/profile
> mobile/searchplugins
> mobile/xul
>
> In order to create the new directory structure, you can follow two
> paths:
>
> 1. download the script from
https://gist.github.com/1500954 and run
> it in your releases/l10n/mozilla-aurora clone, or
>
> 2. file a bug at
http://bit.ly/viHvop and let us migrate your
> directories for you; all you'll have to do in this scenario is to
> hg pull and hg update your local clone when we're done.
>
> If you work on central, then run the script before you migrate to
> aurora for best results.
>
> Once you have the new directory layout, the dashboard will start to
> make sense again for all repositories (central and aurora).
>
> Feel free to ping us in #l10n or reply here if you have questions.
>
> Good luck, and happ
> -stas
>
> [1]
https://bugzilla.mozilla.org/show_bug.cgi?id=708015
> _______________________________________________
> dev-l10n mailing list
>
dev-...@lists.mozilla.org
>
https://lists.mozilla.org/listinfo/dev-l10n