February 2011 - ntg-context - NTG Mailing Lists

Re: [NTG-context] strange hang during compilation
by Jeong Dalyoung 09 Feb '11

09 Feb '11

Dear Hans, > > Localization is not that complex ... mostly a matter of extending tables ... just let us know what you have in mind. > Ok, I'll check what I can do. > Currently we have one set of parameters that you can see in > > local dataset = { > inter_char_stretch_factor = 0.50, -- of quad > inter_char_half_shrink_factor = 0.50, -- of quad > inter_char_hangul_penalty = 50, > } > > It's no big deal to support more sets. Do document mix settings? Does this depend on the font? > I think that it depends on the fonts a little. When I use another font set, the inter-letter space looks better. I'll discuss this matter with font experts in KTUG conference on this saturday, Feb. 12. Since they did a nice job for LaTeX, they know what should be considered. > I uploaded a beta. Is the problem still there? > I just reinstalled the beta and test it. It works really fine!!! Thank you for your efforts. best regards, Dalyoung

1 0

How to control spacing around titles?
by Christian 09 Feb '11

09 Feb '11

Hello, how do I influence the space around titles (i.e heads, in ConTeXt-speak)? What I want to do: 1 Chapter title <there is some whitespace (let's call it #1) here, that I want to change> text in paragraph 1. <thete is some whitespace (#2) here, that I want to change> 1.1 Section title <there is some whitespace (#3) here, that I want to change> text in paragraph 2. <there is some whitespace (#4) here, that I want to change> 1.2 Section title ...and so on. I figure it has to do with setuphead[chapter][-insert magic here-] but I was not able to find something in the wiki nor in the list. Oh, and direkt control (cm or pt) instead of small/medium/big would be great. Christian

2 2

preventing ligatures in Type1 fonts under MKIV
by Mojca Miklavec 09 Feb '11

09 Feb '11

Dear Hans, How can I disable fi ligatures and endashes in Lucida Typewriter? Minimal example: \setupbodyfont[lucida] \starttext {\tt fif\/i} \type{first-setup.sh --extras=t-vim} \stoptext Mojca

3 4

Headers another way
by Procházka Lukáš 09 Feb '11

09 Feb '11

Hello, I'm trying to solve an interesting problem. (The document should be generated by Lua actually, but probably this is not of importance.) I'd need create various headers, but it's not known which command to be used a priori; only their "relative position" is known. The head creating command should be the same (= \HEAD) and the level should be determined by \PUSHHEAD + \POPHEAD commands. I'd need to solve something like this: --- \starttext \HEAD{...} % Should expand to \chapter \PUSHHEAD \HEAD{...} % Should expand to \section \PUSHHEAD \HEAD{...} % Should expand to \subsection \PUSHHEAD \HEAD{...} % Should expand to \subsubsection \PUSHHEAD \HEAD{...} % Should expand to \subsubsubsection \POPHEAD \HEAD{...} % Should expand to \subsubsection again \POPHEAD \POPHEAD \POPHEAD \stoptext --- Any idea how to solve this? (The aim is that Lua should generate or not the \PUSHHEAD + \POPHEAD commands very simply; it's much easier to do this instead to define complicated rules whether to call \section or \subsection at a particular place.) Best regards, Lukas

3 3

FW: beta
by Reviczky, Adam 09 Feb '11

09 Feb '11

>>> I have the same error now with the latest beta (2011-02-05) if there's a folder defined in OSFONTDIR that doesn't exist. >>> Is there a particular reason why the isdir(path) check in globpattern from l-dir.lua was removed? >>> If I add it back then there's no error. >> >>The check broke other globbing (e.g. wildcard) and is not robust so I >>removed it; I need more info about why/where it fails at your end. Sure, For example, I'm using: export OSFONTDIR="/usr/local/share/texmf/fonts;$HOME/.fonts" (which was by accident, because originally I was using /usr/local/share/fonts which exists), where I have fonts in $HOME/.fonts, but my /usr/local/share/texmf/fonts does not exist. "ls: cannot access /usr/local/share/texmf/fonts: No such file or directory" Running mkiv beta gives me this error when I want to use a font that's located in $HOME/.fonts: fontnames > identifying system font files with suffix otf fontnames > adding path from OSFONTDIR: /usr/local/share/texmf/fonts fontnames > adding path from OSFONTDIR: /home/reviczky/.fonts fontnames > globbing path /usr/local/share/texmf/fonts/**.otf ! LuaTeX error /usr/share/texmf/tex/context/base/l-dir.lua:68: cannot open /usr/local/share/texmf/fonts/: No such file or directory stack traceback: [C]: in function 'walkdir' /usr/share/texmf/tex/context/base/l-dir.lua:68: in function 'globpattern' /usr/share/texmf/tex/context/base/l-dir.lua:170: in function 'glob' /usr/share/texmf/tex/context/base/font-syn.lua:354: in function 'walk_tree' /usr/share/texmf/tex/context/base/font-syn.lua:766: in function 'method' /usr/share/texmf/tex/context/base/font-syn.lua:729: in function 'traverse' /usr/share/texmf/tex/context/base/font-syn.lua:765: in function 'analyzefiles' /usr/share/texmf/tex/context/base/font-syn.lua:829: in function 'identify' /usr/share/texmf/tex/context/base/font-syn.lua:854: in function 'load' /usr/share/texmf/tex/context/base/font-syn.lua:865: in function 'load' /usr/share/texmf/tex/context/base/font-syn.lua:1018: in function 'resolvedspecification' /usr/share/texmf/tex/context/base/font-syn.lua:1028: in function 'resolve' /usr/share/texmf/tex/context/base/font-def.lua:264: in function 'r' /usr/share/texmf/tex/context/base/font-def.lua:297: in function 'resolve' /usr/share/texmf/tex/context/base/font-def.lua:636: in function 'read' /usr/share/texmf/tex/context/base/font-ctx.lua:564: in function 'stage_two' <main ctx instance>:1: in main chunk. Log attached. Do you need anything else? Adam

2 1

Re: [NTG-context] strange hang during compilation
by Jeong Dalyoung 09 Feb '11

09 Feb '11

Dear Hans, > > So, it looks like some figure definition going wrong. Can you see what \*externalfigure commands are used (just grep them and mail them) >> \??oi ->@ I am sorry that I am not good at unix commnad. Would you please how to do that? and > how does the whole line looks like (the ...) what do you mean? I have tested in several situation and find that the figure files in the original directory is fine when I make a very short file like \tracingall \startcomponent test \placefigure[][]{} {\externalfigure[./figures/c14][width=.5\makeupwidth]} \stopcomponent I really confused. After testing more, I will summerize it. Thank you. best regards, Dalyoung

1 0

Opentype feature files in Luatex - Mac OS X
by Stef Schoonderwoerd 09 Feb '11

09 Feb '11

Dear all, I just had a quick question, I seem to remember finding the answer some while ago, but after searching all day today nothing came up anymore: what path does one put the opentype feature files on Mac OS X so luatex can read them? The unix standard path does not work.. Thanks in advance, Stef Schoonderwoerd

3 2

changing title of register displayed with \completeregistername
by Daniel Lyons 09 Feb '11

09 Feb '11

Hi, I'm trying to get a register to show a title other than the name of the register in the code, and not having much luck. For example, \defineregister[pgtype][pgtypes] \completepgtype produces a page with the title "Pgtype", when I'd like it to say "PostgreSQL Types" instead. (Also, the documentation led me to believe the function should be called \completepgtypes rather than \completepgtype.) The wiki suggests \setupheadtext[name=PostgreSQL Types] on http://wiki.contextgarden.net/Registers but this seems to have no effect, which makes sense to me, because it doesn't seem to have enough information. What's the trick? Thanks, — Daniel Lyons

2 1

line-break discarded in \getparameters
by pmlists＠free.fr 09 Feb '11

09 Feb '11

Hello, No space is printed between bla2 and bla3 with latest mkiv: \startsetups 1 \getparameters[Prefix][Text={bla1 bla2 bla3}] \stopsetups \starttext \setups{1} \PrefixText, no space between bla2 and bla3... \stoptext -- Peter

2 3

Typescript troubles with semibold font.
by Christian 09 Feb '11

09 Feb '11

Hi all, my goal is to use Minion Pro as text face and Myriad Pro as sans serif in headings etc. I use TeXlive, ConTeXt 2009.11.26 16:28, MKiV. I found a typescipt once provided in this list in 2008 and adopted it. Here it is: \starttypescript [serif] [minionpro] \definefontsynonym [MinionPro-Regular] [name:minionproregular] \definefontsynonym [MinionPro-Bold] [name:minionprobold] \definefontsynonym [MinionPro-It] [name:minionproit] \definefontsynonym [MinionPro-BoldIt] [name:minionproboldit] \stoptypescript \starttypescript [serif] [minionpro] \definefontsynonym [Serif] [MinionPro-Regular] [features=default] \definefontsynonym [SerifBold] [MinionPro-Bold] [features=default] \definefontsynonym [SerifItalic] [MinionPro-It] [features=default] \definefontsynonym [SerifBoldItalic] [MinionPro-BoldIt] [features=default] \stoptypescript \starttypescript [sans] [myriadpro] \setups[font:fallback:sans] \definefontsynonym [MyriadPro-Regular] [name:myriadproregular] \definefontsynonym [MyriadPro-Bold] [name:myriadprosemibold] \definefontsynonym [MyriadPro-It] [name:myriadproit] \definefontsynonym [MyriadPro-BoldIt] [name:myriadprosemiboldit] \stoptypescript \starttypescript [sans] [myriadpro] \definefontsynonym [Sans] [MyriadPro-Regular] [features=default] \definefontsynonym [SansBold] [MyriadPro-Bold] [features=default] \definefontsynonym [SansItalic] [MyriadPro-It] [features=default] \definefontsynonym [SansBoldItalic] [MyriadPro-BoldIt] [features=default] \definefontsynonym [SansCaps] [Sans] [features=latin-smallcaps] \stoptypescript The Problem is, as long as the bold font files are present in my .fonts folder, they get used instead of the semibold (that I declared with name:myriadprosemibold). When I delete them, the semibold ones get used. My question is: Can anyone provide me some insight on how to use bold and semibold in the same document? Lets say chapter headings bold, sectionheadings semibold. Thanks in advance, Christian P.S: A guide "how to get from font files to the desired output" would be great. Steps would include where to put the fonts (.otf in my case), how to make context know the fonts, writing the typescript, using font features.

2 2