Re: [NTG-context] Figures are misplaced with \pagedir TRT\bodydir TRT
On Tue, Sep 02, 2008 at 08:33:50PM +0200, Khaled Hosny wrote: > Figures are shifted to the right (the left edge is where right edge > should) when I set \pagedir TRT\bodydir TRT. This my not be an optimum solution, but putting \externalfigure inside an hbox with TLT direction gets the figure in the correct position: \placefigure[][]{}{\hbox dir TLT\externalfigure[mill]}} Regards, -- Khaled Hosny Arabic localizer and member of Arabeyes.org team 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] End Notes and Minimals
Hans, What's the chances on getting this fixed? Or is there a stable branch somewhere that I can grab? Thanks! Bart On Tuesday 25 November 2008 11:47:38 am Wolfgang Schuster wrote: > Am 25.11.2008 um 19:39 schrieb Bart C. Wise: > > Below are four different ways I've tried to get endnotes to work. > > When I > > compile with "texexec" it work fine --- I get endnotes. However, > > when I > > compile with "texexec --lua" the footnotes are placed on the page > > where they > > are referenced. I would prefer to have the footnote/placefootnotes > > work so > > that I can easily change the output. Any ideas? > > > > *** #1 > > \setupfootnotes[location=none] > > \starttext > > \dorecurse{100}{test \footnote{eee}\endgraf} > > \page > > \placefootnotes[location=none] > > \stoptext > > > > *** #2 > > \setupfootnotes[location=none] > > \starttext > > \dorecurse{100}{test \footnote{eee}\endgraf} > > \page > > \placefootnotes > > \stoptext > > > > *** #3 > > \setupnote[endnote][location=none] > > \starttext > > \dorecurse{100}{test \endnote{eee}\endgraf} > > \page > > \placenotes[endnote] > > \stoptext > > > > *** #4 > > \starttext > > \dorecurse{6}{ \input tufte \endnote{\input knuth\relax} } > > \page > > \placenotes[endnote] > > \stoptext > > It's a bug in the \expdoifcommonelse macro used in MkIV, > it evaluates always the true value and you get footnotes. > > Here is a example for Hans: > > \starttext > > \doifcommonelse{text,page}{none} >{true} >{false} > > \expdoifcommonelse{text,page}{none} >{true} >{false} > > \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 > ___ > ___ 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] printing tab in lua: print('a\tb') fails
Am 26.11.2008 um 20:07 schrieb Mojca Miklavec: > Hello, > > Here's a tiny question. The following command complains about > undefined control sequence. > > \starttext > \startluacode > print('a\tb') print('a\t b') > \stopluacode > hello > \stoptext > > There is a workaround: >print(string.format('a\t%s', 'b')) > but I find it weird. Even if the line above gets commented out with > two dashes it still complains. > > I understand approximately why this happens, but is that intended? > Should I be using something else than \startluacode in the plethora of > different lua triggering commands? \start/stopluacode is defined as \startluacode#1\stopluacode (simplified) and you should take care of TeXs parsing rules. If you want Lua comments and format command (\n, \t ...) use a external file for your Lua code. 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] printing tab in lua: print('a\tb') fails
Hello, Here's a tiny question. The following command complains about undefined control sequence. \starttext \startluacode print('a\tb') \stopluacode hello \stoptext There is a workaround: print(string.format('a\t%s', 'b')) but I find it weird. Even if the line above gets commented out with two dashes it still complains. I understand approximately why this happens, but is that intended? Should I be using something else than \startluacode in the plethora of different lua triggering commands? Thanks, 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 ___
Re: [NTG-context] difference between TeX behavior and ConTeXt
On 11/26/2008 8:11 AM, Taco Hoekwater wrote: > > Lars Huttar wrote: >> Except perhaps the documentation. I have yet to find a reference that >> clearly describes what \rm is to do in ConTeXt. One responder pointed to >> http://www.pragma-ade.com/general/manuals/cont-eni.pdf. The closest >> thing to a definition of \rm there that I could find is on p. 111: "The >> command \rm is used to switch to a roman/serif/regular style,..." > > In his first reply to your message, Aditya posted the link to the new > manual chapter on "Typography". This chapter and the following one > "Fonts" are planned to be the definitive answer to all questions > regarding fonts and font selection in ConTeXt. > > If you believe the text could be improved even further beyond the > changes already made compared to the manual at Pragma ADE, please > tell us how (for sure, the meaning of the macro \rm is not going to > change!). Understood. :-) > We all want the manual to be as good as humanly possible, > but it is often quite hard to write at beginners' level when you > have advanced past that point yourself. Understood too. > If you can find a good (or at least better) way to express what > \rm,\ss,\tt,\hw and \cg do compared to the current prose in > co-typography, please post it. Just keep in mind that the manual > has to remain independant, so texts that presuppose knowledge of > plain TeX and/or LaTeX are not acceptable except as a side/footnote. > Thank you for being willing to take input to improve the documentation. My #1 wish would be a reference section where \rm is described unambiguously. So, for example, it would be very helpful to have it at http://texshow.contextgarden.net/, since that is presented on the ConTeXt garden wiki as a "ConTeXt command reference", "for all user-commands that can be used in ConTeXt" (cc'ing Patrick Gundlach for this reason). I see instructions there for commenting on a command, but no way to request addition of a command. In any case, an unambiguous description would be, instead of switch to a roman/serif/regular style [p. 3 of new manual chapter on typography] something like this: switch to a serif style (if that's what \rm means in ConTeXt -- I still don't know for sure). The word "regular" is ambiguous, as it commonly contrasts with "italic" but sometimes with "bold". (And should I infer now that it sometimes contrasts with sans-serif?) Similarly, "roman" can have multiple meanings. To Knuth it meant "non-italic". As far as I'm aware, the term "serif style" is unambiguous. (But I'm not a professional typographer.) Table 1.2 lists "\rm serif, regular, roman, rm" but does not say whether all the words in the right column are supposed to be synonyms for the same typeface attribute, or constitute a collection of different attributes. It appears that some of them are the internal names of styles? (the last one in each row), while others may be merely descriptive. It would be helpful to have headers on the columns in this table so that the reader knows what the data in each column indicates. If everything in the right column is a command sequence in ConTeXt (perhaps it's a defined font), it would be helpful to know that. The first column could have the header "Command", matching the table caption. The second column header depends on what the stuff in the second column is. If it's intended to be merely a natural-language description of what the command in the first column does, I think it could be clarified as follows: Command / Switch to style/ Internal style name \rm / serif / rm \ss / sans serif (a.k.a. "support") / ss \tt / typewriter (monospaced)/ tt \hw / handwritten/ hw \cg / calligraphic / cg none// mm I put the "Internal style name" column in there for completeness, but it's not clear to me whether this is the meaning that was intended, nor why a user would want to know about internal style names already... but maybe that's just me. Another place I would change it is p.4 under 1.3.1: "Examples of styles within a family are: ‘roman’, ‘sans serif’ and ‘teletype’" could be clarified as "Examples of styles within a family are: ‘roman’ (which in ConTeXt means ‘serif’), ‘sans serif’ and ‘teletype’". Thanks... your hard work and thick skin are appreciated. :-) Lars ___ 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] columnset running into footer when using \setupheader[state=high]
Jelle Huisman wrote: > % columnset running into footer area > \definelayout[1][] > \setupheader[state=high] > \definetext[footerpagenumber][footer][pagenumber] > \setuphead[chapter][page=yes,header=high,footer=footerpagenumber,number=no,align=middle] > \definecolumnset[columnl][n=2] > \showgrid \showframe > \starttext > \chapter{One} > \startcolumnset[column] > \dorecurse{10}{\input knuth} > \stopcolumnset > \stoptext > > Looking in the mail archive it looks like this is an old problem (see: > http://archive.contextgarden.net/message/20060516.092742.d455b795.en.html > ) but I'm wondering about a solution. Any thoughts? One way around this is to use \setupcolumnsetlines[][][] to balance the columns. With a 1200 page publication: no fun. Jelle ___ 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] setup/switchtobodyfont question
Am 26.11.2008 um 12:43 schrieb Alan STONE: > The main manual mentions (ch 5 Typography, pg 92): > > "In most cases, the command \setupbodyfont is only used once: in the > styledefinition. > Fontswitching is done with \switchtobodyfont. Don't mix these two up > because this may > lead to some rather strange but legitimate effects." > > What's recommended when using a product meta-structure > (standardmakeup-frontmatter- > bodypart-appendices-backmatter) where the bodyfont (and in some > cases also the top, > header, footer, bottom fonts change) from one to the other ? > > Declare one (1) setupbodyfont and switchtobodyfont from one meta- > structure element to the > other or use a dedicated setupbodyfont for each ? From font-ini: The next two macros are user ones. With \setupbodyfont one can set the document bodyfont size, font family, style and/or options defined in files, for example: \setupbodyfont[cmr,ams,12pt,roman] This command affects the document as a whole: text, headers and footers. The second macro however affects only the text: \switchtobodyfont[10pt] Both macros look alike. The second one also has to take all kind of keywords into account. 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] setup/switchtobodyfont question
Same question related to setuplayout. On Wed, Nov 26, 2008 at 12:43 PM, Alan STONE <[EMAIL PROTECTED]>wrote: > The main manual mentions (ch 5 Typography, pg 92): > > "In most cases, the command \setupbodyfont is only used once: in the > styledefinition. > Fontswitching is done with \switchtobodyfont. Don't mix these two up > because this may > lead to some rather strange but legitimate effects." > > What's recommended when using a product meta-structure > (standardmakeup-frontmatter- > bodypart-appendices-backmatter) where the bodyfont (and in some cases also > the top, > header, footer, bottom fonts change) from one to the other ? > > Declare one (1) setupbodyfont and switchtobodyfont from one meta-structure > element to the > other or use a dedicated setupbodyfont for each ? > > -- > Best, > Alan > > * TeX engine = LuaTeX > * ConTeXt minimal ver: 2008.11.10 21:40 MKIV fmt: 2008.11.25 int: > english/english > * Ubuntu 8.04 Hardy Heron > ___ 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] difference between TeX behavior and ConTeXt
Lars Huttar wrote: > > Except perhaps the documentation. I have yet to find a reference that > clearly describes what \rm is to do in ConTeXt. One responder pointed to > http://www.pragma-ade.com/general/manuals/cont-eni.pdf. The closest > thing to a definition of \rm there that I could find is on p. 111: "The > command \rm is used to switch to a roman/serif/regular style,..." In his first reply to your message, Aditya posted the link to the new manual chapter on "Typography". This chapter and the following one "Fonts" are planned to be the definitive answer to all questions regarding fonts and font selection in ConTeXt. If you believe the text could be improved even further beyond the changes already made compared to the manual at Pragma ADE, please tell us how (for sure, the meaning of the macro \rm is not going to change!). We all want the manual to be as good as humanly possible, but it is often quite hard to write at beginners' level when you have advanced past that point yourself. If you can find a good (or at least better) way to express what \rm,\ss,\tt,\hw and \cg do compared to the current prose in co-typography, please post it. Just keep in mind that the manual has to remain independant, so texts that presuppose knowledge of plain TeX and/or LaTeX are not acceptable except as a side/footnote. 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] difference between TeX behavior and ConTeXt
On 11/26/2008 7:43 AM, Lars Huttar wrote: ... > and the word "regular" in typography usually (as far as > I can tell... please enlighten) means "upright" in contrast to italic. I now see that "regular" (apparently less often) can refer to weight: "not bold or light". Still, the point remains. Lars ___ 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] chapter-like headings with separate numbering
Am 26.11.2008 um 12:45 schrieb Sanjoy Mahajan: > "luigi scarso" <[EMAIL PROTECTED]> wrote: > >> It seem that interlude is like a section, so it's correct that at >> every chapter there is a reset of the alphabetical counter > > I meant the interludes to be long examples based upon the preceding > few > chapters. So I think of interludes as at the same level as a chapter. > But your comments suggests an idea: Is there a key=value pair that > says > "Don't ever reset the interlude counter (but do reset section numbers > when a new chapter appears!)?" Use the archive my dear padawan. http://archive.contextgarden.net/message/20030415.153451.374310d8.en.html Regards, 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] difference between TeX behavior and ConTeXt
On 11/26/2008 2:41 AM, Marcin Borkowski wrote: > Dnia Tue, Nov 25, 2008 at 10:30:51PM -0600, Lars Huttar napisał(a): >> It makes sense for "italicness" and "serifity" to be independently >> changeable. >> What's discouraging to me as a entrant to the whole TeX world (but an >> experienced programmer) is the (apparently undocumented) redefinition of >> a well-established control sequence that used to mean "non-italic" to >> mean something different (maybe "serif" -- I still don't know for sure). > > Hi, > > and welcome to the TeX world;). > > Me not being an experienced programmer, but (some kind) of more or less > experienced TeX user, I'd add the following. I appreciate your time and the explanations, from an experienced TeX user. (To all) please pardon the frustration apparent in my previous email, from a TeX and especially ConTeXt newbie. > It is probably true that plain TeX is weird and "incomplete" in a sense. > What \rm means in plain TeX is: "switch to upright, serif font in 10pt > size". This is good to know. However what I'm getting at is not just its concrete definition (implementation) in Plain TeX, but its general intent. The reason I ask that question is this: Knuth makes clear in TeXbook ch. 4 that \rm and other macros are intended to be redefined according to the needs of the book section. Therefore \rm is not intended to remain defined always specifically as "switch to upright, serif font in 10pt size". But it is *not* intended that \rm be defined to mean "reduce the left margin to the dimension provided by the following argument", or even "switch to italic, serif font in 10pt size". Sure you could define \rm to mean anything, but your end users would string you up. Somewhere between those extremes is an intended consistency of meaning for \rm. If it were not so, macro packages would be gibberish, intelligible to the executing processor but intractable for humans. My contention is that the intended "invariant" of \rm semantics, communicated in TeXbook (e.g. exercise 4.2 and the bottom of p. 15), is that of "not italic". > [helpful orientation on the major macro packages snipped] > (and level of frustration), sometimes with LaTeX having more wtf per > minute I had not heard of that metric before. :-) > That's right. I would add one more point: if everyone called the > software of ConTeXt quality "beta", then Windows would be pre-alpha and > a typical GNU/Linux probably something between alpha and beta. Except perhaps the documentation. I have yet to find a reference that clearly describes what \rm is to do in ConTeXt. One responder pointed to http://www.pragma-ade.com/general/manuals/cont-eni.pdf. The closest thing to a definition of \rm there that I could find is on p. 111: "The command \rm is used to switch to a roman/serif/regular style,..." These three terms are not explicitly defined; they are given as names of styles in an illustrative table above. One may apparently assume that the meaning "serif" style here actually is intended to mean that the typeface has serifs (not a trivial assumption: see 'regular'). However the examples of serif/regular/roman in the illustrative table are also all non-italic, and the word "regular" in typography usually (as far as I can tell... please enlighten) means "upright" in contrast to italic. Yet apparently \rm does not switch to "regular" (if that means or includes "upright") in ConTeXt. >> Sorry if the above sounds too negative. After all, the TeXbook itself >> does not make the semantics of \rm obvious. > > Well, it does, but _not_ in the context of changing sizes/styles/etc... Again, I think we're talking about two different things: the original macro definition in Plain TeX, vs. the communicated intended invariant meaning over redefinitions of \rm in various "formats" (Knuth's term which I take to mean macro packages or something like that). >> However, once you dig deep enough it becomes clear that \rm does mean >> "switch to a non-italic typeface" in Plain TeX. > > I'll stress it again: no. In plain TeX, it means "switch to cmr10 at > 10pt", full stop. See previous comment. But even in plain TeX, "switch to cmr10 at 10pt" *does* include switching to a non-italic typeface, which is what I meant here. I didn't mean that in plain TeX \rm means *only* "switch to a non-italic typeface." Sorry that wasn't clear. And the jolt here with ConTeXt is that the meaning of \rm no longer includes "switch to a non-italic typeface", and that this change is not clearly documented. Lars ___ 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] bug in mkii xetex: mp figure is not in the right position
On Wed, Nov 26, 2008 at 5:28 PM, <[EMAIL PROTECTED]> wrote: > ConTeXt peaple always have used to say that ConTeXt is better than LaTeX. > > I have been recieving emails from CoNTeXt list and it seems that ConTeXt has > heaps of bugs. > Staying at an older version of ConTeXt (for example, I always use ConTeXt 2005.01 distributed in teTeX 3.0 for book and journal production) will have less bugs. And if bugs were found in these versions, they were always already been fixed some month after this release, so just copy the related code in the later versions to your tex file and then everything works fine again. (in fact, I found no serious bugs in that version). > > LaTeX rocks...! Latex always run into problems here. hyperlink sometimes give me weird characters (it will always give wierd characters if the link contains CJK characters due to the bug in hyperref, whatever driver and engine you are using). packages are incompatible with each other and always runs into problem (I should keep in mind that package A should loaded before package B, and package A-fix should be place after package B to fix the incompatibility in package A and B, most packages have this problem, just to name a few: memoir, hyperref, amsmath, lucidabr, mnsymbol... ). And I cannot do grid typesetting or other advanced stuffs there. In fact, Plain TeX rocks! If you find bug in plain TeX, you can be famous overnight! (and I also love Karl Berry's eplain format, it's lightweight and powerful.) > > Get a FREE AOL Email account with unlimited storage. Experience Email and > instant messaging together - chat while you mail and mail while you chat! > Register for your free email account at http://free.aol.com.au > > ___ > 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 > ___ > > ___ 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] chapter-like headings with separate numbering
"luigi scarso" <[EMAIL PROTECTED]> wrote: > It seem that interlude is like a section, so it's correct that at > every chapter there is a reset of the alphabetical counter I meant the interludes to be long examples based upon the preceding few chapters. So I think of interludes as at the same level as a chapter. But your comments suggests an idea: Is there a key=value pair that says "Don't ever reset the interlude counter (but do reset section numbers when a new chapter appears!)?" -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 ___
[NTG-context] setup/switchtobodyfont question
The main manual mentions (ch 5 Typography, pg 92): "In most cases, the command \setupbodyfont is only used once: in the styledefinition. Fontswitching is done with \switchtobodyfont. Don't mix these two up because this may lead to some rather strange but legitimate effects." What's recommended when using a product meta-structure (standardmakeup-frontmatter- bodypart-appendices-backmatter) where the bodyfont (and in some cases also the top, header, footer, bottom fonts change) from one to the other ? Declare one (1) setupbodyfont and switchtobodyfont from one meta-structure element to the other or use a dedicated setupbodyfont for each ? -- Best, Alan * TeX engine = LuaTeX * ConTeXt minimal ver: 2008.11.10 21:40 MKIV fmt: 2008.11.25 int: english/english * Ubuntu 8.04 Hardy Heron ___ 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] bug in mkii xetex: mp figure is not in the right position
I am on the wrong list because I just said ``LaTeX rocks''? I would like to apologise you and anyone else from the bottom of my heart if I have offended you and others, but honestly I did not mean it. I am just on this list because I want to study ConText (its TeX programming) more deeply. -Original Message- From: Hans Hagen <[EMAIL PROTECTED]> To: mailing list for ConTeXt users Sent: Wed, 26 Nov 2008 9:00 pm Subject: Re: [NTG-context] bug in mkii xetex: mp figure is not in the right position [EMAIL PROTECTED] wrote: > ConTeXt peaple always have used to say that ConTeXt is better than LaTeX. > > I have been recieving emails from CoNTeXt list and it seems that ConTeXt > has heaps of bugs. ? for sure the luatex/mkiv (not to be confused with pdftex/mkii) pair has heaps of bugs (which are solved at some point) but it's just because we move on and because users here are willing to experiment with new stuff > LaTeX rocks...! then you're on the wrong list -) 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 ___ Get a FREE AOL Email account with unlimited storage. Experience Email and instant messaging together - chat while you mail and mail while you chat! Register for your free email account at http://free.aol.com.au ___ 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] bug in mkii xetex: mp figure is not in the right position
Dnia Wed, Nov 26, 2008 at 11:09:08AM +0100, luigi scarso napisał(a): > On Wed, Nov 26, 2008 at 10:54 AM, Marcin Borkowski < > [EMAIL PROTECTED]> wrote: > > > Dnia Wed, Nov 26, 2008 at 10:38:59AM +0100, luigi scarso napisał(a): > > > On Wed, Nov 26, 2008 at 10:28 AM, <[EMAIL PROTECTED]> wrote: > > > > > > > ConTeXt peaple always have used to say that ConTeXt is better than > > LaTeX. > > > > > > yes, true. > > > > Not entirely (see below). > > > please, note: > not **all** context peaple (whatever peaple means!) > have used to say that ConTeXt is better than LaTeX, > but **some** context peaple (I, for example, assuming peaple == people ) > You are a counter example . > So the statement is ** entirely true **. ok, I give up;) > > > > > > > Also > > > LaTeX peaple always have used to say that LaTeX is better than ConTeXt > > > is true > > > > > > yes, as before > > > > > > > > > > > > > > I have been recieving emails from CoNTeXt list and it seems that > > ConTeXt > > > > has heaps of bugs. > > > > > > > > > > There are some bugs. > > > > As in most software projects. And, that;s true, there _are_ lots of > > bugs in ConTeXt. But still, it is very usable. > > > "lots of bug" and "still very usable" > are contradictory statemens . No. Most popular case: M$ Windows (although personally I'll argue about their "usability";)). The point is that ConTeXt bugs do not crash it in usual scenarios, but rather when some complex interactions are involved. So usually everything is fine, _unless_ you want something strange. And then - well, _strange_ things do happen. > > > > > > > > > > > > > > > > LaTeX rocks...! > > > > > > true, if you are from LaTeX peaple. > > > > see before . > > > > > > > > > > > -- > > Marcin Borkowski (http://mbork.pl) > > > > Emacs: Escape-Meta-Alt-Control-Shift. > > > true . ** entirely true **. Glad you like it. (Personally, I use both emacs and vim. Really.) BTW: do you know what "vim" means? It is an old African word meaning "how do you quit this f#g s##t?" Greets -- Marcin Borkowski (http://mbork.pl) People can be divided into three groups: those who can count and those who can't. ___ 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] bug in mkii xetex: mp figure is not in the right position
[EMAIL PROTECTED] wrote: > ConTeXt peaple always have used to say that ConTeXt is better than LaTeX. > > I have been recieving emails from CoNTeXt list and it seems that ConTeXt > has heaps of bugs. ? for sure the luatex/mkiv (not to be confused with pdftex/mkii) pair has heaps of bugs (which are solved at some point) but it's just because we move on and because users here are willing to experiment with new stuff > LaTeX rocks...! then you're on the wrong list -) 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] Weighted colors in MkIV
Hi, in MkIV there is a problem when I set tints for a color. This is a complete minimal example of my setup: \setupcolors[state=start,rgb=no,cmyk=yes,spot=yes] % rgb= no needed in MkII \setupcolor [hex] \definecolor[PantoneOneEightSeven][h=C40F2F,e=Pantone 187 U] \definespotcolor[dtkred] [PantoneOneEightSeven][p=1.0] \definespotcolor[dtkredlight][PantoneOneEightSeven][p=0.7] \starttext \blackrule[width=4cm,height=4cm,color=dtkred,] \blackrule[width=4cm,height=4cm,color=dtkredlight] \stoptext I could also reproduce it with a short setup: \setupcolors[state=start,rgb=no] % rgb= no needed in MkII \definespotcolor[dtkred] [red][p=1.0] \definespotcolor[dtkredlight][red][p=0.7] \starttext \blackrule[width=4cm,height=4cm,color=dtkred,] \blackrule[width=4cm,height=4cm,color=dtkredlight] \stoptext With the setting rgb=yes the color dtkred is correct in the output but dtkredlight is darker than dtkred, with the setting rgb=no dtkred is black in my 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 : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] difference between TeX behavior and ConTeXt
Lars Huttar wrote: > Interesting. > As a newbie to typesetting, reading the TeXbook, I certainly wondered > which "axes" Knuth meant 'roman' to refer to... he simply describes it > as 'normal "roman"' and gives a visual example. So far, all I'd gathered > was that it meant "not italic." you should keep in mind that plain tex is not meant as general puspose macro package but as base under Don Knuths own book related styles for instance, there is no general font system, just a bunch of definitions related to computer modern and math; also there is some math setup, some register management, some structure commands and a bit of tabular stuff at that time i think that the general idea was that one would write a style for each book (or series) and that a plain like package can be used as basis context is (like latex, lamstex, inrstex, amstex, ...) a more generic and configurable macro package both methods (dedicated vs generic) have their (dis)advantages > If it's designed not to do that in ConTeXt -- i.e. the ConTeXt designers > decided to change the semantics of one of the basic control sequences in > TeX, rather than merely providing a different one with new semantics -- not in tex, since tex itself has no macros defined, but in plain tex 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] bug in mkii xetex: mp figure is not in the right position
On Wed, Nov 26, 2008 at 11:20 AM, Yue Wang <[EMAIL PROTECTED]> wrote: > Hi: > > > Please, shut up and code: we need to fix these bugs first! > For statistical reasons, we need some amount of flare wars and off-topics -- 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 : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] bug in mkii xetex: mp figure is not in the right position
Hi: Please, shut up and code: we need to fix these bugs first! Yue Wang On Wed, Nov 26, 2008 at 5:54 PM, Marcin Borkowski <[EMAIL PROTECTED]> wrote: > Dnia Wed, Nov 26, 2008 at 10:38:59AM +0100, luigi scarso napisał(a): >> On Wed, Nov 26, 2008 at 10:28 AM, <[EMAIL PROTECTED]> wrote: >> >> > ConTeXt peaple always have used to say that ConTeXt is better than LaTeX. >> >> yes, true. > > Not entirely (see below). > >> Also >> LaTeX peaple always have used to say that LaTeX is better than ConTeXt >> is true >> >> >> > >> > I have been recieving emails from CoNTeXt list and it seems that ConTeXt >> > has heaps of bugs. >> > >> >> There are some bugs. > > As in most software projects. And, that;s true, there _are_ lots of > bugs in ConTeXt. But still, it is very usable. > >> >> >> > >> > LaTeX rocks...! >> >> true, if you are from LaTeX peaple. > > Well, I've been using LaTeX for several years and I don't think it to be > really rocking. And neither is ConTeXt (yet) - see below. > > And the question is: why to start yet another flame war? > > I am the proof (by example) that the sets of plain TeX people, LaTeX > people and ConTeXt people have a nonempty intersection. There are areas > where LaTeX is much better than ConTeXt: when I write a paper on maths, > almost no journal will accept ConTeXt. Also, LaTeX is very stable and > ConTeXt is not. OTOH, when ConTeXt reaches the maturity level of LaTeX, > it _will_ be much better - but we'll have to wait a while for it to > happen. > > Greets > > -- > Marcin Borkowski (http://mbork.pl) > > Emacs: Escape-Meta-Alt-Control-Shift. > ___ > 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 > ___ > ___ 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] bug in mkii xetex: mp figure is not in the right position
On Wed, Nov 26, 2008 at 10:54 AM, Marcin Borkowski < [EMAIL PROTECTED]> wrote: > Dnia Wed, Nov 26, 2008 at 10:38:59AM +0100, luigi scarso napisał(a): > > On Wed, Nov 26, 2008 at 10:28 AM, <[EMAIL PROTECTED]> wrote: > > > > > ConTeXt peaple always have used to say that ConTeXt is better than > LaTeX. > > > > yes, true. > > Not entirely (see below). > please, note: not **all** context peaple (whatever peaple means!) have used to say that ConTeXt is better than LaTeX, but **some** context peaple (I, for example, assuming peaple == people ) You are a counter example . So the statement is ** entirely true **. > > > Also > > LaTeX peaple always have used to say that LaTeX is better than ConTeXt > > is true > > > yes, as before > > > > > > > > > I have been recieving emails from CoNTeXt list and it seems that > ConTeXt > > > has heaps of bugs. > > > > > > > There are some bugs. > > As in most software projects. And, that;s true, there _are_ lots of > bugs in ConTeXt. But still, it is very usable. > "lots of bug" and "still very usable" are contradictory statemens . > > > > > > > > > > LaTeX rocks...! > > > > true, if you are from LaTeX peaple. > see before . > > > > -- > Marcin Borkowski (http://mbork.pl) > > Emacs: Escape-Meta-Alt-Control-Shift. > true . ** entirely true **. (^___^) -- 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 : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] difference between TeX behavior and ConTeXt
Marcin Borkowski wrote: > Me not being an experienced programmer, but (some kind) of more or less > experienced TeX user, I'd add the following. ... makes a nice 'about tex systems' page for the wiki - 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] embedding 3d pdf
On Wed, Nov 26, 2008 at 9:16 AM, Michail Vidiassov <[EMAIL PROTECTED]>wrote: > Dear All, > > Renaud Aubin wrote: > > See http://www.nibua-r.org/ConTeXt/devel/ > > while the macros there are a great improvement from > what was posted on the list and look extandable for my purposes > (thanks, Renaud), > the other question remains - does it make sense to try to implement > 3d model embedding in proper way for public use now or the underlying > luatex/context part has not been developed/updated yet? > > LuaTeX roadmap promised that > "Think of annotations and object management. The first code will show up > later in 2008." > Did it? > Is there a ConTeXt API to it? > Is it planned to come in some future? > Or spec-pdf dated 1997.09.20 is what we are to live with? > > Sincerely, Michail > > BTW, If you are able to make some samples with context mkiv, please do them and then wikifi it. Something is better than nothing . ___ 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] bug in mkii xetex: mp figure is not in the right position
Dnia Wed, Nov 26, 2008 at 10:38:59AM +0100, luigi scarso napisał(a): > On Wed, Nov 26, 2008 at 10:28 AM, <[EMAIL PROTECTED]> wrote: > > > ConTeXt peaple always have used to say that ConTeXt is better than LaTeX. > > yes, true. Not entirely (see below). > Also > LaTeX peaple always have used to say that LaTeX is better than ConTeXt > is true > > > > > > I have been recieving emails from CoNTeXt list and it seems that ConTeXt > > has heaps of bugs. > > > > There are some bugs. As in most software projects. And, that;s true, there _are_ lots of bugs in ConTeXt. But still, it is very usable. > > > > > > LaTeX rocks...! > > true, if you are from LaTeX peaple. Well, I've been using LaTeX for several years and I don't think it to be really rocking. And neither is ConTeXt (yet) - see below. And the question is: why to start yet another flame war? I am the proof (by example) that the sets of plain TeX people, LaTeX people and ConTeXt people have a nonempty intersection. There are areas where LaTeX is much better than ConTeXt: when I write a paper on maths, almost no journal will accept ConTeXt. Also, LaTeX is very stable and ConTeXt is not. OTOH, when ConTeXt reaches the maturity level of LaTeX, it _will_ be much better - but we'll have to wait a while for it to happen. Greets -- Marcin Borkowski (http://mbork.pl) Emacs: Escape-Meta-Alt-Control-Shift. ___ 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] bug in mkii xetex: mp figure is not in the right position
Dnia Wed, Nov 26, 2008 at 04:28:35AM -0500, [EMAIL PROTECTED] napisał(a): > ConTeXt peaple always have used to say that ConTeXt is better than LaTeX. > > I have been recieving emails from CoNTeXt list and it seems that ConTeXt has > heaps of bugs. > > > LaTeX rocks...! Sorry, but I just can't resist a joke: what you call a "bug" in ConTeXt world is called a "feature" in LaTeX. And to be more serious: I think I was rather fair in my previous post on the difference between (plain) TeX and ConTeXt. Also, LaTeX is "frozen" in some sense: the latest news on the LaTeX project site comes from 2005, IIRC. So the LaTeX "core" (or "kernel") is very stable (and, one has to admit, has very few bugs - and very limited features...). And LaTeX packages are quite a jungle. But still: there are lots of them which are very stable (or frozen), and some which are under constant development (pgf, for instance). Also, LaTeX documents are (usually) much simpler than ConTeXt documents, so it is much easier to have few bugs - there is less room for complex interactions (aside from package clashes, which happen from time to time). So if you want a stable document preparation and markup system with a large userbase, though sometimes limited functionality (try to do a two-column enumerate in LaTeX automatically, something like: 1) ...3) ... 2) ...4) ... without resorting to general multicolumn hackery - and the multicol package, which is not entirely free!), then yes, LaTeX is better. And if you want some features _not_ present in LaTeX or you need to typeset _really_ complex documents (complex in terms of layout, for example), or your documents are not scientific papers then ConTeXt is probably better. Greets -- Marcin Borkowski (http://mbork.pl) Szema Izrael: Adonai Elohenu, Adonai Ehad! ___ 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] embedding 3d pdf
Michail Vidiassov wrote: > Dear All, > > Renaud Aubin wrote: >> See http://www.nibua-r.org/ConTeXt/devel/ > > while the macros there are a great improvement from > what was posted on the list and look extandable for my purposes > (thanks, Renaud), > the other question remains - does it make sense to try to implement > 3d model embedding in proper way for public use now or the underlying > luatex/context part has not been developed/updated yet? > > LuaTeX roadmap promised that > "Think of annotations and object management. The first code will show up > later in 2008." > Did it? > Is there a ConTeXt API to it? > Is it planned to come in some future? > Or spec-pdf dated 1997.09.20 is what we are to live with? spec-fdf and spec-pdf are occasionally extended (but nowadays pdf itself is not so much evolving) there will bea dedicated luatex/mkiv backend module next year; first i need to rewrite lots of other code (currently i'm redoing the reference related code, and when that's done, the backend rewriting is easier) 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] bug in mkii xetex: mp figure is not in the right position
moreover, setupinteraction[state=start, focus=normal] and \goto will always point to the wrong position in xetex. On Wed, Nov 26, 2008 at 5:21 PM, Wolfgang Schuster <[EMAIL PROTECTED]> wrote: > > Am 26.11.2008 um 10:04 schrieb Yue Wang: > >> hi: >> >> it seems that mpfigure will be in the wrong position using the xetex >> engine. >> here is the sample file: >> >> % engine=xetex >> >> \starttext >> >> \setupcolors >> [state=start] >> >> \startMPpage >> path p ; color c[] ; >> p := fullsquare scaled 4cm ; >> c[0] := transparent(1,.5,red) ; >> c[1] := transparent(1,.5,green) ; >> c[2] := transparent(1,.5,blue) ; >> for i = 0 upto 2 : >>fill p rotated (i*30) withcolor white ; >> endfor ; >> for i = 0 upto 2 : >>fill p rotated (i*30) withcolor c[i] ; >> endfor ; >> addbackground withcolor transparent(1,.5,cmyk(0,0,1,0)) ; >> \stopMPpage >> >> \stoptext > > Make a entry in the bug tracker or it will be fogotten, > I had a similiar problem quite some time ago: > > http://archive.contextgarden.net/message/20080812.085450.3b06d189.en.html > > 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 > ___ > ___ 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] bug in mkii xetex: mp figure is not in the right position
On Wed, Nov 26, 2008 at 10:28 AM, <[EMAIL PROTECTED]> wrote: > ConTeXt peaple always have used to say that ConTeXt is better than LaTeX. > > I have been recieving emails from CoNTeXt list and it seems that ConTeXt has > heaps of bugs. > > LaTeX rocks...! "Anyone who has never made a mistake has never tried anything new." (A. Einstein) ___ 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] bug in mkii xetex: mp figure is not in the right position
On Wed, Nov 26, 2008 at 10:28 AM, <[EMAIL PROTECTED]> wrote: > ConTeXt peaple always have used to say that ConTeXt is better than LaTeX. yes, true. Also LaTeX peaple always have used to say that LaTeX is better than ConTeXt is true > > I have been recieving emails from CoNTeXt list and it seems that ConTeXt > has heaps of bugs. > There are some bugs. > > LaTeX rocks...! true, if you are from LaTeX peaple. -- 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 : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] bug in mkii xetex: mp figure is not in the right position
ConTeXt peaple always have used to say that ConTeXt is better than LaTeX. I have been recieving emails from CoNTeXt list and it seems that ConTeXt has heaps of bugs. LaTeX rocks...! Get a FREE AOL Email account with unlimited storage. Experience Email and instant messaging together - chat while you mail and mail while you chat! Register for your free email account at http://free.aol.com.au ___ 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] bug in mkii xetex: mp figure is not in the right position
Am 26.11.2008 um 10:04 schrieb Yue Wang: > hi: > > it seems that mpfigure will be in the wrong position using the xetex > engine. > here is the sample file: > > % engine=xetex > > \starttext > > \setupcolors > [state=start] > > \startMPpage > path p ; color c[] ; > p := fullsquare scaled 4cm ; > c[0] := transparent(1,.5,red) ; > c[1] := transparent(1,.5,green) ; > c[2] := transparent(1,.5,blue) ; > for i = 0 upto 2 : >fill p rotated (i*30) withcolor white ; > endfor ; > for i = 0 upto 2 : >fill p rotated (i*30) withcolor c[i] ; > endfor ; > addbackground withcolor transparent(1,.5,cmyk(0,0,1,0)) ; > \stopMPpage > > \stoptext Make a entry in the bug tracker or it will be fogotten, I had a similiar problem quite some time ago: http://archive.contextgarden.net/message/20080812.085450.3b06d189.en.html 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] bug in mkii xetex: mp figure is not in the right position
hi: it seems that mpfigure will be in the wrong position using the xetex engine. here is the sample file: % engine=xetex \starttext \setupcolors [state=start] \startMPpage path p ; color c[] ; p := fullsquare scaled 4cm ; c[0] := transparent(1,.5,red) ; c[1] := transparent(1,.5,green) ; c[2] := transparent(1,.5,blue) ; for i = 0 upto 2 : fill p rotated (i*30) withcolor white ; endfor ; for i = 0 upto 2 : fill p rotated (i*30) withcolor c[i] ; endfor ; addbackground withcolor transparent(1,.5,cmyk(0,0,1,0)) ; \stopMPpage \stoptext Yue Wang ___ 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] difference between TeX behavior and ConTeXt
On Tue, Nov 25 2008, Lars Huttar wrote: > If it's designed not to do that in ConTeXt -- i.e. the ConTeXt designers > decided to change the semantics of one of the basic control sequences in > TeX, rather than merely providing a different one with new semantics -- > you would think one would want that to be prominently documented. (Maybe > some flashing orange lights? :-) Hello Lars, It's in chapter 5 of the user manual (without flashing orange lights): http://www.pragma-ade.com/general/manuals/cont-eni.pdf or http://www.pragma-ade.com/general/manuals/cont-enp.pdf 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 ___
Re: [NTG-context] difference between TeX behavior and ConTeXt
Dnia Tue, Nov 25, 2008 at 10:30:51PM -0600, Lars Huttar napisał(a): > It makes sense for "italicness" and "serifity" to be independently > changeable. > What's discouraging to me as a entrant to the whole TeX world (but an > experienced programmer) is the (apparently undocumented) redefinition of > a well-established control sequence that used to mean "non-italic" to > mean something different (maybe "serif" -- I still don't know for sure). Hi, and welcome to the TeX world;). Me not being an experienced programmer, but (some kind) of more or less experienced TeX user, I'd add the following. In general, there are three 'mainstream' TeX macropackages: plain TeX (say, plus AMSTeX), LaTeX and ConTeXt. It seems that the majority of the TeX world uses LaTeX; most people, when they say "TeX", mean essentially "LaTeX". LaTeX is a a big beast, and if you are new to TeX _and_ don't want to submit papers to math/cs journals (which are seldom aware of ConTeXt, I'm afraid), learning LaTeX may not be exactly what you want. There is also a very small minority using plain TeX (including Knuth, who doesn't use LaTeX; he was once asked why, and said: "I'm afraid of large systems";)). The TeXbook is about two things: plain TeX and using the TeX engine itself. Then there is another minority (but growing, I believe) of ConTeXt users. For example, I am a plain-to-LaTeX and then (after 5 years or so) LaTeX-to-ConTeXt convert (still using LaTeX when writing papers which I want to submit somewhere, though, and plain TeX when doing something really atypical). It is probably true that plain TeX is weird and "incomplete" in a sense. What \rm means in plain TeX is: "switch to upright, serif font in 10pt size". It _might_ be modified (in the TeXbook spirit) to, e.g., "switch to upright, serif font in _current_ size" - but please note that plain TeX itself has _no_ notion of "current size" (or, in other words, "current size" in plain TeX is fixed at 10pt). What Knuth mentions in the TeXbook is that you might want to write some macros to introduce something like a flexible "current size" - he even shows how to do it in Appendix E - but it is no longer plain vanilla TeX then! So what you did was to extrapolate plain TeX's meaning of \rm to a situation outside plain TeX itself (although in Knuthian spirit). So, everything I said above is trivial when applied just to \rm, but I wanted to try to explain the differences between plain TeX, LaTeX and ConTeXt. So to finish this explanation, I would say the following: * Plain TeX is a DIY thing. Cross-references, automatic numbering of chapters etc., bibliographies, including graphics, etc., etc. - forget it, it just isn't there. This is very fine if you're doing something really unusual (and this happens from time to time) and don't need such features, but you want to _exactly_ know what is happening where: plain TeX is small and easy to grasp (at least, when compared to LaTeX or ConTeXt). * LaTeX is what they call a "document preparation system", but that's a lie. LaTeX is a "scientific paper/monograph preparation system"; you _may_ typeset a cookbook, a school test, or a software manual in LaTeX, but it is a (sometimes small, sometimes big) pain. It is just not the best tool. Of course, it flexible, extensible, even Turing complete, so you can do everything - but it is sometimes like simulating recursion in BASIC using arrays as a stack: possible, but no-one would like to do it. The popularity of LaTeX caused, however, the situation when there is a LaTeX package for everything (and sometimes even three of them, each with different set of features and bugs...), so the pain is (usually) not that big, but still sometimes writing stuff in LaTeX is not very comfortable. * ConTeXt is something much more universal than LaTeX - without the scientific bias - but probably less stable than LaTeX, less documented and with smaller userbase (but: smaller does not mean less active nor less helpful!). The flexibility of plain TeX, LaTeX and ConTeXt is obviously similar (well, with ConTeXt actually bigger since the advent of luatex), but it is sometimes _very_ different in terms of easiness (and level of frustration), sometimes with LaTeX having more wtf per minute and sometimes ConTeXt. It seems, however, that Hans considered much more special cases when writing ConTeXt, so many thing are more natural in ConTeXt than in LaTeX (where even simplest things sometimes need an external package - for example, changing the style of enumerations). > If I were choosing a TeX macro package at this point, I would definitely > look for one that kept semantics of basic TeX command sequences > consistent with the intent expressed in the TeXbook... to avoid package > lock-in, as well as to make the learning curve easier and to be able to > use the resources of the whole TeX community. As said - almost no-one uses plain TeX. Both LaTeX and ConTeXt claim to be "built on top of plain TeX", but in b
Re: [NTG-context] embedding 3d pdf
Dear All, Renaud Aubin wrote: > See http://www.nibua-r.org/ConTeXt/devel/ while the macros there are a great improvement from what was posted on the list and look extandable for my purposes (thanks, Renaud), the other question remains - does it make sense to try to implement 3d model embedding in proper way for public use now or the underlying luatex/context part has not been developed/updated yet? LuaTeX roadmap promised that "Think of annotations and object management. The first code will show up later in 2008." Did it? Is there a ConTeXt API to it? Is it planned to come in some future? Or spec-pdf dated 1997.09.20 is what we are to live with? Sincerely, Michail ___ 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] chapter-like headings with separate numbering
On Tue, Nov 25, 2008 at 4:08 AM, Sanjoy Mahajan <[EMAIL PROTECTED]> wrote: > I'm experimenting with making a heading that is like a chapter in format > but has its own numbering (or lettering). The purpose to have an > interlude, or extended example, every few chapters. The following > almost-minimal example almost does so. However, the second interlude is > numbered with 'A' instead of 'B'. Is there a missing key=value pair, or > is the approach completely wrong? > It seem that interlude is like a section, so it's correct that at every chapter there is a reset of the alphabetical counter > > \definesection[nc] > \setupsection[nc][conversion=Characters] > \definehead[interlude][section=nc,default=chapter] > \setuphead[interlude][incrementnumber=yes] > > \starttext > > \title{Contents} > \placelist[chapter,interlude] > > \chapter{Chap 1} > > \interlude{Interlude 1} > > \chapter{Chap 2} > > \interlude{Interlude 2} > > \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 > > ___ > -- 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 : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___