Re: [NTG-context] non-ascii chars in cmd.exe (Windows)
On 11/12/2020 10:39 PM, Pablo Rodriguez wrote:
Dear list,
I have the following sample:
\starttext
\startluacode
io.write(' Name? ')
document.name = io.read() or ''
\stopluacode
\cldcontext{document.name} is the name.
\stoptext
Running it on Linux, I can input non-ascii characters.
When running in Windows, if the input chars contains a non-ascii one,
document.name is empty.
I have no problem passing arguments from cmd with Unicode characters
(such as in '--arguments="name={αβγ}"'.
I’m using current latest (ConTeXt MkIV 2020.11.08 12:42).
I’m not sure what I am missing or whether I have hit a bug.
This has been discussed before I think. It has to do with how you
configured your system (what encoding) and how consisteltly you take
that into account. If you have some mixed setup, just don't use non-ascii.
Anyway, in LMTX all file, commandline and systemn operations are utf 8
and on windows get translated into wide system calls so there it should
work ok if you use utf8.
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] non-ascii chars in cmd.exe (Windows)
Dear list,
I have the following sample:
\starttext
\startluacode
io.write(' Name? ')
document.name = io.read() or ''
\stopluacode
\cldcontext{document.name} is the name.
\stoptext
Running it on Linux, I can input non-ascii characters.
When running in Windows, if the input chars contains a non-ascii one,
document.name is empty.
I have no problem passing arguments from cmd with Unicode characters
(such as in '--arguments="name={αβγ}"'.
I’m using current latest (ConTeXt MkIV 2020.11.08 12:42).
I’m not sure what I am missing or whether I have hit a bug.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] problems with signature fields
On 11/12/20 12:24 AM, Hans Hagen wrote: > On 11/11/2020 9:46 PM, Pablo Rodriguez wrote: >> Hans, > >> Back then, I thought it was an minor improvement. Now I realized that >> this two objects for signature fiels are only valid for Acrobat. > > the other tools should be fixed ... indirect objects are pretty valid Many thanks for your reply, Hans. I totally agree, these tools need to be fixed. I reported the issue to one of the projects more than two years ago. I’m still waiting for a message about the issue report. >> Would it be possible that signature fields may have only one object, so >> that mupdf-gl and other tools have no problem signing fields PDF >> documents generated by ConTeXt? > all is possible but i'm not sure if i want to uglify the implementation > for the sake of buggy viewers In Windows (and I guess in macOS), saving a copy with Acrobat Reader DC seems to unify both objects. But I’m afraid Acrobat for Linux is too old for that (9.5.5). Many thanks for your help, Pablo -- http://www.ousia.tk ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
