Re: [NTG-context] Section labels in appendices (appendixlabel=)
Am 24.08.2009 um 12:29 schrieb Mojca Miklavec: Hello, I have some problems interpreting the ConTeXt manual. If I want to have the appendices labeled as Appendix A: My first appendix Appendix B: My second appendix ... what is wrong with the following approach? \setupsection [section] [appendixconversion=Character, appendixlabel=appendix] strc-sec.mkii: \setuphead [\v!section] [\v!appendix\c!label=\v!section, \v!bodypart\c!label=\v!section] % bijlageconversie= \Character 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] Section labels in appendices (appendixlabel=)
Am 26.08.2009 um 10:33 schrieb Mojca Miklavec: On Wed, Aug 26, 2009 at 10:08, Wolfgang Schuster wrote: \setuphead [\v!section] [\v!appendix\c!label=\v!section, \v!bodypart\c!label=\v!section] % bijlageconversie= \Character I'm sorry, but I'm blind ... :( :( :( Doesn't it also say appendixlabel= here? I just don't see it how it's used. Maybe I should use something else but section? Enable the label with \setuphead, not \setupsection. 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] Section labels in appendices (appendixlabel=)
On Wed, Aug 26, 2009 at 10:39, Wolfgang Schuster wrote: Am 26.08.2009 um 10:33 schrieb Mojca Miklavec: On Wed, Aug 26, 2009 at 10:08, Wolfgang Schuster wrote: \setuphead [\v!section] [\v!appendix\c!label=\v!section, \v!bodypart\c!label=\v!section] % bijlageconversie=\Character I'm sorry, but I'm blind ... :( :( :( Doesn't it also say appendixlabel= here? I just don't see it how it's used. Maybe I should use something else but section? Enable the label with \setuphead, not \setupsection. Arghhh ... Where on earth did I take \setupsection from? (I was probably reading the manual and saw it used for conversion, but I never noticed it was \setupsection and not \setuphead that I have been using for a long time.) I'm sorry. It sometimes takes someone to look at one's minor mistakes from a distance (in the meantime I just did an ugly hack to solve the problem). Thanks a lot and sorry again :( 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 : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] Why are pretty printer names uppercased?
Hi all, according to the wiki, and the current code, the arguments to \installprettytype should be uppercased. E.g.: \installprettytype [PHP][PHP] Referring to them should be uppercased as well: \definetyping[PHP] [option=PHP] \setuptyping[option=PHP] However, the filename should be lowercase, e.g. pret-php.lua and the pretty printer should register itself in lowercase as well: buffers.newvisualizer(lua). The first thing that happens to the arguments of installprettytype is to lowercase them, and every option= argument that points to a pretty printer is lowercased by setvisualizer in lua before being used. If everything is lowercased, why do we still recommend the arguments to \installprettytype and option= to be uppercase? IMHO this makes things confusing when trying to understand which PHP refers to which php or PHP in the greater picture of things. Why not recommend people to use lowercase identifiers instead, since we're changing everything into lowercase anyway? Or perhaps go a bit further and remove the lowercasing code alltogether, since I don't see any real gain. If the strings / filenames should just match exactly, things will get a lot more predictable? Gr. Matthijs signature.asc Description: Digital signature ___ 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] Why are pretty printer names uppercased?
Matthijs Kooijman wrote: Hi all, according to the wiki, and the current code, the arguments to \installprettytype should be uppercased. E.g.: because want uppercase \startTEX \stopTEX \startMP \stopMP \startLUA \stopLUA \installprettytype [PHP][PHP] Referring to them should be uppercased as well: \definetyping[PHP] [option=PHP] defining indeed, as it is an instance, but option also accepts lowercase However, the filename should be lowercase, e.g. pret-php.lua and the pretty printer should register itself in lowercase as well: buffers.newvisualizer(lua). The first thing that happens to the arguments of installprettytype is to lowercase them, and every option= argument that points to a pretty printer is lowercased by setvisualizer in lua before being used. indeed. as i don't like casing in filenames, and function names If everything is lowercased, why do we still recommend the arguments to \installprettytype and option= to be uppercase? IMHO this makes things confusing when trying to understand which PHP refers to which php or PHP in the greater picture of things. because they generate commands and it's quite valid to say \definetyping[myphp] etc Why not recommend people to use lowercase identifiers instead, since we're changing everything into lowercase anyway? Or perhaps go a bit further and remove the lowercasing code alltogether, since I don't see any real gain. If the strings / filenames should just match exactly, things will get a lot more predictable? actually, the advice is that user definitions use uppercase \definehead[MySection][section] etc, just to avoid clashes with built in commands 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] Why are pretty printer names uppercased?
Hi Hans, according to the wiki, and the current code, the arguments to \installprettytype should be uppercased. E.g.: \installprettytype [PHP][PHP] because want uppercase \startTEX \stopTEX Well, those would be coming from the first argument of definetyping. AFAIU, neither argument to installprettytype is related to these commands. \definetyping[PHP] [option=PHP] indeed. as i don't like casing in filenames, and function names Agreed, me neither. actually, the advice is that user definitions use uppercase \definehead[MySection][section] etc, just to avoid clashes with built in commands That makes sense for commands, which is not what I'm proposing to change. I would propose making it look like the following: \installprettytype [php][php] \definetyping [PHP][option=php] Here, the second php refers to pret-php.lua, the first and last php refer to each other and to the php in newvisualizer(php). The command defined is still \startPHP, but now the values that refer to other lowercase things (filename, pretty printer name) are lowercase consistently. How's this? Gr. Matthijs signature.asc Description: Digital signature ___ 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] Why are pretty printer names uppercased?
Matthijs Kooijman wrote: Hi Hans, according to the wiki, and the current code, the arguments to \installprettytype should be uppercased. E.g.: \installprettytype [PHP][PHP] because want uppercase \startTEX \stopTEX Well, those would be coming from the first argument of definetyping. AFAIU, neither argument to installprettytype is related to these commands. sure but they are somewhat related (also with the color palets then) \definetyping[PHP] [option=PHP] indeed. as i don't like casing in filenames, and function names Agreed, me neither. actually, the advice is that user definitions use uppercase \definehead[MySection][section] etc, just to avoid clashes with built in commands That makes sense for commands, which is not what I'm proposing to change. I would propose making it look like the following: \installprettytype [php][php] \definetyping [PHP][option=php] Here, the second php refers to pret-php.lua, the first and last php refer to each other and to the php in newvisualizer(php). The command defined is still \startPHP, but now the values that refer to other lowercase things (filename, pretty printer name) are lowercase consistently. How's this? in order to get that working and remain compatible, we'd also need to redefine \definepalet [TEXcolorpretty] [colorpretty] \definepalet [TEXgraypretty] [graypretty] (ans use some nasty trickery to let texcolorpretty and TEXcolorpretty both be valid) etc and as users themselves seldom see the low level definitions it's not worth the trouble 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 ___
[NTG-context] Footnotes and body text
Hello, Looks like my previous message was overlooked. Let me cry again. In my document footnotes' upper line clashes with body text. In result, last line of body text looks underlined. Please, take a look at the attachment. Regards, Vyatcheslav Pages from Help.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 ___
Re: [NTG-context] Footnotes and body text
Vyatcheslav Yatskovsky wrote:
Hello,
Looks like my previous message was overlooked. Let me cry again.
In my document footnotes' upper line clashes with body text. In result,
last line of body text looks underlined.
Please, take a look at the attachment.
Context does not take the best possible decision, but that is because
the document page is over-constrained.
Either both the 'Five Jazz Piece.' line and the footnote have to be
on the page, or neither one. If this is the final document then to
get out of the impasse, I would simply add a \vadjust{\page} command on
the 'Those complex stuff' line, but there probably is a better solution
possible by playing with \setupfootnotes and \setuptolerance.
Best wishes,
Taco
___
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] Footnotes and body text
On Wed, 26 Aug 2009 07:26:31 -0600, Vyatcheslav Yatskovsky yatskov...@gmail.com wrote: Hello, Looks like my previous message was overlooked. Let mecry again. ^^^ = try That's what we call a Freudian slip in English ;-) In my document footnotes' upper line clashes with body text. In result, last line of body text looks underlined. Please, take a look at the attachment. I've run into this before. Play with \setupfootnotes[before=\vskip1ex] Although I suppose may be a bug in mkiv, since this spacing should be automatic. Best wishes Idris -- Professor Idris Samawi Hamid, Editor-in-Chief International Journal of Shi`i Studies Department of Philosophy Colorado State University Fort Collins, CO 80523 ___ 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] lang-ita.tex is broken for spanish
Enrique Jiménez Gallego wrote: \setuplabeltext [\s!fr] [\v!chapter=] ! \setuplabeltext [\s!es] [\v!chapter=Cap\'\itulo] ! \setuplabeltext [\s!ca] [\v!chapter=Cap\'\itol] add a space ... \i tulo - 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] PDF x1a:2001 and Context
PDF X/1a:2001 is an old pdf standard still required by some important American printers. Han The Thanh et al. has created a package for pdfLatex. I wonder if there is a route to this output using Context? -- John Culleton Able Indexers and Typesetters ___ 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] PDF x1a:2001 and Context
John Culleton wrote: PDF X/1a:2001 is an old pdf standard still required by some important American printers. Han The Thanh et al. has created a package for pdfLatex. I wonder if there is a route to this output using Context? it depends ... what do validators report? 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 ___
