Re: [NTG-context] Need some hints to fix my standalon installation

2022-04-20 Thread Christoph Hintermüller via ntg-context
Hi Hans

[Inline Response to message by Hans Hagen via ntg-context, Mi, 2022-04-
20 19:18 +0200: Answers and comments below corresponding cited
paragraphs.]
> We had to adapt the lfg file for lm (other fonts are ok) so i'll make
> an 
> update.
> 
> If you're in a hurry, in lm.lfg:
> 
>  parameters = {
>  FractionNumeratorDisplayStyleShiftUp = 600, -- used to
> be a 
> function
>  NoLimitSupFactor =   0,
>  NoLimitSubFactor = 900,
>   -- AccentBaseHeight =   0,
>  AccentBaseDepth  =  50,
>  },
> 
> can be adapted.
> 



That's fine. As soon as post that update is ready for pulling I will
pull.
Till then i can wait.

Best
Xristoph



___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] Need some hints to fix my standalon installation

2022-04-20 Thread Christoph Hintermüller via ntg-context
Hi Michael


[Inline Response to message by Mikael Sundqvist via ntg-context, Mi,
2022-04-20 17:12 +0200: Answers and comments below corresponding cited
paragraphs.]

> 
> The strange thing with fractions seems to be due to the parameter
> FractionNumeratorDisplayStyleShiftUp in lm.lfg. If you always set it
> to 600, it seems to work also for luatex. (This will be fixed.)
> 
> Another thing: Instead of using \over, I suggest that you use \frac
> (less surprises). Something like:
> 
> \starttext
> \startformula
> a=b + 1
> \stopformula
> 
> \startformula
> a = \frac{ b + \mu }{ c }
> \stopformula
> 
> \startformula
> a = \frac{\frac{ b + \mu }{ c } + e}{ d + i }
> \stopformula
> \stoptext
> 



Thank you very much for the hints. \frac didn't help either even after
moving broken installation aside and doing a fresh install with
 
sh ./first-setup.sh --modules=all --context=latest


Results still similar see attached.



> /Mikael
> _
> __
> If your question is of interest to others as well, please add an
> entry to the Wiki!
> 
> maillist : ntg-context@ntg.nl / 
> http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> _
> __


test_strange.tar.bz
Description: application/bzip-compressed-tar
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] Need some hints to fix my standalon installation

2022-04-20 Thread Christoph Hintermüller via ntg-context
Hi
Have updated my standalone installation from one of the 2020 releases
to the latest one running

./first-setup.sh --context=latest --modules=all

Now i see the strange behavior that fraction in second equation is not
typeset instead typesetting math aborts after typesetting the upper
part of the fraction. A short example showing this is attached (pdf,
tex, and log)

Therefore i have the following questions
 - would it help to sacrifice the updated standalone installation and
   do a fresh install
 - What else i would have to check and probably fix to make the math 
   working as expected
 - any thing else to change






test_strange.tar.bz
Description: application/bzip-compressed-tar
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] Need some hints to fix my standalon installation

2022-04-20 Thread Christoph Hintermüller via ntg-context
Hi
Have updated my standalone installation from one of the 2020 releases
to the latest one running

./first-setup.sh --context=latest --modules=all

Now i see the strange behavior that fraction in second equation is not
typeset instead typesetting math aborts after typesetting the upper
part of the fraction. A short example showing this is attached (pdf,
tex, and log)

Therefore i have the following questions
 - would it help to sacrifice the updated standalone installation and
   do a fresh install
 - What else i would have to check and probably fix to make the math 
   working as expected
 - any thing else to change




-- 
-- 
Christoph Hintermüller
Dipl.-Ing. Dr. MBA. MSc
JKU Institute of Biomedical Mechatronics
Altenberger Straße 69,
4040 Linz, Austria,
Cell: +43 650 8827347
Tel. +43 732 2468 4813
Email: christoph.hintermuel...@jku.at


test_strange.tar.bz
Description: application/bzip-compressed-tar
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] Few quick questions

2022-03-09 Thread Christoph Hintermüller via ntg-context
Ok replaced everything i could find with \start* \stop* pairs which got
me far down the document just the last about 4 pages.

The only thing when comparing with examples for using exporter which
still differs is that i use blank line in my sources. Does this
implicit definition of paragraphs cause any hickups in exporter and
would it be adviseable to enclose each paragraph in \startparagraph and
\stopparagraph? Or should that be no issue for xmlexporter and would
ensuring clean recent install be more efficient in this case.

Best
Xristoph



___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] Few quick questions

2022-03-09 Thread Christoph Hintermüller via ntg-context

Sorry for multi posting. Had yesterday a problem with my mail system
and was not sure if mail was sent at all.


On Tue, 2022-03-08 at 21:26 +0100, Marco Patzer via ntg-context wrote:
> On Tue, 08 Mar 2022 20:45:17 +0100
> Christoph Hintermüller via ntg-context  wrote:
> 
> > Hans indicated a tool, a program, which allows to verify that that
> > all start* stop* tag pairs are symmetric and placed in correct
> > order. I just cant remember how it is called. Can anybody help
> > here?
> 
>   mtxrun --autogenerate --script check 
> 


Thank you very much. If there is not any other tool it seems that there
are no errors.


> The following will not report missing tags but will find other
> common issues and report them on the console:
> 
>   context --errors='*' 


I guess this is equal to

\enabledirectives[logs.errors]

With which only the following error on plain pdf is remaining after
fixing any other indicated

error logging   > start possible issues

fonts   > start missing characters:
/usr/local/texlive/2021/texmf-dist/fonts/opentype/public/lm/lmroman12-
regular.otf
fonts   >2  U+1START OF HEADING
fonts   > stop missing characters

error logging   > stop possible issues



OK, I guess I figured the cause of why xml export aborts in the middle
of the document. It came to me while writing the above lines and
wanting to report that i see some warnings about fuzzy paragraphs
(forget about them).

To make it short it triggered a memory about a rather old thread, where
Hans mentioned that the exporter is not so fond of and keen about LaTeX
style \chapter, \section commands and that he advises to use
\startchapter \stopchapter, \startsection \stopsection, etc. pairs
instead. So i gave it a try and exchanged all occurrences of \chapter,
\section, \subsection, \subsection by their \start* \stop* equivalents
and now the xml document and the html document are a lot largen. They
now conatin nearly the whole document. 

There are sill plenty of LaTeX style commands around in the document
for which exporter friendly \start* \stop* replacements exist. I will
continue this route and 'am comfident that in the end  will get get a
full xhtml and true e-book for my lecture notes.
:-)

Thank you very much for triggering memories.

Christoph


___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] Few quick questions

2022-03-08 Thread Christoph Hintermüller via ntg-context
Hi 

I'm still stuck with also providing my lecture notes as epub in addtion
to its PDF version.

The last year, when I tried figure what is wrong, Hans indicated a
tool, a program, which allows to verify that that all start* stop* tag
pairs are symmetric and placed in correct order. I just cant remember
how it is called. Can anybody help here?

Second are there any limits in how large files exproted to XML, XHTML
etc can be. Does the exporter automatically try to split huge documents
into multiple exported documents when some size is exceeded or was or
is such a feature allways experiemental up to mkIV and what could break
proper slitting which contexts, commands should not be active to avoid
breakage. 

My current setup is neither a fresh install of latest standalone nor
texlive installation. This task is still pending. I just have done some
partial update mixing 2020 Texlife with 2021 standlalone by calling
update.sh. So the aborting of the export in the middle of a hundred
pages long document with plenty of floats and the heavy use of Aditya's
t-vim package might additionally be worsened by some inconsistencies of
my currently not clean installation. But to rule out or properly tackle
down I think I believe knowing about possible Limitations of exporter
in mkIV if any to be saving a lot of time

The abort in xml export also occurs when i inline all files exempt t-
vim code snippets, png or svg files replacing meta post images into one
huge document removing any \input commands. Therefore i want to check
first on the inlined document if there would by any asymetric start*
stop* before persuing further.




___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] Few quick questions

2022-03-08 Thread Christoph Hintermüller via ntg-context
Hi 

I'm still stuck with also providing my lecture notes as epub in addtion
to its PDF version.

The last year, when I tried figure what is wrong, Hans indicated a
tool, a program, which allows to verify that that all start* stop* tag
pairs are symmetric and placed in correct order. I just cant remember
how it is called. Can anybody help here?

Second are there any limits in how large files exproted to XML, XHTML
etc can be. Does the exporter automatically try to split huge documents
into multiple exported documents when some size is exceeded or was or
is such a feature allways experiemental up to mkIV and what could break
proper slitting which contexts, commands should not be active to avoid
breakage. 

My current setup is neither a fresh install of latest standalone nor
texlive installation. This task is still pending. I just have done some
partial update mixing 2020 Texlife with 2021 standlalone by calling
update.sh. So the aborting of the export in the middle of a hundred
pages long document with plenty of floats and the heavy use of Aditya's
t-vim package might additionally be worsened by some inconsistencies of
my currently not clean installation. But to rule out or properly tackle
down I think I believe knowing about possible Limitations of exporter
in mkIV if any to be saving a lot of time

The abort in xml export also occurs when i inline all files exempt t-
vim code snippets, png or svg files replacing meta post images into one
huge document removing any \input commands. Therefore i want to check
first on the inlined document if there would by any asymetric start*
stop* before persuing further.



-- 
-- 
Christoph Hintermüller
Dipl.-Ing. Dr. MBA. MSc
JKU Institute of Biomedical Mechatronics
Altenberger Straße 69,
4040 Linz, Austria,
Cell: +43 650 8827347
Tel. +43 732 2468 4813
Email: christoph.hintermuel...@jku.at

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___