Thanks, Eva!
What are your thoughts on editing the XLIFF (version 1) files by hand
instead of XMB? I ask because it's the default type used by Angular, we
have special tools for merging new strings into existing XLIFF files, and
it's the most commonly supported format used by various translation
Hi all,
I don't think that translations using XML editing would be an unbeatable
problem for translators especially if we understood this as a temporary
solution. This would at least give the community some more time to prepare
for further necessary steps.
I've reviewed the attached files and it
Hi Ben,
Attached is a tar file of 3 different message bundles: XLIFF, XLIFF2, and
XMB. These are the formats supported by Angular.
Thanks for looking into this!
-b
On Thu, Aug 16, 2018 at 9:32 AM Ben Shum wrote:
> The other reason I'd like to get a copy of the generated xliff is to
>
The other reason I'd like to get a copy of the generated xliff is to
start seeing how much change we're expecting between the strings. I
imagine that the translators should get a head's up that there'll be
major upheaval coming for them if we cannot bring forward too much of
the existing PO
Hi Bill,
Spinning up a Pootle instance has been on our community to-do list for
awhile as part of our ongoing discussions about the desire/plans to
switch off Launchpad. I started playing with this during the last
couple conferences locally in a VM on my laptop, but we still have yet
to agree on
Hi All,
Now that others have installed and run the Angular 6 code, and we're on the
home stretch for 3.2, I have started putting the finishing touches on the
code in hopes we can merge for 3.2.
The biggest changes since my last wiki update [1] are related to continued
locale support. The client
