[dev-context] LuaTeX 1.18.0

[luigi scarso]

The upcoming version 1.18.0 has some changes that are not compatible with
previous versions but should only apply in kpse mode:

1) the debug library is disabled; can be enabled with --luadebug

2) os.rename os.remove and lfs library functions are checked
from kpse to see if the path is legal

I'm sure some packages that use debug won't work without --luadebug at
least.

LuaLaTeX should be ok, and also ConTeXt mkiv should be ok.


--
luigi
___
dev-context mailing list -- dev-context@ntg.nl
To unsubscribe send an email to dev-context-le...@ntg.nl

Re: [dev-context] Italic correction missing when using \left...\right

[luigi scarso]

On Tue, Apr 26, 2022 at 10:04 AM luigi scarso 
wrote:

>
>
> On Tue, Apr 26, 2022 at 8:59 AM Henri Menke  wrote:
>
>> On Mon, 2022-04-25 at 22:09 +0200, Henri Menke wrote:
>> > Dear devs,
>> >
>> > When using delimiter with \left...\right the italic correction
>> > between
>> > the preceding letter and the delimiter is dropped. I've tried this
>> > with
>> > a few fonts and all show the problem. For Libertinus Math the glyphs
>> > even overlap.
>> >
>> > MWE for mtxrun --script plain (TeX Live 2022)
>> >
>> >%\input luaotfload.sty
>> >\font\mathfont="file:LibertinusMath-
>> > Regular.otf:mode=base;script=math" at 10pt
>> >\textfont0=\mathfont
>> >\textfont2=\mathfont
>> >
>> >\Umathcodenum`f="1D453
>> >\protected\def\langle{\Udelimiter"4"0"27E8\relax}
>> >\protected\def\rangle{\Udelimiter"5"0"27E9\relax}
>> >
>> >$f\rangle$
>> >
>> >\nulldelimiterspace=0pt
>> >$\left.f\right\rangle$
>> >
>> >\bye
>>
>> Ulrike pointed out \mathitalicsmode=1 on TeX Stack Exchange, but there
>> is still an issue with sub_mlists:
>>
>>%\input luaotfload.sty
>>\font\mathfont="file:LibertinusMath-Regular.otf:mode=base;script=math"
>> at 10pt
>>\textfont0=\mathfont
>>\textfont2=\mathfont
>>
>>\Umathcodenum`f="1D453
>>\protected\def\langle{\Udelimiter"4"0"27E8\relax}
>>\protected\def\rangle{\Udelimiter"5"0"27E9\relax}
>>
>>\mathitalicsmode=1
>>
>>$f\rangle$
>>
>>\nulldelimiterspace=0pt
>>$\left.f\right\rangle$
>>
>>${-f}\rangle$
>>
>>$\left.{-f}\right\rangle$
>>
>>\bye
>>
>
> I will check it, but have  you already seen mlist.c  ?
>
> --
> luigi
>

Hans has enabled \mathitalicsmode=2.
Committed revision 7525.
-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] Italic correction missing when using \left...\right

[luigi scarso]

On Tue, Apr 26, 2022 at 8:59 AM Henri Menke  wrote:

> On Mon, 2022-04-25 at 22:09 +0200, Henri Menke wrote:
> > Dear devs,
> >
> > When using delimiter with \left...\right the italic correction
> > between
> > the preceding letter and the delimiter is dropped. I've tried this
> > with
> > a few fonts and all show the problem. For Libertinus Math the glyphs
> > even overlap.
> >
> > MWE for mtxrun --script plain (TeX Live 2022)
> >
> >%\input luaotfload.sty
> >\font\mathfont="file:LibertinusMath-
> > Regular.otf:mode=base;script=math" at 10pt
> >\textfont0=\mathfont
> >\textfont2=\mathfont
> >
> >\Umathcodenum`f="1D453
> >\protected\def\langle{\Udelimiter"4"0"27E8\relax}
> >\protected\def\rangle{\Udelimiter"5"0"27E9\relax}
> >
> >$f\rangle$
> >
> >\nulldelimiterspace=0pt
> >$\left.f\right\rangle$
> >
> >\bye
>
> Ulrike pointed out \mathitalicsmode=1 on TeX Stack Exchange, but there
> is still an issue with sub_mlists:
>
>%\input luaotfload.sty
>\font\mathfont="file:LibertinusMath-Regular.otf:mode=base;script=math"
> at 10pt
>\textfont0=\mathfont
>\textfont2=\mathfont
>
>\Umathcodenum`f="1D453
>\protected\def\langle{\Udelimiter"4"0"27E8\relax}
>\protected\def\rangle{\Udelimiter"5"0"27E9\relax}
>
>\mathitalicsmode=1
>
>$f\rangle$
>
>\nulldelimiterspace=0pt
>$\left.f\right\rangle$
>
>${-f}\rangle$
>
>$\left.{-f}\right\rangle$
>
>\bye
>

I will check it, but have  you already seen mlist.c  ?

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] Where is the LuaTeX SVN?

[luigi scarso]

On Mon, Apr 18, 2022 at 12:10 PM Henri Menke  wrote:

> Dear list,
>
> On the ConTeXt wiki there are links to the LuaTeX SVN:
>
>https://wiki.contextgarden.net/ConTeXt_Standalone/Implementation#LuaTeX
>
>SVN: https://foundry.supelec.fr/svn/luatex
>ViewVC: https://foundry.supelec.fr/scm/viewvc.php/?root=luatex
>Files: http://foundry.supelec.fr/gf/project/luatex/frs/
>
> However, none of these links work. All connections time out.
>
> Somewhere on the mailing list I found this alternative server
>
>https://serveur-svn.lri.fr/svn/modhel/luatex/
>
> but this doesn't have ViewVC to browse the history.
>

This is the official site, already from a while,  is
 https://www.luatex.org/download.html

As per https://tug.org/pipermail/luatex/2022-April/007668.html
I am trying to set up a git mirror of the svn site, but I am not able to
see the vendor branch yet.

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] Bug: Null-byte in csname not handled correctly

[luigi scarso]

On Wed, Apr 13, 2022 at 9:29 AM luigi scarso  wrote:

>
>
> On Mon, Apr 11, 2022 at 8:16 PM Henri Menke  wrote:
>
>> Dear devs,
>>
>> A control sequence that only contains a single null byte is not
>> correctly stringified. Comparison between Knuth TeX and LuaTeX:
>>
>>$ tex test.tex
>>! \^^@.
>>l.2 \errmessage{\string\^^@}
>>
>>$ luatex test.tex
>>! \.
>>l.2 \errmessage{\string\^^@}
>>
>> MWE:
>>
>>\catcode0=11
>>\errmessage{\string\^^@}
>>\bye
>>
>>
> looking at it.
>
>
Committed revision 7521.
-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] Bug: Null-byte in csname not handled correctly

[luigi scarso]

On Mon, Apr 11, 2022 at 8:16 PM Henri Menke  wrote:

> Dear devs,
>
> A control sequence that only contains a single null byte is not
> correctly stringified. Comparison between Knuth TeX and LuaTeX:
>
>$ tex test.tex
>! \^^@.
>l.2 \errmessage{\string\^^@}
>
>$ luatex test.tex
>! \.
>l.2 \errmessage{\string\^^@}
>
> MWE:
>
>\catcode0=11
>\errmessage{\string\^^@}
>\bye
>
>
looking at it.

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] [luatex] Bug: attempt to double-free kern node

[luigi scarso]

On Sat, Apr 9, 2022 at 6:07 PM luigi scarso  wrote:

>
>
> On Sat, Apr 9, 2022 at 6:05 PM Henri Menke via luatex 
> wrote:
>
>> Dear devs,
>>
>>! error:  (nodes): attempt to double-free kern node 239, ignored
>>!  ==> Fatal error occurred, no output PDF file produced!
>>
>> MWE:
>>
>>\catcode`@=11
>>
>>\Umathordordspacing\displaystyle=\thinmuskip
>>\Umathordordspacing\textstyle=\thinmuskip
>>
>>\def\operator@font{\fam0}
>>
>>\def\qopname#1#2#3{%
>>  \mathop{\mathpalette\@qopname{#1\kern\z@\operator@font#3}}\csname
>> n#2limits@\endcsname
>>}
>>\def\@qopname#1#2{%
>>  \hbox{$
>>\Umathordordspacing\displaystyle=0mu
>>\Umathordordspacing\textstyle=0mu
>>\m@th#1#2
>>$}}
>>
>>\def\max{\qopname\relax m{max}}
>>\def\min{\qopname\relax m{max}}
>>
>>\catcode`@=12
>>
>>$$\max a b / \min a b$$
>>
>>\bye
>>
>
> ok, thank you . Checking it now.
>


It should be fixed in rev7518.

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] [luatex] Bug: attempt to double-free kern node

[luigi scarso]

On Sat, Apr 9, 2022 at 6:05 PM Henri Menke via luatex 
wrote:

> Dear devs,
>
>! error:  (nodes): attempt to double-free kern node 239, ignored
>!  ==> Fatal error occurred, no output PDF file produced!
>
> MWE:
>
>\catcode`@=11
>
>\Umathordordspacing\displaystyle=\thinmuskip
>\Umathordordspacing\textstyle=\thinmuskip
>
>\def\operator@font{\fam0}
>
>\def\qopname#1#2#3{%
>  \mathop{\mathpalette\@qopname{#1\kern\z@\operator@font#3}}\csname
> n#2limits@\endcsname
>}
>\def\@qopname#1#2{%
>  \hbox{$
>\Umathordordspacing\displaystyle=0mu
>\Umathordordspacing\textstyle=0mu
>\m@th#1#2
>$}}
>
>\def\max{\qopname\relax m{max}}
>\def\min{\qopname\relax m{max}}
>
>\catcode`@=12
>
>$$\max a b / \min a b$$
>
>\bye
>

ok, thank you . Checking it now.

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

[dev-context] Luatex 1.11.1 announcement

[luigi scarso]

==
LuaTeX 1.11.1 2019-10-28
==

First release of luahbtex / luajithbtex,
luatex / luajittex with harfbuzz.
Small bug fixes, code clean up and a couple of new primitives
to match eTeX.
A new callback lua.getcodepage()  for diagnostic purposes.
*** DROPPED the   "page_objnum_provider" callback, replaced with
"page_order_index". ***
See ChangeLog and the manual.

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] attachments in PDF/A-3

[luigi scarso]

Il Dom 17 Mar 2019, 16:42 Pablo Rodriguez  ha scritto:

> Dear list,
>
> my sample to add attachments to a PDF/A-3 valid document is the following:
>
> \setuptagging[state=start]
>
> \setupbodyfont[30pt]
>
> \setupbackend
>   [format=PDF/A-3a,
>intent=sRGB IEC61966-2.1,
>profile={sRGB.icc,default_gray.icc},
>level=0]
>
> \setupcolors[pagecolormodel=auto]
>
> \setupinteraction[state=start]
> \starttext
> \startTEXpage[offset=1em]
> an attachment\attachment[file=xml-mkiv.pdf]
> \stopTEXpage
> \stoptext
>
> There are five reported errors when tested with the latest development
> version of veraPDF (http://downloads.verapdf.org/dev/verapdf-installer.zip
> ):
>
> - Annotation should have /F value
> (
> https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-and-3-rules#rule-632-1
> );
> unless their Rect key value 1 equal to value 3 and value 2 equal to
> value 4, or the annotation subtype is /Popup or /Link.
>
> - Although not reported, the /F value should conform these considerations:
>
> If present, the F key's Print flag bit shall be set to 1 and its
> Hidden, Invisible, ToggleNoView, and NoView flag bits shall be set
> to 0.
>
> https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-and-3-rules#rule-632-2
>
> - Annotations need an appearance dictionary
> (
> https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-and-3-rules#rule-633-1
> );
> unless the same exception for the /F value apply.
>
> - The /EmbeddedFile dictionary should specify the MIME type in its
> /Subtype entry
> (
> https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-and-3-rules#rule-68-1
> ).
>
> - The /AFRelationship key is missing from the /Filespec dictionary
> (
> https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-and-3-rules#rule-68-3
> ).
> Possible values are: Source, Data, Alternative, Supplement,
> EncryptedPayload, FormData, Schema or Unspecified (from
> https://www.pdfa.org/wp-content/uploads/2018/10/PDF20_AN002-AF.pdf).
>
> - The /Filespec lacks association with the PDF document or any of its
> parts, such as pages
> (
> https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-and-3-rules#rule-68-4
> ).
>
> From
> https://www.pdfa.org/wp-content/uploads/2018/10/PDF20_AN002-AF.pdf,
> it seems that either the /Catalog or a /Page dictionary (there are
> other ones, but I would limit attachments in ConTeXt to those two
> [if not to the /Catalog itself only]) should contain an /AF entry
> with the reference to the /Filespec object(s). I assume that
> the value type for the /AF entry is an array of one or multiple
> object references.
>
> These are all the issues veraPDF finds when validating the PDF document
> generated from the source above.
>
> I hope it helps. Many thanks for your help,
>
> Pablo
> --
> http://www.ousia.tk
> ___
> dev-context mailing list
> dev-context@ntg.nl
> https://mailman.ntg.nl/mailman/listinfo/dev-context
>

Ok, thank you very much.
--
luigi

>
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] attachments with PDF/A-3

[luigi scarso]

On Tue, Mar 12, 2019 at 8:59 PM Pablo Rodriguez  wrote:

> Dear list,
>
> I have generated a PDF/A-3 compilant document, but as I add attachments
> the validation from veraPDF warns about errors.
>
> There are five issues, which I can document here. Sorry, but I’m afraid
> I cannot provide patches.
>
> Can we discuss these issues now, or is it better to wait until TeX Live
> 2019 has been released?
>
>
it's better to discuss it now. Could be go in context on texlive 2019 or
not, but
context users usually update context independently from texlive, so we can
check it early.



-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

[dev-context] Luatex 1.09.2 announcement

[luigi scarso]

==
LuaTeX 1.09.2 2019-01-19
==

This is a transitional release to LuaTeX 1.10 for TeX Live 2019




The LuaTeX team
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] Bug#480725: (fwd) Bug#480725: mptopdf does not work with beginfig(-1)

[luigi scarso]

On Tue, Jan 29, 2019 at 9:15 AM Hilmar Preuße  wrote:

> tags 480725 - patch
> stop
>
>




> On 15.05.08 09:49, Taco Hoekwater wrote:
> > Norbert Preining wrote:
>
> Dear Taco,
>
> >> forwarded 480725 dev-context@ntg.nl
> >> thanks
> >>
> >> Dear Hans, dear Taco,
> >>
> >> on the Debian side we got the attached bug report together with a patch
> >> for mptopdf.pl. Can you comment on it, or consider it for inclusion?
> >
> The issue reported in https://bugs.debian.org/480725 is nevertheless
> still present and reproducible. When pasting the following content into
> a file called input.mp and calling "mptopdf input.mp" no pdf file is
> created, just the intermediate ps file.
>
> This needs to be handled.
>
> > The patch would have to be a bit elaborated on before inclusion
> > can be considered, I believe. A random file named .ps
> > is highly likely not to be metapost output at all. The extra
> > functionality would be cool to have, but mptopdf had better check
> > if the .ps really was created by metapost (by grepping for the
> > %%Creator comment).
> >
>

Thank you for the report, we will try to fix it for the upcoming texlive
2019.

With texlive 2018 you can produce the pdf directly

%% test.mp
input metauml;
beginfig(-1);
  Begin.b;
  End.e;
  e.w = b.e + (15,0);
  drawObjects(b,e);
  clink(transition)(b, e);
endfig;
end

$> mtxrun --script metapost --metafun test.mp


-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] ARMv7 hardfp or softfp detection

[luigi scarso]

On Mon, Nov 5, 2018 at 6:14 PM Sebastian Miele 
wrote:

> first-setup.sh from ConTeXt standalone contains the following lines:
>
> readelf -A /proc/self/exe | grep -q '^ \+Tag_ABI_VFP_args'
> if [ ! $? ]; then
>
> That probably does not work as intended, because [ ! $? ] is
> equivalent to [ ! -n $? ]. It does not return the negation of the
> return code of the previous command. [ ! 0 ] and [ ! 1 ] both have
> exit code 1, because the strings '0' and '1' are both non-null.
>
> Probably no-one actually uses ARMv7 with softfp, including me.
>

Ok, thank you very much.
(I think that the script could be something like
readelf -A /proc/self/exe | grep -q '^ \+Tag_ABI_VFP_args' && true ||
platform="linux-armel"
)

Are you using 32bit linux-gnueabi ?


-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

[dev-context] Luatex 1.09.0 announcement

[luigi scarso]

==
LuaTeX 1.09 2018-10-23
==

(1) This is a release that fixed some bugs, and the latest
with lua 5.2.

(2) luaffi is still incomplete, so very likely there will be
a new release 1.09.1 before the next year.


The LuaTeX team
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

[dev-context] Luatex 1.08.0 announcement

[luigi scarso]

==
LuaTeX 1.08 2018-08-28
==


(1) This release is a prelude to 1.10, the next stable iteration of LuaTeX
after version 1.00.

(2) Lua 5.3 is now considered to be default and we might use 5.4 in version
1.10. There are no real functional changed expected. You still need to
rename
the binary for 5.3!

(3) Binary mode is no longer available in MPlib but it is still available in
stand alone MetaPost. This simplifies compilation and reduces dependencies.

(4) The dependency on Poppler for pdf image inclusion has been removed. We
now use a small dedicated library written by Pawel Jakowski. We no longer
need c++ compilers. We're in the process of making it behave well on all
platforms. It has been tested on intel platforms.

(5) We know that there can be some (alignment) issues with the arm platform
but these are looked into. Therefore, later this year we will release 1.09.
Version 1.10 is planned for TeXlive. We hope that ffi works ok on intel and
arm platforms at that point.

(6) There have been some extensions to the Lua libraries and some callbacks
have been added. Also, a few new primitives have been introduced. The
documentation mentions the stable extensions.

(7) There are the usual bug fixes and cleanups but there have been no real
fundamental changes in the API.

The LuaTeX team
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

[dev-context] Luatex 1.07.0 announcement

[luigi scarso]

==
LuaTeX 1.07 2018-01-17
==

(1) This release brings Lua 5.3 to LuaTeX. We have tested an experimental
version
for a few months and not encountered issues.

(2) If you use Lua 5.3 you should be aware of a few changes in the language
and
its implementation. Numbers are now either integers or floats but are cast
automatically.

(3) In some cases (e.g. string.format) there is a more strict check. A
float always
has a decimal appended when serialized, so 1 becomes 1.0 as string.

(4) We keep supporting the bit32 library on top of the new bit operators.
Be aware
of the fact that currently LuajitTeX does not have these operators.

(5) Performance of LuaTeX with Lua 5.3 can be slightly better than with 5.2
but this
really depends on your usage of Lua. In practice there should be no
slowdown.

(6) We are aware of possible substantial slowdown of string.format
depending on the
platform and compiler. This depends on Lua too and will be resolved in due
time.

(7) If you want to test with Lua 5.3 then have to build LuaTeX with
--lua53. Because
ConTeXt will switch to 5.3 after this release there will be binaries
available at the
ConTeXt garden.

(8) The 2018 TeXlive distribution will ship with LuaTeX using Lua 5.2 but
there will
likely be an additional binary LuaTeX53 available.

(9) From 2019 TeXlive will ship with LuaTeX and Lua 5.3 as default. We
provide --lua52
as build flag for a while. By then we might be looking at Lua 5.4 already.

(10) There are the usual patches and cleanups and a few small additions
(mentioned
in the manual) but there have been no fundamental changes in the API (apart
from
removing depricated and undocumented functionality).



The LuaTeX team
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] fix output intent subtype

[luigi scarso]

On Tue, Oct 24, 2017 at 9:48 PM, Pablo Rodriguez  wrote:
> I will investigate the issue myself and report here (or in the user
> list) the results.

this is the right list

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] fix output intent subtype

[luigi scarso]

On Tue, Oct 24, 2017 at 8:21 PM, Alan Braslau  wrote:
> "Let the buyer beware".
>
> Given that bitmap graphics are NOT OK (think bloat, an MS/Office
> specialty), there must be a better solution. Perhaps simply detecting a
> conflict between an included PDF and the "host" PDF and printing a
> warning! Then it could be up to the user to "fix" the included PDF so
> not to break the host PDF.
For the purpose of pdf/a (long term preservation, reproducibility and
robustness of the file )
bitmap graphics are ok. RGB is one of the best color space.


-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] fix output intent subtype

[luigi scarso]

On Tue, Oct 24, 2017 at 7:42 PM, Pablo Rodriguez <oi...@gmx.es> wrote:
> On 10/24/2017 07:06 PM, luigi scarso wrote:
>> a pdf ?
>> As said previously , including pdf can break the rules of
>> format=PDF/A-3a.
>> Simply include bitmap images, it's way more robust.
>
> Allow me a fair and respectful disagreement, Luigi.
>
> Bitmap images are less problematic in PDF/A because they include their
> own color space. This is why they work even with /S /GTS_PDFA3.
>
> But replacing vectors with bitmaps is a way of avoiding the issue, not
> of fixing it (if this needs to be fixed).
yes, it's a  clean way to resolve a problem that could not be solvable.
The point is that is more easy to make a correct pdf than fix an
arbitrary pdf to make it conform to the document
---  there are tools like pitstop for that.


-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] fix output intent subtype

[luigi scarso]

On Tue, Oct 24, 2017 at 7:27 PM, Alan Braslau <braslau.l...@comcast.net> wrote:
> On Tue, 24 Oct 2017 19:06:51 +0200
> luigi scarso <luigi.sca...@gmail.com> wrote:
>
>> is this
>>  \externalfigure[cow]
>> a pdf ?
>> As said previously , including pdf can break the rules of
>> format=PDF/A-3a.
>> Simply include bitmap images, it's way more robust.
>
> Isn't that non-optimal, using bitmap images rather than vector graphics?
> Must there not be a way to correctly include PDF graphics, perhaps
> modifying the included file to make it conforming?
Forgetting for the moment that a generic pdf could not have the right
structure (and fix it can be quite complicate)
you can have a "guest" pdf file that is valid pdf/a but once included
with  \externalfigure can conflicts with the "host" pdf, because the
host specifies a different color spaces, for example.
On the other side, if you include it as bitmap, you are safe on the
color spaces and the structure.
Of course This sound not ok if the pdf is only text --- but even in
this case the situation is not so simple:
the fonts must be correct (it's known that we have math fonts that are
not ok ), the tounicode also..
so also in this case a high res bitmap can be the only solution.,
-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] fix output intent subtype

[luigi scarso]

On Tue, Oct 24, 2017 at 7:02 PM, Pablo Rodriguez  wrote:
> On 10/24/2017 01:48 PM, Peter Rolf wrote:
>> [...]
>> Well, the good news is that the actual problem does not effect any A1
>> documents. And even with an incomplete (99.9%) validity the documents
>> stay usable. I'm sure that (alien) historians will love any ConTeXt
>> created PDF/A document :D
>
> Sorry, Peter, but I’m afraid that the bad news is that CMYK in form
> xobjects doesn’t work fine :-(:
>
> \nopdfcompression
>
> \setupexternalfigures[location=default]
>
> \setuptagging[state=start]
>
> \setupbackend
>   [format=PDF/A-3a,
>intent=sRGB IEC61966-2.1,
>profile={isocoated_v2_eci.icc,default_gray.icc},
>level=0]
>
> \setupcolors[pagecolormodel=auto]
>
> \starttext
> \startTEXpage[offset=1em]
> \externalfigure[cow]
> \stopTEXpage
> \stoptext
>
> I don’t use CMYK myself, but am I missing something or is this something
> that needs further investigation?
is this
 \externalfigure[cow]
a pdf ?
As said previously , including pdf can break the rules of
format=PDF/A-3a.
Simply include bitmap images, it's way more robust.

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] fix output intent subtype

[luigi scarso]

On Tue, Oct 24, 2017 at 10:23 AM, luigi scarso <luigi.sca...@gmail.com> wrote:
> On Tue, Oct 24, 2017 at 10:14 AM, luigi scarso <luigi.sca...@gmail.com> wrote:
> infact
> $ convert cow-brown.pdf --flatten -density 300 cow-brown.png
>
>
> %% unrgb.tex
> \nopdfcompression
> \setupexternalfigures[location=default]
> \setuptagging[state=start]
> \setupbackend
>   [format=PDF/A-3a,
>intent=sRGB IEC61966-2.1,
>profile={sRGB.icc,default_gray.icc},
>level=0]
> \setupcolors[cmyk=no, pagecolormodel=auto]
> \starttext
> \startTEXpage[offset=1em]
> \externalfigure[cow-brown.png]
> \stopTEXpage
> \stoptext
>
> $ context unrgb.tex
>
> $ verapdf -f 3a unrgb.pdf
> 
> 
>   
>  buildDate="2017-08-14T09:56:00+02:00">
>  buildDate="2017-08-21T14:17:00+02:00">
>  buildDate="2017-08-21T14:49:00+02:00">
>   
>   
> 
>   
> /opt/luatex/harald/Indien-2015/unrgb.pdf
>   
>statement="PDF file is compliant with Validation Profile
> requirements." isCompliant="true">
>  failedChecks="0">
>   
>finish="1508833359138">00:00:00.395
> 
>   
>   
>  failedJobs="0">1
> 0
> 0
>  finish="1508833359162">00:00:00.479
>   
> 
>
>
> --
> luigi

ah yes, of course
11 0 obj
<< /DestOutputProfile 7 0 R /Info (sRGB IEC61966-2.1) /OutputCondition
() /OutputConditionIdentifier (Custom) /RegistryName
(http://www.color.org) /S /GTS_PDFA3 /Type /OutputIntent >>
endobj


-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] fix output intent subtype

[luigi scarso]

On Tue, Oct 24, 2017 at 10:14 AM, luigi scarso <luigi.sca...@gmail.com> wrote:
> On Tue, Oct 24, 2017 at 10:01 AM, Peter Rolf <peter.r...@arcor.de> wrote:
>>
>> Yes. My guess (as I have no ISO documention) at that time was, that the
>> number should be increased with the versions. I couldn't imagine, why
>> the should use a number in that flag (there may be reasons for it, but I
>> donno them).
>>
>> Anyhow, I'll download veraPDF and test all variants with the actual
>> beta. I doubt that the results will differ. If I find any other errors
>> you can fix them at one go. Will report back (probably after lunch
>> break). I hope nobody is in a hurry :D
>
> I have made a test with pdf/a-2a, pdf/a-3a, they pass  both the
> verapdf 1.8.4 and 1.9.46-dev
> The problem with the file
> $ cat unrgb.tex
> \nopdfcompression
> \setupexternalfigures[location=default]
> \setuptagging[state=start]
> \setupbackend
>   [format=PDF/A-3a,
>intent=sRGB IEC61966-2.1,
>profile={sRGB.icc,default_gray.icc},
>level=0]
> \setupcolors[cmyk=no, pagecolormodel=auto]
> \starttext
> \startTEXpage[offset=1em]
> \externalfigure[cow-brown]
> \stopTEXpage
> \stoptext
>
> is that it includes a pdf (cow-brown.pdf)  and this can lead to
> conflicts with the specs. of the setupbackend.
> There is no way to solve this: even is both the pdf are pdf/a-3a ok,
> they can conflict.
> So, the safest way is always to include bitmap images.
>
> --
> luigi

infact
$ convert cow-brown.pdf --flatten -density 300 cow-brown.png


%% unrgb.tex
\nopdfcompression
\setupexternalfigures[location=default]
\setuptagging[state=start]
\setupbackend
  [format=PDF/A-3a,
   intent=sRGB IEC61966-2.1,
   profile={sRGB.icc,default_gray.icc},
   level=0]
\setupcolors[cmyk=no, pagecolormodel=auto]
\starttext
\startTEXpage[offset=1em]
\externalfigure[cow-brown.png]
\stopTEXpage
\stoptext

$ context unrgb.tex

$ verapdf -f 3a unrgb.pdf


  



  
  

  
/opt/luatex/harald/Indien-2015/unrgb.pdf
  
  

  
  00:00:00.395

  
  
1
0
0
00:00:00.479
  



-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] fix output intent subtype

[luigi scarso]

On Tue, Oct 24, 2017 at 10:01 AM, Peter Rolf  wrote:
>
> Yes. My guess (as I have no ISO documention) at that time was, that the
> number should be increased with the versions. I couldn't imagine, why
> the should use a number in that flag (there may be reasons for it, but I
> donno them).
>
> Anyhow, I'll download veraPDF and test all variants with the actual
> beta. I doubt that the results will differ. If I find any other errors
> you can fix them at one go. Will report back (probably after lunch
> break). I hope nobody is in a hurry :D

I have made a test with pdf/a-2a, pdf/a-3a, they pass  both the
verapdf 1.8.4 and 1.9.46-dev
The problem with the file
$ cat unrgb.tex
\nopdfcompression
\setupexternalfigures[location=default]
\setuptagging[state=start]
\setupbackend
  [format=PDF/A-3a,
   intent=sRGB IEC61966-2.1,
   profile={sRGB.icc,default_gray.icc},
   level=0]
\setupcolors[cmyk=no, pagecolormodel=auto]
\starttext
\startTEXpage[offset=1em]
\externalfigure[cow-brown]
\stopTEXpage
\stoptext

is that it includes a pdf (cow-brown.pdf)  and this can lead to
conflicts with the specs. of the setupbackend.
There is no way to solve this: even is both the pdf are pdf/a-3a ok,
they can conflict.
So, the safest way is always to include bitmap images.

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] fix output intent subtype

[luigi scarso]

On Tue, Oct 24, 2017 at 9:15 AM, Hans Hagen  wrote:
>
> Well, for me it means that all that validation esp of keys like this are
> rather useless (creating work) because docs validated in the past and
> archived now are suddenly no longer valid.
Hm I have made a pdf with
format={pdf/a-3a},
where I see
  /S /GTS_PDFA3
verapdf 1.8.4 says that it's valid.
I need to investigate, perhaps my  version of verapdf is older.
-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] fix output intent subtype

[luigi scarso]

On Mon, Oct 23, 2017 at 11:14 PM, Peter Rolf <peter.r...@arcor.de> wrote:
> Am 23.10.2017 um 19:14 schrieb Hans Hagen:
>> On 10/23/2017 7:01 PM, luigi scarso wrote:
>>> On Mon, Oct 23, 2017 at 6:25 PM, Pablo Rodriguez <oi...@gmx.es> wrote:
>>>> Hans,
>>>>
>>>> according to Boris Doubrov (one of the developers of the veraPDF parser
>>>> for PDF/A validation) the subtype of the /OutputIntent dictionary for
>>>> all PDF/A intents should be GTS_PDFA1 (no GTS_PDFA2 or GTS_PDFA3).
>>>>
>>>> Here is his reply for reference:
>>>> https://github.com/veraPDF/veraPDF-parser/issues/317#issuecomment-338613962.
>>>>
>>>>
>>>> The attached patch fixes the issue. I have tried it myself and it solves
>>>> the problems with color space profiles.
>>>>
>>>> Could you apply it to ConTeXt?
>>>>
>>>> Many thanks for your help,
>>> sure, but it's better if we have an example that fails
>>> --- I mean, the source code,  the version of the parser , the command
>>> line used.
>>> It could be that other parts are also not ok.
>> i also want to check with Peter
>>
>
> No objections, the 'gts_flag' is also fix for the PDF/X variants.
>
> I think I have tested all variants at that time (around Oct 2015) and
> 'veraPDF' didn't throw an error. Looks like they have improved their
> parser on that part.

yes, the parser looks better, and a nice thing is that an error shows the
reference to the part of the standard that is interested to the failure.

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] fix output intent subtype

[luigi scarso]

On Mon, Oct 23, 2017 at 6:25 PM, Pablo Rodriguez  wrote:
> Hans,
>
> according to Boris Doubrov (one of the developers of the veraPDF parser
> for PDF/A validation) the subtype of the /OutputIntent dictionary for
> all PDF/A intents should be GTS_PDFA1 (no GTS_PDFA2 or GTS_PDFA3).
>
> Here is his reply for reference:
> https://github.com/veraPDF/veraPDF-parser/issues/317#issuecomment-338613962.
>
> The attached patch fixes the issue. I have tried it myself and it solves
> the problems with color space profiles.
>
> Could you apply it to ConTeXt?
>
> Many thanks for your help,
sure, but it's better if we have an example that fails
--- I mean, the source code,  the version of the parser , the command line used.
It could be that other parts are also not ok.
-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

[dev-context] LuaTeX 1.0.3 announcement

[luigi scarso]

==
LuaTeX Release 1.0.3  was released 2017021514
==

This is a minor upgrade and probably this version will go on texlive.
There are a couple
of fixes and additions.
- We added a few a few more helpers in the pdf namespace (like
set|get]gentounicode,
  [set|get]omitcidset and set|get]decimaldigits. Some helpers were
moved from the tex
  to the pdf namespace.

- We added a build_page_insert callback for inserts so that one can
for instance adapt
  spacing on demand.

- On the agenda has been some more control over word start and end in
hyphenation and
  this is now possible via hyphenationbounds. We also updated the
manual with some more
  details.

- An old tracker item with respect to control over spacing around math
was revived and
  has resulted in mathsurroundmode (one can wonder how useful this is).

- We improved the resolution detection in included jpeg images.


- An ffi library has been added to luatex so that it is more in sync
with luajittex. This
  permits easy and flexible loading of libraries. Our policy is to
make luatex as lean
  as possible with no dependencies and this is a step towards that.
Eventually we hope
  to support all relevant platforms.

- The glue and skip register accessors have been improved as a step in
freeing the user
  from glue spec management.

- We added a few more getters and setters for nodes in order to get a
more consistent
  set.

- Irrelevant fields have been removed from the status table and an
engine identifier
  has been added.

- Of course there are numerous fixes and improvements but none of
these have consequences
  for the interfaces.

- The manual has been updated but will be improved over time.




Have fun,
Hans, Luigi, Taco
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] bad i-common-value.xml

[luigi scarso]

On Mon, Oct 10, 2016 at 1:54 PM, luigi scarso <luigi.sca...@gmail.com> wrote:
> tex/texmf-context/tex/context/interface/mkiv$ xmllint *.xml >/dev/null
> i-common-value.xml:14: parser error : Opening and ending tag mismatch:
> parameter line 10 and define
> 
> ^
> i-common-value.xml:577: parser error : Opening and ending tag
> mismatch: define line 9 and interface
> 
>^
> i-common-value.xml:578: parser error : Premature end of data in tag
> interface line 5
>
> --
> luigi

$ diff -u i-common-value.xml.wrong i-common-value.xml
--- i-common-value.xml.wrong 2016-10-10 14:01:57.270898721 +0200
+++ i-common-value.xml 2016-10-10 14:01:06.106900873 +0200
@@ -7,7 +7,7 @@
 

 
-
+
 
 
 


-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

[dev-context] bad i-common-value.xml

[luigi scarso]

tex/texmf-context/tex/context/interface/mkiv$ xmllint *.xml >/dev/null
i-common-value.xml:14: parser error : Opening and ending tag mismatch:
parameter line 10 and define

^
i-common-value.xml:577: parser error : Opening and ending tag
mismatch: define line 9 and interface

   ^
i-common-value.xml:578: parser error : Premature end of data in tag
interface line 5

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

[dev-context] Luatex 1.0.0 announcement

[luigi scarso]

Version 1.0.0

After some ten years of development and testing, today we have released
LuaTeX 1.0.0! Instead of staying below one and ending up with versions
like 0.99.1234, we decided that the moment is there to show the TeX
audience that LuaTeX is stable enough to loose its beta status. Although
functionality has evolved and sometimes been replaced, we have been using
LuaTeX in production right from the start. Of course there are bugs
and for sure we will fix them.

Our main objective is to provide a variant of TeX that permits user
extensions without the need to adapt the inner workings. We did add a few
things here and there but they mostly relate to opening up the inner parts
and/or the wish to influence some hard coded behaviour. Via Lua we managed
to support modern functionality without bloating the code or adding more
and more dependencies on foreign code. In the process a stable and flexible
MetaPost library became part of the engine.

The functionality as present now will stay. We might open up some more
parts, we will stepwise clean up the code base while staying as close as
possible to the Knuthian original, we will try to document bits and pieces.
We might also experiment a bit with better isolation of the backend, and
simplify some internals. For that we might use the experimental version
but if we divert too much we may need to give that another name.

We want to thank all those who have tested the betas and helped to make
LuaTeX better.

Hans Hagen
Hartmut Henkel
Taco Hoekwater
Luigi Scarso
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

[dev-context] Luatex 0.95.0 announcement

[luigi scarso]

==
LuaTeX Release 0.95 for TeX Live 2016 was released 2016042515
==

This is the official frozen TeXlive 2016 version and
a prerelease of the stable 1.0 version.

- deleted 'beta' from the luatex_version_string
- glues now have gluespec merged in (idem math and insert)
- registers are still glue specs
- the spec field in glues are gone
- extra tex.setglue and tex.setmuglue
- obsolete dvi related dir fields removed



Have fun,
Hans, Luigi, Taco
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

[dev-context] Luatex 0.89.0 announcement

[luigi scarso]

==
Luatex Release 0.89.0 was released 2016020500
==

No fundamental changes, just some fixes / improvements (and of course new
bugglets).

- New backend things:
 \pdfvariable pkfixeddpi = integer % > 0 : use only default dpi (so one can
do with one high res instance)
 \pdfvariable ignoreunknownimages = integer % > 0 : ignore missing and
inject something empty (to be used with care)
  and one can do this:
 \edef\foo{\pdfvariable foo}
 \def \oof{foo}
 \ifx\foo\oof don't fool me\fi
 (side effect of no longer aborting on missing, so one implement a catch)




As usual,
the archives can be downloaded from supelec:

https://foundry.supelec.fr/projects/luatex/

You could also check out the sources via anonymous svn:

  svn co --username anonsvn --password anonsvn  \
  https://foundry.supelec.fr/svn/luatex/tags/beta-0.87.0

Bugs and feature requests can be added to the issue tracker at

   http://tracker.luatex.org

When you use context or latex you need an updated format. The latest
version of
context can be fetched from the context garden, latex from ctan. For latex
you can contact David and Joseph as they are dealing with the update.


Have fun,
Hans, Luigi, Taco
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

[dev-context] Luatex 0.88.0 announcement

[luigi scarso]

==
Luatex Release 0.88.0 was released 2016011500
==

This is a next step upto 0.90 and it has the following changes:

- mostly small bug fixes

- a few setters/getters added to the pdf namespace (were in the tex one
before)

- The current libraries under libs are now:
  * poppler-0.40.0
  * mpfr-3.1.3
  * luajit-2.1.0-beta1
  * gmp-6.1.0
  * zziplib-0.13.62
  * zlib-1.2.8
  * lua52-5.2.4
  * pixman-0.32.8
  * libpng-1.6.21
  * cairo-1.14.6


Have fun,
The luatex team
___
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

[dev-context] Luatex 0.87.0 announcement

[luigi scarso]

New luatex release, 0.87.0
>From NEWS:

==
This is a next step upto 0.90 and it has the following changes:

- image data is no longer stored in the format (it was fragile anyway)

- pdf backend data generated when in ini mode is no longer stored in  the
format

- (incomplete) \mag support removed from pdf backend (this functionality is
  kept in dvi mode)

- there are a couple of improvements that should make luatex run a little
bit faster
  (but of course that depends on the job at hand)

- some further pending issues / cleanup has been done (but this is not
reflected in the
  interface)

- there is a new primitive \nospace:

  \nospace=1   do now not inject glue for spaces (not even zero glue)
  \nospace=2   inject zero glue for spaces

- there are new primitives \hpack, \vpack and \tpack that are like \hbox,
\vbox and
  \vtop but they don't trigger callbacks

- we no longer keep track of older math character and delimiter definition
states,
  but this should normally go unnoticed

- from now on only ^^XX, ^^C,  and ^^XX are supported so no
funny odd
  values (three and five)

- texio.setescape(0) disables escaping to terminal (a matter of taste)

- the (current) lc codes are now saved with the (current) language when
patterns are
  loaded unless one hs used \hjcode instead of \lccode; overloading of
\hjcodes is
  possible (but of course goes ahead of hyphenation which is delayed till
parbuilding or
  packaging

- active characters can now be set with: \letcharcode123=\foo (experimental)

- there are some experimental new primitives but these will be described
when they are
  stable (currently being tested)

- there is more backend error reporting and all error messages adn warnings
(the non-tex
  ones) have been normalized

- of course there are the usual small fixes and additional setters and
getters in libraries
  (see manual)
==

Last minute note:
 --synctex
doesn't work. It will be fixed in the next release.

As usual,
the archives can be downloaded from supelec:

https://foundry.supelec.fr/projects/luatex/

You could also check out the sources via anonymous svn:

  svn co --username anonsvn --password anonsvn  \
  https://foundry.supelec.fr/svn/luatex/tags/beta-0.87.0

Bugs and feature requests can be added to the issue tracker at

   http://tracker.luatex.org

When you use context or latex you need an updated format. The latest
version of
context can be fetched from the context garden, latex from ctan. For latex
you can contact David and Joseph as they are dealing with the update.






Have fun,
Hans, Luigi, Taco (in alphabetical order this time)
___
dev-context mailing list
dev-context@ntg.nl
http://mailman.ntg.nl/mailman/listinfo/dev-context

[dev-context] Luatex 0.85.0 announcement

[luigi scarso]

New luatex release, 0.85.0

It's really a big change respect to 0.81.0
(see NEWS for a full report)
and, well,   there can be bugs (that of course we will solve).


The archives can be downloaded from supelec as usual:

https://foundry.supelec.fr/projects/luatex/

You could also check out the sources via anonymous svn:

  svn co --username anonsvn --password anonsvn  \
  https://foundry.supelec.fr/svn/luatex/tags/beta-0.85.0

Bugs and feature requests can be added to the issue tracker at

   http://tracker.luatex.org

When you use context or latex you need an updated format. The latest
version of
context can be fetched from the context garden, latex from ctan. For latex
you can contact David and Joseph as they are dealing with the update.

Have fun,
Hans, Taco, Luigi (in this order :-) )
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

[dev-context] Luatex 0.81.0 announcement

[luigi scarso]

New luatex release, 0.81.0

Hans already explained the changes on primitives;
I only add
* new epdf.openMemStream(s,l,docid)
to create a pdf from a lightuserdata or  string.
(experimental, do not use in production.)

* uniform random generator in mplib is now specific for each numbersystem;

* too_precise implemented for binary number system;

* several bug fixes.



The archives can be downloaded from supelec as usual:

https://foundry.supelec.fr/projects/luatex/

You could also check out the sources via anonymous svn:

  svn co --username anonsvn --password anonsvn  \
  https://foundry.supelec.fr/svn/luatex/tags/beta-0.81.0


Bugs and feature requests can be added to the issue tracker at

   http://tracker.luatex.org



Have fun,
Hans, Taco, Luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] pdf bookmarks remarks

[luigi scarso]

On Wed, Sep 30, 2015 at 9:44 AM, Taco Hoekwater  wrote:

>
> > On 29 Sep 2015, at 10:22, Hans Hagen  wrote:
> >
> > On 9/24/2015 1:19 PM, Taco Hoekwater wrote:
> >> Hi,
> >>
> >> I was writing up my pdf bookmarks article. Two remarks:
> >>
> >>
> >> 1. (for Hans)
> >>
> >>   “With a long heading in a huge font, you might want to add linebreaks
> by hand. No problem, just use \\. The bookmark code ignores \\, so the
> bookmark itself won't have a linebreak.”
> >>
> >> That is not actually true at the moment. Somehow the \\ got converted
> into a single \, instead of an empty space.
> >>
> >> Adding
> >>
> >>  \appendtoks
> >>  \let\\\space
> >>  \to \simplifiedcommands
> >>
> >> fixed it, but it would be nice if that was corrected inside ConTeXt…
> >
> > i've added in typo-wrp.mkiv:
> >
> > \appendtoks
> >\let\spac_crlf\space
> > \to \everysimplifycommands
>
> Dat zit nog niet in de laatste beta he? (als wel, dan werkt het niet)
>
> Groetjes,
> Taco
>
>
>
maybe on the ftp site ?


-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

[dev-context] Luatex 0.80.0 announcement

[luigi scarso]

New luatex release, 0.80.0
This is the release of TeXLive 2015, which is now available for downloading
(see http://tug.org/texlive/ for more info).


Changes:

* New library newtokenlib. It will replace the current token lib.
* Fixed a bug on the normal random generator for double/decimal/binary
  number systems.
* Several others bugs fixed.


The archives can be downloaded from supelec as usual:

https://foundry.supelec.fr/projects/luatex/

You could also check out the sources via anonymous svn:

  svn co --username anonsvn --password anonsvn  \
  https://foundry.supelec.fr/svn/luatex/tags/beta-0.80.0
https://foundry.supelec.fr/svn/luatex/tags/beta-0.79.1

Bugs and feature requests can be added to the issue tracker at

   http://tracker.luatex.org

Have fun,
Hans, Taco, Luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

[dev-context] Luatex 0.79.2 announcement

[luigi scarso]

New luatex release, 0.79.2 .

Changes:

* WARNING: the structure of the format file is changed.
  After  the  Web2C \TeX's magic constant: W2TX  there is now
  a FORMAT_ID, a 32bit field that cannot be between 0 and 256 (included)
  so that there are no conflicts with the preexisting  structure
  of the format.
  The value can be seen with --debug-format and currently is
  907 (the sum of the values of the bytes of the ASCII string don knuth).

* There is a new set of lua functions for StructElement and Attribute,
  convenient (even if not indispensable) for tagged pdf.


* several bugfixes and improvements.


The archives can be downloaded from supelec as usual:

https://foundry.supelec.fr/projects/luatex/

You could also check out the sources via anonymous svn:

  svn co --username anonsvn --password anonsvn  \
  https://foundry.supelec.fr/svn/luatex/tags/beta-0.79.2
https://foundry.supelec.fr/svn/luatex/tags/beta-0.79.1

Bugs and feature requests can be added to the issue tracker at

   http://tracker.luatex.org

Have fun,
Hans, Taco, Luigi

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

[dev-context] lpdf-tag.lua

[luigi scarso]

--- lpdf-tag.lua.orig 2014-07-21 00:50:10.548623199 +0200
+++ lpdf-tag.lua 2014-07-21 00:48:50.564626563 +0200
@@ -64,7 +64,7 @@
 local setfield= nuts.setfield

 local traverse_nodes  = nuts.traverse
-local tosequence  = nuts.tosequence
+local tosequence  = nodes.tosequence
 local copy_node   = nuts.copy
 local slide_nodelist  = nuts.slide
 local insert_before   = nuts.insert_before

I don't see signs of nuts.tosequence elsewhere

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

[dev-context] Luajittex 0.76.0 announcement

[luigi scarso]

New beta release of luajittex.
Site:
https://foundry.supelec.fr/projects/luajittex/

svn repo.:
svn checkout --username anonsvn
https://foundry.supelec.fr/svn/luajittex/tags/beta-0.76.0


--
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] [Dev-luatex] Luatex 0.74.0 announcement -issues

[luigi scarso]

On Tue, Dec 25, 2012 at 9:43 AM, Taco hoekwater t...@docwolves.nl wrote:
 Hi all,

 So far, it looks like we have three issue groups:

 1) the compile errors for metapost with the missing png.h
 2) various luatex compile problems for luasocket
 3) broken context / texdoc (lualatex?)with texlive

 Issue 1) appears to be a timestamp problem. It is probably possible to work 
 around it by manually running 'make' in build/libs/zlib and 
 build/libs/libpng, then 'make mpost' in build/texk/web2c. Somehow, the build 
 rules are not quite right yet, and I probably need help from PEB to fix it 
 properly.

 Issue 2) probably comes down to the bleeding edge luasocket not being as 
 portable as the released version, and should be relatively easy to fix.

 Issue 3) means that some package updates should go to tlcontrib asap.

 But for today, I just wish you all a blessed christmas / yule. Programming is 
 for tomorrow.
ok.
Merry christmas to all of you !!
--
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

[dev-context] overrightarrow and underrightarrow give the same result

[luigi scarso]

$\overrightarrow{ab}$
$\underrightarrow{ab}$

both give the same result  ($\underrightarrow{ab}$)


-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] bTABLE in header and document give unexpected behavior

[luigi scarso]

On Mon, Jun 11, 2012 at 11:46 AM, Sietse Brouwer sbbrou...@gmail.com wrote:
 Sido wrote:
 I had posted a question on stack-exchange and it was suggested to
 post a bug report here. I’m not sure if this is a bug, but it was
 unexpected behavior to me.

 Wolfgang wrote:
 BTW: Please use next time the normal mailing list for such problems and not 
 the developer list.

 That was my mistake: I thought it was a bug, and so I advised him to
 post to dev-context instead of ntg-context. Just to check: is
 dev-context@ntg.nl also for bug reports, or is it exclusively for
 development discussions and should (probable) bugs also go on
 ntg-cont...@ntg.nl?
Lets' say that dev-context@ntg.nl is for developers (features request
and bugs) .
Features request and bugs from users should be addressed to ntg-cont...@ntg.nl .

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] wrong css attr.

[luigi scarso]

On Mon, Mar 5, 2012 at 10:49 AM, Hans Hagen pra...@wxs.nl wrote:

 On 3-3-2012 14:26, Mojca Miklavec wrote:

 On Sat, Mar 3, 2012 at 00:13, Hans Hagen wrote:

 On 2-3-2012 22:34, Mojca Miklavec wrote:

  (However there is lower-serbo-croatian and upper-serbo-croation,
 lower-macedonian and upper-macedonian. I should ask for
 lower-slovenian and upper-slovenian ;)


 I have no problem adding them but you have to key them in.


 I was talking about asking CSS people to add it to specification ;)
 ConTeXt already has slovenian itemize.


 I know, but not yet in the export css file, but I guess Luigi will define
 one for you now.


lost with jquery 
It's impossible to do a paginator with CSS2.1 and  CSS3 is still a draft.
Some kind of javascript is necessary then.
Of course you can also use a heavy xslt - standard xhtml , but still you
need javascript to paginate.

I've added html5 to my personal notes nice idea to explore  for next
eurotex meeting .


 --

luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

[dev-context] [OT] Github compromised

[luigi scarso]

https://lwn.net/Articles/485162/
-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

[dev-context] wrong css attr.

[luigi scarso]

Errata
itemgroup[symbol=5] { list-style-type : circ ; }
itemgroup[symbol=A] { list-style-type : alpha ; }
itemgroup[symbol=G] { list-style-type : upper-greek ; }

Corrige
itemgroup[symbol=5] { list-style-type : circle ; }
itemgroup[symbol=A] { list-style-type : upper-alpha ; }
itemgroup[symbol=G] { list-style-type : upper-roman ; }

Note
upper-greek  doesn't exist

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] wrong css attr.

[luigi scarso]

On Sat, Mar 3, 2012 at 12:13 AM, Hans Hagen pra...@wxs.nl wrote:

 On 2-3-2012 22:34, Mojca Miklavec wrote:

 On Fri, Mar 2, 2012 at 17:28, luigi scarso wrote:
On Fri, Mar 2, 2012 at 5:20 PM, Hans Hagen wrote:
  
On 2-3-2012 11:39, luigi scarso wrote:
  
Errata
itemgroup[symbol=5] { list-style-type : circ ; }
itemgroup[symbol=A] { list-style-type : alpha ; }
itemgroup[symbol=G] { list-style-type : upper-greek ; }
  
Corrige
itemgroup[symbol=5] { list-style-type : circle ; }
itemgroup[symbol=A] { list-style-type : upper-alpha ; }
itemgroup[symbol=G] { list-style-type : upper-roman ; }
  
Note
upper-greek  doesn't exist
  
  
hm, I is upper-roman ... is there no way to get greek?
  
Hans
  
Not with list-style-type --- maybe list-style-image as svg ?
  

 http://www.w3.org/TR/CSS2/**generate.html#propdef-list-**style-typehttp://www.w3.org/TR/CSS2/generate.html#propdef-list-style-type

  From http://www.w3.org/TR/css3-**lists/http://www.w3.org/TR/css3-lists/
 :

 Issue: According to a native Greek speaker, the lower-greek and
 upper-greek styles aren't actually used. I've removed upper-greek for
 now, but kept lower-greek because CSS2.1 included the keyword. Do
 these have actual use-cases?

 @counter-style lower-greek {
 type: alphabetic;
 glyphs: '\3B1' '\3B2' '\3B3' '\3B4' '\3B5' '\3B6' '\3B7' '\3B8'
  '\3B9' '\3BA' '\3BB' '\3BC' '\3BD' '\3BE' '\3BF' '\3C0' '\3C1' '\3C3'
  '\3C4' '\3C5' '\3C6' '\3C7' '\3C8' '\3C9';
 /* 'α' 'β' 'γ' 'δ' 'ε' 'ζ' 'η' 'θ' 'ι' 'κ' 'λ' 'μ' 'ν' 'ξ' 'ο'
 'π' 'ρ' 'σ' 'τ' 'υ' 'φ' 'χ' 'ψ' 'ω' */
 /* This style is only defined because CSS2.1 has it.  It
 doesn't appear to actually be used in Greek texts. */
 }

 (However there is lower-serbo-croatian and upper-serbo-croation,
 lower-macedonian and upper-macedonian. I should ask for
 lower-slovenian and upper-slovenian ;)


 I have no problem adding them but you have to key them in.


  You need to ask Thomas about his opinion, but I see no reason for not
 using lowercase greek for mathematical purposes.


 indeed. also, it's in context because someone asked for it (mkii times)

 In css3 we can define our style: so for example
@counter-style upper-greek {
type: non-repeating;
glyphs:
'Α','Γ','Δ','Ε','Ζ','Η','Θ','Ι','Κ','Λ','Μ','Ν','Ξ','Ο','Π','Ρ','Σ','Τ','Υ','Φ','Χ','Ψ','Ω'
;
suffix: '.';
}
(not sure if the sequence is  correct.)


-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

[dev-context] problems with xtable and export xhtml

[luigi scarso]

It seems that xtable doesn't export @rows and @columns
This patch to tabl-xtb.mkvi works, not sure if it is a good style.

\unexpanded\def\tabl_x_start_cell_construct_yes[#settings]%
  {\dostarttagged\t!tablecell\empty % can't we just tag the box
   \setbox\b_tabl_x\hbox\bgroup
   \setupcurrentxtable[#settings]
   \letxtableparameter\c!width \d_tabl_x_width  % overloads given width
   \letxtableparameter\c!height\d_tabl_x_height % overloads given height
   \ctxcommand{x_table_init_construct()}%
   \inheritedxtableframed\bgroup
   \tabl_x_begin_of_cell
   \def\tablecellcolumns{%
  \ifnum\csname \m_mult_interfaces_namespace nx\endcsname\csname
\m_mult_interfaces_namespace nc\endcsname%
\csname \m_mult_interfaces_namespace nx\endcsname%
  \else
\csname \m_mult_interfaces_namespace nc\endcsname%
  \fi}%
   \def\tablecellrows{%
 \ifnum\csname \m_mult_interfaces_namespace ny\endcsname\csname
\m_mult_interfaces_namespace nr\endcsname%
   \csname \m_mult_interfaces_namespace ny\endcsname%
 \else
   \csname \m_mult_interfaces_namespace nr\endcsname%
 \fi}
   \dotagxtablecell}


-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] problems with xtable and export xhtml

[luigi scarso]

On Fri, Feb 24, 2012 at 1:06 PM, luigi scarso luigi.sca...@gmail.com wrote:
 It seems that xtable doesn't export @rows and @columns
 This patch to tabl-xtb.mkvi works, not sure if it is a good style.

 \unexpanded\def\tabl_x_start_cell_construct_yes[#settings]%
  {\dostarttagged\t!tablecell\empty % can't we just tag the box
   \setbox\b_tabl_x\hbox\bgroup
   \setupcurrentxtable[#settings]
   \letxtableparameter\c!width \d_tabl_x_width  % overloads given width
   \letxtableparameter\c!height\d_tabl_x_height % overloads given height
   \ctxcommand{x_table_init_construct()}%
   \inheritedxtableframed\bgroup
   \tabl_x_begin_of_cell
   \def\tablecellcolumns{%
      \ifnum\csname \m_mult_interfaces_namespace nx\endcsname\csname
 \m_mult_interfaces_namespace nc\endcsname%
        \csname \m_mult_interfaces_namespace nx\endcsname%
      \else
        \csname \m_mult_interfaces_namespace nc\endcsname%
      \fi}%
   \def\tablecellrows{%
     \ifnum\csname \m_mult_interfaces_namespace ny\endcsname\csname
 \m_mult_interfaces_namespace nr\endcsname%
       \csname \m_mult_interfaces_namespace ny\endcsname%
     \else
       \csname \m_mult_interfaces_namespace nr\endcsname%
     \fi}
   \dotagxtablecell}
Hm, no it's wrong .

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] problems with xtable and export xhtml

[luigi scarso]

On Fri, Feb 24, 2012 at 4:40 PM, Wolfgang Schuster
schuster.wolfg...@googlemail.com wrote:

 Am 24.02.2012 um 13:06 schrieb luigi scarso:

 It seems that xtable doesn't export @rows and @columns
 This patch to tabl-xtb.mkvi works, not sure if it is a good style.

 \unexpanded\def\tabl_x_start_cell_construct_yes[#settings]%
  {\dostarttagged\t!tablecell\empty % can't we just tag the box
   \setbox\b_tabl_x\hbox\bgroup
   \setupcurrentxtable[#settings]
   \letxtableparameter\c!width \d_tabl_x_width  % overloads given width
   \letxtableparameter\c!height\d_tabl_x_height % overloads given height
   \ctxcommand{x_table_init_construct()}%
   \inheritedxtableframed\bgroup
   \tabl_x_begin_of_cell
   \def\tablecellcolumns{%
      \ifnum\csname \m_mult_interfaces_namespace nx\endcsname\csname
 \m_mult_interfaces_namespace nc\endcsname%
        \csname \m_mult_interfaces_namespace nx\endcsname%
      \else
        \csname \m_mult_interfaces_namespace nc\endcsname%
      \fi}%
   \def\tablecellrows{%
     \ifnum\csname \m_mult_interfaces_namespace ny\endcsname\csname
 \m_mult_interfaces_namespace nr\endcsname%
       \csname \m_mult_interfaces_namespace ny\endcsname%
     \else
       \csname \m_mult_interfaces_namespace nr\endcsname%
     \fi}
   \dotagxtablecell}


 You need this

 \appendtoks
   %\def\dotagxtablecell  
 {\taggedctxcommand{settagtablecell(\number\tablecellrows,\number\tablecellcolumns,\number\raggedstatus)}}%
    \def\dotagxtablecell  
 {\taggedctxcommand{settagtablecell(\number\c_tabl_x_nx,\number\c_tabl_x_ny,\number\raggedstatus)}}%
    \def\dotagxtablesignal{\char\zerocount}% not used
 \to \everyenableelements

 and this change

 %\unexpanded\def\tabl_x_start_cell_construct_yes[#settings]%
 %  {\dostarttagged\t!tablecell\empty % can't we just tag the box
 %   \setbox\b_tabl_x\hbox\bgroup
 %   \setupcurrentxtable[#settings]%
 %   \letxtableparameter\c!width \d_tabl_x_width  % overloads given width
 %   \letxtableparameter\c!height\d_tabl_x_height % overloads given height
 %   \ctxcommand{x_table_init_construct()}%
 %   \inheritedxtableframed\bgroup
 %   \tabl_x_begin_of_cell
 %   \dotagxtablecell}

 \unexpanded\def\tabl_x_start_cell_construct_yes[#settings]%
  {\dostarttagged\t!tablecell\empty % can't we just tag the box
   \setbox\b_tabl_x\hbox\bgroup
   %
   \letxtableparameter\c!nx\plusone
   \letxtableparameter\c!ny\plusone
   \letxtableparameter\c!nc\plusone
   \letxtableparameter\c!nr\plusone
   %
   \setupcurrentxtable[#settings]%
   %
   \c_tabl_x_nx\directxtableparameter\c!nc\relax
   \c_tabl_x_ny\directxtableparameter\c!nr\relax
   \ifnum\c_tabl_x_nx=\plusone
     \c_tabl_x_nx\directxtableparameter\c!nx\relax
   \fi
   \ifnum\c_tabl_x_ny=\plusone
     \c_tabl_x_ny\directxtableparameter\c!ny\relax
   \fi
   %
   \letxtableparameter\c!width \d_tabl_x_width  % overloads given width
   \letxtableparameter\c!height\d_tabl_x_height % overloads given height
   \ctxcommand{x_table_init_construct()}%
   \inheritedxtableframed\bgroup
   \tabl_x_begin_of_cell
   \dotagxtablecell}

 Wolfgang
yes, I suppose something similar -- I'm checking


-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

[dev-context] strc-tag.mkiv

[luigi scarso]

Maybe

\unexpanded\def\strc_tags_element_start_yes_indeed
  {\iftrialtypesetting
 \expandafter\strc_tags_element_start_yes_indeed_yes
   \else
 \expandafter\strc_tags_element_start_nop_indeed
   \fi}

\unexpanded\def\strc_tags_element_stop
  {\iftrialtypesetting
 \expandafter\strc_tags_element_stop_yes
   \else
 \expandafter\strc_tags_element_stop_nop
   \fi}


should be

\unexpanded\def\strc_tags_element_start_yes_indeed
  {\iftrialtypesetting
\expandafter\strc_tags_element_start_nop_indeed
   \else
 \expandafter\strc_tags_element_start_yes_indeed_yes
   \fi}

\unexpanded\def\strc_tags_element_stop
  {\iftrialtypesetting
 \expandafter\strc_tags_element_stop_nop
   \else
 \expandafter\strc_tags_element_stop_yes
   \fi}


?

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] strc-tag.mkiv

[luigi scarso]

On Fri, Feb 17, 2012 at 3:06 PM, Hans Hagen pra...@wxs.nl wrote:
 On 17-2-2012 14:55, luigi scarso wrote:

 Maybe

 \unexpanded\def\strc_tags_element_start_yes_indeed
   {\iftrialtypesetting
      \expandafter\strc_tags_element_start_yes_indeed_yes
    \else
      \expandafter\strc_tags_element_start_nop_indeed
    \fi}

 \unexpanded\def\strc_tags_element_stop
   {\iftrialtypesetting
      \expandafter\strc_tags_element_stop_yes
    \else
      \expandafter\strc_tags_element_stop_nop
    \fi}


 maybe_indeed -)
or
maybe_yes
?

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

[dev-context] back-exp.mkiv

[luigi scarso]

\appendtoks
   
%\def\dotagcombination{\taggedctxcommand{settagcombination(\combinationparameter\c!nx,\combinationparameter\c!ny)}}%

\unexpanded\def\dotagcombination{\taggedctxcommand{settagcombination(\number\horcombination,\number\totcombination)}}%
\to \everyenableelements

should be

\appendtoks
   
\def\dotagcombination{\taggedctxcommand{settagcombination(\combinationparameter\c!nx,\combinationparameter\c!ny)}}%
   % 
\unexpanded\def\dotagcombination{\taggedctxcommand{settagcombination(\number\horcombination,\number\totcombination)}}%
\to \everyenableelements


-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] \page_one_place_float_text undefined in ftp

[luigi scarso]

On Tue, Feb 7, 2012 at 9:17 AM, Hans Hagen pra...@wxs.nl wrote:
 On 6-2-2012 12:04, luigi scarso wrote:

 On Fri, Feb 3, 2012 at 6:45 PM, Hans Hagenpra...@wxs.nl  wrote:

 On 3-2-2012 17:34, luigi scarso wrote:


 \page_one_place_float_text is undefined in latest ftp

 strc-flt:

 \def\page_one_place_float_text[#1]%
      was strc



 ! Use of \page_one_place_float_text doesn't match its definition.


 example needed
yes I know, infact I'm still trying to make a small example with xtables.
It's in the middle part of a long document, I've tried to isolate only
the culprit but the error vanish.

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] new beta

[luigi scarso]

On Mon, Feb 6, 2012 at 11:05 AM, Hans Hagen pra...@wxs.nl wrote:
 On 6-2-2012 09:57, luigi scarso wrote:

 On Fri, Feb 3, 2012 at 10:20 PM, Hans Hagenpra...@wxs.nl  wrote:

 Hi,

 I've uploaded a beta to the ftp server. There is some work in progress:

 - otr (page-* files)
 - descriptions, enumerations, notes (and their parent: constructions)

 I'm not yet satisfied but it shows where we're heading.

 Hans


 ! LuaTeX error ...tex/texmf-context/tex/context/base/strc-mar.lua:663:
 attempt to call field 'savedtitle' (a nil value)
 stack traceback:
        ...tex/texmf-context/tex/context/base/strc-mar.lua:663: in function
 'title'
        main ctx instance:1: in main chunk.

 system  tex  error on line 1 in file xtabl-b.tex: LuaTeX error  ...


 \sectionheadmarkingtitle ...arks.title(#1,#2)}

 l.1 \markingcommand{chapter}{li::2}

 \ctxcommand ...\directlua \zerocount {commands.#1}

 argument  ...rking(chapter,\v!page ,first)}
                                                   \fi \endgroup
 \firstofoneargument #1-#1

 to be read again
                    }


        commands.savedlisttitle(tag,listindex,marking)
        commands.savedlisnumber(tag,listindex,marking)



 -
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
    tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
 -
in strc-not.lua should be

function commands.notetitle(tag,n)
commands.savedlisttitle(tag,notedata[tag][n])
end
?


-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] \page_one_place_float_text undefined in ftp

[luigi scarso]

On Fri, Feb 3, 2012 at 6:45 PM, Hans Hagen pra...@wxs.nl wrote:
 On 3-2-2012 17:34, luigi scarso wrote:

 \page_one_place_float_text is undefined in latest ftp

 strc-flt:

 \def\page_one_place_float_text[#1]%
      was strc


! Use of \page_one_place_float_text doesn't match its definition.

system   tex  error on line 2 in file xtabl-b.tex: Use of  ...


\strc_floats_get_box ...loatmethod \endcsname \fi

\strc_floats_place_packaged_boxes ...oats_get_box
  \global \insidefloatfalse
\strc_floats_finish_placement ...e_packaged_boxes
  \dostoptagged \global \sid...
l.2 ...bottom][width=20pt,height=20pt,factor=fit]}
   \tfx \setupinterlinespace...
inserted text ...ntext(t) end end context('}') }

\luat_start_lua_code_indeed ...ua \zerocount {#1}}


-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

[dev-context] error in setuplist[alternative=command]

[luigi scarso]

\def\ChapterCommand#1#2#3{#1 #2 #3}%
\setuplist[chapter]
[alternative=command,
   command=\ChapterCommand]
\starttext
\placecontent
\startpart[title=aaa]
\startchapter[title=bbb]
\startsection[title=ccc]
\input knuth
\stopsection
\stopchapter
\stoppart
\stoptext

! Argument of \ChapterCommand has an extra }.

Perhaps

*** strc-lst.mkvi.new2012-01-26 16:47:46.0 +0100
--- strc-lst.mkvi2012-01-23 19:44:00.0 +0100
***
*** 755,757 
  \startsetups[\??listrenderings:\v!command]
! \def\p_command{\listalternativeparameter\c!command}%
  \ifx\p_command\empty
--- 755,757 
  \startsetups[\??listrenderings:\v!command]
! \edef\p_command{\listalternativeparameter\c!command}%
  \ifx\p_command\empty

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] showframe is unknown

[luigi scarso]

On Tue, Jan 24, 2012 at 6:33 PM, Wolfgang Schuster 
schuster.wolfg...@googlemail.com wrote:


 Am 24.01.2012 um 18:06 schrieb luigi scarso:

  \showframe put
   [unknown command \showframe]
  but it  doesn'h stop halt the run.

 file-mod.mkvi (change \setgvalue to \letgvalue):

 \def\dofetchruntimecommand#1#2% actually a test on #1 being define would
 be ok as well
  {\ifcsname\??runtimeloaded#2\endcsname
 % already loaded
   \else
 \global\let#1\undefined
 \startreadingfile
 \startnointerference % \bgroup
 \cleanupfeatures % better \setnormalcatcodes / test first
 \readfile{#2.\mksuffix}\donothing\donothing
 \stopnointerference  % \egroup
 \stopreadingfile
 -\setgvalue{\??runtimeloaded#2}\empty
 +\letgvalue{\??runtimeloaded#2}\empty
   \fi
   \ifx#1\undefined
 \writestatus\m!system{command \string#1 not found in file #2}%
 \unexpanded\gdef#1{{\infofont[unknown command \string#1]}}%
   \fi
   #1}

 Wolfgang

ok4me


-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

[dev-context] showframe is unknown

[luigi scarso]

\showframe put
 [unknown command \showframe]
but it  doesn'h stop halt the run.
-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] beta on ftp

[luigi scarso]

On Thu, Jan 19, 2012 at 8:05 PM, Hans Hagen pra...@wxs.nl wrote:

 Hi,

 For those with access to the ftp server .. there is a new beta with quite
 some low level changes in the font subsystem (leaner, faster, design sizes
 dealt with differently). Also type-otf.mkiv has been split up (mostly more
 will follow) which gives a faster startup.



! Missing number, treated as zero.

   ,
argument ...t_face , \number \relativefontid ,
Sorry, no help file --- I've just seen it.

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

[dev-context] \c!suffixstopper undefined

[luigi scarso]

In strc-flt.mkvi \c!suffixstopper is undefined

\unexpanded\def\thecurrentfloatnumbersuffix
  {\doifsomething{\floatcaptionparameter\c!suffix}
 {\floatcaptionparameter\c!suffixseparator
  \floatcaptionparameter\c!suffix
  \floatcaptionparameter\c!suffixstopper}}

Perhaps it need to be added  to \setupcaptions ?

\setupcaptions
  [\c!location=\v!bottom,
   \c!grid=,
   \c!before=, % not used (yet)
   \c!inbetween={\blank[\v!medium]},
   \c!after=, % not used (yet)
   \c!spacebefore=,
   \c!spaceinbetween=, % replaces fuzzy inbetween dual usage
   \c!spaceafter=,
   \c!width=\v!fit,
   \c!minwidth=\v!fit, % id est: the width of the floatbox in some cases
   \c!headstyle=\v!bold,
   \c!headcolor=,
   \c!leftmargin=\zeropoint,
   \c!rightmargin=\zeropoint,
   \c!outermargin=\zeropoint,
   \c!innermargin=\zeropoint,
   \c!setups=,
   \c!style=\v!normal,
   \c!color=,
   \c!textstyle=,
   \c!textcolor=,
   \c!align=,
   \c!number=\v!yes,
 % \c!expansion=\v!no
 % \c!prefix=\v!no,
 % \c!prefixconnector=.,
 % \c!way=\v!by\v!chapter,
 % \c!prefixsegments=2:2,
 % \c!way=\@@nrway,
 % \c!blockway=\@@nrblockway,
 % \c!sectionnumber=\@@nrsectionnumber,
 % \c!separator=\@@koseparator,
 % \c!starter=\@@kostarter,
 % \c!stopper=\@@kostopper,
   \c!suffixseparator=, % currently rather hard coded
   \c!suffixstopper=, %% added
   \c!suffix=\floatcaptionsuffix,
   \c!distance=1em,
   \c!conversion=\v!numbers,
   \c!command=]

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] ConTeXt Book: Request for help!

[luigi scarso]

2011/8/14 Idris Samawi Hamid ادريس   سماوي حامد isha...@colostate.edu:
 Dear gang,

 As some of you may know, I'm working on a professional introductory book for
 learning ConTeXt. Part of the philosophy of this book is to be as
 self-contained as possible, so we'll be using a preferred editor.

 Not one editor/ide out there is ideal for ConTeXt (including bidi editing
 and other user-friendly configurability). The best balance I could find is
 Notepad++ (Npp), and that's what I'm going with. I have done a lot of work
 to contextify it, and I have added some new features, such as a context-menu
 where one can right-click and get a list of ConTeXt typography and
 description options, experimental support for tooltips (giving options for
 commands etc), no more manual braces (so far less run errors) etc.

 To take this to the next level I need help: Is there anyone on the list who
 knows how to write and compile lexers for scintilla-based editors? Also, how
 to compile C++ for M$-Windows based applications such as Npp?

I've used gub
http://lilypond.org/gub/
to cross-compile object modules
from linux to windows

Under Windows there is mingw
http://www.mingw.org
but I don't know about something similar to gub

There is also the  express edition of the microsoft compiler,see
http://www.microsoft.com/express


-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] \rotation is broken

[luigi scarso]

Still broken in latest beta.

On Tue, Jun 14, 2011 at 12:19 PM, luigi scarso luigi.sca...@gmail.com wrote:
 ! Undefined control sequence.
 \starttext \rotate[rotation=90]{FOO}    \stoptext



 system           tex  error on line 1 in file test.tex: Undefined
 control sequence ...

  1   \starttext \rotate[rotation=90]{FOO} \stoptext


 \dodorotatenextbox ...ta \fi \dododorotatenextbox
                                                  \wd \nextbox \if!!donea \s...
 \dorotatenextbox ...otatenextbox \@@rorotation #2}
                                                  \hbox {\boxcursor \flushne...
 \dodowithnextbox ...xtbox \@@rorotation \!!counta
                                                  \egroup
 l.1 \starttext \rotate[rotation=90]{FOO}
                                         \stoptext



 core-mis.mkiv:

 % We can completely do this in lua .. when 'I'm bored ...

 % \def\dododorotatenextbox
 %   {\setbox\nextbox\vbox to \@@layerysiz
 %      {\vfill
 %       \hbox to \@@layerxsiz
 %         {\dostartrotation\@@rorotation
 %            \nextboxwd\zeropoint
 %            \nextboxht\zeropoint
 %            \flushnextbox
 %          \dostoprotation
 %          \hfill}%
 %       \kern\@@layerypos}%
 %   \setbox\nextbox\hbox
 %     {\kern\@@layerxpos
 %      \kern\@@layerxoff
 %      \lower\@@layeryoff\flushnextbox



 --
 luigi




-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

[dev-context] \rotation is broken

[luigi scarso]

! Undefined control sequence.
\starttext \rotate[rotation=90]{FOO}\stoptext



system   tex  error on line 1 in file test.tex: Undefined
control sequence ...

 1   \starttext \rotate[rotation=90]{FOO} \stoptext


\dodorotatenextbox ...ta \fi \dododorotatenextbox
  \wd \nextbox \if!!donea \s...
\dorotatenextbox ...otatenextbox \@@rorotation #2}
  \hbox {\boxcursor \flushne...
\dodowithnextbox ...xtbox \@@rorotation \!!counta
  \egroup
l.1 \starttext \rotate[rotation=90]{FOO}
 \stoptext



core-mis.mkiv:

% We can completely do this in lua .. when 'I'm bored ...

% \def\dododorotatenextbox
%   {\setbox\nextbox\vbox to \@@layerysiz
%  {\vfill
%   \hbox to \@@layerxsiz
% {\dostartrotation\@@rorotation
%\nextboxwd\zeropoint
%\nextboxht\zeropoint
%\flushnextbox
%  \dostoprotation
%  \hfill}%
%   \kern\@@layerypos}%
%   \setbox\nextbox\hbox
% {\kern\@@layerxpos
%  \kern\@@layerxoff
%  \lower\@@layeryoff\flushnextbox



-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] Luatex 0.61.0 announcement

[luigi scarso]

On Wed, Jul 28, 2010 at 3:41 PM, Taco Hoekwater t...@elvenkind.com wrote:
 Hi,

 I have just uploaded the archives for a new luatex release, 0.61.0,
 the first of the betas toward 0.70.0.

 New features:

 * New lua library 'epdf' for introspection of PDF inclusions,
  see the manual for details.
Can I then build a luatex script that mimic  pdftoppm  pdftops ?

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] Luatex 0.61.0 announcement

[luigi scarso]

On Wed, Jul 28, 2010 at 3:57 PM, luigi scarso luigi.sca...@gmail.com wrote:
 On Wed, Jul 28, 2010 at 3:41 PM, Taco Hoekwater t...@elvenkind.com wrote:
 Hi,

 I have just uploaded the archives for a new luatex release, 0.61.0,
 the first of the betas toward 0.70.0.

 New features:

 * New lua library 'epdf' for introspection of PDF inclusions,
  see the manual for details.
 Can I then build a luatex script that mimic  pdftoppm  pdftops ?
Hm, it seems that the answer is no.


-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] context commands in lua-files

[luigi scarso]

On Fri, Jul 16, 2010 at 4:41 PM, Peter Münster pmli...@free.fr wrote:

 Hello,

 Here some new ideas:

 http://pmrb.free.fr/tmp/context-commands/

 All feedback is welcome!

 Cheers, Peter

 --
 Contact information: http://pmrb.free.fr/contact/


 ___
 dev-context mailing list
 dev-context@ntg.nl
 http://www.ntg.nl/mailman/listinfo/dev-context

Why don't put them into a table as is in
http://www.lua.org/pil/10.1.html
For exampl e placefloat.lua should be
placefloat ={
props = {
generated = true,   -- default = false
fixpart = place,
varpart = float,
generator = definefloat,
categories = {Structure, Graphic}
-- first category is main category, in the other categories, there are
-- just references
}
-- ... more data
}

It's very powerful then to manage this file with lua functions.


-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] Checksum of original font files stored in the cache?

[luigi scarso]

On Sat, Jun 19, 2010 at 1:01 PM, Mojca Miklavec
mojca.miklavec.li...@gmail.com wrote:
 On Sat, Jun 19, 2010 at 09:06, Taco Hoekwater wrote:

 Anyone with recent experience with wxWindows?

 No recent experience; I can only tell that somebody has written wx
 terminal in gnuplot (the idea was to make a nice multi-platform
 terminal), but ever since its introduction (must be a few years
 already) nobody was able to compile it on Mac (it should be possible,
 but none of current developers was able to do it properly). I do think
 that some people have managed to compile it on Windows, but I have no
 idea about its state. And I have no idea how to link it statically on
 linux or mac.

 Mojca

I'm impressed by
http://code.google.com/p/luaforwindows/
I 'm also used to visit wxwidgets from time to time
and I believe that 2.8 branch is good
I have compiled gnuplot4.4 because I like its lua interface, but not
with wxterminal -- I can check eventually

BTW,IUP can be another guit toolkit to consider:
it's in Lua, it has some TeX ideas, it comes from
http://www.tecgraf.puc-rio.br/iup

(Aditya also starts to use wxMaxima)
-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] Checksum of original font files stored in the cache?

[luigi scarso]

On Fri, Jun 18, 2010 at 9:40 AM, Taco Hoekwater t...@elvenkind.com wrote:
 Khaled Hosny wrote:

 On Fri, Jun 18, 2010 at 09:10:47AM +0200, Taco Hoekwater wrote:

 Oliver Buerschaper wrote:

 Do you think it would be a good idea to store a checksum of the
 actual font file used while generating the cache?

 This sounds useful. As it will need backend support in luatex,
 I will add a tracker item for this.

Isn't mtxrun --script fonts reload enough ?
-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] Checksum of original font files stored in the cache?

[luigi scarso]

On Fri, Jun 18, 2010 at 11:34 AM, Hans Hagen pra...@wxs.nl wrote:
 nowadays i always just drop 'm in

 texmf*/fonts/data/origin/collection

 so for example in

 texmf-fonts/fonts/data/khaled/xits

 (and i no longer bother about separating type1 file into different paths
 anyway as data is patr of all path vars)
And then run  mtxrun --script font reload, I suppose
--
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] Checksum of original font files stored in the cache?

[luigi scarso]

On Fri, Jun 18, 2010 at 12:17 PM, luigi scarso luigi.sca...@gmail.com wrote:
 On Fri, Jun 18, 2010 at 12:03 PM, Hans Hagen pra...@wxs.nl wrote:
 On 18-6-2010 11:40, luigi scarso wrote:

 mtxrun --script fonts reload

 this is only needed when you access fonts by name and if a name cannot be
 found, the name cache will be regenerated automatically
 And it's ok, because the next runs mkiv will *not* rebuild the cache,
 and in mkiv we use fonts mostly by name.
 If I understand correctly, checksum or something similar  (why not a
 binary cmp then ? just one byte is enough)  must be done at *every*
 runs -- make no  sense ,most the times check will be useless .
Also a changing of a font in a middle of a run can be dangerous: the
next run can be faked.





-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] Checksum of original font files stored in the cache?

[luigi scarso]

On Fri, Jun 18, 2010 at 12:03 PM, Hans Hagen pra...@wxs.nl wrote:
 On 18-6-2010 11:40, luigi scarso wrote:

 mtxrun --script fonts reload

 this is only needed when you access fonts by name and if a name cannot be
 found, the name cache will be regenerated automatically
And it's ok, because the next runs mkiv will *not* rebuild the cache,
and in mkiv we use fonts mostly by name.
If I understand correctly, checksum or something similar  (why not a
binary cmp then ? just one byte is enough)  must be done at *every*
runs -- make no  sense ,most the times check will be useless .








-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] Checksum of original font files stored in the cache?

[luigi scarso]

On Fri, Jun 18, 2010 at 4:37 PM, Mojca Miklavec
mojca.miklavec.li...@gmail.com wrote:
 On Fri, Jun 18, 2010 at 11:34, Hans Hagen wrote:
 On 18-6-2010 11:09, Mojca Miklavec wrote:

 Maybe a lua script to install fonts is better -- we can eventually
 think to a wxLua gui interface .

 Or start expanding fontinst to handle OpenType fonts? Anyone?

 no, and i see no reason why ... afaik fontinst does things with type 1 fonts

 I thought it was ironic enough to understand it as a joke :)

 Mojca

http://www.wxwidgets.org/
wxWidgets is a C++ library that lets developers create applications
for Windows, OS X, Linux and UNIX on 32-bit and 64-bit architectures
as well as several mobile platforms including Windows Mobile, iPhone
SDK and embedded GTK+. It has popular language bindings for Python,
Perl, Ruby  and many other languages. Unlike other cross-platform
toolkits, wxWidgets gives its applications a truly native look and
feel because it uses the platform's native API rather than emulating
the GUI. It's also extensive, free, open-source and mature. Why not
give it a try, like many others have?

http://wxlua.sourceforge.net/
wxLua is a set of bindings to the C++ wxWidgets  cross-platform  GUI
library for the Lua programming language. You can write complex,
graphical, interactive programs with wxLua to develop and deliver your
software with the programming ease of an interpreted language like
Lua. Nearly all of the functionality of wxWidgets is exposed to Lua,
meaning that your programs can have windows, dialogs, menus, toolbars,
controls, image loading and saving, drawing, sockets, streams,
printing, clipboard access... and much more.

For Lua x windows already comes with a set of examples of wxLua...
erlang come with a wx binding by default...
ah yes, wxPython is also good...




-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] audit of commands

[luigi scarso]

 \usemodule[set-11]

 \loadsetups

 \starttext
    \showsetup{framed}
 \stoptext

 works -)
here too with last current
-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] audit of commands

[luigi scarso]

2010/5/6 Idris Samawi Hamid ادريس  سماوي حامد isha...@colostate.edu:


 Dear gangsters,

 I'm interested in an audit of all current mid-to-high-level mkiv commands,
 including experimental or undocumented ones. I'm trying to come up with, as
 much as possible, a set of context commands which is

 mutually exclusive

 jointly exhaustive.

 By 'mutually exlcusive' in this context I mean that I want to identify, for
 redundant commands, the deprecated commands and use only the current. No
 point teaching old methods.

 By 'jointly exhaustive' I mean that i don't want to leave anything out, at
 least not yet. Some of, eg, the bidi and otf control is undocumented, and I
 can dig those up. OTOH there are lots of other areas where there may be some
 commands of interest that only get brought up on the list occasionally...

 by mid-level I mean commands like

 \define

 or other user-friendly non-plain commands that may be used to create mkiv
 macros etc.

 Aside from core developers Hans and Taco: Luigi, Wolfgang and Mojca seem to
 have extensive knowledge of the internals... any ideas how we can do this in
 an efficient manner?

 My idea is to organize this list in interesting ways for pedagogical
 purposes, for the current book project.

 Again, ONLY MKIV is under consideration; as far as this book project is
 concerned, only mkiv exists ;-)

 Any help is greatly appreciated!
I remember a tally variable in pdftex that governs the lenght of
line used in trace commands
Starting from it, and modifying the pdftew.web, I've produced the
lists of all macros and their meaning simple put something like
\tracingmacros3
etc at the beginning of context.tex and then rebuild the format.
I can revisit it now for luatex:
this should still work for TeX macros but  not for Lua functions, I believe.




-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] audit of commands

[luigi scarso]

if you have problems
http://www.logosrl.it/luatex/cont-en.log.bz2

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] audit of commands

[luigi scarso]

On Fri, May 7, 2010 at 4:05 PM, Marius mariau...@gmail.com wrote:
 Idris, maybe this is what you are looking for:
 http://www.pragma-ade.com/general/qrcs/setup-en.pdf

 And at the same time I have a question. Does this list of commands is
 the most recent? Is it generated automaticaly?
If I remember well the sources are here
minimals/tex/texmf-context/tex/context/interface

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

[dev-context] update modules

[luigi scarso]

Update modules.

http://groups.foundry.supelec.fr/modules/

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] last modules frozen acrobat 8

[luigi scarso]

On Sun, May 25, 2008 at 12:51 PM, luigi scarso [EMAIL PROTECTED] wrote:
 It was reported that last modules freeze acrobat 8 .
 I have no problem with xpdf 3.02,
 GNOME evince 2.22.1.1
 and gs 8.62
fixed in #1296 (thanks taco,I was not able to test 1293)

ASAP I will make a new release of modules.



-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

[dev-context] modules at supelec

[luigi scarso]

Hi all
I start modules project at
http://foundry.supelec.fr/projects/modules

Suggestions are welcome , of course.

Thank you all

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context

Re: [dev-context] modules at supelec

[luigi scarso]

 Fabrice is expecting suggestions about some new hierarchy on supelec,
 to be able to find TeX-related projects more easily.
I need to know gforge a bit more than now.

Maybe a (sub)Topic
'typesetting'
in Trove
http://foundry.supelec.fr/softwaremap/trove_list.php

-- 
luigi
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context