Re: [NTG-context] Bugs using \startTEXpage ... \stopTEXpage, Metapost and text
On 12/6/20 3:29 PM, Jairo A. del Rio wrote:
> [...]
> gives a normal output in MkIV, but buggy output in LMTX. It seems only
> TeX commands in Metapost (textext, thetextext, etc.) are affected. Am I
> missing something?
Hi Jairo,
the sample can be much simpler:
\starttext
\startMPcode
draw textext("some text");
\stopMPcode
\stoptext
This might be related to the issue that I reported about text scaling in
lmt_followtext
(https://mailman.ntg.nl/pipermail/ntg-context/2020/100573.html).
Just in case it helps,
Pablo
--
http://www.ousia.tk
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] Bugs using \startTEXpage ... \stopTEXpage, Metapost and text
Hi. The following:
\starttext
%Using \startMPpage instead doesn't help
\startTEXpage[width=1920px,height=1080px,margin=1em]
\startplacefigure[location=force,number=no]
\startMPcode
draw textext("some text");
\stopMPcode
\stopplacefigure
\stopTEXpage
\stoptext
gives a normal output in MkIV, but buggy output in LMTX. It seems only TeX
commands in Metapost (textext, thetextext, etc.) are affected. Am I missing
something?
Thank you in advance.
Regards,
Jairo :)
___
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] Bugs in \framed
On 9/6/2019 10:02 PM, Henning Hraban Ramm wrote:
In
ConTeXt ver: 2019.08.24 22:42 MKIV beta fmt: 2019.9.6
LuaTeX, Version 1.10.1
(i.e. today’s beta)
* framecorner doesn’t work any more (all the same)
typo .. i'll fix it
* backgroundoffset is shifted downwards (used to be centered, but is wrong for
a while)
hm
\framed[
frame=on, corner=round,
frameoffset=0.5em, framecolor=black,
background=color, backgroundcolor=darkgreen,
backgroundoffset=1em,
foreground=color,color=white,
]{{\color[white]{\ss\bf I wanted Center Green!}}}
btw, use
foregroundcolor=white
so
> backgroundoffset=1em,
> foregroundcolor=white]
> {\ss\bf I wanted Center Green!}
will do
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] Bugs in \framed
In
ConTeXt ver: 2019.08.24 22:42 MKIV beta fmt: 2019.9.6
LuaTeX, Version 1.10.1
(i.e. today’s beta)
* framecorner doesn’t work any more (all the same)
* backgroundoffset is shifted downwards (used to be centered, but is wrong for
a while)
examples:
\starttext
{\setupframed[foregroundstyle=mono,rulethickness=1pt,offset=0.5em,framecolor=darkgreen]
\startcombination[3*10]
{\framed[framecorner=00]{framecorner=00}}{}
{\framed[framecorner=01]{framecorner=01}}{}
{\framed[framecorner=02]{framecorner=02}}{}
{\framed[framecorner=03]{framecorner=03}}{}
{\framed[framecorner=04]{framecorner=04}}{}
{\framed[framecorner=05]{framecorner=05}}{}
{\framed[framecorner=06]{framecorner=06}}{}
{\framed[framecorner=07]{framecorner=07}}{}
{\framed[framecorner=08]{framecorner=08}}{}
{\framed[framecorner=09]{framecorner=09}}{}
{\framed[framecorner=10]{framecorner=10}}{}
{\framed[framecorner=11]{framecorner=11}}{}
{\framed[framecorner=12]{framecorner=12}}{}
{\framed[framecorner=13]{framecorner=13}}{}
{\framed[framecorner=14]{framecorner=14}}{}
{\framed[framecorner=15]{framecorner=15}}{}
{\framed[framecorner=16]{framecorner=16}}{}
{\framed[framecorner=17]{framecorner=17}}{}
{\framed[framecorner=18]{framecorner=18}}{}
{\framed[framecorner=19]{framecorner=19}}{}
{\framed[framecorner=20]{framecorner=20}}{}
{\framed[framecorner=21]{framecorner=21}}{}
{\framed[framecorner=22]{framecorner=22}}{}
{\framed[framecorner=23]{framecorner=23}}{}
{\framed[framecorner=24]{framecorner=24}}{}
{\framed[framecorner=25]{framecorner=25}}{}
{\framed[framecorner=26]{framecorner=26}}{}
{\framed[framecorner=27]{framecorner=27}}{}
{\framed[framecorner=28]{framecorner=28}}{}
{}{}
\stopcombination
% I had no idea how to do that with recursion
}
\framed[frame=off,
background=color,backgroundcolor=yellow,
]{Textmarker}
\framed[
background=color,backgroundcolor=red,
foreground=color,color=white,
]{{\color[white]{Pommes Rot-Weiß}}}
\framed[
frame=on, corner=round,
frameoffset=0.5em, framecolor=black,
background=color, backgroundcolor=darkgreen,
backgroundoffset=1em,
foreground=color,color=white,
]{{\color[white]{\ss\bf I wanted Center Green!}}}
\stoptext
Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD
___
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] Bugs with minimals 2015.05.24 12:42
On 24 May 2016 at 12:06, Meer, Hans van der wrote: >> On 02 Jun 2015, at 14:51, Hans Hagen wrote: >> >> If you install extra fonts and files, you should put them in >> >> tex/texmf-fonts >> tex/texmf-project >> >> as these are left untouched. That has always been the recommendation. The >> other trees will be synchronized in an update and that also includes >> deleting obsolete files. > > I guess the same applies to /tex/texmf-local? > > And how is that with tex/texmf-modules? I am asking because there is also a > modules directory: > context/tex/texmf-context/tex/context/modules > It would be nice if I safely can put my modules there instead of burying them > somewhere else in the trees. If you put files under texmf-context, they will be removed automatically with next update. You can install official modules with "--modules=t-tikz" for example and those will stay. But if you want your own unrelated modules, you should not use texmf-modules unless you remove the "--delete" flag for rsync (but then you'll end up with other obsolete files). The trees texmf-local, texmf-fonts, texmf-projects are all fine. Mojca ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Bugs with minimals 2015.05.24 12:42
> On 02 Jun 2015, at 14:51, Hans Hagen wrote: > > If you install extra fonts and files, you should put them in > > tex/texmf-fonts > tex/texmf-project > > as these are left untouched. That has always been the recommendation. The > other trees will be synchronized in an update and that also includes deleting > obsolete files. I guess the same applies to /tex/texmf-local? And how is that with tex/texmf-modules? I am asking because there is also a modules directory: context/tex/texmf-context/tex/context/modules It would be nice if I safely can put my modules there instead of burying them somewhere else in the trees. Hans van der Meer ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Bugs with minimals 2015.05.24 12:42
On Tue, Jun 2, 2015 at 2:26 PM, david.boerschl...@juno.com wrote: > > (*) tex error > error on line 1 in file > /var/www/vhosts/door43.org/tools/nototest.tex: ! Undefined control sequence > l.1 \useregime > [utf] > 1 >> \useregime[utf] > 2 \enableregime[utf] > Version: 2015.05.24 12:42 If you are using MkII (that is: if you are running "texexec"), you should use \enableregime[utf-8] If you use LuaTeX, there's no need to enable UTF-8. It's already the default. > (*) Upgrading with "first-setup.sh" deleted all the third-party fonts which > we had spent months installing. I'm sorry to hear that. The idea is to install fonts to texmf-local or texmf-fonts or texmf-project or somewhere else. But the files get removed from "texmf", "texmf-context", "texmf-modules" etc. I'm sorry that that wasn't clear (or maybe not even mentioned) in the documentation. > (*) Installing the "context=current" installed a "beta" version of luatex: > context --version > mtx-context | current version: 2015.05.24 12:42 > luatex --version > This is LuaTeX, Version beta-0.80.0 (TeX Live 2015) (rev 5238) A "non-beta" version of LuaTeX doesn't exist. > (*) http://tug.org/pracjourn/2005-2/schmitz/schmitz.pdf (none of the commands > texfont, ttf2afm, updmap, come with the latest ConTeXt minimals 2015.05.24 > 12:42) [Is this really the up-to-date documentation on how to install a > true-type font?]It does not seem to discuss what to do if all we have is > an ".otf" but no ".ttf" The documentation is from 2005 as the URL suggests. So no, it's not up-to-date. Use LuaTeX instead and you can forget about dirty workarounds to get the fonts to work. > (*) Documentation request: typescripts for "ttf" and "otf" files which may or > may not have bold, italics, etc with fallback-families and Unicode ranges and > separate files for Unicode-ranges (e.g., Google Noto fonts). This is all possible (it might require a bit of work to get everything set up properly), but you should definitely switch to LuaTeX. Mojca ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Bugs with minimals 2015.05.24 12:42
On 6/2/2015 2:26 PM, david.boerschl...@juno.com wrote: (*) tex error > error on line 1 in file /var/www/vhosts/door43.org/tools/nototest.tex: ! Undefined control sequence l.1 \useregime [utf] 1 >> \useregime[utf] 2 \enableregime[utf] Version: 2015.05.24 12:42 (*) Upgrading with "first-setup.sh" deleted all the third-party fonts which we had spent months installing. If you install extra fonts and files, you should put them in tex/texmf-fonts tex/texmf-project as these are left untouched. That has always been the recommendation. The other trees will be synchronized in an update and that also includes deleting obsolete files. (*) Installing the "context=current" installed a "beta" version of luatex: context --version mtx-context | current version: 2015.05.24 12:42 luatex --version This is LuaTeX, Version beta-0.80.0 (TeX Live 2015) (rev 5238) (*) http://tug.org/pracjourn/2005-2/schmitz/schmitz.pdf (none of the commands texfont, ttf2afm, updmap, come with the latest ConTeXt minimals 2015.05.24 12:42) [Is this really the up-to-date documentation on how to install a true-type font?]It does not seem to discuss what to do if all we have is an ".otf" but no ".ttf" (*) Documentation request: typescripts for "ttf" and "otf" files which may or may not have bold, italics, etc with fallback-families and Unicode ranges and separate files for Unicode-ranges (e.g., Google Noto fonts). you can put the fonts in tex/texmf-fonts/fonts/data/someplace and run mtxrun --generate and then try the selectfont command Hans - 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 - ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] Bugs with minimals 2015.05.24 12:42
(*) tex error > error on line 1 in file /var/www/vhosts/door43.org/tools/nototest.tex: ! Undefined control sequence l.1 \useregime [utf] 1 >> \useregime[utf] 2 \enableregime[utf] Version: 2015.05.24 12:42 (*) Upgrading with "first-setup.sh" deleted all the third-party fonts which we had spent months installing. (*) Installing the "context=current" installed a "beta" version of luatex: context --version mtx-context | current version: 2015.05.24 12:42 luatex --version This is LuaTeX, Version beta-0.80.0 (TeX Live 2015) (rev 5238) (*) http://tug.org/pracjourn/2005-2/schmitz/schmitz.pdf (none of the commands texfont, ttf2afm, updmap, come with the latest ConTeXt minimals 2015.05.24 12:42) [Is this really the up-to-date documentation on how to install a true-type font?]It does not seem to discuss what to do if all we have is an ".otf" but no ".ttf" (*) Documentation request: typescripts for "ttf" and "otf" files which may or may not have bold, italics, etc with fallback-families and Unicode ranges and separate files for Unicode-ranges (e.g., Google Noto fonts). David Boerschlein (214) 412-3275 home office land (585) 278-4687 cell www.linkedin.com/in/davidboerschlein Old School Yearbook Pics View Class Yearbooks Online Free. Search by School & Year. Look Now! http://thirdpartyoffers.juno.com/TGL3141/556da14029abe214072e9st01duc ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] BUGS with \setupbodyfontenvironment
> Am 22.05.2015 um 13:07 schrieb david.boerschl...@juno.com: > > I have the following: > > \setupbodyfontenvironment[default][em=italic,x=9.0pt,xx=8.0pt,a=12.0pt,b=14.0pt,c=16.0pt,d=18.0pt,e=24.0pt,small=8.0pt] > > Per: http://wiki.contextgarden.net/Font_Switching > > However Context has a syntax error. > > ! Missing \endcsname inserted > ! You can't use `\dimexpr' in restricted horizontal mode > > If I change the above to: > \setupbodyfontenvironment[default][em=italic,x=0.9,xx=0.8,a=1.2,b=1.4,c=1.6,d=2.4,e=3.0,f=4.0,small=0.8] > > then the .tex compiles and runs and generates PDF output. > > Also, \tfe is documented to work but it is being flagged as a undefined > control sequence error whereas \tfd works. We are using context current > version: 2014.01.03 00:40 Only the a–d sizes are predefined, to get the e you have to add \definefontsize[e] to your document. Wolfgang ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] BUGS with \setupbodyfontenvironment
I have the following: \setupbodyfontenvironment[default][em=italic,x=9.0pt,xx=8.0pt,a=12.0pt,b=14.0pt,c=16.0pt,d=18.0pt,e=24.0pt,small=8.0pt] Per: http://wiki.contextgarden.net/Font_Switching However Context has a syntax error. ! Missing \endcsname inserted ! You can't use `\dimexpr' in restricted horizontal mode If I change the above to: \setupbodyfontenvironment[default][em=italic,x=0.9,xx=0.8,a=1.2,b=1.4,c=1.6,d=2.4,e=3.0,f=4.0,small=0.8] then the .tex compiles and runs and generates PDF output. Also, \tfe is documented to work but it is being flagged as a undefined control sequence error whereas \tfd works. We are using context current version: 2014.01.03 00:40 David Boerschlein (214) 412-3275 home office land (585) 278-4687 cell www.linkedin.com/in/davidboerschlein Heavy rains mean flooding Anywhere it rains it can flood. Learn your risk. Get flood insurance. http://thirdpartyoffers.juno.com/TGL3141/555f0e2e7d243e2e5e2dst04duc ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] bugs in page breaks with items
Dear Hans,
sorry for bothering you with this, but today I found an ugly pagebreak
such as the following in a book I’m writting:
\showframe\showgrid
\setupbodyfont[pagella,15pt]
\starttext
\chapter{Chapter title}
\section{Section title}
\dorecurse{10}{\dorecurse{10}{Sentence. }\par}
\startitemize
\item \dorecurse{5}{This is an item. }
\item \dorecurse{15}{This is an item. }
\item \dorecurse{5}{This is an item. }
\stopitemize
\stoptext
The second item from the list has the page break in the sample above.
But if you comment the last item from the list, first two items fit in
the first page.
For some strange reason, ConTeXt is not able to leave the third item in
that list alone in the second page.
I have the strong impression that items themselves (not the paragraphs
they contain) are handled by ConTeXt with rules for widow and orphan lines.
The example above shows this. If you change recursion in the second item
from 15 to 10 (so that the item has three lines), the whole list is
moved to the second page. I think that the first item should remain on
the first page.
Another sample that shows the same behavior:
\showframe\showgrid
\setupbodyfont[pagella,15pt]
\starttext
\chapter{Chapter title}
\section{Section title}
\dorecurse{10}{\dorecurse{10}{Sentence. }\par}
\startitemize
\dorecurse{4}{\item This is an item.\par}
\stopitemize
\stoptext
If there are four items, all text fits in one page. If there are five
items, three items remain in the first page and two items move to the
second page (not only the last one, as it should).
But if there are six items in the list, the first four ones remain in
the first page and the other two move to the second page.
Could you fix these page breaks?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in page break (relevant for TeX Live 2014)
On 6/1/2014 7:09 AM, Pablo Rodriguez wrote:
Dear Hans,
there is a wrong page break introduced in the stable version intended
for TeX Live 2014.
it's unlikely to be fixed in tl 2014 ... already frozen ... but there is
updating built-in texlive so it's no big deal
Here you have the sample that shows the issue:
\showframe\showgrid
\setupbodyfont[pagella,15pt]
\starttext
\chapter{Chapter title}
\section{Section title}
\dorecurse{140}{Sentence. }
\subsection{Subsection title}
This is another line.
\stoptext
Page break is wrong when \subsection is active or replaced with
\subsubsection. Page break is right when \subsection is disabled or
replaced with \section.
By the way, I experience another page break with lists (I guess it was
introduced with the same beta as above, but I’m not sure).
Here is the sample:
\showframe\showgrid
\setupbodyfont[pagella,15pt]
\starttext
\chapter{Chapter title}
\section{Section title}
\dorecurse{140}{Sentence. }
\startitemize
\dorecurse{4}{\item This is an item.\par}
\stopitemize
\stoptext
Page break above is wrong when recursion is over 2.
actually it's okay as context prevents a break between the first two and
last two item entries (has always been the case)
\startitemize[loose]
disables this
Hans
-
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
-
___
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
[NTG-context] bugs in page break (relevant for TeX Live 2014)
Dear Hans,
there is a wrong page break introduced in the stable version intended
for TeX Live 2014.
Here you have the sample that shows the issue:
\showframe\showgrid
\setupbodyfont[pagella,15pt]
\starttext
\chapter{Chapter title}
\section{Section title}
\dorecurse{140}{Sentence. }
\subsection{Subsection title}
This is another line.
\stoptext
Page break is wrong when \subsection is active or replaced with
\subsubsection. Page break is right when \subsection is disabled or
replaced with \section.
By the way, I experience another page break with lists (I guess it was
introduced with the same beta as above, but I’m not sure).
Here is the sample:
\showframe\showgrid
\setupbodyfont[pagella,15pt]
\starttext
\chapter{Chapter title}
\section{Section title}
\dorecurse{140}{Sentence. }
\startitemize
\dorecurse{4}{\item This is an item.\par}
\stopitemize
\stoptext
Page break above is wrong when recursion is over 2.
Could you fix these wrong page breaks?
I think both fixes should be included in TeX Live 2014.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Bugs in linenumbering ?
Le Thu, 03 Apr 2014 23:02:41 -0400, Rik Kabel a écrit : > On 2014-04-03 20:15, Stéphane Goujet wrote: > >Here is what I have done so far. Not too bad a result, but there > > are still 2 main problems: > > -- when the quotation begins after the beginning of the paragraph, > > the whole paragraph is affected by *narrower*; > > -- when the text continues after the end of the quotation, it is > > impossible to insert the *\par* that, as Hans noticed and told us, > > is needed to have *narrower* work, so it is as if there was no > > *narrower* and the whole line numbering of the paragraph is messed > > up. > That is the big one for me. As the example png I posted shows, I need > to have support for multiple quoted sections and unquoted text at the > end. Same for me. I understand that it makes little sense (or perhaps no sense at all) for line numbering to deal with such situations; this is why in first post concerning our quotation matter, I was asking whether linenumbering would be the way to go or not. Goodbye, Stéphane. ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Bugs in linenumbering ?
On 2014-04-03 20:15, Stéphane Goujet wrote: ... Here is what I have done so far. Not too bad a result, but there are still 2 main problems: -- when the quotation begins after the beginning of the paragraph, the whole paragraph is affected by *narrower*; -- when the text continues after the end of the quotation, it is impossible to insert the *\par* that, as Hans noticed and told us, is needed to have *narrower* work, so it is as if there was no *narrower* and the whole line numbering of the paragraph is messed up. That is the big one for me. As the example png I posted shows, I need to have support for multiple quoted sections and unquoted text at the end. and 2 minor ones: -- no paragraph indentation in footnotes. I have some very long footnotes and have moved to endnotes. The same issues present themselves, and many others related to commands that do not work in margins, footnotes, and other floating environments, but I think the solution is to write them as a separate chapter and manage the cross-references (footnote marks) myself. -- Alignment of the first quoted paragraph in respect to the following quoted paragraphs is not perfect (because I use different symbols for the quotation opening («) and the quotation repetition (»), I guess). But this point is good enough for me. The opening and repetition guillemot in paragraphs started by \startbloccite and \bloccitepar align correctly. The difference in alignment of the first text character in those paragraphs appears to be about 0.45pt, which can be handled by the \hskip at the end of the definition of \bloccitepar. That value is absolute, so may need adjusting for other fonts and sizes. Perhaps an hskip of 0.375em might be more flexible. Another problem occurs when protrusion is enabled. A guillemot in running text that happens to be placed at the beginning of a line will protrude into the left margin channel, but the guillemots that are generated by this mechanism will not protrude. When these are on the same page it is ugly. ... Goodbye, Stéphane. -- Rik ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Bugs in linenumbering ?
Le Thu, 03 Apr 2014 13:01:04 -0400,
Rik Kabel a écrit :
> On 2014-04-03 13:16, Stéphane Goujet wrote:
> > Le Thu, 03 Apr 2014 16:19:18 +0200,
> > Hans Hagen a écrit :
> >
> >> with respect to text: you need to go narrower or set the distance
> >> to (e.g.) -1cm
> >It seems I can indeed get nice results with
> >
> > \setuplinenumbering[location=text]
> > \startnarrower[left]
> > \startlinenumbering
> >
> >> i've added support for notes (somewhat tricky)
> >>
> >> \starttext
> >> Here we have a footnote \footnote{%
> >> \startlinenumbering
> >> \input tufte
> > A few numbers : 012345679.
> >> \par % somehow needed
> >> \stoplinenumbering
> >> }
> >> \stoptext
> As to the size in footnotes, try:
>
> \definelinenumbering[fntext]
> \setuplinenumbering[fntext][style=\ssxx]
If I could avoid defining another set of different macros, I would
prefer... (For I have already 2 start macros, 2 stop macros, and 1
intermediate macro: it already lacks a bit of automatising).
> However, for the general case, there is still an issue with
> linenumbering that begins after the beginning of a paragraph. The
> work-around of \startnarrower cannot help in this case, since it
> appears to always start a new paragraph.
So, with the [before=] (and [after=] for continuing text after
\stopnarrower), it is possible.
Here is what I have done so far. Not too bad a result, but there are
still 2 main problems:
-- when the quotation begins after the beginning of the paragraph, the
whole paragraph is affected by *narrower*;
-- when the text continues after the end of the quotation, it is
impossible to insert the *\par* that, as Hans noticed and told us, is
needed to have *narrower* work, so it is as if there was no *narrower*
and the whole line numbering of the paragraph is messed up.
and 2 minor ones:
-- no paragraph indentation in footnotes.
-- Alignment of the first quoted paragraph in respect to the following
quoted paragraphs is not perfect (because I use different symbols for
the quotation opening («) and the quotation repetition (»), I guess).
But this point is good enough for me.
==
\setuppapersize[A4]
\enableregime[utf-8]
\mainlanguage[fr]
\language[fr]
\setcharacterspacing[frenchpunctuation]
\setupindenting[first,yes,medium]
\setupnotation[footnote][location=margin]
\define\repsym{»}
\newdimen\repshift
\repshift=.75em
\definelinenumbering[repcite]
\setuplinenumbering[repcite][location=text,command=\repmark,before=,after=]
\definelinenumbering[repcitel]
\setuplinenumbering[repcitel][location=text,command={\repsym\gobbleoneargument}]
\defineexpandable[1]\repmark{\doifnot{#1}{1}{\repsym}}
\definenarrower[narcite][left=\repshift,before=,after=]
\define\startbloccite{\startnarcite[left]\setupindenting[first,yes,\dimexpr\parindent-\repshift]\startlinenumbering[repcite]«}
\define\startbloccitel{\startnarcite[left]\setupindenting[first,yes,\dimexpr\parindent-\repshift]\startlinenumbering[repcitel]«}
\define\stopbloccite{»\par\stoplinenumbering\stopnarrower}
\define\stopbloccitel{»\stoplinenumbering\stopnarrower}
\define\bloccitepar{\stoplinenumbering
\par
\startlinenumbering[repcite]\leavevmode\hbox to\repshift{\repsym}\hskip0pt
}
\starttext
First check: «normal spacing of guillemets».
Second check: a normal paragraph, to show {\bf normal right margin limit}.
\input tufte
«Third check : paragraph starting with guillemets.»
Let's start with a quote block on a {\bf new line} :
\startbloccite
%First paragraph ({\bf quote repetition symbol is really not wanted here}):
\input tufte (\the\hsize)
Second paragraph ({\bf indenting and margins are correct}): \input tufte
\bloccitepar
Second paragraph ({\bf indenting and margins are correct}): \input tufte
\bloccitepar
Third paragraph ({\bf now I put a different sentence here to check hyphenation.
Weird, it looks OK now, I cannot reproduce the overflow.}): \input tufte
\stopbloccite
Now, a quote block starting just there, {\bf in the middle of a line}
({\bf the problem is that \char`\\startnarrower affects the whole paragraph :
every lines are narrowed, even the ones before the environment
starts}):\startbloccitel\input tufte
\bloccitepar
\input tufte
\stopbloccitel . This a bit of text at the end of the quotation.
{\bf The whole paragraph is wrong because I could not end it with a
\char`\\par}.
And let's call a {\bf footnote}\footnote{\startbloccite\input tufte
\bloccitepar
\input tufte
\stopbloccite}. {\bf Fine : quote repetition symbols do now appear
in it. But there is no paragraph indentation.}.
\stoptext
==
Goodbye,
Stéphane.
___
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://tex.aanhet.net
archive : http://foundry.sup
Re: [NTG-context] Bugs in linenumbering ?
Le Thu, 03 Apr 2014 13:01:04 -0400, Rik Kabel a écrit : > However, for the general case, there is still an issue with > linenumbering that begins after the beginning of a paragraph. The > work-around of \startnarrower cannot help in this case, since it > appears to always start a new paragraph. Have you tried \startnarrower[before=] ? I haven't yet, but I will go back to it soon. ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Bugs in linenumbering ?
On 2014-04-03 13:16, Stéphane Goujet
wrote:
Le Thu, 03 Apr 2014 16:19:18 +0200,
Hans Hagen a écrit :
you probably didn't test with the beta because most looks ok
Dammit, you are right. And yet I was using fairly recent versions
(25/03 and 27/03).
with respect to text: you need to go narrower or set the distance to
(e.g.) -1cm
It seems I can indeed get nice results with
\setuplinenumbering[location=text]
\startnarrower[left]
\startlinenumbering
Thanks !
i've added support for notes (somewhat tricky)
\starttext
Here we have a footnote \footnote{%
\startlinenumbering
\input tufte
A few numbers : 012345679.
\par % somehow needed
\stoplinenumbering
}
\stoptext
Thank you again. To annoy you one more time, still one thing : the
font size of the line numbers is the one of the main text, no the
smaller one that numbers should have in the footnote part (just add a
few numbers in the footnote text to compare easily).
As to the size in footnotes, try:
\definelinenumbering[fntext]
\setuplinenumbering[fntext][style=\ssxx]
or similar.
However, for the general case, there is still an issue with
linenumbering that begins after the beginning of a paragraph. The
work-around of \startnarrower cannot help in this case, since it
appears to always start a new paragraph. Thus, it cannot be used to
reproduce the form of quotation we are trying to replicate (from
Thomas Bowdler, The Family Shakespeare, 1807):
___
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Bugs in linenumbering ?
Le Thu, 03 Apr 2014 16:19:18 +0200,
Hans Hagen a écrit :
> you probably didn't test with the beta because most looks ok
Dammit, you are right. And yet I was using fairly recent versions
(25/03 and 27/03).
> with respect to text: you need to go narrower or set the distance to
> (e.g.) -1cm
It seems I can indeed get nice results with
\setuplinenumbering[location=text]
\startnarrower[left]
\startlinenumbering
Thanks !
> i've added support for notes (somewhat tricky)
>
> \starttext
> Here we have a footnote \footnote{%
> \startlinenumbering
> \input tufte
A few numbers : 012345679.
> \par % somehow needed
> \stoplinenumbering
> }
> \stoptext
Thank you again. To annoy you one more time, still one thing : the
font size of the line numbers is the one of the main text, no the
smaller one that numbers should have in the footnote part (just add a
few numbers in the footnote text to compare easily).
Faithfully yours,
Stéphane.
___
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Bugs in linenumbering ?
On 04/03/2014 04:19 PM, Hans Hagen wrote: > On 4/2/2014 3:17 PM, Stéphane Goujet wrote: >> >> 3) linenumbering does not work within footnotes (neither with line >> numbers in margin nor in text). > > i've added support for notes (somewhat tricky) Sorry, but I cannot refrain from asking: how about having line numbers in \setupnote and being optional to have different or the same counting than the rest of the page? Pablo -- http://www.ousia.tk ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Bugs in linenumbering ?
On 4/2/2014 3:17 PM, Stéphane Goujet wrote:
Hello,
Here is an example that highlights a few problems I have with
linenumbering.
When the line numbers are located in the margin, everything is fine.
But when the number is located in the text:
1) Text overflows in the right margin.
2) Paragraph indenting does not work. We can even see a kind of right
indentation appear.
1+2 => First line of the paragraph is too short, netx ones are too long.
3) linenumbering does not work within footnotes (neither with line
numbers in margin nor in text).
Perhaps (3) is not implemented, but I suppose (1) and (2) are not
the expected behaviour.
==
\setuppapersize[A4]
\setupindenting[yes,first,medium]
\definelinenumbering[lnbasic]
\definelinenumbering[lntext]
\definelinenumbering[lntextandnullwidth]
\definelinenumbering[lntextandwidth]
\setuplinenumbering[lnbasic][]
\setuplinenumbering[lntext][location=text]
\setuplinenumbering[lntextandnullwidth][location=text,width=0pt]
\setuplinenumbering[lntextandwidth][location=text,width=.75em]
\starttext
{\bf A normal paragraph for reference}. \input tufte
\startlinenumbering[lnbasic]
{\bf Numbers in margin : correct right margin, paragraph indentation.}
\input tufte \stoplinenumbering
\startlinenumbering[lntext]
{\bf Numbers in text, default width : overflow, no indentation of the
first line but some kind of right indentation!} \input tufte
\stoplinenumbering
\startlinenumbering[lntextandnullwidth]
{\bf Numbers in text, 0 width : no overflow but overtype on numbers,
same problem with indentation.} \input tufte
\stoplinenumbering
\startlinenumbering[lntextandwidth]
{\bf Numbers in text, average width : average overflow, same problem
with indentation.} \input tufte
\stoplinenumbering
It also affects the previous lines when {em line numbering} starts from
the middle of the line and not on a new paragraph.
\startlinenumbering[lntext]
{\bf Numbers in text, default width : overflow, no indentation of the
first line but some kind of right indentation!} \input tufte
\stoplinenumbering
Line numbering does not work in footnotes\footnote{
\startlinenumbering[lnbasic]
{\bf Numbers in margins.} \input tufte
\stoplinenumbering
}
\footnote{
\startlinenumbering[lntext]
{\bf Numbers in text.} \input tufte
\stoplinenumbering
}.
\stoptext
you probably didn't test with the beta because most looks ok
i've added support for notes (somewhat tricky)
\starttext
Here we have a footnote \footnote{%
\startlinenumbering
\input tufte
\par % somehow needed
\stoplinenumbering
}
\stoptext
with respect to text: you need to go narrower or set the distance to
(e.g.) -1cm
-
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
-
___
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
[NTG-context] Bugs in linenumbering ?
Hello,
Here is an example that highlights a few problems I have with
linenumbering.
When the line numbers are located in the margin, everything is fine.
But when the number is located in the text:
1) Text overflows in the right margin.
2) Paragraph indenting does not work. We can even see a kind of right
indentation appear.
1+2 => First line of the paragraph is too short, netx ones are too long.
3) linenumbering does not work within footnotes (neither with line
numbers in margin nor in text).
Perhaps (3) is not implemented, but I suppose (1) and (2) are not
the expected behaviour.
==
\setuppapersize[A4]
\setupindenting[yes,first,medium]
\definelinenumbering[lnbasic]
\definelinenumbering[lntext]
\definelinenumbering[lntextandnullwidth]
\definelinenumbering[lntextandwidth]
\setuplinenumbering[lnbasic][]
\setuplinenumbering[lntext][location=text]
\setuplinenumbering[lntextandnullwidth][location=text,width=0pt]
\setuplinenumbering[lntextandwidth][location=text,width=.75em]
\starttext
{\bf A normal paragraph for reference}. \input tufte
\startlinenumbering[lnbasic]
{\bf Numbers in margin : correct right margin, paragraph indentation.}
\input tufte \stoplinenumbering
\startlinenumbering[lntext]
{\bf Numbers in text, default width : overflow, no indentation of the
first line but some kind of right indentation!} \input tufte
\stoplinenumbering
\startlinenumbering[lntextandnullwidth]
{\bf Numbers in text, 0 width : no overflow but overtype on numbers,
same problem with indentation.} \input tufte
\stoplinenumbering
\startlinenumbering[lntextandwidth]
{\bf Numbers in text, average width : average overflow, same problem
with indentation.} \input tufte
\stoplinenumbering
It also affects the previous lines when {em line numbering} starts from
the middle of the line and not on a new paragraph.
\startlinenumbering[lntext]
{\bf Numbers in text, default width : overflow, no indentation of the
first line but some kind of right indentation!} \input tufte
\stoplinenumbering
Line numbering does not work in footnotes\footnote{
\startlinenumbering[lnbasic]
{\bf Numbers in margins.} \input tufte
\stoplinenumbering
}
\footnote{
\startlinenumbering[lntext]
{\bf Numbers in text.} \input tufte
\stoplinenumbering
}.
\stoptext
==
Goodbye,
Stéphane.
___
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Bugs in XML export (for ePub)
Am 2014-03-12 um 09:24 schrieb Henning Hraban Ramm :
> Am 2014-03-11 um 23:54 schrieb Thangalin :
>
>> Here is the thread from last year for your reference:
>> https://www.mail-archive.com/ntg-context@ntg.nl/msg71376.html
>
> Thank you, that’s what I was referring to.
> Hans says, ConTeXt would export XML, but that isn’t true, since the exported
> „XML“ lacks a root element.
> (Issue [1] in my previous post.)
Ok, I take it partially back: If I have just one standalone document, the
output is ok.
So the problem is mostly in the combination of export with project structure.
But … please see below.
Minimal succeeding example:
———
%
\setupbackend[export=export.xml]
\settaggedmetadata[
title={Export Test Solo},
author={Hraban},
version=\currentdate % why that doesn’t work?
]
\starttext
\startchapter[title={Chapter One}]
\startsection[title={Section One}]
\input tufte
\stopsection
\startsection[title={Section Two}]
\input knuth
\stopsection
\stopchapter
\stoptext
———
gives
———
http://www.w3.org/1998/Math/MathML";>
Hraban
Export Test Solo
\currentdate
1
Chapter One
1.1
Section One
We thrive in information--thick worlds because of our marvelous and everyday
capacity to select, edit, single out, structure, highlight, group, pair, merge,
harmonize, synthesize, focus, organize, condense, reduce, boil down, choose,
categorize, catalog, classify, list, abstract, scan, look into, idealize,
isolate, discriminate, distinguish, screen, pigeonhole, pick over, sort,
integrate, blend, inspect, filter, lump, skip, smooth, chunk, average,
approximate, cluster, aggregate, outline, summarize, itemize, review, dip into,
flip through, browse, glance into, leaf through, skim, refine, enumerate,
glean, synopsize, winnow the wheat from the chaff and separate the sheep from
the goats.
1.2
Section Two
Thus, I came to the conclusion that the designer of a new system must not only
be the implementer and first large--scale user; the designer should also write
the first user manual.
The separation of any of these four components would have hurt TEX
significantly. If I had not participated fully in all these activities,
literally hundreds of improvements would never have been made, because I would
never have thought of them or perceived why they were important.
But a system cannot be successful if it is too strongly influenced by a single
person. Once the initial design is complete and fairly robust, the real test
begins as people with many different viewpoints undertake their own experiments.
———
The wiki page about ePub says, it should be possible to define metadata in
\setupexport like this:
\setupexport[
firstpage={koe.pdf},
title={My Fine Title},
]
But that is completely ignored - it does neither show up in the export, nor in
a produced ePub.
If I include an image with \externalfigure[koe][width=\textwidth], I get in
export:
That’s not really usable without file extension. In my case, it was even a GIF
„giraffe.gif“ that got converted to „m_k_i_v_giraffe.gif.pdf“ .
Would it be possible to set the actually used file name as an additional
attribute in ?
I’ll document the issues with export in project structure in my next post.
Greetlings, Hraban
___
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Bugs in XML export (for ePub)
Am 2014-03-11 um 23:54 schrieb Thangalin : > Here is the thread from last year for your reference: > https://www.mail-archive.com/ntg-context@ntg.nl/msg71376.html Thank you, that’s what I was referring to. Hans says, ConTeXt would export XML, but that isn’t true, since the exported „XML“ lacks a root element. (Issue [1] in my previous post.) Following Wolfang’s advice I’ll provide minimal examples. Greetlings, Hraban --- http://www.fiee.net/texnique/ http://wiki.contextgarden.net https://www.cacert.org (I'm an assurer) ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Bugs in XML export (for ePub)
Hi, Hraban. Here is the thread from last year for your reference: https://www.mail-archive.com/ntg-context@ntg.nl/msg71376.html ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Bugs in XML export (for ePub)
Am 11.03.2014 um 09:09 schrieb Henning Hraban Ramm :
> more issues:
>
> [5] emphasis
>
> How to markup emphasize (\em, \bf, \it, \sl) so that it gets exported? {\em
> Something} doesn’t.
You have to create a command for them which add tags, e.g.
\definehighlight[important][style=italic]
or
\definestartstop[important][style=italic]
and use
normal text \important{important text} normal text
> And hey, can I bribe you to look into that issues? Some nice felt hats from
> Kyrgyzstan perhaps?
>
> The ePub/export stuff is not in a workable state. If you don’t want to work
> at it, we should really remove it to avoid raising false hopes.
>
> I can’t tell how easy it is to fix/enhance. Would it make sense for me to
> start somewhere?
You can make a few minimal examples with bugs in export mechanism.
Wolfgang
___
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Bugs in XML export (for ePub)
more issues:
[5] emphasis
How to markup emphasize (\em, \bf, \it, \sl) so that it gets exported? {\em
Something} doesn’t.
And hey, can I bribe you to look into that issues? Some nice felt hats from
Kyrgyzstan perhaps?
The ePub/export stuff is not in a workable state. If you don’t want to work at
it, we should really remove it to avoid raising false hopes.
I can’t tell how easy it is to fix/enhance. Would it make sense for me to start
somewhere?
Greetlings, Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
___
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Bugs in XML export (for ePub)
Am 2014-03-11 um 12:42 schrieb Thangalin : > In practice, ConTeXt cannot actually produce ePub content of any > sufficient complexity that an ePub reader (such as Kindle) can read. I > abandoned that development line a while ago. That said, ConTeXt is > orders of magnitude easier to work with than LaTeX (for me) and has an > architecture that holds a promising future. > ... > Unless anyone says otherwise (or there have been momentous > improvements in this area), I would recommend that you do not use > ConTeXt to create ePub files. While technically it can produce an ePub > archive, you will waste countless hours hitting wall after wall. I was thinking about starting with markdown or the like, but I *want* to use ConTeXt, and if it should be able to produce ePub, then I want it to succeed. And maybe I can get on Hans’ and Wolfgang’s nerves enough to make it possible ;-) Greetlings, Hraban --- http://www.fiee.net/texnique/ http://wiki.contextgarden.net https://www.cacert.org (I'm an assurer) ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Bugs in XML export (for ePub)
Hi Hraban, I tried to create ePubs using ConTeXt late last year (it was a driving factor for me to switch from LaTeX). In practice, ConTeXt cannot actually produce ePub content of any sufficient complexity that an ePub reader (such as Kindle) can read. I abandoned that development line a while ago. That said, ConTeXt is orders of magnitude easier to work with than LaTeX (for me) and has an architecture that holds a promising future. Since my project exports XML, I began an ePub solution using XSLT and DocBook. The ant4docbook Java application can produce ePub files from DocBook using an ant task, making the API simple to use. The resulting ePub archive can be read by various e-readers. http://ant4docbook.sourceforge.net/ Unless anyone says otherwise (or there have been momentous improvements in this area), I would recommend that you do not use ConTeXt to create ePub files. While technically it can produce an ePub archive, you will waste countless hours hitting wall after wall. ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] Bugs in XML export (for ePub)
Hi again.
I understand you don’t want to export some arbitrary (X)HTML. That’s fine, I
can make my own XSLT.
And I’m glad that \setupexport doesn’t kill hyphenation any more.
But there are serious errors in export, that have nothing to do with „there’s
no usable standard“.
[1] root node
First, the exported XML file lacks a root node!
Just call it or or whatever you like, but it MUST be there,
otherwise it’s no wellformed XML.
If I enable xhtml mode like
\setupbackend[export=export.xml,xhtml=yes]
the exported file stops after a few lines.
If I set xhtml=somefile.xhtml, I get the broken export.xml and the complete
somefile.xhtml, so I guess xhtml=yes causes overwriting the complete file with
the incomplete one.
As far as I remember previous discussions, this incomplete content is caused by
the project structure (using project, product, environment); from single file
it seemed to work, at least at that time, I didn’t check.
Since xhtml mode doesn’t do anything useful anyway, I can just drop the setting.
[2] metadata
The metadata from \setupexport is completely ignored.
The metadata from \settaggedmetadata is exported just fine, but it ends up
within the first block of the first page, if that’s not empty.
e.g. my text starts with \startlines Title etc. \stoplines, then
etc. is exported within .
If I add something like \startparagraph \stopparagraph to contain the metadata,
it disappears. Of course I don’t want to add something visible (then it works
again).
[3] cover picture
The firstpage key of setupexport is supposed to define a cover picture for the
ePub, but it doesn’t do anything, as far as I can tell.
Or is something wrong in:
\setupexport[firstpage={img/cover.jpg}]
?
[4] delimited
If \quotation{} contains more than one paragraph (in my case it’s a quote), the
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
___
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
[NTG-context] bugs in linenote?
Hi there,
I have the following sample:
\definelinenote[A]
\setupnote[A][rule=off, paragraph=yes, split=strict, inbetween=\hskip1.5em]
\setupnotation[A][numbercommand=,alternative=serried,distance=1em,compress=yes,compressseparator=]
\starttext
\startlinenumbering
\dorecurse{500}{body\A{note} }
\stoplinenumbering
\stoptext
I'm afraid it shows to bugs with latest beta.
The first one is that there is no proper separation between body and notes.
The second one is that when no compressseparator is set, there is a
wrong blank space at the beginning of the line.
Can anyone confirm whether they are real bugs or I am doing something wrong?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Bugs with newest beta
On Tue, Dec 7, 2010 at 10:16 AM, Hans Hagen wrote: > On 6-12-2010 5:55, Andreas Harder wrote: >> >> Hello Hans, >> >> I've downloaded the newest beta, but \comments still don't work. Besides >> of that there is a curious indenting problem with delimited text definitions >> (and floats). I will attach some test files. > > comments work here in acrobat 10, so you use another viewer? if so, luigi > might know more I will download the beta to check -- luigi ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Bugs with newest beta
On 6-12-2010 5:55, Andreas Harder wrote: Hello Hans, I've downloaded the newest beta, but \comments still don't work. Besides of that there is a curious indenting problem with delimited text definitions (and floats). I will attach some test files. comments work here in acrobat 10, so you use another viewer? if so, luigi might know more Hans - 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 - ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] Bugs with newest beta
Hello Hans, I've downloaded the newest beta, but \comments still don't work. Besides of that there is a curious indenting problem with delimited text definitions (and floats). I will attach some test files. test-comment.tex Description: Binary data test-delimitedtext-indenting.tex Description: Binary data test-floats-identnext.tex Description: Binary data test-sorting.tex Description: Binary data Thank you in advance Andreas___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Bugs in current beta (streams)
On 13-8-2010 1:59, Salil Sayed wrote:
\usemodule[streams]
\def\StartCouple{\page\SwitchToNormal}
\def\StopCouple {\SwitchToNormal \SynchronizeLeftAndRight \FlushLeftAndRight}
\def\Original {\SwitchToNormal\SynchronizeLeftAndRight\SwitchToLeft}
\def\Translation{\SwitchToRight}
\Original\en
Are you sleeping, brother John?
\Translation\de
Bruder Jakob, schläfst du noch?
I will pick up streams some day soon. But I needs to think of an
interface. Maybe in the meantime you can start collecting user wishes.
\setuplayout[grid=yes] \showgrid
\starttext
\enableoutputstream[en]
Are you sleeping, brother John?\footnote{xxx}
x \footnote{note \recurselevel}\input tufte \par \pushoutputstream
Are you sleeping, brother John?\footnote{xxx} \par \pushoutputstream
x \footnote{note \recurselevel}\input tufte \par \pushoutputstream
Are you sleeping, brother John?\footnote{xxx} \par \pushoutputstream
\enableoutputstream[de]
Bruder Jakob, schläfst du noch?\footnote{yyy}
x \footnote{note \recurselevel}\input ward \par \pushoutputstream
Bruder Jakob, schläfst du noch?\footnote{yyy} \par \pushoutputstream
x \footnote{note \recurselevel}\input ward \par \pushoutputstream
Bruder Jakob, schläfst du noch?\footnote{yyy} \par \pushoutputstream
\disableoutputstream
\input tufte
\synchronizestreams[en,de]
\page \flushoutputstream[en]
\page \flushoutputstream[de]
\stoptext
-
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
-
___
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Bugs in current beta (streams)
Hi,
and how does one do this in mkiv now?
http://wiki.contextgarden.net/Columns#Streams
\usemodule[streams]
\def\StartCouple{\page\SwitchToNormal}
\def\StopCouple {\SwitchToNormal \SynchronizeLeftAndRight \FlushLeftAndRight}
\def\Original {\SwitchToNormal\SynchronizeLeftAndRight\SwitchToLeft}
\def\Translation{\SwitchToRight}
\Original\en
Are you sleeping, brother John?
\Translation\de
Bruder Jakob, schläfst du noch?
i get the same error of course.
thanks,
Salil
From: Hans Hagen
To: mailing list for ConTeXt users
Cc: Andreas Harder
Sent: Wed, August 11, 2010 12:22:02 PM
Subject: Re: [NTG-context] Bugs in current beta
On 10-8-2010 5:36, Andreas Harder wrote:
> Hi all,
>
> for me (OS X 10.6.4)
> mtxrun –script server –auto
> do not work. If I click on a font name I get:
> MTXrun | request from: 127.0.0.1
> MTXrun | requested action:
>/mtx-server-ctx-fonttest.lua?selection=hoeflertextregular
> MTXrun | performing action:
>/mtx-server-ctx-fonttest.lua?selection=hoeflertextregular
> MTXrun | requested file
>'/mtx-server-ctx-fonttest.lua?selection=hoeflertextregular'
> MTXrun | handling error 404: Not Found
>
> Another thing is the streams-module. Here is an example:
>
> \usemodule[streams]
> \definestreamlayer[test][method=overlay]
> \setupbackgrounds[page][background=test]
>
> \starttext \showframe
> \startstreamlayer[test]
>\startcolumns
> \input knuth
>\stopcolumns
> \stopstreamlayer
>
> \setlayer[test][x=5cm,y=10cm]{\placestreamlayer[test]}
> \stoptext
>
> And here the error:
> ! Undefined control sequence.
> l.19 \defineoutputstream[\v!left]
This is not really a bug. Streams in mkii are an experiment and will not be
developed further (is a module after all). In mkiv there will be a different
mechanism. There is some experimental code ... copied from the source:
\enabletrackers[streams.flushing]
\setuplayout[grid=yes] \showgrid
\starttext
\input tufte
\startoutputstream[nl]
Wat doen we hier?
\enableoutputstream[en]
Are you sleeping, brother John?\footnote{xxx}
\dorecurse{4}{x \footnote{note \recurselevel}\input tufte \par
\pushoutputstream}
\enableoutputstream[de]
Bruder Jakob, schläfst du noch?\footnote{yyy}
\dorecurse{4}{x \footnote{note \recurselevel}\input ward \par \pushoutputstream}
\disableoutputstream
\stopoutputstream
Vader Jacob, slaap je nog?\footnote{zzz}
\input tufte
\synchronizestreams[en,de,nl]
\page \flushoutputstream[en] \input knuth
\page \flushoutputstream[de] \input knuth
\page \flushoutputstream[nl] \input knuth
\stoptext
Hans
-
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
-
___
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
___
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Bugs in current beta
Am 11.08.2010 um 11:22 schrieb Hans Hagen:
> On 10-8-2010 5:36, Andreas Harder wrote:
>> Hi all,
>>
>> for me (OS X 10.6.4)
>> mtxrun –script server –auto
>> do not work. If I click on a font name I get:
>> MTXrun | request from: 127.0.0.1
>> MTXrun | requested action:
>> /mtx-server-ctx-fonttest.lua?selection=hoeflertextregular
>> MTXrun | performing action:
>> /mtx-server-ctx-fonttest.lua?selection=hoeflertextregular
>> MTXrun | requested file
>> '/mtx-server-ctx-fonttest.lua?selection=hoeflertextregular'
>> MTXrun | handling error 404: Not Found
>>
>> Another thing is the streams-module. Here is an example:
>>
>> \usemodule[streams]
>> \definestreamlayer[test][method=overlay]
>> \setupbackgrounds[page][background=test]
>>
>> \starttext \showframe
>> \startstreamlayer[test]
>> \startcolumns
>> \input knuth
>> \stopcolumns
>> \stopstreamlayer
>>
>> \setlayer[test][x=5cm,y=10cm]{\placestreamlayer[test]}
>> \stoptext
>>
>> And here the error:
>> ! Undefined control sequence.
>> l.19 \defineoutputstream[\v!left]
>
> This is not really a bug. Streams in mkii are an experiment and will not be
> developed further (is a module after all). In mkiv there will be a different
> mechanism. There is some experimental code ... copied from the source:
>
> \enabletrackers[streams.flushing]
>
> \setuplayout[grid=yes] \showgrid
>
> \starttext
>
> \input tufte
>
> \startoutputstream[nl]
>
> Wat doen we hier?
>
> \enableoutputstream[en]
>
> Are you sleeping, brother John?\footnote{xxx}
>
> \dorecurse{4}{x \footnote{note \recurselevel}\input tufte \par
> \pushoutputstream}
>
> \enableoutputstream[de]
>
> Bruder Jakob, schläfst du noch?\footnote{yyy}
>
> \dorecurse{4}{x \footnote{note \recurselevel}\input ward \par
> \pushoutputstream}
>
> \disableoutputstream
>
> \stopoutputstream
>
> Vader Jacob, slaap je nog?\footnote{zzz}
>
> \input tufte
>
> \synchronizestreams[en,de,nl]
>
> \page \flushoutputstream[en] \input knuth
> \page \flushoutputstream[de] \input knuth
> \page \flushoutputstream[nl] \input knuth
>
> \stoptext
>
> Hans
Hello Hans,
big thanks for the explanation.
Andreas
___
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Bugs in current beta
On 10-8-2010 5:36, Andreas Harder wrote:
Hi all,
for me (OS X 10.6.4)
mtxrun –script server –auto
do not work. If I click on a font name I get:
MTXrun | request from: 127.0.0.1
MTXrun | requested action:
/mtx-server-ctx-fonttest.lua?selection=hoeflertextregular
MTXrun | performing action:
/mtx-server-ctx-fonttest.lua?selection=hoeflertextregular
MTXrun | requested file
'/mtx-server-ctx-fonttest.lua?selection=hoeflertextregular'
MTXrun | handling error 404: Not Found
Another thing is the streams-module. Here is an example:
\usemodule[streams]
\definestreamlayer[test][method=overlay]
\setupbackgrounds[page][background=test]
\starttext \showframe
\startstreamlayer[test]
\startcolumns
\input knuth
\stopcolumns
\stopstreamlayer
\setlayer[test][x=5cm,y=10cm]{\placestreamlayer[test]}
\stoptext
And here the error:
! Undefined control sequence.
l.19 \defineoutputstream[\v!left]
This is not really a bug. Streams in mkii are an experiment and will not
be developed further (is a module after all). In mkiv there will be a
different mechanism. There is some experimental code ... copied from the
source:
\enabletrackers[streams.flushing]
\setuplayout[grid=yes] \showgrid
\starttext
\input tufte
\startoutputstream[nl]
Wat doen we hier?
\enableoutputstream[en]
Are you sleeping, brother John?\footnote{xxx}
\dorecurse{4}{x \footnote{note \recurselevel}\input tufte \par
\pushoutputstream}
\enableoutputstream[de]
Bruder Jakob, schläfst du noch?\footnote{yyy}
\dorecurse{4}{x \footnote{note \recurselevel}\input ward \par
\pushoutputstream}
\disableoutputstream
\stopoutputstream
Vader Jacob, slaap je nog?\footnote{zzz}
\input tufte
\synchronizestreams[en,de,nl]
\page \flushoutputstream[en] \input knuth
\page \flushoutputstream[de] \input knuth
\page \flushoutputstream[nl] \input knuth
\stoptext
Hans
-
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
-
___
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Bugs in current beta
On 10-8-2010 11:44, Andreas Harder wrote:
\starttext
\input tufte
\writetolist[test]{.1}{test}
\input tufte
\stoptext
There shouldn't be a whitespace between the paragraphs, should there?
this is a side effect of the fact that the write becomes a node which is
needed because we need to know where (on what page) the entry is written
we can make an \directwritetolist is needed but that is hardly useful as
it does not carry the right info then
Hans
-
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
-
___
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Bugs in current beta
Am 10.08.2010 um 17:36 schrieb Andreas Harder:
> Hi all,
>
> for me (OS X 10.6.4)
> mtxrun –script server –auto
> do not work. If I click on a font name I get:
> MTXrun | request from: 127.0.0.1
> MTXrun | requested action:
> /mtx-server-ctx-fonttest.lua?selection=hoeflertextregular
> MTXrun | performing action:
> /mtx-server-ctx-fonttest.lua?selection=hoeflertextregular
> MTXrun | requested file
> '/mtx-server-ctx-fonttest.lua?selection=hoeflertextregular'
> MTXrun | handling error 404: Not Found
>
> Another thing is the streams-module. Here is an example:
>
> \usemodule[streams]
> \definestreamlayer[test][method=overlay]
> \setupbackgrounds[page][background=test]
>
> \starttext \showframe
> \startstreamlayer[test]
> \startcolumns
>\input knuth
> \stopcolumns
> \stopstreamlayer
>
> \setlayer[test][x=5cm,y=10cm]{\placestreamlayer[test]}
> \stoptext
>
> And here the error:
> ! Undefined control sequence.
> l.19 \defineoutputstream[\v!left]
One more:
\definelist[test]
\starttext
\input tufte
\writetolist[test]{.1}{test}
\input tufte
\stoptext
There shouldn't be a whitespace between the paragraphs, should there?
Greeting
Andreas
___
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
[NTG-context] Bugs in current beta
Hi all,
for me (OS X 10.6.4)
mtxrun –script server –auto
do not work. If I click on a font name I get:
MTXrun | request from: 127.0.0.1
MTXrun | requested action:
/mtx-server-ctx-fonttest.lua?selection=hoeflertextregular
MTXrun | performing action:
/mtx-server-ctx-fonttest.lua?selection=hoeflertextregular
MTXrun | requested file
'/mtx-server-ctx-fonttest.lua?selection=hoeflertextregular'
MTXrun | handling error 404: Not Found
Another thing is the streams-module. Here is an example:
\usemodule[streams]
\definestreamlayer[test][method=overlay]
\setupbackgrounds[page][background=test]
\starttext \showframe
\startstreamlayer[test]
\startcolumns
\input knuth
\stopcolumns
\stopstreamlayer
\setlayer[test][x=5cm,y=10cm]{\placestreamlayer[test]}
\stoptext
And here the error:
! Undefined control sequence.
l.19 \defineoutputstream[\v!left]
Greeting
Andreas
___
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs (and sectionstopper in MkII)
On 28-5-2010 10:36, Rogutės Sparnuotos wrote:
* Why are the spaces of prefix and suffix of \in{}{}[] trimmed with MkII?
\starttext
\section[one]{One}
\in{( sec. }{ sec. )}[one]
\stoptext
will be fixed in next beta
-
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
-
___
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
[NTG-context] bugs (and sectionstopper in MkII)
Dear list,
I thought I would try switching to MkII (+XeTeX), because MkIV looks bad
tempered [1], but...
* How does one do the equivalent of \setupheads[sectionstopper=.] ?
* Why are the spaces of prefix and suffix of \in{}{}[] trimmed with MkII?
\starttext
\section[one]{One}
\in{( sec. }{ sec. )}[one]
\stoptext
[1] MkIV problems so far:
* \in[] bug after \definereferenceformat[][]:
http://archive.contextgarden.net/message/20100525.013929.6c0016f2.en.html
* Interaction is not working (works fine with MkII):
http://archive.contextgarden.net/message/20100525.002043.bb202b94.en.html
* Footnotes get put in the wrong page (didn't manage to create a minimal
example in the first try).
P.S. Perhaps I should be using the bug tracker for the above, instead of
this mailing list?
--
-- Rogutės Sparnuotos
___
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
[NTG-context] Bugs in defineenumeration
Hi all,
The example below shows: lemma 1 (lemma"title )
Problems:
- the word "lemma" is repeated before the title : (lemma"title
- spaces after the title: "title" )
Example:
%MTXrun | current version: 2009.09.23 10:07
%linux-32, current beta
\defineenumeration[lemma][title=yes]
\starttext
\startlemma{"title"}
\stoplemma
\stoptext
Kind regards,
Bernard
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in math engine?
On Thu, 21 May 2009, Hans Hagen wrote:
Aditya Mahajan wrote:
On Wed, 20 May 2009, Oliver Buerschaper wrote:
Proposed patch:
diff math-def.mkiv.orig math-def.mkiv
100,105c100,105
< \definemathcommand [integers] {\mathblackboard{Z}}
< \definemathcommand [reals] {\mathblackboard{R}}
< \definemathcommand [rationals] {\mathblackboard{Q}}
< \definemathcommand [naturalnumbers]{\mathblackboard{N}}
< \definemathcommand [complexes] {\mathblackboard{C}}
< \definemathcommand [primes]{\mathblackboard{P}}
---
\definemathcommand [integers] {{\mathblackboard Z}}
\definemathcommand [reals] {{\mathblackboard R}}
\definemathcommand [rationals] {{\mathblackboard Q}}
\definemathcommand [naturalnumbers]{{\mathblackboard N}}
\definemathcommand [complexes] {{\mathblackboard C}}
\definemathcommand [primes]{{\mathblackboard P}}
Hans, Aditya, does this make sense?
Yes, I should unlearn amsmath syntax at some stage.
\unexpanded\def\mathscript{\setmathalphabet{script}}
\unexpanded\def\mathfraktur {\setmathalphabet{fraktur}}
\unexpanded\def\mathblackboard{\setmathalphabet{blackboard}}
we can make these into
\unexpanded\def\mathscript#1{{\setmathalphabet{script}#1}}
\unexpanded\def\mathfraktur #1{{\setmathalphabet{fraktur}#1}}
\unexpanded\def\mathblackboard#1{{\setmathalphabet{blackboard}#1}}
\unexpanded\def\mathsr{\setmathalphabet{script}}
\unexpanded\def\mathfr{\setmathalphabet{fraktur}}
\unexpanded\def\mathbb{\setmathalphabet{blackboard}}
does that make sense?
Actually, better will be if we go for full ams compatibility:
Leave \mathscript, \mathfraktur, and \mathblackboard as they are, and
define
\unexpanded\def\mathcal #1{{\setmathalphabet{script}#1}}
\unexpanded\def\mathfrak#1{{\setmathalphabet{fraktur}#1}}
\unexpanded\def\mathbb #1{{\setmathalphabet{blackboard}#1}}
%TODO: Once bold is settled
%unexpanded\def\mathbf #1{{\setmathalphabet{bold}#1}}
% TODO: I need to actually see what exactly these commands to
%unexpanded\def\mathrm #1{{}
%unexpanded\def\mathit #1{{}
% TODO: Probably better will be \mathss since we use ss for sans serif
%unexpanded\def\mathsf #1{{}
% TODO: \mathscr is euler script. We can add this, but need to figure out
% how to deal with two script families in a configurable way
% For LM one can go with either euler script or RSFS (or both?)
%unexpanded\def\mathscr #1{{...}
Aditya
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in math engine?
Aditya Mahajan wrote:
On Wed, 20 May 2009, Oliver Buerschaper wrote:
Proposed patch:
diff math-def.mkiv.orig math-def.mkiv
100,105c100,105
< \definemathcommand [integers] {\mathblackboard{Z}}
< \definemathcommand [reals] {\mathblackboard{R}}
< \definemathcommand [rationals] {\mathblackboard{Q}}
< \definemathcommand [naturalnumbers]{\mathblackboard{N}}
< \definemathcommand [complexes] {\mathblackboard{C}}
< \definemathcommand [primes]{\mathblackboard{P}}
---
\definemathcommand [integers] {{\mathblackboard Z}}
\definemathcommand [reals] {{\mathblackboard R}}
\definemathcommand [rationals] {{\mathblackboard Q}}
\definemathcommand [naturalnumbers]{{\mathblackboard N}}
\definemathcommand [complexes] {{\mathblackboard C}}
\definemathcommand [primes]{{\mathblackboard P}}
Hans, Aditya, does this make sense?
Yes, I should unlearn amsmath syntax at some stage.
\unexpanded\def\mathscript{\setmathalphabet{script}}
\unexpanded\def\mathfraktur {\setmathalphabet{fraktur}}
\unexpanded\def\mathblackboard{\setmathalphabet{blackboard}}
we can make these into
\unexpanded\def\mathscript#1{{\setmathalphabet{script}#1}}
\unexpanded\def\mathfraktur #1{{\setmathalphabet{fraktur}#1}}
\unexpanded\def\mathblackboard#1{{\setmathalphabet{blackboard}#1}}
\unexpanded\def\mathsr{\setmathalphabet{script}}
\unexpanded\def\mathfr{\setmathalphabet{fraktur}}
\unexpanded\def\mathbb{\setmathalphabet{blackboard}}
does that make sense?
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in math engine?
On Wed, 20 May 2009, Oliver Buerschaper wrote:
Proposed patch:
diff math-def.mkiv.orig math-def.mkiv
100,105c100,105
< \definemathcommand [integers] {\mathblackboard{Z}}
< \definemathcommand [reals] {\mathblackboard{R}}
< \definemathcommand [rationals] {\mathblackboard{Q}}
< \definemathcommand [naturalnumbers]{\mathblackboard{N}}
< \definemathcommand [complexes] {\mathblackboard{C}}
< \definemathcommand [primes]{\mathblackboard{P}}
---
\definemathcommand [integers] {{\mathblackboard Z}}
\definemathcommand [reals] {{\mathblackboard R}}
\definemathcommand [rationals] {{\mathblackboard Q}}
\definemathcommand [naturalnumbers]{{\mathblackboard N}}
\definemathcommand [complexes] {{\mathblackboard C}}
\definemathcommand [primes]{{\mathblackboard P}}
Hans, Aditya, does this make sense?
Yes, I should unlearn amsmath syntax at some stage.
Aditya
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in math engine?
1. The symbols for number sets in Cambria Math aren't taken from
the double-struck variant.
Hans, please apply the following patch to math-def.mkiv
diff --git a/math-def.mkiv b/math-def.mkiv
index 31db66e..30beb5c 100644
--- a/math-def.mkiv
+++ b/math-def.mkiv
@@ -97,12 +97,12 @@
\definemathcommand [tanh][nolop] {\mfunction{tanh}}
\definemathcommand [tan] [nolop] {\mfunction{tan}}
-\definemathcommand [integers]{\mfunction{Z}}
-\definemathcommand [reals] {\mfunction{R}}
-\definemathcommand [rationals] {\mfunction{Q}}
-\definemathcommand [naturalnumbers] {\mfunction{N}}
-\definemathcommand [complexes] {\mfunction{C}}
-\definemathcommand [primes] {\mfunction{P}}
+\definemathcommand [integers]{\mathblackboard{Z}}
+\definemathcommand [reals] {\mathblackboard{R}}
+\definemathcommand [rationals] {\mathblackboard{Q}}
+\definemathcommand [naturalnumbers] {\mathblackboard{N}}
+\definemathcommand [complexes] {\mathblackboard{C}}
+\definemathcommand [primes] {\mathblackboard{P}}
% using attributes
Many thanks! Although this doesn't quite solve the bug yet, now I know
where to look ...
Test case:
---
\starttext
\math{\primes P},
\math{\naturalnumbers N},
\math{\integers Z},
\math{\rationals Q},
\math{\reals R},
\math{\complexes C}
\stoptext
---
Proposed patch:
diff math-def.mkiv.orig math-def.mkiv
100,105c100,105
< \definemathcommand [integers] {\mathblackboard{Z}}
< \definemathcommand [reals] {\mathblackboard{R}}
< \definemathcommand [rationals] {\mathblackboard{Q}}
< \definemathcommand [naturalnumbers]{\mathblackboard{N}}
< \definemathcommand [complexes] {\mathblackboard{C}}
< \definemathcommand [primes]{\mathblackboard{P}}
---
> \definemathcommand [integers] {{\mathblackboard Z}}
> \definemathcommand [reals] {{\mathblackboard R}}
> \definemathcommand [rationals] {{\mathblackboard Q}}
> \definemathcommand [naturalnumbers]{{\mathblackboard N}}
> \definemathcommand [complexes] {{\mathblackboard C}}
> \definemathcommand [primes]{{\mathblackboard P}}
Hans, Aditya, does this make sense?
Oliver
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in math engine?
Hi Aditya (and others), Aditya Mahajan writes: > How about two branches: one for all officical stable releases, and one > for all beta releases (from Hans's ftp server, synced periodically). I > believe that alpha releases are rare enough to be ignored[1]. Unless > disk space is a problem, I do not see a reason for not storing all > betas. Official betas can be tagged with the release date and time. OK, thats what I had in mind. Perhaps Mojca can tell me where all the files are on the server, if not I will find out by myself. I promise I will give it a try next week sunday, until then I don't have internet access (vacation :) and my battery from my notebook is almost empty because I've forgot my power supply at home :-) Patrick -- ConTeXt wiki and more: http://contextgarden.net ___ 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://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] bugs in math engine?
On Fri, 15 May 2009, Patrick Gundlach wrote: Hi, We (Patrick, Mojca, and I) have discussed hosting a git repo on the garden. I do not think it was implemented. I am Ccing Patrick and Mojca, and maybe they can shed more light on the status of git server on the garden. It is not implemented (yet). If someone can give me a strategy (pseudo code welcome) which alpha/beta/stable to put into the repository this should be quite easy to do. How about two branches: one for all officical stable releases, and one for all beta releases (from Hans's ftp server, synced periodically). I believe that alpha releases are rare enough to be ignored[1]. Unless disk space is a problem, I do not see a reason for not storing all betas. Official betas can be tagged with the release date and time. Aditya [1]: Actually, at least for this year, there have been more alpha releases than stable releases :-) ___ 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://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] bugs in math engine?
Hi, > We (Patrick, Mojca, and I) have discussed hosting a git repo on the > garden. I do not think it was implemented. I am Ccing Patrick and > Mojca, and maybe they can shed more light on the status of git server > on the garden. It is not implemented (yet). If someone can give me a strategy (pseudo code welcome) which alpha/beta/stable to put into the repository this should be quite easy to do. Patrick -- ConTeXt wiki and more: http://contextgarden.net ___ 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://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] bugs in math engine?
Aditya Mahajan wrote: Hans, please apply the following patch to math-def.mkiv ok - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] bugs in math engine?
On Fri, 15 May 2009, Oliver Buerschaper wrote:
Dear list,
the following are probably bugs in the new math engine as of yesterday's beta
(2009.05.14 16:44):
1. The symbols for number sets in Cambria Math aren't taken from the
double-struck variant.
Hans, please apply the following patch to math-def.mkiv
diff --git a/math-def.mkiv b/math-def.mkiv
index 31db66e..30beb5c 100644
--- a/math-def.mkiv
+++ b/math-def.mkiv
@@ -97,12 +97,12 @@
\definemathcommand [tanh][nolop] {\mfunction{tanh}}
\definemathcommand [tan] [nolop] {\mfunction{tan}}
-\definemathcommand [integers]{\mfunction{Z}}
-\definemathcommand [reals] {\mfunction{R}}
-\definemathcommand [rationals] {\mfunction{Q}}
-\definemathcommand [naturalnumbers] {\mfunction{N}}
-\definemathcommand [complexes] {\mfunction{C}}
-\definemathcommand [primes] {\mfunction{P}}
+\definemathcommand [integers]{\mathblackboard{Z}}
+\definemathcommand [reals] {\mathblackboard{R}}
+\definemathcommand [rationals] {\mathblackboard{Q}}
+\definemathcommand [naturalnumbers] {\mathblackboard{N}}
+\definemathcommand [complexes] {\mathblackboard{C}}
+\definemathcommand [primes] {\mathblackboard{P}}
% using attributes
2. Vector arrows look somewhat strange in Cambria Math ... is this perhaps
due to the font itself?
---
\usetypescript[cambria]
\setupbodyfont[cambria]
\starttext
The arrows should neither extend over the right bracket nor into the primes:
\startformula{}
[\alpha(\vec{k})\alpha(\vec{k}'),\alpha^\dagger(\vec{k}'')]
\stopformula
\stoptext
---
I don't know whether the font or luatex/context is at fault.
3. The command \implies is undefined (see previous posting).
Hans, can we add this somewhere?
%D This is a temporary hack until we figure out how to do this correctly.
\unexpanded\def\implies{\mathrel{\;\Longrightarrow\;}}
\unexpanded\def\impliedby {\mathrel{\;\Longleftarrow\;}}
\unexpanded\def\And{\mathrel{\;\internalAnd\;}}
\unexpanded\def\iff{\;\Longleftrightarrow\;}
Aditya
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
[NTG-context] bugs in math engine?
Dear list,
the following are probably bugs in the new math engine as of
yesterday's beta (2009.05.14 16:44):
1. The symbols for number sets in Cambria Math aren't taken from the
double-struck variant.
---
\usetypescript[cambria]
\setupbodyfont[cambria]
\starttext
\math{\naturalnumbers}, \math{\integers}, \math{\rationals},
\math{\reals}, \math{\complexes}, \math{\primes}
\stoptext
---
2. Vector arrows look somewhat strange in Cambria Math ... is this
perhaps due to the font itself?
---
\usetypescript[cambria]
\setupbodyfont[cambria]
\starttext
The arrows should neither extend over the right bracket nor into the
primes:
\startformula{}
[\alpha(\vec{k})\alpha(\vec{k}'),\alpha^\dagger(\vec{k}'')]
\stopformula
\stoptext
---
3. The command \implies is undefined (see previous posting).
---
\starttext
\startformula
A\implies B
\stopformula
\stoptext
---
Oliver
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in beta (footnotes)
Wolfgang Schuster wrote:
Am 12.05.2009 um 19:07 schrieb Henning Hraban Ramm:
Only footnotes in section titles don't work - should they?
[...]
I couldn't construct a minimal failing example - any hints?
No solution but here is a test file:
\setupinteraction[state=start]
\starttext
\section{foo\footnote{bar}}
\stoptext
repaired
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in beta (footnotes)
Am 12.05.2009 um 19:07 schrieb Henning Hraban Ramm:
Only footnotes in section titles don't work - should they?
[...]
I couldn't construct a minimal failing example - any hints?
No solution but here is a test file:
\setupinteraction[state=start]
\starttext
\section{foo\footnote{bar}}
\stoptext
Wolfgang
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in beta (footnotes)
Am 2009-05-10 um 18:44 schrieb Henning Hraban Ramm:
But it doesn't work, it's always "bytext", i.e. numbering runs
through from start to end.
And the marks still don't show up in the text!
(Latest minimals beta, 2009-05-10 18.30 MESZ)
I find this is fixed now (Beta 2009.05.12 17:37). Great, thanks!
Only footnotes in section titles don't work - should they?
\chapter{My chapter\footnote{Note: might be also a section or
subsection}}
Shows the note mark, but eats the footnote text.
I can work around that like so:
\footnotetext[chap]{blah}
\subsection{My chapter\note[chap]}
It works in a minimal example, but in my actual project I get this
error:
! Argument of \dostructurecomponent has an extra }.
\par
}
\dostructurecomponent ...ctureparameter \c!title }
}}\endgroup \fi \fi
\fi \g...
\doregisterstructurehead ... \c!command =, #2][#3]
\reportcurrentstructure
\dohandlestructurehead ...ructurehead {#1}{#2}{#3}
\let
\getstructureheadsync...
l.76 \subsection{The European Dream\note[dream]}
I couldn't construct a minimal failing example - any hints?
Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in beta (footnotes)
Am 2009-05-07 um 20:04 schrieb Hans Hagen:
Henning Hraban Ramm wrote:
Thank you for the hints; I still don't understand what's the
replacement for "way=bypage".
no replacement, just the same -)
But it doesn't work, it's always "bytext", i.e. numbering runs through
from start to end.
And the marks still don't show up in the text!
(Latest minimals beta, 2009-05-10 18.30 MESZ)
This is my test file:
\setuphead[chapter][page=no]
\setupheadertexts[text][chapter][pagenumber]
\setupheader[text][state=start]
\setupregister[index]%
[n=2, balance=no, align=yes, alternative=A, indicator=yes,
pagestyle=normal, location=right, style=type]
\setupnote[footnote][way=bypage] % DOES NOTHING
\starttext
\dorecurse{20}{%
\expanded{\chapter{My chapter \recurselevel}}
\expanded{\index{Index entry \recurselevel}}
\input zapf\expanded{\footnote{Zapf \recurselevel}}
\input tufte\expanded{\footnote{Tufte \recurselevel}}
}
\completeindex % OK
\completecontent[criterium=all] % OK
\stoptext
Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in beta
Alan BRASLAU wrote: On Thursday 07 May 2009 23:17:38 Hans Hagen wrote: Alan BRASLAU wrote: I still get a major sectioning bug using the new beta mkiv 1. minimals from the garden 2. beta from http://pragma-ade.nl/context/beta/cont-tmf.zip Am I alone in seeing this? i'm still strugling with defaults (it's not so much a matter of not working but more of how to set up the defaults with reasonable inheritance) so it will take a while before things stabelize i uploaded a beta with a (temp) fix OK, it sort-of works. I get: 1 first section 1.1 first subsection of first section 1.1.1 subsubsection 1.2 second subsection of first section 2 second section 2.1 first subsection of second section 2.2 second subsection of second section But now I am being difficult: \setupsection[section-3][bodypartconversion=Character] \setupsection[section-4][previousnumber=no,bodypartconversion=number] \setupsection[section-5][previousnumber=no,bodypartconversion=character] see top of strc-def.tex ... you need to define sets no documentation yet Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] bugs in beta
On Thursday 07 May 2009 23:17:38 Hans Hagen wrote:
> Alan BRASLAU wrote:
> > I still get a major sectioning bug using the new beta mkiv
> > 1. minimals from the garden
> > 2. beta from http://pragma-ade.nl/context/beta/cont-tmf.zip
> >
> > Am I alone in seeing this?
>
> i'm still strugling with defaults (it's not so much a matter of not
> working but more of how to set up the defaults with reasonable
> inheritance) so it will take a while before things stabelize
>
> i uploaded a beta with a (temp) fix
OK, it sort-of works. I get:
1 first section
1.1 first subsection of first section
1.1.1 subsubsection
1.2 second subsection of first section
2 second section
2.1 first subsection of second section
2.2 second subsection of second section
But now I am being difficult:
\setupsection[section-3][bodypartconversion=Character]
\setupsection[section-4][previousnumber=no,bodypartconversion=number]
\setupsection[section-5][previousnumber=no,bodypartconversion=character]
\starttext
\section{first section}
\subsection{first subsection of first section}
\subsubsection{subsubsection}
\subsection{second subsection of first section}
\section{second section}
\subsection{first subsection of second section}
\subsection{second subsection of second section}
\stoptext
which yields (in mkii):
A first section
1 first subsection of first section
a subsubsection
2 second subsection of first section
B second section
1 first subsection of second section
2 second subsection of second section
but not in mkiv...
Alan
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in beta
On Fri, May 8, 2009 at 3:22 PM, Hans Hagen wrote: > Yanrui Li wrote: >> >> On Fri, May 8, 2009 at 5:17 AM, Hans Hagen wrote: >>> >>> Alan BRASLAU wrote: I still get a major sectioning bug using the new beta mkiv 1. minimals from the garden 2. beta from http://pragma-ade.nl/context/beta/cont-tmf.zip Am I alone in seeing this? >>> >>> i'm still strugling with defaults (it's not so much a matter of not >>> working >>> but more of how to set up the defaults with reasonable inheritance) so it >>> will take a while before things stabelize >>> >>> i uploaded a beta with a (temp) fix >>> >> >> I failed to update the latest beta and got the following error message: > > ok, will be fixed in 10 min > Recently I have found some environment variables in setuptex script are commented out sometimes, such as TEXMFLOCAL, TEXMFCONTEXT and so on. Is this be done deliberately? -- Best wishes, Li Yanrui ___ 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://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] bugs in beta
Yanrui Li wrote: On Fri, May 8, 2009 at 5:17 AM, Hans Hagen wrote: Alan BRASLAU wrote: I still get a major sectioning bug using the new beta mkiv 1. minimals from the garden 2. beta from http://pragma-ade.nl/context/beta/cont-tmf.zip Am I alone in seeing this? i'm still strugling with defaults (it's not so much a matter of not working but more of how to set up the defaults with reasonable inheritance) so it will take a while before things stabelize i uploaded a beta with a (temp) fix I failed to update the latest beta and got the following error message: ok, will be fixed in 10 min Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] bugs in beta
On Fri, May 8, 2009 at 7:06 AM, Yanrui Li wrote:
> On Fri, May 8, 2009 at 5:17 AM, Hans Hagen wrote:
>> Alan BRASLAU wrote:
>>>
>>> I still get a major sectioning bug using the new beta mkiv
>>> 1. minimals from the garden
>>> 2. beta from http://pragma-ade.nl/context/beta/cont-tmf.zip
>>>
>>> Am I alone in seeing this?
>>
>> i'm still strugling with defaults (it's not so much a matter of not working
>> but more of how to set up the defaults with reasonable inheritance) so it
>> will take a while before things stabelize
>>
>> i uploaded a beta with a (temp) fix
>>
>
> I failed to update the latest beta and got the following error message:
>
> ... ...
> ) (/opt/context/tex/texmf-context/tex/context/base/core-fil.tex
> loading : ConTeXt Core Macros / File Support
> )
> ! I can't find file `core-con.tex'.
>
> \relax
> l.103 \loadcorefile{core-con.tex}
>
> (Press Enter to retry, or Control-D to exit)
> Please type another input file name:
> ... ...
>
Inputing "core-con.mkii" can resolve the problem.
--
Best wishes,
Li Yanrui
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in beta
On Fri, May 8, 2009 at 5:17 AM, Hans Hagen wrote:
> Alan BRASLAU wrote:
>>
>> I still get a major sectioning bug using the new beta mkiv
>> 1. minimals from the garden
>> 2. beta from http://pragma-ade.nl/context/beta/cont-tmf.zip
>>
>> Am I alone in seeing this?
>
> i'm still strugling with defaults (it's not so much a matter of not working
> but more of how to set up the defaults with reasonable inheritance) so it
> will take a while before things stabelize
>
> i uploaded a beta with a (temp) fix
>
I failed to update the latest beta and got the following error message:
... ...
) (/opt/context/tex/texmf-context/tex/context/base/core-fil.tex
loading : ConTeXt Core Macros / File Support
)
! I can't find file `core-con.tex'.
\relax
l.103 \loadcorefile{core-con.tex}
(Press Enter to retry, or Control-D to exit)
Please type another input file name:
... ...
--
Best wishes,
Li Yanrui
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in beta
Alan BRASLAU wrote: I still get a major sectioning bug using the new beta mkiv 1. minimals from the garden 2. beta from http://pragma-ade.nl/context/beta/cont-tmf.zip Am I alone in seeing this? i'm still strugling with defaults (it's not so much a matter of not working but more of how to set up the defaults with reasonable inheritance) so it will take a while before things stabelize i uploaded a beta with a (temp) fix - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] bugs in beta
I still get a major sectioning bug using the new beta mkiv
1. minimals from the garden
2. beta from http://pragma-ade.nl/context/beta/cont-tmf.zip
Am I alone in seeing this?
Thanks.
Alan
Minimal example:
(works as expected under mkii)
\starttext
\section{first section}
\subsection{first subsection of first section}
\subsubsection{subsubsection}
\subsection{second subsection of first section}
\section{second section}
\subsection{first subsection of second section}
\subsection{second subsection of second section}
\stoptext
gives
1 first section
1 first subsection of first section
1 subsubsection
1 second subsection of first section
2 second section
2 first subsection of second section
2 second subsection of second section
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in beta
Henning Hraban Ramm wrote: Thank you for the hints; I still don't understand what's the replacement for "way=bypage". no replacement, just the same -) - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] bugs in beta
Am 2009-05-07 um 18:34 schrieb Hans Hagen:
5. Footnotes
- footnote marks are missing in the text
- footnote numbering is strange (e.g. jumps from 3 to 24 and from
29 to 210 in my project - that was 2.4, 2.9 and 2.10 before, I
guess, but these aren't even the right part or chapter numbers; in
my minimal example the numbers are "chapternumber footnotenumber")
Can I motivate you (Hans etc.) to fix this anyhow? Swiss Chocolate?
Money? Prayers?
let me think about that ...
anyhow, a new beta with some footnote fixes ... keep in mind that
we're moving towards more control and some settings have changed:
\setupnote[footnote][numberconversion=set 1]
there are a lot of new keys (see top of strc-ini.tex) depending on
what number is used; the settings travel with the number
also, footnotes are now enumerations and can have subnotes which is
handy for users like Idris and Thomas who normally have more notes
than text in their documents so any additional structure helps
one: \footnote{Note One}
sub one: \subfootnote{Sub Note One}
sub two: \subfootnote{Sub Note Two}
sub sub one: \subsubfootnote{Sub Sub Note One}
but it needs documentation
Thank you for the hints; I still don't understand what's the
replacement for "way=bypage".
Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in beta
Henning Hraban Ramm wrote:
Am 2009-05-06 um 21:58 schrieb Thomas A. Schmitz:
Hi Hans,
so you're back from Bachotek and ready to attack the bugs? The beta
you uploaded today is still badly broken. Most of this has been
reported before; I just collect it here for your convenience :-)
Sorry Thomas, but you forgot one:
5. Footnotes
- footnote marks are missing in the text
- footnote numbering is strange (e.g. jumps from 3 to 24 and from 29 to
210 in my project - that was 2.4, 2.9 and 2.10 before, I guess, but
these aren't even the right part or chapter numbers; in my minimal
example the numbers are "chapternumber footnotenumber")
Can I motivate you (Hans etc.) to fix this anyhow? Swiss Chocolate?
Money? Prayers?
let me think about that ...
anyhow, a new beta with some footnote fixes ... keep in mind that we're
moving towards more control and some settings have changed:
\setupnote[footnote][numberconversion=set 1]
there are a lot of new keys (see top of strc-ini.tex) depending on what
number is used; the settings travel with the number
also, footnotes are now enumerations and can have subnotes which is
handy for users like Idris and Thomas who normally have more notes than
text in their documents so any additional structure helps
one: \footnote{Note One}
sub one: \subfootnote{Sub Note One}
sub two: \subfootnote{Sub Note Two}
sub sub one: \subsubfootnote{Sub Sub Note One}
but it needs documentation
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in beta
Am 07.05.2009 um 16:32 schrieb Henning Hraban Ramm: Unfortunately it is critical, where to put \expanded, and I tend to take always the wrong place... Therefore the minimal example is fixed; header and toc handlings seems right, as I presumed. http://randomdeterminism.wordpress.com/2009/03/05/tex-programming-the-past-the-present-and-the-future/ Wolfgang ___ 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://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] bugs in beta
Am 2009-05-07 um 15:28 schrieb Wolfgang Schuster:
My minimal example shows some more problems, but these are
probably because \recurselevel isn't expanded at the right time...
\dorecurse{1000}{Use \type{\expanded{...}}\par}
Use \expanded{...}
Use \expanded{...}
...
Hä? Was soll das?
I don't want to \type some command, but just to expand
\recurselevel before processing.
Brett + Kopf = ?
\dorecurse{20}{%
\expanded{\chapter{My chapter \recurselevel}}
\expanded{\index{Index entry \recurselevel}}
\input zapf\expanded{\footnote{Zapf \recurselevel}}
\input tufte\expanded{\footnote{Tufte \recurselevel}}
}
Ja, Blockhaus vorm Kopf, sorry.
Unfortunately it is critical, where to put \expanded, and I tend to
take always the wrong place...
Therefore the minimal example is fixed; header and toc handlings seems
right, as I presumed.
Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in beta
On Thursday 07 May 2009 15:56:19 Wolfgang Schuster wrote: > Am 07.05.2009 um 15:51 schrieb Alan BRASLAU: > > On Thursday 07 May 2009 15:27:35 Hans Hagen wrote: > >> when i mention beta, i mean the one on the website ... the minimals > >> lag > >> upto an hour behind > > > > Please, I am confused: which one on which website? > > > > http://www.pragma-ade.nl/download-1.htm > > contains files from october 2008 > > http://pragma-ade.nl/download-2.htm ;-) > > Wolfgang Yes, I figured out http://pragma-ade.nl/context/beta/cont-tmf.zip However, I have been unable to test ANY recent version as the installations on my test machine are hopelessly broken. In producing real work using context, I have reverted to an ancient (several week-old) installation on a backup (stable) machine. Maybe I should just wait another hour until the minimals on the garden get updated before asking any more questions ;-) ___ 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://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] bugs in beta
Am 07.05.2009 um 15:51 schrieb Alan BRASLAU: On Thursday 07 May 2009 15:27:35 Hans Hagen wrote: when i mention beta, i mean the one on the website ... the minimals lag upto an hour behind Please, I am confused: which one on which website? http://www.pragma-ade.nl/download-1.htm contains files from october 2008 http://pragma-ade.nl/download-2.htm ;-) Wolfgang ___ 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://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] bugs in beta
On Thursday 07 May 2009 15:27:35 Hans Hagen wrote: > when i mention beta, i mean the one on the website ... the minimals lag > upto an hour behind Please, I am confused: which one on which website? http://www.pragma-ade.nl/download-1.htm contains files from october 2008 rsync://contextgarden.net/minimals/setup/first-setup.sh "lag up to an hour behind" Thanks. ___ 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://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] bugs in beta
Am 07.05.2009 um 15:08 schrieb Henning Hraban Ramm:
Am 2009-05-07 um 13:38 schrieb Wolfgang Schuster:
My minimal example shows some more problems, but these are
probably because \recurselevel isn't expanded at the right time...
\dorecurse{1000}{Use \type{\expanded{...}}\par}
Use \expanded{...}
Use \expanded{...}
...
Hä? Was soll das?
I don't want to \type some command, but just to expand \recurselevel
before processing.
Brett + Kopf = ?
\dorecurse{20}{%
\expanded{\chapter{My chapter \recurselevel}}
\expanded{\index{Index entry \recurselevel}}
\input zapf\expanded{\footnote{Zapf \recurselevel}}
\input tufte\expanded{\footnote{Tufte \recurselevel}}
}
Wolfgang
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in beta
Henning Hraban Ramm wrote: Am 2009-05-07 um 14:44 schrieb Hans Hagen: Henning Hraban Ramm wrote: Am 2009-05-07 um 10:41 schrieb Thomas A. Schmitz: Sorry Thomas, but you forgot one: We'd be incredibly lucky if there's only one that I missed :-) Well, ATM I've some problems with headers and ToC, but I guess that's only in my setup; couldn't reproduce it in my minimal example. BTW (1) font problems: can you test the mkiv beta? the problem has to do with merging fonts in basemode and such so we have some safeguards for it now Just ran "first-setup" again; the problem with small caps stays; I didn't experience other font problems. when i mention beta, i mean the one on the website ... the minimals lag upto an hour behind - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] bugs in beta
Am 2009-05-07 um 14:44 schrieb Hans Hagen: Henning Hraban Ramm wrote: Am 2009-05-07 um 10:41 schrieb Thomas A. Schmitz: Sorry Thomas, but you forgot one: We'd be incredibly lucky if there's only one that I missed :-) Well, ATM I've some problems with headers and ToC, but I guess that's only in my setup; couldn't reproduce it in my minimal example. BTW (1) font problems: can you test the mkiv beta? the problem has to do with merging fonts in basemode and such so we have some safeguards for it now Just ran "first-setup" again; the problem with small caps stays; I didn't experience other font problems. Greetlings from Lake Constance! Hraban --- http://www.fiee.net/texnique/ http://wiki.contextgarden.net https://www.cacert.org (I'm an assurer) ___ 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://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] bugs in beta
Am 2009-05-07 um 13:38 schrieb Wolfgang Schuster:
My minimal example shows some more problems, but these are probably
because \recurselevel isn't expanded at the right time...
\dorecurse{1000}{Use \type{\expanded{...}}\par}
Hä? Was soll das?
I don't want to \type some command, but just to expand \recurselevel
before processing.
Of course I tried \expanded before, but I only get an error:
! Argument of \rawprocesscommalist has an extra }.
\par
}
\@@ddfootnotetitle ...{\expanded {\recurselevel }}
\par
\doif #1#2->\edef \!!stringa {#1
}\edef \!!stringb {#2}\ifx \!!stringa
\!!str...
\dododescriptioncomponent ...er \c!title }\v!none
{\global
\nodescriptioncap...
\@@notemakedescription ... ={#3},\c!bookmark =,][]
\edef
\currentnotenumber {...
...
l.17 }
Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in beta
Henning Hraban Ramm wrote: Am 2009-05-07 um 10:41 schrieb Thomas A. Schmitz: Sorry Thomas, but you forgot one: We'd be incredibly lucky if there's only one that I missed :-) Well, ATM I've some problems with headers and ToC, but I guess that's only in my setup; couldn't reproduce it in my minimal example. BTW (1) font problems: can you test the mkiv beta? the problem has to do with merging fonts in basemode and such so we have some safeguards for it now Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] bugs in beta
Am 07.05.2009 um 10:31 schrieb Henning Hraban Ramm:
My minimal example shows some more problems, but these are probably
because \recurselevel isn't expanded at the right time...
\dorecurse{1000}{Use \type{\expanded{...}}\par}
Wolfgang
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in beta
Henning Hraban Ramm wrote: BTW (1) font problems: I'm using TeX Gyre and some Type1 fonts with MkIV nearly without problems; didn't need to copy any files like you. looks like an engine problem; we'll look into it - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] bugs in beta
Am 2009-05-07 um 10:41 schrieb Thomas A. Schmitz:
Sorry Thomas, but you forgot one:
We'd be incredibly lucky if there's only one that I missed :-)
Well, ATM I've some problems with headers and ToC, but I guess that's
only in my setup; couldn't reproduce it in my minimal example.
BTW (1) font problems:
I'm using TeX Gyre and some Type1 fonts with MkIV nearly without
problems; didn't need to copy any files like you.
Only \sc with TeX Gyre serif fonts (Pagella, Schola, Termes, Bonum)
gives really ugly spacing - maybe a problem of the fonts' internal
kerning. Sans serif fonts (Heros, Adventor) look ok in small caps.
Strangely this wrong spacing sometimes "bleeds" into the whole non-
smallcaps text, but I couldn't reproduce that in a minimal example.
Additionally, "cursor" doesn't work, only "courier".
\starttypescript[gyr-mix]
\definetypeface [gyr-mix] [rm] [serif] [schola] % pagella, bonum,
termes
\definetypeface [gyr-mix] [ss][sans] [heros] % adventor
\definetypeface [gyr-mix] [tt][mono] [cursor] % courier!
\stoptypescript
\usetypescript [gyr-mix]
\setupbodyfont [gyr-mix,rm,18pt]
\starttext
{\ss\sc Kerning Problem With Small Caps}
{\sc Kerning Problem With Small Caps}
{\tt\sc Kerning Problem With Small Caps}
\input tufte
\stoptext
Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in beta
On May 7, 2009, at 10:31 AM, Henning Hraban Ramm wrote: Am 2009-05-06 um 21:58 schrieb Thomas A. Schmitz: Hi Hans, so you're back from Bachotek and ready to attack the bugs? The beta you uploaded today is still badly broken. Most of this has been reported before; I just collect it here for your convenience :-) Sorry Thomas, but you forgot one: We'd be incredibly lucky if there's only one that I missed :-) Thomas ___ 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://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] bugs in beta
Am 2009-05-06 um 21:58 schrieb Thomas A. Schmitz:
Hi Hans,
so you're back from Bachotek and ready to attack the bugs? The beta
you uploaded today is still badly broken. Most of this has been
reported before; I just collect it here for your convenience :-)
Sorry Thomas, but you forgot one:
5. Footnotes
- footnote marks are missing in the text
- footnote numbering is strange (e.g. jumps from 3 to 24 and from 29
to 210 in my project - that was 2.4, 2.9 and 2.10 before, I guess, but
these aren't even the right part or chapter numbers; in my minimal
example the numbers are "chapternumber footnotenumber")
Can I motivate you (Hans etc.) to fix this anyhow? Swiss Chocolate?
Money? Prayers?
My minimal example shows some more problems, but these are probably
because \recurselevel isn't expanded at the right time...
\setuphead[chapter][page=no]
\setupheadertexts[text][chapter][pagenumber]
\setupheader[text][state=start]
\setupregister[index]%
[n=2, balance=no, align=yes, alternative=A, indicator=yes,
pagestyle=normal, location=right, style=type]
\starttext
\dorecurse{20}{%
\chapter{My chapter \recurselevel}
\index{Index entry \recurselevel}
\input zapf\footnote{Zapf \recurselevel}
\input tufte\footnote{Tufte \recurselevel}
}
\completeindex
\completecontent[criterium=all]
\stoptext
Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in beta
Am 06.05.2009 um 22:25 schrieb Thomas A. Schmitz:
On May 6, 2009, at 10:12 PM, Wolfgang Schuster wrote:
2. The new structure code doesn't expand xmlflushes in sections.
Here's an example:
\setuphead[section][expansion=yes]
Thank you, that works! This is new, right?
Yes it is.
Another way is to use \expanded (without 'expansion=yes'), e.g.
\startxmlsetups xml:title
\expanded{\section{\xmlflush{#1}}}
\stopxmlsetups
Wolfgang
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] bugs in beta
On May 6, 2009, at 10:12 PM, Wolfgang Schuster wrote: 2. The new structure code doesn't expand xmlflushes in sections. Here's an example: \setuphead[section][expansion=yes] Wolfgang Thank you, that works! This is new, right? Thomas ___ 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://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] bugs in beta
Am 06.05.2009 um 21:58 schrieb Thomas A. Schmitz: 2. The new structure code doesn't expand xmlflushes in sections. Here's an example: \setuphead[section][expansion=yes] Wolfgang ___ 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://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] bugs in beta
Hi Hans,
so you're back from Bachotek and ready to attack the bugs? The beta
you uploaded today is still badly broken. Most of this has been
reported before; I just collect it here for your convenience :-)
1. The most urgent bug: The beta still fails to generate the files
luatex-cache/context/XXX/names.tma
and names.tmc. Which means only Latin Modern works, all other fonts
fail. I get this both on OS X and linux; I have to use an older
version to produce these files and copy them over. Once that is done,
fonts work normally.
2. The new structure code doesn't expand xmlflushes in sections.
Here's an example:
\startbuffer[xmltest]
First section
Hello world
\stopbuffer
\startxmlsetups xml:mysetups
\xmlsetsetup{\xmldocument}{section|content|title}{xml:*}
\stopxmlsetups
\xmlregistersetup{xml:mysetups}
\startxmlsetups xml:section
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:content
\xmlflush{#1} \par
\stopxmlsetups
\startxmlsetups xml:title
\section{\xmlflush{#1}}
\stopxmlsetups
\starttext
\xmlprocessbuffer{main}{xmltest}{}
\stoptext
3. Section numbers in markings are duplicated. Example:
\setuphead
[section]
[page=yes,
style=normal]
\setupuserpagenumber[state=start,way=bysection]
\setupfootertexts[{\getmarking[sectionnumber]} – \userpagenumber]
\starttext
\section{One}
\input tufte
\page
\input linden
\section{Two}
\input bryson
\page
\input davis
\stoptext
4. The latest beta still does not work with the bib module (and yes, I
am using the latest version t-bib-2009.04.27.zip). Here is a minimal
file:
\usemodule[bib]
\startpublication[k=kasselpoeticedition,t=book,
a={{Aristoteles}},y=1965,
n=1046,s=Ari65]
\author[]{}[]{}{Aristoteles}
\pubyear{1965}
\title{De arte poetica liber}
\city{Oxford}
\pubname{Oxford UP}
\stoppublication
\starttext
Hello world!
\nocite[kasselpoeticedition]
\placepublications[criterium=cite]
\stoptext
On my big bibliography files, I get errors such as this:
LuaTeX warning (ext4): destination with the same identifier
(name{6:fsstraub}) has been already used, duplicate ignored
\egroup
\thisisdestination ... \dostartthisislocation {#1}
\dostopthisislocation \fi ...
l.2 \thisisdestination{6:fsstraub}
\dosetreference ...ls ",\nextinternalreference ) }
\fi \fi
...ibrefprefix fsstraub]{\bibcounter }}
\strut
\dotypesetapublicat...
\listtextcommand #1->\begstrut #1
\endstrut
...
l.184 ...lications[criterium=cite,option=continue]
but I have no idea if these problems are related.
I have to deliver a paper tomorrow and am glad I kept an older
version...
All best
Thomas
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Bugs in latest beta: \Bbb broken
On 16 avr. 09, at 11:18, Hans Hagen wrote: […] i'll add \let\Bbb\mathblackboard Thanks Hans. Indeed \mathblackboard works fine in mkiv. Best regards: OK ___ 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://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Bugs in latest beta: \Bbb broken
Otared Kavian wrote:
Hi Hans,
It seems that in the latest beta (mkiv) the command \Bbb is broken (but
it works fine in mkii).
Minimal example:
\starttext
The set ${\Bbb C}$ is the set of complex numbers.
\stoptext
i'll add
\let\Bbb\mathblackboard
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
[NTG-context] Bugs in latest beta: \Bbb broken
Hi Hans,
It seems that in the latest beta (mkiv) the command \Bbb is broken
(but it works fine in mkii).
Minimal example:
\starttext
The set ${\Bbb C}$ is the set of complex numbers.
\stoptext
Thanks for your attention: OK
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
[NTG-context] Bugs in latest beta: line numbering in verbatim
Hi Hans, This bug was reported by Wolfgang Schuster a few months ago, but it persists: line numbering in verbatim is broken in mkiv (it works as expected in mkii). Minimal example: \setuptyping[numbering=line] \setupcolors[state=start] \starttext \startframedtext[frame=off,background=color,backgroundcolor=darkyellow] \starttyping one two three \stoptyping \stopframedtext \stoptext Thanks for your attention: OK ___ 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://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] bugs in arranging in mkiv interface=xp
With the following snippet
\setuppapersize[A6][A4] \setuparranging[2*4, doublesided]
\starttext
\dorecurse{8}{
\input tufte
\page}
\stoptext
and todays beta using the xp interface with
context --interface=xp
I got the surprising attached result with the arrange pages thrown
onto the sheet with a seemingly random rotation. Also, in a more
complex example with a toc, no toc is made, as if using texexec and
forgetting the --arrange switch. However, adding the --arrange switch
here has an entirely different consequence: only one of the arranged
pages is placed on each sheet, so in effect there is no longer any
arranging. I assume these are not intended behaviours, but would be
happy to be informed I made an error in usage.
Regards, Johan
--
Johan Sandblom, MD PhD
m +46735521477 Sweden
"What is wanted is not the will to believe, but the
will to find out, which is the exact opposite"
- Bertrand Russell
arr-test.pdf
Description: Adobe PDF document
___
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
[NTG-context] bugs found while trying to support utf-8 Korean Hangul under ConTeXt
Hi,
http://210.94.201.157/~nomos/KTUG/context-korean-test.tar.gz (3.4Mb)
Recently I have tried to support typesetting UTF-8 Korean document
under ConTeXt.
In the course of that trying, I found some possible bugs of recent
ConTeXt beta.
You can see most of the bugs (or missing features) I found in the file
named `testme.tex',
which is contained in the tarball linked above.
For those who do not want to download that large tarball,
I here replicate those bugs or missing features:
%%%
% should be added to unic-cjk.tex
% Hangul Syllables
\dostepwiserecurse{172}{215}{1}{\expanded{\defineunicodecommand {\recurselevel}}
{\lookaheaduchar}}
% CJK Compatibility Ideographs
\dostepwiserecurse{249}{250}{1}{\expanded{\defineunicodecommand {\recurselevel}}
{\lookaheaduchar}}
%%%
% modify \enableunicodefont in font-uni.tex
\def\enableunicodefont#1%
{\definefontsynonym[\s!Unicode][\getvalue{\??uc#1\c!file}]%
\def\unicodescale {\getvalue{\??uc#1\c!scale}}%
\def\unicodeheight{\getvalue{\??uc#1\c!height}}%
\def\unicodedepth {\getvalue{\??uc#1\c!depth}}%
\def\unicodedigits{\getvalue{\??uc#1\c!conversion}}%
\def\handleunicodeglyph {\getvalue{\??uc#1\c!command}}%
\doifnot\currentregime{utf}{\enableregime[unicode]}%
% the following \relax's are realy needed
\doifvalue{\??uc#1\c!interlinespace}\v!yes
\setupinterlinespace\relax
\doifvalue{\??uc#1\c!strut}\v!yes
{\setunicodestrut\unicodeheight\unicodedepth}% <- `%' inserted by nomos
{\resetunicodestrut}%
\getvalue{\??uc#1\c!commands}\relax}
%%%
% modify \sanitizePDFuniencoding in spec-tst.tex
\long\def\sanitizePDFuniencoding#1\to#2%
{\enablePDFunicrlf
\simplifycommands % <- this line inserted by nomos
\let\unicodechar\relax % prevent further expansion
\retainlccodes\lccode32=255 % slooow
\lowercasestring\PDFunicodetrigger#1\to#2%
\edef#2{\expandafter\doPDFuni#2\empty\empty}} % slooow
%%%
% modify mps file insertion code in spec-dpx.tex
\definefileinsertion{dpx}{mps} % tpd -> dpx modified by nomos
{\hbox
{\convertMPtoPDF\@@DriverImageFile{1}{1}%
\global\let\PDFimagereference\empty}}
Certainly, the last is not problem confined to Hangul typesetting.
As you know, however, CJK peoples do use heavily dvipdfmx to obtain PDF.
Anyway, I hope these four files be modified in the near future.
In addition, when I compiled LaTeX2ConTeXt.tex by Berend de Boer
( http://www.berenddeboer.net/tex/LaTeX2ConTeXt.tex ),
I found there being inserted unintended large vertical whitespace
in page 27 of resulting PDF.
Though it seems to be a bug related to \setupbackground,
I could not find the cause of problem as the code related to that command
is too complicated for me.
--
Dohyun Kim
http://people.ktug.or.kr/~nomos/
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] bugs?
Idris Samawi Hamid said this at Mon, 26 Sep 2005 12:22:45 -0600: >The footnote numeral `1' is indented further than the footnote numeral `2'. I'm not sure I see this: the width of `1' is less than `2', but the default LM font has monospaced numbers, so the visual space to the left of the `1' may appear to be greater... not the cleanest visualisation, but you can see the left sides are the same here: \setupfootnotes[command=\framed] ...that or there's something different in your configuration? -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. [EMAIL PROTECTED] Lancaster University, InfoLab21+44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] bugs?
Dear gang,
A couple of apparent bugs, apparently related:
[ConTeXt ver: 2005.08.15 fmt: 2005.8.20 int: english mes: english]
==
% output=pdf interface=en
\starttext
Test.\footnote{Test}
Test.\footnote{Test}
\stoptext
==
The footnote numeral `1' is indented further than the footnote numeral `2'.
Similarly:
==
% output=pdf interface=en
\useURL
[Pragma1]
[http://www.pragma-ade.com/download-1.htm]
[]
[{\sc Pragma}]
\useURL
[Pragma2]
[http://www.pragma-ade.com/download-1.htm]
[]
[{\sc Pragma}]
\starttext
\Context\ can be downloaded from \from[Pragma1].
\Context\ can be downloaded from \from[Pragma2].
\stoptext
==
The first `Pragma' is indented further than the second.
Please advise.
Best
Idris
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Bugs
Looks great to me. Thanks Hans. Dirar. ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Bugs
Dirar BOUGATEF wrote: Thanks all. Would be nice to know how to switch the left and right keywords to do the opposite of what it does now. there is a switcj but it would spoil the use of modules, you can use flushleft and flushright as alternatives Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
RE: Re[2]: [NTG-context] Bugs
Thanks all. Would be nice to know how to switch the left and right keywords to do the opposite of what it does now. ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
