625c625
< becomes opened (note that \TEX\ does not even know it's \tex{jobname}
---
> becomes opened (note that \TEX\ does not even know its \tex{jobname}
681c681
< string field in it's attributes table (\type{permissions}).
---
> string field in its attributes table (\type{permissions}).
713a714,719
> 
> Note: The \lua{string} library functions \luatex{find} etc. are not
> Unicode-aware. In cases where this is required (i.e. because the
> pattern used for searching contains characters above code point 127),
> the corresponding functions from \lua{unicode.utf8} should be used.
> 
1519c1525
< This converts a single type name to it's internal numeric
---
> This converts a single type name to its internal numeric
1528c1534
< This converts a single whatsit name to it's internal numeric
---
> This converts a single whatsit name to its internal numeric
1631c1637
< is created using the natural width of it's components. In the three
---
> is created using the natural width of its components. In the three
1702c1708
< (it's \type{next} field will be cleared). The returned \type{head} is
---
> (its \type{next} field will be cleared). The returned \type{head} is
1845,1846c1851,1852
< texio.write(string target, string s)
< texio.write(string s)
---
> texio.write(string target, string s, ...)
> texio.write(string s, ...)
1849c1855
< Without the \type{target} argument, writes the string to the same
---
> Without the \type{target} argument, writes all given strings to the same
1857c1863,1868
< \subsubsection{\luatex{tex.write_nl}}
---
> Note: If several strings are given, and if the first of these strings
> is or might be one of the targets above, the \type{target} must be
> specified explicitely to prevent \LUA\ from interpreting the first
> string as the target.
> 
> \subsubsection{\luatex{texio.write_nl}}
1860,1861c1871,1872
< texio.write_nl(string target, string s)
< texio.write_nl(string s)
---
> texio.write_nl(string target, string s, ...)
> texio.write_nl(string s, ...)
1864,1866c1875,1877
< Like \luatex{texio.write}, but make sure that the string~\type {s} will
< appear at the beginning of a line. You can use an empty string if you
< only want to move to the next line.
---
> Like \luatex{texio.write}, but make sure that the given strings will
> appear at the beginning of a line. You can pass a single empty string
> if you only want to move to the next line.
1911,1912c1922,1923
< callback.register(string callback_name,function callback_func)
< callback.register(string callback_name,nil)
---
> id, error = callback.register(string callback_name,function callback_func)
> id, error = callback.register(string callback_name,nil)
1916c1927,1930
< below.
---
> below. The function returns the internal \type{id} of the callback
> or \type{nil}, if the callback could not be registered. In the latter
> case, \type{error} contains an error message, otherwise it is
> \type{nil}.
1923a1938,1939
> Currently, callbacks are not dumped in the format file.
> 
2039c2055
< \type{name} is a bit special in this case. It's form is
---
> \type{name} is a bit special in this case. Its form is
2246c2262
< list level, with it's token type set to \quote{inserted}. In either case,
---
> list level, with its token type set to \quote{inserted}. In either case,
2553c2569
< nil. Likewise, the retrieved value is either a function or nil.
---
> nil. Likewise, the retrieved value is either a function or \type{nil}.
2561c2577,2582
< file as actual \LUA\ bytecode, so it can also be used to preload lua code.
---
> file as actual \LUA\ bytecode, so it can also be used to preload \LUA\ code.
> 
> Note: The function must not contain any upvalues. Currently, functions
> containing upvalues can be stored (and their upvalues are set to
> \type{nil}), but this is an artefact of the current \LUA\
> implementation and thus subject to change.
2569a2591,2605
> Note: Since a \LUA\ file loaded using \luatex{loadfile(filename)} is
> essentially an anonymous function, a complete file can be stored in a
> bytecode register like this:
> 
> \startfunctioncall
> lua.bytecode[n] = loadfile(filename)
> \stopfunctioncall
> 
> Now all definitions (functions, variables) contained in the file can be
> created by executing this bytecode register:
> 
> \startfunctioncall
> lua.bytecode[n]()
> \stopfunctioncall
> 
2763c2799
< by using it's name as an index into \type{status}.
---
> by using its name as an index into \type{status}.
3895c3931
< \quote{character} nodes, consistent with it's changed meaning in \XETEX.
---
> \quote{character} nodes, consistent with its changed meaning in \XETEX.
4038c4074
<   (and it's lua counterpart \luatex{lang.patterns}) can be used at any
---
>   (and its lua counterpart \luatex{lang.patterns}) can be used at any
4455c4491
< \NC full      \NC include this font in it's entirety \NC\NR
---
> \NC full      \NC include this font in its entirety \NC\NR
5564c5600
< Single|-|character commands are no longer treated aspecially in the
---
> Single|-|character commands are no longer treated specially in the
