On Friday, May 1, 2015 at 3:25:07 PM UTC-4, Zibi Braniecki wrote: > On Friday, May 1, 2015 at 11:47:56 AM UTC-4, Matjaz Horvat wrote: > > Speaking with my l10n-tool-developer hat on, I prefer option A, which makes > > source strings available directly. > > > Yeah, roger that. > > On the other hand we would prefer not to inflate the AST if possible because > it costs runtime memory and/or storage. So we either diverge ASTs or we go > with b).
Ok, I added parseString/serializeString for now. Once we start adding source annotations for editors, we will have to figure out how to do this (either fork the parser or extend it), and then we will start providing you an AST more suited for your needs (including a source for the complexString). For now, just pass the value to serializer.serializeString and it will give you a string. zb. _______________________________________________ tools-l10n mailing list [email protected] https://lists.mozilla.org/listinfo/tools-l10n
