Re: [dev-context] lpdf-ini.lmt: lpdf.tosixteen(), wrong conversion to UTF-16BE

2021-02-13 Thread Hans Hagen
Hi, +v = v - 0x1 ah, i hadn't noted that line (btw, in the file there is a remark where i add the 0x1 that it is inconsistent so i should have looked into it then, sigh) My other suggestion, which does the subtraction only for one surrogate is below. btw,

Re: [dev-context] lpdf-ini.lmt: lpdf.tosixteen(), wrong conversion to UTF-16BE

2021-02-12 Thread Michal Vlasák
On Tue Feb 9, 2021 at 7:49 PM CET, Hans Hagen wrote: > On 2/9/2021 6:57 PM, Michal Vlasák wrote: > > Hello, > > > > conversion to UTF-16BE PDF strings used for example in bookmarks / PDF > > outlines is not right. > > > > Take the following example: > > > > ``` > > \starttext > >

Re: [dev-context] lpdf-ini.lmt: lpdf.tosixteen(), wrong conversion to UTF-16BE

2021-02-09 Thread Hans Hagen
On 2/9/2021 6:57 PM, Michal Vlasák wrote: Hello, conversion to UTF-16BE PDF strings used for example in bookmarks / PDF outlines is not right. Take the following example: ``` \starttext \setupinteraction[state=start] \placebookmarks[section][number=no] \section[bookmark=필] \stoptext ```

[dev-context] lpdf-ini.lmt: lpdf.tosixteen(), wrong conversion to UTF-16BE

2021-02-09 Thread Michal Vlasák
Hello, conversion to UTF-16BE PDF strings used for example in bookmarks / PDF outlines is not right. Take the following example: ``` \starttext \setupinteraction[state=start] \placebookmarks[section][number=no] \section[bookmark=필] \stoptext ``` Produces: for 필 (U+1D544), instead of the