···
On 5/13/2014 8:16 PM, Aíre Funvake wrote:
On Tue May 13 19:56:34 2014, Hans Hagen wrote:
On 5/13/2014 7:48 PM, Aíre Funvake wrote:
On Mon May 12 23:12:06 2014, Aíre Funvake wrote:
On 2014-05-12, 22:59 , Aíre Funvake wrote:
On Mon May 12 22:52:43 2014, Hans Hagen wrote: > On 5/12/2014 10:46 PM, Aíre Funvake wrote: >> On Mon May 12 22:01:04 2014, Hans Hagen wrote: >>> On 5/12/2014 9:48 PM, Aíre Funvake wrote: >>>> Hi all, >>>> >>>> Trying to select "slashed zero" and "lining figures" from a >>>> font. For Lucida Bright OT, as another example, +scmp works, >>>> but not for Charter ITC Pro. But the font that concerns me >>>> the most right now, is TheSansMono Condensed... >>>> >>>> Font URL: >>>> http://www.lucasfonts.com/fonts/thesansmono/thesansmono-condensed/features/ >>>> >>>> >>>> >>>> >>>> PDF Info: >>>> https://dl.dropboxusercontent.com/u/6613992/TheSansMonoCd-info.pdf >>>> >>>> 8<-------------------minimal example---------------------------->8 >>>> \newdimen\fntcodesz >>>> \fntcodesz = 11.5pt >>>> \font\kwr = name:thesansmonocdw5regular:+lnum;+zero at \fntcodesz >>>> \kwr >>>> 0123456789 >>>> \bye >>>> 8<-------------------------------------------------------------->8 >>> >>> sometimes you need to select a script/language combination too >>> or when >>> digits are concerned disable oldstyle >> >> I'm too inexperienced to know what that means, or how to apply that. > > there is some info in font manuals and the context wiki > >> I've opened the font in FontForge, and can see the glyphs I'm >> looking for, but again, it does not carry much applicable meaning >> for me. For example, can I use this information?: >> >> Slash 0, Lining Figures: (0x10120) U+0030 "zero.lf.slashed" DIGIT >> ZERO >> 1, Lining Figures: (0x10121) U+0031 "one.lf" DIGIT ONE >> ... >> Slash 0, "Basic": (0x1012b) U+0030 "zero.basic.slashed" DIGIT ZERO >> 1, "Basic": (0x1012c) U+0031 "one.basic" DIGIT ONE >> ... > > so you need to select the lnum feature too > Was this not it?: ... \font\kwr = name:thesansmonocdw5regular:+lnum;+zero at \fntcodesz ... But thanks; will keep on reading; if solution found, will add it here. Regards, Aíre
Solution: \font\tt = name:thesansmonocdw5regular:script=latn;+lnum;+zero} at 12pt Thank you!
Spoke too soon. The "zero.slashed" is selected, instead of "zero.lf.slashed", so that the zero is smaller than the rest of the lining figure numbers. In desperation, tried luatex with 'luaotfload.sty' under TeXLive2013, and it worked fine. `;color=XXXXXX` also works with `luaotfload`, but not with LuaTeX-plain from ConTeXt.
no, and that is unlikely to show up in context as it makes no sense to specify colors that way .. just use the normal color commands
Any ideas would be welcome. Exhausted Google query permutations and most font info if for LaTeX, pdfTeX, pdfLaTeX, LuaLaTeX or ConTeXt.
Can I maybe as a hack switch the glyphs, or something?
how about adding
mode=node
in the plain setup (often not needed in context)
Hans
Thanks for the reply. Tried `mode=node`. Read about it, but never thought of putting it here!? The correct specification then is:
\font\mono = {TheSansMonoCd-W5Regular:% script=latn;+lnum;+zero;mode=node} at \fntsze
Confused about the color though. Read most of luatexref-t.pdf, and may have missed it. The only reference (and it works in `luaotfload` under TeXLive2013) is like this:
\font\mono = {TheSansMonoCd-W5Regular:% script=latn;+lnum;+zero;mode=node;color=336699} at \fntsze ~~~~~~~~~~~~
so it looks like oftload adds that (or maybe the latex font definition code) but even then, it's probably implemented someplace else in the latex code
Found no other reference to setting color on fonts in LuaTeX-plain (the ConTeXt version). Would love a pointer to the information though.
it must be something latex i think (maybe to provide xetex compatibility) but it's definitely not in luatex (nor will be) and also not in context (which has more advanced color support than hex specs anyway)
That’s correct. The “color” key triggers a custom callback that tints every glyph of the defined font. It’s part of Luaotfload solely for compatibility for Xetex. IMO it’s not worth the hassle; I recommend using a proper color package instead.
if you want color, use context instead of plain
Probably the best suggestion =) Philipp