697386 - Put native UI strings in a separate .dtd, and keep a copy in mozilla-central and friends

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect, P3)

Description

[Axel Hecht [:Pike]]

Let's move the nativeUi strings into a separate file on birch, and land that next to the xul-ui strings.dtd on mozilla-central (and aurora as time comes).

That way, we can get the localized strings gathered on l10n-central/aurora, and still use birch for the en-US development.

Comment 1

[Doug Turner (:dougt)]

we have no plans on landing anything on mozilla-central for the next few months.  Could you explain why the l10n bits should land prematurely (that is, not with the rest of the code).

Comment 2

[Axel Hecht [:Pike]]

We won't be able to localize birch as a separate repository in a short time frame.

The easiest path to get the strings to localizers and back is to land the strings in the standard repos. We need their content for gecko anyway. Just make birch reference a file that's different from android_strings.dtd as we use it for the xul ui.

Comment 3

[chris hofmann]

we need this badly to get started with  experiments on how the localization process will work.   can we get a patch together and landed this week?

Comment 4

[Mark Finkle (:mfinkle) (use needinfo?)]

Please note that the DTD file we are talking about in this bug is not 100% of the strings used in the Java chrome UI. We show dialog prompts, system notifications, door hanger notifications and other UI built from JS/Gecko. Those are created using strings in the /mobile/locale/ folder.

Those string changes would not be tracked by this bug.

Comment 5

[Doug Turner (:dougt)]

over to pike per our meeting.

Comment 6

[Axel Hecht [:Pike]]

Resolving this WONTFIX.

I think the better way to do this is to run the l10n-dashboard for mobile between birch and l10n-central (and shift that as gecko in native UI matures).

In the meeting, we also emphasized that we need to follow our standard coding procedures in terms of bumping keys when changing strings. Nothing new, other than that this now spans two repositories. Given that we want to merge central into birch without conflicts, it's not too big a deal.