= Сообщение: 311 из 1367 ============================================= UTF-8 = От : Michiel van der Vlist 2:280/5555 26 Nov 16 01:05:15 Кому : Maurice Kinal 26 Nov 16 01:05:15 Тема : UTF-8 for Region 80 FGHI : area://UTF-8?msgid=2:280/5555+5838d648 На : area://UTF-8?msgid=1:153/7001.0+5837a96a = Кодировка сообщения определена как: UTF-8 ================================== Ответ: area://UTF-8?msgid=1:153/7001.0+5838de21 ============================================================================== Hello Maurice,
On Friday November 25 2016 03:00, you wrote to me:
MvdV>> many nodelist processing softweres will see the presence of a MvdV>> BOM as an error condition.
MK> Which nodelist and what nodelist processing software?
Any nodelist and AFAIK all nodelist processing software except the latest version of MakeNl with the "REMOVEBOM 1" option set.
MK> I believe it was clear that the current subject was related a utf-8 MK> nodelist and not the distributed nodelist which is 7 bit ascii MK> characters only,
Then why bring up the 7 bit nodelist?
MK> with exactly only three of which are C0 control codes. The BOM being MK> three 8 bit bytes *should* produce an error for any nodelist MK> processing software given that the BOM isn't 7 bit ascii. But then MK> what does any of this have to do with creating a utf-8 nodelist?
Most nodelist processor software is not as shy as the old MakeNl. The old MakeNL will rigidly replace any non ASCII character with a question mark, but most other software is character encoding agnostic and will just pass them on "as is". This does not generate an error in the fields where "free text" is allowed.
The reason that a BOM causes an error is that a BOM normally appears at the start of a file, and therefore at the start of a line. And the start of a nodelist line is not "free text". The start of a line in the nodelist must be a semicolon, a comma or a valid keyword en a BOM is none of that.
MK> The original question was (and I quote); "How can we receive and MK> process the UTF-8 nodelists?" I don't believe you've properly MK> answered this question yet.
This thread has not ended. I did not plan to give all the answers in one message. I just give the first steps.
