Great, thanks Zibi. If we decide to add support for \n in the future we won't be breaking any existing translations since \n is now illegal.
On Thu, May 14, 2015 at 9:19 AM, Zibi Braniecki < [email protected]> wrote: > Per conversation on l20n weekly call I updated all three parsers to > support unescaping of: > > - opchar (" or ') > - \ > - {{ > - \uXXXX > > The benefit of that is that I can serialize it back knowing that if those > characters (except of \uXXXX) are in the string, they must have been > escaped. So RCS will show no diff. > > The exception is \uXXXX - at this point I have no way to tell if in the > source it was escaped or not and since I unescaped it in AST, I serialize > unescaped. > > I can add \t, \n and \r at any point (with the same limitation on > serialization). > > zb. > _______________________________________________ > tools-l10n mailing list > [email protected] > https://lists.mozilla.org/listinfo/tools-l10n > _______________________________________________ tools-l10n mailing list [email protected] https://lists.mozilla.org/listinfo/tools-l10n
