- ntg-context - Mailing Lists

RE: [NTG-context] footnote reference mark font switch
by Idris Samawi Hamid 14 Apr '05

14 Apr '05

Hi Adam and all... >===== Original Message From "Adam Lindsay" <atl(a)comp.lancs.ac.uk> ===== >\setupfootnotes[style=italic,textcommand=,command=,textstyle=boldslanted] Ok, now we're getting somewhere... The setup you presented was overkill-) but very instructive: 1. \setupfootnotes[style=italic,textcommand=,command=,textstyle=boldslanted] i. This changes the footnote marker in the main text (marker1), but also makes it a regular numeral aligned with the pre-footnote text. b. The footnote marker in the note (marker2) also becomes aligned with the text of the note. c. Marker1 is boldit and marker2 is italic. d. Running text is normal; 2. \setupfootnotes[style=italic,command=,textstyle=boldslanted] Marker1 is now super, marker2 is text-aligned, marker1 is boldit and marker2 is italic. 3. \setupfootnotes[command=,textstyle=boldslanted] Marker1 is super, marker2 is text-aligned, marker1 is bold, and marker 2 is normal; 4. \setupfootnotes[textstyle=boldslanted] Marker1 is super, marker2 is super, marker1 is bold, marker2 is normal; 5. \setupfootnotes[style=italic,textstyle=boldslanted] Both markers are super, marker2 is italic and marker1 is boldit. ======== This last is the one I was looking for. \setupfootnotes[style=\it,textstyle=\bs] also works. This is interesting, because I thought that all options involving control sequences had to be surrounded by curly brackets. With curly brackets it does not work. Thank you for your help! And that trick is forthcoming... Best Idris ============================ Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523

1 0

footnote reference mark font switch
by Idris Samawi Hamid 14 Apr '05

14 Apr '05

Dear cartel, I need to switch to a different font for the footnote reference markers. First attempt failed: ======================= % output=pdf interface=en \setupfootnotes[before=\ss,after=\sc] \starttext This is a test.\footnote{This is a test} \stoptext ======================= The idea is to print the reference marker, in this case `1', in a different font from both the main text and from the footnote text. That is, \setupfootnotes should let me transparently distinguish between 1. main text font; 2. reference marker font 3. footnote text font. Please advise, and I have a nice trick to show you once this is done:-) Best Idris ============================ Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523

3 4

\definetype[...][option=...] problems
by Nikolai Weibull 14 Apr '05

14 Apr '05

Try running \setupcolors[state=start] \definetype[JS][option=JS] \starttext \JS{function}\par \JS{function }\par \JS{ function}\par \JS{ function } \stoptext The first paragraph will only be the first character, f, the reason is made clear from the following two paragraphs. In the second paragraph, function comes out, but it isn't highlighted as a keyword, as the initial f has been consumed and thus the "unction" part doesn't match any keywords. I guess this is due to the type-handling checking for double characters, like in \type<< ... >>? In the third paragraph, only the initial space is output. The rest will never be output, as \PLsequence never gets a chance to be printed. Only in the fourth paragraph is "function" output correctly, although it is now surrounded by two spaces. Any suggestions on possible solutions, other than removing the option=JS?, nikolai -- Nikolai Weibull: now available free of charge at http://bitwi.se/! Born in Chicago, IL USA; currently residing in Gothenburg, Sweden. main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}

1 0

confused on which table
by Paul Tremblay 13 Apr '05

13 Apr '05

I'm looking over the table overview at the wiki garden: http://contextgarden.net/Tables_Overview It states that: "ConTeXt has a whole bunch of possibilities to typeset tables. Not each provides everything you may need, and the older ones are deprecated." Yet on looking at all of the different types of tables, I can't exactly see which ones are deprecated. Are any deprecated? I also see that there are three different types of tables for spanning across pages ("\starttablehead", "\bTABLE", and "\startlinetable"). Do each of these have strengths and weaknesses? Perhaps I could make a table for each type of tables, if someone could guide me: name tabulate TaBlE etable ETC =================================== Use short table Notes does not have vertical lines ETC. Thanks for whoever did this wiki page, since it is helping me get started. Paul -- ************************ *Paul Tremblay * *phthenry(a)iglou.com * ************************

4 9

page number in \cite
by Robert Ullrey 13 Apr '05

13 Apr '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I apologize because I swear I just saw the answer to this, but I can not find it in my achieves. Is there a way, or work around, to place pagenumbers in a \cite? For example, see (T. Hoekwater, 1994, pp 12-14). I have use (I think) \cite[pp 127-129]{key} in Latex, what I would love though is in ConTeXt to use \cite[hoekwater94{pp 123-129}] to get {T.Hoekwater, 1994, pp 123-129). I have a paper I am trying to meet the these guidelines on <http://journal.philsci.org/Guidelines/> Thanks, Robert -----BEGIN PGP SIGNATURE----- Version: PGP 8.1 iQA/AwUBQlv9WvFTYcwurb3FEQLGyQCgxo0FCBAob3CkNWHlg1wxdtphyigAn1ny luOol3vLSlaH72hy/h7jCi5W =ri1O -----END PGP SIGNATURE-----

2 2

bib translation
by Patrick Gundlach 13 Apr '05

13 Apr '05

Hello out there, in a bibliography created by Tacos' module I have something like this: Knuth, D. E. and Plass, M. F. (1999). Breaking paragraphs into lines. In Digital Typography, pages 67–155. CSLI Publications. Ursrpünglich publiziert in Software – Practice and Experience 11 (1981), 1119–1184. But now I'd like to have 'und' instead of 'and', 'Seiten' instead of 'pages' etc. What is the suggested way to do this? Patrick -- ConTeXt wiki and more: http://contextgarden.net

2 4

formatted pagenumbers in registers
by sjoerd siebinga 13 Apr '05

13 Apr '05

I have noticed a strange irregularity in the formatting of pagenumbers in one of my registers. Somehow not every pagenumber that should be bold has been rendered bold. I have defined this register as follows. <cite> \defineregister[indexri][Dialect of Riustring 1] % \setupregister[indexri][lemma][pagestyle=bold] </cited> Does anyone know how to solve this problem? Sjoerd

1 0

MetaPost 0.893 announcement
by Taco Hoekwater 13 Apr '05

13 Apr '05

The MetaPost team is happy to announce the release of a new beta: ---------------------------------------------------------------------- MetaPost 0.893 (beta for 0.9) ---------------------------------------------------------------------- This is a public beta release for the upcoming version 0.9. The sources and a win32 package can be downloaded immediately from http://sarovar.org/projects/metapost/ 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 fptex or a similar web2c-based installation, and has been tested only with TeXLive 2003. The executables will *not* work for miktex, sorry. After beta testing, this version will hopefully become the next official release of MetaPost, at the end of April 2005. That is roughly two weeks from today, so test reports are very welcome. 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 this message for a more formal way to report bugs and feature requests. For those of you who have noted the large gap between 0.641 and 0.9: We have deliberately chosen to step over some minor version numbers, such that the first major release by the current team (this release is planned for the autumn of 2005) can become version 1.0 without causing additional confusion. ---------------------------------------------------------------------- What is new in version 0.9: ---------------------------------------------------------------------- 1. There is a new internal quantity called mpversion that reports the current metapost version, and the version information is also written to the PostScript file. 2. The LaTeX sources of the mpman, mpintro, and mpgraph manuals have become part of the distribution package. 3. TEX.mp now has TeX format support through a pair of macros called TEXPRE() and TEXPOST(). This llows you to process the contents of the TEX() macro with, for example, LaTeX (instead of plain TeX). An example is given in the manual. 4. metapost now writes a %%HiReSBoundingBox comment 5. The EPS output no longer contains actual spaces within PostScript strings as for example output by label("a space"), but their octal escape (\040) instead. 6. The EPS output now also has a %%BeginProlog DSC comment as well as %%EndProlog 7. The comments in the Web source have been changed to point out that on modern machines, acquiring the random seed has actually become a system-dependant operation (a granularity of whole seconds is not small enough on new machines). 8. The 'newer' command now accepts more than 2 arguments, testing each of the files in turn. ---------------------------------------------------------------------- Bugfixes in version 0.9: ---------------------------------------------------------------------- 1. Documentation improvements: all known errata and typos have been removed, better explanations of e.g. dash patterns and dotlabel have been provided, and a number of omissions has been rectified. 2. The BoundingBox was not computed correctly when a filldraw command with a noticeable pen size was used at the edge of the picture. 3. Paths starting with degenerate constructions like (0,0)--(0,0)--(0,0) could overflow memory. 4. The PostScript output could accidentally contain 8-bit characters within PostScript strings in previous versions because a test was shared between terminal printing and PostScript printing. 5. A bug has been found in the assignment of serial numbers to independant variables in metafont 2.71828. This bug affected MP as well, and the same patch has been applied. 6. The turningnumber was sometimes wrong in unexpected ways. The new implementation is still sometimes wrong (when there are strange path segments involved), but in a much more predictable way: the new code always draws straight lines between the actual points, and calculates the turningnumber based on that path instead of the actual path. The effect is that cusps and loops within segments are now completely ignored. A more thorough fix of turningnumber is planned for the next release. 7. There was an 'off by one' error in dvitomp wrt. the interpretation of virtual fonts. 8. mpto uses a new TeX macro for the generation of labels, making it more robust wrt. strange user code within the actual label text. 9. A missing colon in boxes.mp has been added 10. A missing save in mfplain.mp has been added 11. The generisize in boxes.mp has been fixed so that it now accepts [[ as a valid variable name ---------------------------------------------------------------------- Legal notice / license / bug reports ---------------------------------------------------------------------- MetaPost is a system for producing graphics developed by John Hobby at AT&T, 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 Sarovar, http://www.sarovar.org/projects/metapost; please report bugs and request enhancements through there if possible. Alternatively, you can reach us through the <metapost(a)tug.org> mailing list as well. (Please do not send bug reports or feature requests directly to Dr. Hobby any more) Have fun! Taco Hoekwater, for the MetaPost team, April 12, 2005 _______________________________________________ metapost mailing list http://tug.org/mailman/listinfo/metapost

1 0

Re: ntg-context Digest, Vol 10, Issue 21
by Kai Straube 12 Apr '05

12 Apr '05

Am Freitag, 8. April 2005 09:55 schrobst Du: > Kai Straube wrote: > > ! Undefined control sequence. > > l.15 \startfontclass > > [modern] > > > > Whats wrong? > > different version than mine -) Thank you, this does it! But (sorry, the questions never ending) how can I get the sansserif-font in formulas in bold letters? Kai

1 0

RE: [NTG-context] Encoding and mapping glyphs from an expert font
by Idris Samawi Hamid 12 Apr '05

12 Apr '05

Hi Thomas, Adam, and all... >===== Original Message From "Thomas A.Schmitz" <thomas.schmitz(a)uni-bonn.de> >So there is no simple answer to your question. TeX knows to pick up >zerooldstyle instead of zero either >1. because you have a virtual font that says MAPFONT 1, so it knows it >will have to use a different pfb than for the rest, or >2. because the encoding file points to character zerooldstyle within >the ttf. You are right. I just realized that I misunderstood what Hans meant by avoiding virtual fonts: I was assuming all this time that the \usetypescript[map][latin-modern-os][texnansi] setup was mapping latin modern to cmmi10, etc. I looked at the log of a test file for latin-modern-os: no mention of cmmi10, etc. I looked at the pdf, listed all fonts, and boom, only one font, lmr12.pfb. I opened lmr12 in FontLab and, lo and behold, it contains a palette of old style numerals! So what Hans meant was that there is no need for a virtual font to remap lmr itself, not that you could actually map the numerals of lmr to cmmibi without a virtual font. The OldStyle to MathItalic mappings are apparently useful for local switches like \os, but not for global setups. Oh well, I certainly learned a lot about fonts and ConTeXt this past day-and-a-half, so I guess it was not a total waste of time. Now I guess I have to make some virtual fonts (sigh), so it's now on to Thomas' how-to. Thnx to all Idris ============================ Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523

2 1