14 Nov
2015
14 Nov
'15
6:19 p.m.
On Sat, Nov 14, 2015 at 09:19:37PM +0200, Serhiy Storchaka wrote:
If the support of UTF-16 and UTF-32 is planned, I'll take this to attention during refactoring. But in many places besides the tokenizer the ASCII compatible encoding of source files is expected.
Perhaps another way of looking at this: Is it feasible to drop support for arbitrary encodings and just require UTF-8 (with or without a pseudo-BOM)? -- Steve