Re: [NTG-context] Referencing Itemized Items?
Wow. How embarrassing - I am usually the one who chides my users about never actually trying simple experiments to see if something works. ___ 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] Referencing Itemized Items?
2008/4/30, Michael P. Urban [EMAIL PROTECTED]: Wow. How embarrassing - I am usually the one who chides my users about never actually trying simple experiments to see if something works. ___ 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 ___ -- 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 ___ 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] Greek module still in use?
On May 1, 2008, at 4:26 AM, [EMAIL PROTECTED] wrote: I have unzipped the folder to my texmf tree so it looks like this: [EMAIL PROTECTED]:~ cd /usr/share/texmf [EMAIL PROTECTED]:/usr/share/texmf ls bibtex context dvipsls-R mft text- greek-2008.04.30 bin doc fmtutil makeindex scripts texconfig web2c chktex dvipdfm fontsmetafont teTeXtexmf xdvi [EMAIL PROTECTED]:/usr/share/texmf Then I ran texhash. I am using Linux OpenSuse 10.3 KDE. armando martins OK, there's nothing inherently wrong with what you did. I would advise, however, to install additional packages either to the local texmf tree or to you personal tree. These are defined in the file /etc/ texmf/web2c/texmf.cnf as TEXMFLOCAL = /usr/local/share/texmf and TEXMFHOME = $HOME/TEXMF You have unzipped into the main tree, so it should work as well. I would ask you to make sure that the important files are in the right position, so run ls /usr/share/texmf/tex/context/third and that the files are seen by TeX, so run kpsewhere t-ancientgreek.tex Post the output of these commands. 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] Trouble with Index
On Thu, May 1, 2008 at 4:22 AM, [EMAIL PROTECTED] wrote:
Indeed. Question to the developers: given that our rule of thumb is
material within {} will be typeset; material within [] is for setups
etc., wouldn't it make sense to have the command as index[]? (Maybe
with an alternative \index{} which will typeset the word AND put it in
the index?)
Ok, but what am I doing wrong? Should I typeset \index[] or \index{}?
Or am I missing some trick? Or is this problem waiting for solution.
I have put both ways in my file and the page with Index is still empty.
\starttext
Tantrums\index{Tantrum} can be normal for
toddlers\index{tantrum+toddlers}. Young children have them for
many reasons like being tired, feeling out of control, over-stimulated,
or wanting something they can't have.
General hints: Toddlers and preschoolers cannot regulate themselves
because they don't yet know their own limits.
\completeindex
\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
___
[NTG-context] MetaPost 1.004 announcement
The MetaPost team is happy to announce a new release of MetaPost: -- MetaPost 1.004 -- The sources and a win32 package can be downloaded immediately from http://foundry.supelec.fr/projects/metapost/ This release will also be available from CTAN soon, and it will be included in the next TeXLive. The source package should compile normally on all systems that are capable of compiling a modern web2c-based TeX distribution. The win32 package is intended for texlive or a similar web2c-based installation, and has been tested only with TeXLive 2007. These executables will *not* work for miktex, sorry. Of course, we welcome any comments (either good or bad) that you may have. Simply replying to this message is fine, but see the bottom of the message for a more formal way to report bugs and feature requests. -- What is new in version 1.004: -- * The picture color component commands misbehaved in 1.003: the current (default) colormodel was not taken into consideration, so all colors had to be explicit for redpart etc. to work. (this bug is the one broke the graph.mp package) In 1.004 for defaulted colors, the suitable value in the current (default) colormodel is returned without any errors. This change also reverts to silently defaulting a 'black' color when asking for the redpart etc. of an object that cannot be colored at all. * The picture color component commands misbehaved in 1.003 in a different manner also: the defaults for uninitialized CMYK color picture parts were still assuming 'black' was defined as (1,1,1,1) instead of as (0,0,0,1). * The macro Gwithpc_ in the graph.mp package did not work properly with non-rgb colormodel objects. * plain.mp has a new macro, 'colorpart', that returns the color parts of a graphical object within a picture in a form suitable for feeding it back to 'withcolor'. * The latest kpathsea library from TeXLive is included. * There is now a separate manual for the boxes package (mpboxes.pdf). -- Legal notice / license / bug reports -- MetaPost is a system for producing graphics developed by John Hobby at ATT, based on Donald Knuth's Metafont. The MetaPost home page is http://tug.org/metapost. MetaPost and related programs are in the public domain. The MetaPost development project is currently hosted at Supelec, https://foundry.supelec.fr/projects/metapost; please report bugs and request enhancements through there if possible. Alternatively, you can reach us through the [EMAIL PROTECTED] mailing list as well. Have fun! Taco Hoekwater, for the MetaPost team, May 1, 2008. ___ 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] two small questions about the mkiv roadmap
On Apr 30, 2008, at 6:10 PM, Hans Hagen wrote:
Wolfgang Schuster wrote:
The DTD is a problem with the ConTeXts XML parser and has
nothing to do with LuaTeX (hope this is right).
i need a test file then (can look into it next week; i'm at bachotek
now)
OK, I hope this is a minimal test: I have this xml file (which, I
think, is valid xml):
?xml version=1.0 encoding=utf-8?
!DOCTYPE context [
!ELEMENT document (section)
!ELEMENT section (title,content)
!ELEMENT title(#PCDATA)
!ELEMENT content (#PCDATA)
!ENTITY ndash #x02013;
]
document
section
titleThe Title/title
content
pA line of text ndash; with a dash./p
/content
/section
/document
and this environment myenv.tex:
\startxmlsetups xml:mysetups
\xmlsetsetup{\xmldocument}{document|section|}{xml:*}
\stopxmlsetups
\xmlregistersetup{xml:mysetups}
\startxmlsetups xml:document
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:section
\section{\xmlfirst{#1}{title}}
\xmlfirst{#1}{content}\par
\stopxmlsetups
\enableregime[utf]
\defineXMLentity[ndash]{--}
\starttext
\xmlprocess{main}{\inputfilename}{}
\stoptext
If I process this with
texexec --lua --env=myenv test.xml, the typeset output I get is
invalid xml file. If I remove the entire DTD (so the first line is
document), it is typeset normally.
Have fun in Poland!
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] two small questions about the mkiv roadmap
On Thu, May 1, 2008 at 11:00 AM, Thomas A. Schmitz
[EMAIL PROTECTED] wrote:
On Apr 30, 2008, at 6:10 PM, Hans Hagen wrote:
Wolfgang Schuster wrote:
The DTD is a problem with the ConTeXts XML parser and has
nothing to do with LuaTeX (hope this is right).
i need a test file then (can look into it next week; i'm at bachotek
now)
OK, I hope this is a minimal test: I have this xml file (which, I
think, is valid xml):
\startbuffer[test]
?xml version=1.0 encoding=utf-8?
!DOCTYPE context [
!ELEMENT document (section)
!ELEMENT section (title,content)
!ELEMENT title(#PCDATA)
!ELEMENT content (#PCDATA)
!ENTITY ndash #x02013;
]
document
section
titleThe Title/title
content
pA line of text ndash; with a dash./p
/content
/section
/document
\stopbuffer
and this environment myenv.tex:
\startxmlsetups xml:mysetups
\xmlsetsetup{\xmldocument}{document|section|}{xml:*}
\stopxmlsetups
\xmlregistersetup{xml:mysetups}
\startxmlsetups xml:document
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:section
\section{\xmlfirst{#1}{title}}
\xmlfirst{#1}{content}\par
\stopxmlsetups
\enableregime[utf]
\defineXMLentity[ndash]{--}
\starttext
\xmlprocess{main}{\inputfilename}{}
\xmlprocessbuffer{main}{est}{}
\stoptext
Easier for test because you need only one file.
If I process this with
texexec --lua --env=myenv test.xml, the typeset output I get is
invalid xml file. If I remove the entire DTD (so the first line is
document), it is typeset normally.
Have fun in Poland!
It's fathers day :-)
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] two small questions about the mkiv roadmap
On May 1, 2008, at 11:12 AM, Wolfgang Schuster wrote: Easier for test because you need only one file. Thanks Wolfgang! Have fun in Poland! It's fathers day :-) I know. My two sons insisted on bringing me breakfast at 6.45. And they wanted to charge for it too :-) 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 ___
[NTG-context] Line break and \in{....}[] command; bookmarks
Hi all, I use \definereferenceformat[insection][text=Section] however, sometimes the item is that long that Section 5.5 .. looks much nicer than a 5.5 sticking out of the margin. Is there a possibility to allow a line break between the text and the number? Secondly, I want to use acroread's bookmarks. But I have two problems: a) I failed to create a bookmark for the title page. What is the best way to do so? Currently, I use: \startmakeup[standard][doublesided=no,page=right] ... \stopmakeup b) Somehow the bookmark list goes wrong. I have: \placebookmarks[chapterEP,chapter,section,subsection] where chapterEP is a specially designed version of \chapter but should be on the same level. First, everything goes nice, but then a chapterEP becomes a descendant of another chapterEP. I have no idea how I can reduce the problem to a small example or how to fix it. Any idea? ... chapterEP section subsection subsection section subsection subsection chapterEP section section chapterEP section chapterEP --- Wrong! section section chapterEP (still wrong level) section section chapterEP -- Another wrong level) chapterEP (still wrong level) chapterEP (still wrong level, but one less) chapterEP (still wrong level) chapterEP -- OK again chapterEP Tobias ___ 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] Line break and \in{....}[] command; bookmarks
On Thu, May 01 2008, Tobias Burnus wrote:
I use
\definereferenceformat[insection][text=Section]
however, sometimes the item is that long that
Section
5.5 ..
looks much nicer than a 5.5 sticking out of the margin. Is there a
possibility to allow a line break between the text and the number?
Something sticking out the margin (overfull hbox) is never good, but I
think the unbreakable space between the text and the number should
stay. The preferred solution is breaking sec-tion. But this only works
with \setupinteraction[state=stop].
See also the feature request
http://foundry.supelec.fr/tracker/index.php?func=detailaid=59group_id=21atid=164
Cheers, Peter
--
http://pmrb.free.fr/contact/
___
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] typo or bug report in type-buy.tex
Hi folks, From line 199 to 206 : \starttypescript [lucida,lucidabfm] [texnansi,ec,8r,uc] \definetypeface [lucida] [rm] [serif] [lucida] [default] [encoding=\typescripttwo] \definetypeface [lucida] [ss] [sans][lucida] [default] [encoding=\typescripttwo] \definetypeface [lucida] [tt] [mono][lucida] [default] [encoding=\typescripttwo] \definetypeface [lucida] [hw] [handwriting] [lucida] [default] [encoding=\typescripttwo] \definetypeface [lucida] [cg] [calligraphy] [lucida] [default] [encoding=\typescripttwo] \loadmapfile [\typescriptthree-bh-lucida.map] \stoptypescript I assume it should be : \starttypescript [lucida,lucidabfm] [texnansi,ec,8r,uc] \definetypeface [lucida] [rm] [serif] [lucida] [default] [encoding=\typescripttwo] \definetypeface [lucida] [ss] [sans][lucida] [default] [encoding=\typescripttwo] \definetypeface [lucida] [tt] [mono][lucida] [default] [encoding=\typescripttwo] \definetypeface [lucida] [hw] [handwriting] [lucida] [default] [encoding=\typescripttwo] \definetypeface [lucida] [cg] [calligraphy] [lucida] [default] [encoding=\typescripttwo] \loadmapfile [\typescripttwo-bh-lucida.map] \stoptypescript Cheers, Renaud ___ 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] typo or bug report in type-buy.tex
On Thu, 01 May 2008 17:37:17 +0200 Renaud AUBIN [EMAIL PROTECTED] wrote: Hi folks, From line 199 to 206 : \starttypescript [lucida,lucidabfm] [texnansi,ec,8r,uc] \definetypeface [lucida] [rm] [serif] [lucida] [default] [encoding=\typescripttwo] \definetypeface [lucida] [ss] [sans][lucida] [default] [encoding=\typescripttwo] \definetypeface [lucida] [tt] [mono][lucida] [default] [encoding=\typescripttwo] \definetypeface [lucida] [hw] [handwriting] [lucida] [default] [encoding=\typescripttwo] \definetypeface [lucida] [cg] [calligraphy] [lucida] [default] [encoding=\typescripttwo] \loadmapfile [\typescriptthree-bh-lucida.map] \stoptypescript I assume it should be : \starttypescript [lucida,lucidabfm] [texnansi,ec,8r,uc] \definetypeface [lucida] [rm] [serif] [lucida] [default] [encoding=\typescripttwo] \definetypeface [lucida] [ss] [sans][lucida] [default] [encoding=\typescripttwo] \definetypeface [lucida] [tt] [mono][lucida] [default] [encoding=\typescripttwo] \definetypeface [lucida] [hw] [handwriting] [lucida] [default] [encoding=\typescripttwo] \definetypeface [lucida] [cg] [calligraphy] [lucida] [default] [encoding=\typescripttwo] \loadmapfile [\typescripttwo-bh-lucida.map] \stoptypescript It makes also sense to replace \definetypeface [lucida] ... with \definetypeface [\typescriptone] ..., allows you to write \usetypescript[lucidabfm] \setupbodyfont[lucidabfm] 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] typescript and memory usage
Hello list, Thanks to Hans, Hraban, Wolfgang and Aditya, I've successfully played with typescripts and Garamond PP as provided by Adobe with luatex. But I still have a little question :) By reducing my typescript to the strict minimum, as below, I'm still using 232 Mo (sic) of ram. My document test only contains nothing but a \switchtobodyfont but it takes 8.7 seconds to compile on a 4000 bogomips machine (athlon 2400+). For the C lover I am, that seems, errh, HUGE. Is it normal? Note that if I remove the [features=default] argument, mem is divided by 2, and time by 3. Also note that if I use more faces, it can go to 2Go of ram and 2 minutes of computing. Thanks for your reply, -AJ %% typescript \starttypescript[serif][garamondpp] \definefontsynonym [GaramondPP-Roman][file:GaramondPremrPro] \stoptypescript \starttypescript[serif][garamondpp][name] \definefontsynonym [Serif][GaramondPP-Roman] \stoptypescript \starttypescript [GaramondPP] \definetypeface [GaramondPP][rm][serif][garamondpp][default] \stoptypescript %% minimal doc \usetypescriptfile[type-garamondpp] \usetypescript[GaramondPP] \starttext \setupbodyfont[GaramondPP] \stoptext ___ 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] defineitemgroup interferes with item reference
I cannot figure out the error in the following nested itemization with a
reference. Is it a bug or am I overlooking something? Here is the
smallest example I could make. Strangely, if I change the
startproblemlist to startitemize and stopproblemlist to stopitemize, all
is well.
\defineitemgroup[problemlist]
\starttext
\startproblemlist
\item Drag
\startitemize
\item[ref] blah
\stopitemize
\stopproblemlist
\stoptext
I'm using context 2008.01.28 21:28 (mkii), Debian GNU/Linux 'unstable'
for i386, and the 2008.04.27 version on the Garden gives the same error.
The error is
! Undefined control sequence.
write ...realfolio }{\relax \@@opitemizesymbol1
\relax .?}
inserted text
}\endwrite
\actualshipout ... \box \postponedcontent \box 0}}
\else \message {[\ifarrang...
\myshipout ... \fi {\thisisrealpage \realfolio #1}
\gotonextrealpage \aftersh...
\dofinaloutput ...agebody #1#2\setpagecounters }}}
\fi \the \everyaftershipou...
\finaloutput ...EAEAEA \dofinaloutput \fi \fi #1#2
\resetselectiepagina \incr...
...
l.14 \stoptext
-Sanjoy
`Until lions have their historians, tales of the hunt shall always
glorify the hunters.' --African Proverb
___
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
___
