From jerome.laurens at u-bourgogne.fr  Mon May  2 15:26:41 2022
From: jerome.laurens at u-bourgogne.fr (=?utf-8?Q?J=C3=A9r=C3=B4me_LAURENS?=)
Date: Mon, 2 May 2022 15:26:41 +0200
Subject: [luatex] Documentation of tex.print
Message-ID: <DD3BFCB7-0FCA-4ED3-9829-919F9DC4D499@u-bourgogne.fr>

luatex.pdf v 1.15 p 24, reads

"The most simple use of these is tex.print(<string> s)"

Next examples on the same page read

"tex.print(tex.count[10]+5)"
and
"tex.print(math.pi)"
Both arguments are not strings: this is an unrelated and undocumented usage of "tex.print" that would deserve a note in the appropriate section

According to the documentation p201, next instruction

\directlua{tex.print({?1?, 2, ?3'})}

should stop printing at 2 because it is not a string.
Actually it prints all the elements of the table, at least in luatex 1.13.2



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/luatex/attachments/20220502/ce3a6a1f/attachment.html>

From P.Taylor at Hellenic-Institute.Uk  Mon May  2 15:50:51 2022
From: P.Taylor at Hellenic-Institute.Uk (Philip Taylor (Hellenic Institute))
Date: Mon, 2 May 2022 14:50:51 +0100
Subject: [luatex] [EXT]  Documentation of tex.print
In-Reply-To: <DD3BFCB7-0FCA-4ED3-9829-919F9DC4D499@u-bourgogne.fr>
References: <DD3BFCB7-0FCA-4ED3-9829-919F9DC4D499@u-bourgogne.fr>
Message-ID: <c0400d6c-a45a-3904-8198-f85bce9120a1@Hellenic-Institute.Uk>

On 02/05/2022 14:26, J?r?me LAURENS wrote:
> luatex.pdf v 1.15 p 24, reads
>
> "The most simple use of these is tex.print(<string> s)"
>
> Next examples on the same page read
>
> "tex.print(tex.count[10]+5)"
> and
> "tex.print(math.pi)"
> Both arguments are not strings: this is an unrelated and undocumented 
> usage of "tex.print" that would deserve a note in the appropriate section

"Undocumented" ?? Does 10.3.14.1 not read

> 10.3.14.1 print
> tex.print(<string> s, ...)
> tex.print(<number> n, <string> s, ...)
> tex.print(<table> t)
> tex.print(<number> n, <table> t)
-- 
/Philip Taylor/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/luatex/attachments/20220502/d82f20c5/attachment.html>

From jerome.laurens at u-bourgogne.fr  Mon May  2 16:11:02 2022
From: jerome.laurens at u-bourgogne.fr (=?utf-8?Q?J=C3=A9r=C3=B4me_LAURENS?=)
Date: Mon, 2 May 2022 16:11:02 +0200
Subject: [luatex] [EXT]  Documentation of tex.print
In-Reply-To: <c0400d6c-a45a-3904-8198-f85bce9120a1@Hellenic-Institute.Uk>
References: <DD3BFCB7-0FCA-4ED3-9829-919F9DC4D499@u-bourgogne.fr>
 <c0400d6c-a45a-3904-8198-f85bce9120a1@Hellenic-Institute.Uk>
Message-ID: <997A648C-42EE-47D8-8A8D-5D1B231B802A@u-bourgogne.fr>

According to the documentation you pointed out, a unique argument can be either a string or a table, but nothing about a single number

Notice that the undocumented tex.print(<number>n) prints the number n whereas tex.print(<number>n, nil) prints nothing, which is expected despite it may feel "a little" out of bounds...


> Le 2 mai 2022 ? 15:50, Philip Taylor (Hellenic Institute) <P.Taylor at Hellenic-Institute.Uk> a ?crit :
> 
> On 02/05/2022 14:26, J?r?me LAURENS wrote:
>> luatex.pdf v 1.15 p 24, reads
>> 
>> "The most simple use of these is tex.print(<string> s)"
>> 
>> Next examples on the same page read
>> 
>> "tex.print(tex.count[10]+5)"
>> and
>> "tex.print(math.pi)"
>> Both arguments are not strings: this is an unrelated and undocumented usage of "tex.print" that would deserve a note in the appropriate section
> "Undocumented" ?  Does 10.3.14.1 not read 
> 
>> 10.3.14.1 print
>> tex.print(<string> s, ...)
>> tex.print(<number> n, <string> s, ...)
>> tex.print(<table> t)
>> tex.print(<number> n, <table> t)
> -- 
> Philip Taylor
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/luatex/attachments/20220502/5edafe45/attachment.html>

From luigi.scarso at gmail.com  Mon May  2 17:00:57 2022
From: luigi.scarso at gmail.com (luigi scarso)
Date: Mon, 2 May 2022 17:00:57 +0200
Subject: [luatex] [EXT] Documentation of tex.print
In-Reply-To: <997A648C-42EE-47D8-8A8D-5D1B231B802A@u-bourgogne.fr>
References: <DD3BFCB7-0FCA-4ED3-9829-919F9DC4D499@u-bourgogne.fr>
 <c0400d6c-a45a-3904-8198-f85bce9120a1@Hellenic-Institute.Uk>
 <997A648C-42EE-47D8-8A8D-5D1B231B802A@u-bourgogne.fr>
Message-ID: <CAG5iGsD8uWJKGbps5ABFcKuDo6XFi-mu=Rt1fJFoL6STHd+gQQ@mail.gmail.com>

On Mon, May 2, 2022 at 4:11 PM J?r?me LAURENS <jerome.laurens at u-bourgogne.fr>
wrote:

> According to the documentation you pointed out, a unique argument can be
> either a string or a table, but nothing about a single number
>
> Notice that the undocumented tex.print(<number>n) prints the number n
> whereas tex.print(<number>n, nil) prints nothing, which is expected despite
> it may feel "a little" out of bounds...
>
>
Numbers are converted to string --  this is quite common in Lua when there
is something to print -- but in this case the catcode regime can be
confusing.
I will add a note.


-- 
luigi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/luatex/attachments/20220502/b8111294/attachment.html>

From jerome.laurens at u-bourgogne.fr  Fri May  6 22:49:22 2022
From: jerome.laurens at u-bourgogne.fr (=?utf-8?Q?J=C3=A9r=C3=B4me_LAURENS?=)
Date: Fri, 6 May 2022 22:49:22 +0200
Subject: [luatex] Documentation improvement about open_read_file callbacks
	and readers
Message-ID: <887D2786-5D5D-4F1D-8ADD-4A1D4B20AF61@u-bourgogne.fr>

The documentation about readers (p 172 for v1.15) is

```
Your function should return either a string or nil. The value nil signals that the end of file has
occurred, and will make TEX call the optional close function next.

```
This is partly exact. If the reader returns nil since the very first call, then it is called once again and only then the close function is eventually called. The reader is always called at least twice. It is worth mentioning because it may be counterintuitive.



From luigi.scarso at gmail.com  Sun May  8 13:04:56 2022
From: luigi.scarso at gmail.com (luigi scarso)
Date: Sun, 8 May 2022 13:04:56 +0200
Subject: [luatex] Documentation improvement about open_read_file
 callbacks and readers
In-Reply-To: <887D2786-5D5D-4F1D-8ADD-4A1D4B20AF61@u-bourgogne.fr>
References: <887D2786-5D5D-4F1D-8ADD-4A1D4B20AF61@u-bourgogne.fr>
Message-ID: <CAG5iGsBYupDAUeoMHuAkuNkWv8iWt7uX1_C39U3UGSctS=H4QA@mail.gmail.com>

On Fri, May 6, 2022 at 10:50 PM J?r?me LAURENS <
jerome.laurens at u-bourgogne.fr> wrote:

> The documentation about readers (p 172 for v1.15) is
>
> ```
> Your function should return either a string or nil. The value nil signals
> that the end of file has
> occurred, and will make TEX call the optional close function next.
>
> ```
> This is partly exact. If the reader returns nil since the very first call,
> then it is called once again and only then the close function is eventually
> called. The reader is always called at least twice. It is worth mentioning
> because it may be counterintuitive.
>
>
(sorry for the delay)
For sake of completeness,  can you add an example ?



-- 
luigi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/luatex/attachments/20220508/5c52e4cf/attachment.html>

From jerome.laurens at u-bourgogne.fr  Wed May 11 01:05:57 2022
From: jerome.laurens at u-bourgogne.fr (=?utf-8?Q?J=C3=A9r=C3=B4me_LAURENS?=)
Date: Wed, 11 May 2022 01:05:57 +0200
Subject: [luatex] Bug in the documentation
Message-ID: <B579D594-6A27-4922-A8D0-15333045DD6A@u-bourgogne.fr>

LuaTeX manual v1.15 p221 section 10.6.6 nota bene

All 3 examples read

```
foo: foo
bar : bar
myFirstBar:
```
despite the `\bar` command has been redefined multiple times.

JL


From dietzbt at gmail.com  Wed May 11 05:45:30 2022
From: dietzbt at gmail.com (dietzbt at gmail.com)
Date: Wed, 11 May 2022 09:15:30 +0530
Subject: [luatex] Xetexinterwordspaceshaping command in LuaTeX
Message-ID: <83c2ed5e-1f11-646f-ed1b-e34dfdbac8bd@gmail.com>

An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/luatex/attachments/20220511/760dd9f5/attachment.html>