if i recall correctly, syck doesn't handle utf-8/16. does/will tap
care about that?
That's true -- I think Audrey patched the perl version to work properly,
but I forgot that other languages are without that functionality. Ruby
doesn't properly support Unicode either, so Unicode support probably
doesn't matter to them. (I think Syck is originally a Ruby project, and
Ruby has some moral qualm with Unicode, so that's why Syck doesn't work
with Unicode.) As for Python, dunno.
I do actually do test UTF-8 data structures in some of my tests, so this
is actually a relevant concern. I think things will work fine if you're
just outputting UTF8 data to your UTF8 terminal, but if you're doing
colation or charset conversion (maybe your terminal is EUC_JP for
example), then you'll run into problems. This is something to look
into, if we want YAML TAP to work for languages other than Perl.
What else is TAP targeted to? C / C++ / Java?
oh, and while i'm thinking about it, i think it would be wise to
include a tap version in the tap header, so as this protocol changes,
parsers will have a chance to handle different tap versions
gracefully.
Good idea.
