- ntg-context - NTG Mailing Lists

proposed convention for variation switching [wasRE:inheriting ...
by Idris Samawi Hamid 22 Apr '05

22 Apr '05

>===== Original Message From "Adam Lindsay" <atl(a)comp.lancs.ac.uk> ===== >I don't have time to really delve into the implementation details, but it >looks like the difference is that ConTeXt isn't so responsive with user- >defined alternatives with more than two characters. Compare the stripped >down version with your own. Your \scsb has been changed to \SB, effectively. Hmm, I was a little worried at first about >2-char switches at first, till I noticed that type-siz.tex uses some four-letter switches as well, e.g. ============line-575============== \definebodyfont [12pt] [mm] [mrbf=xcmb12, exbf=cmex10 at 12pt, mibf=cmmib10 at 12pt, sybf=cmbsy10 at 12pt] ===================================== So I assumed that such a scheme would work. My suggestion: Either a) the \*a(b)(c) etc mechanism needs modification to accomodate >2-char switches, or b) an official 2-char switching convention for dealing with semibold and the standard five variants of small caps in ConTeXt is needed. Ideally users should not have to define switches for these standard variants anyway. Here is an idea (further discussion needed): a) Let's assume no change to the ConTeXt internals to accomodate >2-char switches. b) There are twelve basic style variants in a professional modern serif font (math, greek, etc excluded): six for lower case and six for small caps. On this basis, here is my suggestion for an official ConTeXt convention for professional fonts: %% lowercase % medium \tf % semibold \sb % bold \bf % italic \it % semibold italic \st % bold italic \bi %% small caps % medium \TF % semibold \SB % bold \BF % italic \IT % semibold italic \ST % bold italic \BI The small caps versions are identical to the lowercase versions, with the difference that the small caps versions use caps. This serves as a mnemonic device. We also need some long-winded control sequences: \definestyle [semiboldroman,semibold] [\sb][] \definestyle [semibolditalic] [\st][] \definestyle [smallcapssemibold,semiboldsmallcaps] [\SB][] \definestyle [smallcapsbold,boldsmallcaps] [\BF][] \definestyle [smallcapsitalic,italicsmallcaps] [\IT][] \definestyle [smallcapssemibolditalic,semibolditalicsmallcaps][\ST][] \definestyle [smallcapsbolditalic,bolditalicsmallcaps] [\BI][] An identical or similar analysis may work for sans-serif, but I have to check... Thank you very much for pinning down the source of this! Best Idris ============================ Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523

5 9

Will the real palatino please stand up?
by John R. Culleton 22 Apr '05

22 Apr '05

In the typescript file type-syn.tex the palatino font is defined four times, twice for math and twice for serif. The headers in each pair are identical, e.g.: \starttypescript [serif] [palatino] [name] Assume I want to use the second serif typescript, the one that uses the Palladio fonts. Using the \usetypescript statement, how do I specify that particular script? -- John Culleton Able Indexers and Typesetters http://wexfordpress.com

2 2

Re: total with of TABLE ?
by Steffen Wolfrum 22 Apr '05

22 Apr '05

For example: I'd like to set a "total width" that fits both tables without specifying also the 2nd and 3rd column: \setupTABLE[totalwidth=10cm,offset=5pt] \setupTABLE[column][1][width=1cm,align=left] \setupTABLE[column][5][width=1cm,align=middle] \bTABLE \bTR\bTD aa \eTD\bTD bb \eTD\bTD cc \eTD\bTD dd \eTD\eTR \bTR\bTD aa \eTD\bTD bb \eTD\bTD cc \eTD\bTD dd \eTD\eTR \bTR\bTD aa \eTD\bTD bbbbbbbbbbbbbbbb \eTD\bTD cc \eTD\bTD dd \eTD\eTR \bTR\bTD aa \eTD\bTD bb \eTD\bTD cc \eTD\bTD dd \eTD\eTR \bTR\bTD aa \eTD\bTD bb \eTD\bTD cc \eTD\bTD dd \eTD\eTR \eTABLE \blank \bTABLE \bTR\bTD aa \eTD\bTD bb \eTD\bTD cc \eTD\bTD dd \eTD\eTR \bTR\bTD aa \eTD\bTD bb \eTD\bTD cc \eTD\bTD dd \eTD\eTR \bTR\bTD aa \eTD\bTD bb \eTD\bTD cc \eTD\bTD dd \eTD\eTR \bTR\bTD aa \eTD\bTD bb \eTD\bTD cccccccccccccccc \eTD\bTD dd \eTD\eTR \bTR\bTD aa \eTD\bTD bb \eTD\bTD cc \eTD\bTD dd \eTD\eTR \eTABLE Steffen

2 1

Re: total with of TABLE ?
by Steffen Wolfrum 22 Apr '05

22 Apr '05

luigi.scarso <luigi.scarso(a)logosrl.it> wrote: > Hans Hagen wrote: > > > Hi, > > > > I'm fighting deadlines right now, but later i'll try to get a look at > > the current table thread (maybe someone can summarize the problem) > > > > Hans ... > > So the problem seem to be > "Can I set the total width of a TABLE using a macros like > \setupTABLE[tablewidth=10cm] ?" ... > luigi Yes, this is what I was/am looking for: Setting up the width of an entire table. (Without having to specify the width of columns or cells.) Steffen

1 0

Turning off background(s)
by John R. Culleton 22 Apr '05

22 Apr '05

I wanted the title page to have a yellow background so I used: \setupbackgrounds[page][state=start,background=color,backgroundcolor=yellow] before \starttext. After that one page I wanted to go back to no background, but I am having trouble turning it off. Here is some of my code: --------------------------------- \setupbackgrounds[page][state=start,background=color,backgroundcolor=yellow] \starttext \startfrontmatter \startstandardmakeup ...(title page stuff) \stopstandardmakeup \setupbackgrounds[page][state=stop] ------------------------ I get one white page and then everything goes back to yellow again. How do I turn off the yellow background permanently? -- John Culleton Able Indexers and Typesetters http://wexfordpress.com

2 2

Re: [NTG-context] total with of TABLE ?
by Duncan Hothersall 22 Apr '05

22 Apr '05

Luigi wrote: > \SetTableToWidth{10cm} \starttable[|c|c|c|]...\stoptable set width to > 10 cm, but if I don't care about cell I can have an overfull box. > > So the problem seem to be "Can I set the total width of a TABLE using > a macros like \setupTABLE[tablewidth=10cm] ?" > > To solve this problem, I usually set every cell width using > \setupTABLE[x][n][width=..]; > > > But with \setupTABLE[tablewidth=...] I will avoid to specify every > single cell width, and the TABLE will find the right dimensions. > > I will look into core-ntb.tex. > > luigi If you want your TABLE to find natural column widths to fit the content, use [option=stretch] on the \bTABLE command. (NB it doesn't work as an option to \setupTABLE, only on the actual \bTABLE.) Then, assuming you don't need splitting over pages, you can set your TABLE inside a vbox to define its width. (If you do need splitting, try putting the TABLE into a textbackground - with no background color set unless you want it - and set the width and/or margins of that?) Hope that helps. Duncan

2 1

total with of TABLE ?
by Steffen Wolfrum 22 Apr '05

22 Apr '05

Hi, a quite basic question, nevertheless I couldn'T find an answer: How do I determine the total with of a TABLE? I though it should be ... \setupTABLE[width=\textwidth] \bTABLE \bTR \bTD aa \eTD \bTD bb \eTD \bTD cc \eTD \bTD dd \eTD \eTR \bTR \bTD aa \eTD \bTD bb \eTD \bTD cc \eTD \bTD dd \eTD \eTR \bTR \bTD aa \eTD \bTD bb \eTD \bTD cc \eTD \bTD dd \eTD \eTR \bTR \bTD aa \eTD \bTD bb \eTD \bTD cc \eTD \bTD dd \eTD \eTR \bTR \bTD aa \eTD \bTD bb \eTD \bTD cc \eTD \bTD dd \eTD \eTR \bTR \bTD aa \eTD \bTD bb \eTD \bTD cc \eTD \bTD dd \eTD \eTR \bTR \bTD aa \eTD \bTD bb \eTD \bTD cc \eTD \bTD dd \eTD \eTR \bTR \bTD aa \eTD \bTD bb \eTD \bTD cc \eTD \bTD dd \eTD \eTR \eTABLE ... but this means that all column's INDIVIDUAL width=\textwidth ! But what about the TOTAL width - regardless of the individual column's width? Steffen

3 5

RE: [NTG-context] proposed convention for variation switching [wasRE:inheriting ...
by Idris Samawi Hamid 22 Apr '05

22 Apr '05

>===== Original Message From Vit Zyka <vit.zyka(a)seznam.cz> ===== >Adam Lindsay wrote: >> >> It's not that I'm trying to rain on your parade, it's just that I've lost >> a bit of enthusiasm for standardisation. ok, but this is my take: although I can find workarounds that work for me, next month other some users will have to go through the same pain as I did, which seems to me to be a waste of collective energy. A standard solution for the 12 or so common variants of professional fonts just makes things easier for others, which is part of the whole ConTeXt philosophy (or so I thought). Everybody should not have to go through more than the minimal energy and time writing typescripts and defining font sizes. A standard convention will ensure some consistency and predictability. >I generally agree with Adam, fonts are very varios. But the next Idris >idea is nice. More intuitive then \sc, \bc, \ic, and \bic. I would vote >for it, but ... at least \sc needs some backward compatibility :-( Let's keep \sc. After all, ConTeXt already contains many redundancies (and that's a good thing imho->) >>>%% small caps >>>% medium \TF >>>% bold \BF >>>% italic \IT >>>% bold italic \BI Let's keep the semibold options: medium, semibold, and bold form a common spectrum _within_ many a professional font family. If we as users and writers of typescripts can agree on a common framework, it is perhaps more likely that the developers will implement it. My sole interest here is saving future users as much pain and frustration as possible. And I want to see more and more future users, including those with little technical facility. Fonts carry more _standard_ options than before: I don't think that updating to 12 standard style switches from 7 should be such a big deal:-) >Another discussion proposal: I will get the rest font families from >Storm to make the support complete. So I will have to solve many similar >problems with naming conventions. So I am interesting about some >recommendations. What way to solve via >A) variants via \Var[...] >B) \tf, \bf, ... switches, >C) different font family. > >For now I am using: >A) for extended glyph definitions and old style digits {Var[os]} (if >they are not default in the font - in that case there might be reverse >normal style digit variant \Var[ns?]). >B) standard 4 + small caps + symbols/ornaments designed to the font {\sy} >C) condensed, extended, medium, ... >Some comments? If pdfeTeX ever incorporates aleph's features this would all be much easier-) Till then... Not sure I fully understand but here are some comments: For A) If there is a global issue (like oldstyle) that covers all font variations, then your Var[#1] idea sounds nice. One could even do that with small caps for professional fonts but those are so ubiquitous that an exception would be in order for them (so small caps should always have a switch); (I think that \Var[up] (for upright figures) is more intuituve that \Var[ns]), at least in English:-))) B) Again, for a comprehensive framework we should keep semibold (and perhaps add light), for a total of 6(7)+symbols/ornaments; C) If an option like condensed is global over all style variants, then it should go in \Var[#1]. If it is local and is a common feature of professional fonts (like semibold), then we need a local switch framework, in which case the switch mechanism needs to be improved so that user-defined switches work in harmony with the predefined ones in every relevant respect. These are not final thoughts, but the beginnings of what could develop into a coherent framework for weights and style variation. I truly hope we can come to a common undestanding for the sake of future neophytes. ADDENDUM: Proposed framework: Global options across all style variants and weights should go into something like Vit's \Var[#1] or a separate font-definition typescript. For local options we can go on indefinitely but if we have to stop somewhere then we should by default have at least: % lowercase light \lf medium \tf semibold \sb bold \bf lightitalic \lt italic \it semibold italic \st bold italic \bi % small caps light \LF medium \TF semibold \SB bold \BF lightitalic \LT italic \IT semibold italic \ST bold italic \BI for a total of 16 simple and easy to remember switches, which should be rich enough to accomodate most professional modern fonts in \definebodyfont. Less common weights etc. can mostly be defined in terms of the standard 16 in \definebodyfont, then used as \Var. Of course the user can still define his/her own, but the idea is to make the most convenient reasonable framework to cover the most-often encountered situations. I think that the above 16 strikes a reasonable balance between the mundane and the esoteric. Sorry for the verbosity. Best Idris ============================ Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523

4 3

inheriting size characteristics
by Idris Samawi Hamid 22 Apr '05

22 Apr '05

Dear fellow knights, Given predefined switches like \tf and \bf, one inherits the size characteristics of the one already declared. But for user-defined switches this does not work. The following minimal files (typescript and test) is a bit long, but it accurately illustrates the problem and uses the default fonts. My user-defined switch works, but does not inherit from, e.g., \tfc. But \bf does inherit. What am I missing? Thnx in advance Idris ======================type-lmtest=================== \definestyle[smallcapssemibold,semiboldsmallcaps][\scsb][] \starttypescript[serif] [lm][default] \definefontsynonym [LM] [texnansi-lmr12] \definefontsynonym [LMBold] [texnansi-lmr12] \definefontsynonym [LMSemiboldCaps] [texnansi-lmr12] \stoptypescript \starttypescript[serif] [lm] [name] \definefontsynonym [Serif] [LM] \definefontsynonym [SerifBold] [LMBold] \definefontsynonym [SerifSemiboldCaps][LMSemiboldCaps] \stoptypescript \starttypescript[serif] [lm] [size] \definebodyfont [20.7pt,24.9pt,17.3pt,14.4pt,12pt,11pt,10pt,9pt,8pt] [rm] [tf=Serif sa 1, bf=SerifBold sa 1, scsb=SerifSemiboldCaps sa 1, scsba=SerifSemiboldCaps sa a, scsbb=SerifSemiboldCaps sa b, scsbc=SerifSemiboldCaps sa c, scsbd=SerifSemiboldCaps sa d] \stoptypescript \starttypescript[LMtest] \definebodyfontenvironment [lmtest] [default] [interlinespace=2.8ex] \definetypeface [lmtest] [rm] [serif] [lm] [lm] [encoding] \stoptypescript ==================================================== ====================test-lm.tex===================== % output=pdf interface=en \usetypescriptfile[type-lmtest] \usetypescript[LMtest] \setupbodyfont[lmtest] \starttext \tfc This is a test of Minion~Pro Opticals. 123467689 \bf This is a test of Minion~Pro Opticals. 123467689 \scsb This is a test of Minion~Pro Opticals. 123467689 \stoptext ==================================================== ============================ Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523

3 2

Re:[NTG-context] proposed convention for variation switching [wasRE:inheriting ...
by Idris Samawi Hamid 21 Apr '05

21 Apr '05

>On this basis, here is my suggestion for an official ConTeXt convention for >professional fonts: I forgot to mention one of the most important advantages of implementing an official ConTeXt standard (aside from inheritance): There will be no need to define \*a--\*d, \*x, and \*xx in user-defined typescripts, saving much time, space and debugging;-) Best Idris ============================ Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523

1 0