Perhaps we can create a global struct (or maybe just share
AppConstants?) that holds the set of all to-be-translated strings.
That way, it's easy to see these strings together without grepping,
and we don't need to worry about which "magic comment" to use.

On Fri, Jun 5, 2015 at 11:15 AM, Stefan Arentz <[email protected]> wrote:
> TL;DR If you have strings that are not final yet, for example because they
> have to be approved or correctly written, please include them inline and
> mark them with a TODO L10N comment.
>
> I got in trouble for doing something like this:
>
>   let s = NSLocalizedString("Some string here. Do not translate this yet.",
>     comment: "Do not translate this yet.")
>
> This resulted in confusion. So instead, please do this:
>
>   let s = "Some string here." // TODO L10N
>
> Then the string will not show up in the l10n export. And it will be easy to
> find with a simple search.
>
> I'll be grepping the code as part of the periodic strings export. And make
> sure we have bugs online for these strings.
>
>  S.
>
>
> _______________________________________________
> mobile-firefox-dev mailing list
> [email protected]
> https://mail.mozilla.org/listinfo/mobile-firefox-dev
>
_______________________________________________
mobile-firefox-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/mobile-firefox-dev

Reply via email to