>>>>> "Cantor," == Cantor, Scott <[email protected]> writes:
Cantor,> I'm working with an absence of understanding of exactly how
Cantor,> the display form would be used, but my experience with XML
Cantor,> data in general is that sticking with UTF-8 where possible
Cantor,> tends to keep things simpler, since an application can
Cantor,> always do whatever converting it wants to from that
Cantor,> baseline.
Me too.
I'm not really sure what you'd do with the display form other than dump
into a debug log.
I was hoping to get input from those who added the display form to the
API.
Cantor,> But in a related question, wouldn't it be bad to have
Cantor,> different name attributes expressing themselves in either
Cantor,> raw or display form with different encodings? How would the
Cantor,> application know what the encoding was meant to be in each
Cantor,> case?
That's part of my concern. I'm wondering whether the display form is
expected to have encoding under the implementation's control rather than
under the attribute's control?
I really don't know what the right answer is. I've left it unspecified
in the current version and will be happy to change that if we figure out
what should be done there.
_______________________________________________
abfab mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/abfab
