On Aug 11, 5:32 pm, Jerry Coffin <jerryvcof...@yahoo.com> wrote:
In article <c2a6204c-889c-4498-b9bf-406366b093f1@
18g2000yqa.googlegroups.com>, james.ka...@gmail.com says...
[ ... ]
What I meant was more general. On one hand, Windows seems
to tend toward UTF-16; on the other Visual Studios doesn't
allow you to create it.
Ah, yes, that's more or less reasonable. VS _does_ seem to
allow you to create it, but not necessarily easily or
consistently. A bit more looking shows, for one example, that
it does have a setting to create Unicode files if they contain
characters that can't be represented in the current code page.
At least to me, that sounds like really lousy idea -- I have a
file that's in one format, but I enter one wrong character,
and suddenly (and apparently without warning) its format
changes completely...
Yes. Without any consideration for backwards compatibility, I'd
offer a simple choice of "native" (UTF-16, CRLF line
separators), "internet" (UTF-8, CRLF line terminators) and
"unix" (UTF-8, LF line teminators). But compatibility means
that all of the other existing combinations, which are already
there, have to be supported somehow as well. (Until recently,
most of my sources were ISO 8859-1, CR line terminators. Which
didn't seem to cause the VC++ compiler any problems, but the
only characters not in the basic character set were in comments,
so I'm not sure that means anything---I've converted to UTF-8,
and the sources compile just as well, with no change in the
compiler configuration.)
If you're using Comeau that may be a good strategy. Otherwise you may want to
get a more comprehensible error message for something. And g++ does not accept