[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff-comment] Formats other than xml
|
In specific I am working with Flash that reads in the xliff
and uses it for displaying localized text. In fairness it works fine, for this provided
the xml avoids or has any html characters encoded correctly and is just being
read by Flash. If however we are exporting the content from flash to php to
create the xml Flash does not support CData nodes, and adds additional tags to
html based text which prove problematic. This is definitely a Flash specific
issue, but it has caused us to reconsider utilizing xml entirely, and one
option that has been brought up is JSON. The main advantage that JSON has over XML has to do with
smaller file size as it does not require closing tags for nodes, while still
supporting complex data objects. I understand that functionality wise JSON has
its own issues though surrounding backslash and single quote characters. My question is more in the way of investigation into how tied
to the xml file format the structure is, and if other formats had been
considered while retaining the actual structure of the XLIFF object. Brandon Bradley Member of Technical Staff P Please consider the environment before printing this e-mail From: Yves Savourel [mailto:yves@opentag.com] Oh, I think I
mis-understood the question. You meant: XLIFF as
an non-XML format (rather than supporting non-XML input). For example an XLIFF
in JSON for instance. At the very early
stage yes, XML was not necessarily the only option to create XLIFF, but after
that no: XML has been working fine as far as I can tell. What kind of
XML-related issues are you finding that could be solve with JSON but not XML? -ys From: Bradley, Brandon
[mailto:Brandon.Bradley@Pearson.com] Has
there been any consideration of supporting other data formats for the xliff
data structure besides xml? For example a json object? I’ve done some
preliminary conversion of some of my sample files, and it seems to port with no
real issues, but currently the official specification is locked to xml which
has issues round-tipping to and from some systems, especially in regards to
html formatted text. Brandon Bradley |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]