Here is the output of mtxrun. Note that there are two versions: T (title)
and ST (subtitle). I want the title version.
mtxrun --script fonts --list --all --pattern=DTL
identifier familyname fontname
filenamesubfont instances
dtldocumentait
Am 25.05.22 um 22:23 schrieb Stefan Nedeljkovic via ntg-context:
Dear list,
A quick question about a font that has a separate file for small caps. I
have the following:
\starttypescript [sans] [dtl-documenta-sans-t]
\definefontsynonym[Sans] [name:dtldocumentasanst][features=default]
\definef
Dear list,
A quick question about a font that has a separate file for small caps. I
have the following:
\starttypescript [sans] [dtl-documenta-sans-t]
\definefontsynonym[Sans] [name:dtldocumentasanst][features=default]
\definefontsynonym[SansItalic]
[name:dtldocumentasanstitalic][features=defaul
Hello,
On Thu, 14 Dec 2017 10:16:33 +0100, Hans Hagen wrote:
On 12/14/2017 8:37 AM, Procházka Lukáš Ing. wrote:
Hello,
I'm trying to typeset some text in bold + smallcaps.
But even the sample on wiki:
http://wiki.contextgarden.net/Bold_small_caps
extended to:
\starttext
\set
Hello,
I'm trying to typeset some text in bold + smallcaps.
But even the sample on wiki:
http://wiki.contextgarden.net/Bold_small_caps
extended to:
\starttext
\setff{smallcaps} Normal and \bf bold Small Caps.
{\sc Normal and \bf bold Small Caps.}
\stoptext
doesn't prod
On Sat, 10 Aug 2013 19:24:17 +0200
Philipp Gesang wrote:
> Hi John!
>
> ·
>
> > I have asked everywhere else to no avail. In (plain) luatex how do I
> > specify the small cap version of an otf font? I use context for
> > non-fiction but pdftex and now luatex for fiction.
>
> Plain uses
Hi John!
·
> I have asked everywhere else to no avail. In (plain) luatex how do I
> specify the small cap version of an otf font? I use context for
> non-fiction but pdftex and now luatex for fiction.
Plain uses a feature syntax similar to Xetex’s:
\font \foo = "file:Iwona-Regular.otf
I have asked everywhere else to no avail. In (plain) luatex how do I
specify the small cap version of an otf font? I use context for
non-fiction but pdftex and now luatex for fiction.
--
John Culleton
___
If your que
Am 25.07.2012 um 09:43 schrieb Mojca Miklavec:
> On Wed, Jul 25, 2012 at 9:04 AM, Marco wrote:
>> On 2012-07-25 Shriramana Sharma wrote:
>>
>> Hi Shriramana,
>>
>>> Hi thanks for your help. Sorry to keep returning with errors (but as I
>>> said I'm a noob):
>>>
>>> loading : ConTeXt Us
On Jul 25, 2012, at 1:06 AM, Shriramana Sharma wrote:
> On Wed, Jul 25, 2012 at 10:29 AM, Rogers, Michael K wrote:
>>
>> Here's a hack, which sort of works, definitely doesn't handle --
>> there must be a better way. I hope you don't mind my using your text as
>> text. :-)
>
> Hi thanks for
On 25-7-2012 10:16, Shriramana Sharma wrote:
Hi thanks everyone for their responses.
On Wed, Jul 25, 2012 at 1:23 PM, Hans Hagen wrote:
But it lacks Indic scripts, so it's not an option for him, at least not
yet.
Indic scripts will be supported in mkiv some day soon (at the ntg meeting
there
On Wed, Jul 25, 2012 at 10:16 AM, Shriramana Sharma wrote:
> Hi thanks everyone for their responses.
>
> On Wed, Jul 25, 2012 at 1:23 PM, Hans Hagen wrote:
> >> But it lacks Indic scripts, so it's not an option for him, at least not
> >> yet.
> >
> > Indic scripts will be supported in mkiv some d
Hi thanks everyone for their responses.
On Wed, Jul 25, 2012 at 1:23 PM, Hans Hagen wrote:
>> But it lacks Indic scripts, so it's not an option for him, at least not
>> yet.
>
> Indic scripts will be supported in mkiv some day soon (at the ntg meeting
> there has been a presentation about devanag
On 25-7-2012 09:41, Mojca Miklavec wrote:
On Wed, Jul 25, 2012 at 9:35 AM, Hans Hagen wrote:
On 25-7-2012 04:33, Shriramana Sharma wrote:
Basically I'm trying to move away from wordprocessors, and while I'm
not looking for meaningless effects like "walking ants" (from MS Word)
to be provided b
On Wed, Jul 25, 2012 at 9:04 AM, Marco wrote:
> On 2012-07-25 Shriramana Sharma wrote:
>
> Hi Shriramana,
>
>> Hi thanks for your help. Sorry to keep returning with errors (but as I
>> said I'm a noob):
>>
>> loading : ConTeXt User Module / Simplefonts
>> ! Undefined control sequence.
>> l.
On Wed, Jul 25, 2012 at 9:35 AM, Hans Hagen wrote:
> On 25-7-2012 04:33, Shriramana Sharma wrote:
>
>> Basically I'm trying to move away from wordprocessors, and while I'm
>> not looking for meaningless effects like "walking ants" (from MS Word)
>> to be provided by TeX macro packages, faux smallca
On 25-7-2012 04:33, Shriramana Sharma wrote:
Basically I'm trying to move away from wordprocessors, and while I'm
not looking for meaningless effects like "walking ants" (from MS Word)
to be provided by TeX macro packages, faux smallcaps (and oblique and
bold) is not an unreasonable thing to exp
On 2012-07-25 Shriramana Sharma wrote:
Hi Shriramana,
> Hi thanks for your help. Sorry to keep returning with errors (but as I
> said I'm a noob):
>
> loading : ConTeXt User Module / Simplefonts
> ! Undefined control sequence.
> l.144 \ctxloadluafile
> {t-simplefont
On Wed, Jul 25, 2012 at 10:29 AM, Rogers, Michael K wrote:
>
> Here's a hack, which sort of works, definitely doesn't handle --
> there must be a better way. I hope you don't mind my using your text as
> text. :-)
Hi thanks for your help. Sorry to keep returning with errors (but as I
said I'm
On Jul 24, 2012, at 10:33 PM, Shriramana Sharma wrote:
> Hi -- is there absolutely no way for obtaining these "fake small caps"
> in ConTeXT?
Here's a hack, which sort of works, definitely doesn't handle -- there
must be a better way. I hope you don't mind my using your text as text. :-)
\us
Hello Aditya and thanks for your help. However, the following file
still does not my particular selected font to be shown in faux small
caps:
\def\fakesmallcaps{\let\processword\dofakesmallcapped\processwords}
\def\dofakesmallcapped#1{\dostartfakesmallcapped#1\dostopfakesmallcapped}
\def\dostartfa
On Wed, 25 Jul 2012, Shriramana Sharma wrote:
On Wed, Jul 25, 2012 at 1:04 AM, Marco wrote:
My guess is that DejaVu Sans Condensed has no small caps. That's why
you get the unexpected result. LibO might fake the small caps, which
should usually be avoided, since it often leads to typographical
Thanks to all who replied.
On Wed, Jul 25, 2012 at 1:04 AM, Marco wrote:
> My guess is that DejaVu Sans Condensed has no small caps. That's why
> you get the unexpected result. LibO might fake the small caps, which
> should usually be avoided, since it often leads to typographically
> bad results
On Tue, Jul 24, 2012 at 11:21:22PM +0200, Hans Hagen wrote:
> On 24-7-2012 21:29, Shriramana Sharma wrote:
> >On Wed, Jul 25, 2012 at 12:55 AM, Wolfgang Schuster
> > wrote:
> >>\definehighlight[smallcaps][style=\setff{smallcaps}]
> >
> >Hello and thanks for your help but even if I copy-paste your e
On 24-7-2012 21:29, Shriramana Sharma wrote:
On Wed, Jul 25, 2012 at 12:55 AM, Wolfgang Schuster
wrote:
\definehighlight[smallcaps][style=\setff{smallcaps}]
Hello and thanks for your help but even if I copy-paste your example
into TeXWorks and typeset it (remember, I'm using ConTeXT with XeTe
On 2012-07-25 Shriramana Sharma wrote:
> Can anyone please advise me what to do to get small caps in my current
> font like in LibO and other popular GUI word-processing systems?
My guess is that DejaVu Sans Condensed has no small caps. That's why
you get the unexpected result. LibO might fake t
On Wed, Jul 25, 2012 at 12:55 AM, Wolfgang Schuster
wrote:
> \definehighlight[smallcaps][style=\setff{smallcaps}]
Hello and thanks for your help but even if I copy-paste your example
into TeXWorks and typeset it (remember, I'm using ConTeXT with XeTeX)
I get the error:
Undefined control sequence
Am 24.07.2012 um 21:11 schrieb Shriramana Sharma:
> Hello. I'm a veritable noob to both TeX and ConTeXT, so please bear
> with my ignorance. I request your kind guidance. (BTW as I use Indic
> scripts a lot, my typesetting engine is XeTeX.)
>
> I want to produce small caps like those I can get i
Hello. I'm a veritable noob to both TeX and ConTeXT, so please bear
with my ignorance. I request your kind guidance. (BTW as I use Indic
scripts a lot, my typesetting engine is XeTeX.)
I want to produce small caps like those I can get in LibreOffice by
doing Right Click > Character > Font Effects
Barry Schwartz wrote:
Are there fonts that have a or b in the "numr" and "dnom" features but
where they do not work in "frac"?
that is unrelated, the replacement rules refer to glyphs an doften they
stick to digits so you get a/b with a large a and b and the fractional
slash which then gives
Hans Hagen skribis:
> so, its not that frac itself is the problem dealing with in the engine,
> because if so, many features would be a problem, it's just that font
> makers stick to a couple of simple rules like:
>
> (1) replace all
>
> by
>
>
> (1) replace all
>
Barry Schwartz wrote:
Hans Hagen skribis:
but even then, if a font is not clear about issues, then one can get
unwanted side effects (the frac feature for instance is often quite
bugged and can only be applied selectively)
Yeah, I think trying to be fancy with contextual substitutions is a
b
Barry Schwartz wrote:
Hans Hagen skribis:
Barry Schwartz wrote:
If base mode uses the traditional TeX mechanism for ligatures, I don't
see any way the font can be blamed.
Ant does the same thing, I believe, using the OT tables and heuristics
to run the TeX processor. That's okay, as long as
Hans Hagen skribis:
> but even then, if a font is not clear about issues, then one can get
> unwanted side effects (the frac feature for instance is often quite
> bugged and can only be applied selectively)
Yeah, I think trying to be fancy with contextual substitutions is a
bit like getting dru
Hans Hagen skribis:
> Barry Schwartz wrote:
>
> > If base mode uses the traditional TeX mechanism for ligatures, I don't
> > see any way the font can be blamed.
Ant does the same thing, I believe, using the OT tables and heuristics
to run the TeX processor. That's okay, as long as the results ar
Barry Schwartz wrote:
If base mode uses the traditional TeX mechanism for ligatures, I don't
see any way the font can be blamed.
sure
Hans
-
Hans Hagen | PRAGMA ADE
Ridders
Barry Schwartz wrote:
The font is unambiguous about it, though. Are you sure the software
isn't performing the feature list in order rather than lookup list? Or
is the software performing substitutions in its own ad hoc order?
in basemode we use built in traditional tex methods, so only ligatu
Am 18.09.2009 um 19:57 schrieb Hans Hagen:
Question for wolfgang ... do you enable node mode?
No.
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg
Derek CORDEIRO skribis:
> On Fri, Sep 18, 2009 at 11:24 PM, Hans Hagen wrote:
>
> > Derek CORDEIRO wrote:
> >
> > That does not work for me at all. The following does work with generating
> >> the same ThOMAS
> >>
> >
> > can you try ..
> >
> > \definefontfeature[smallcaps][smallcaps][liga=no]
Hans Hagen skribis:
> Barry Schwartz wrote:
> > Hans Hagen skribis:
> >> could it be a bug in the font? i.e. a Th ligature showing up in
> >> smallcaps? if so, then simplefonts should disable ligatures in smallcaps
> >
> > I'm looking at AGaramondPro-Regular in fontforge and it has the lookup
>
On Fri, Sep 18, 2009 at 11:31 PM, Hans Hagen wrote:
> Derek CORDEIRO wrote:
>
> That does not work for me at all. The following does work with generating
>> the same ThOMAS
>>
>
> another test:
>
> \definefontfeature[default] [default] [mode=node]
> \definefontfeature[smallcaps][smallcaps][mod
On Fri, Sep 18, 2009 at 11:24 PM, Hans Hagen wrote:
> Derek CORDEIRO wrote:
>
> That does not work for me at all. The following does work with generating
>> the same ThOMAS
>>
>
> can you try ..
>
> \definefontfeature[smallcaps][smallcaps][liga=no]
>
> \usemodule[simplefonts]
>
> \setmainfont[A
Barry Schwartz wrote:
Hans Hagen skribis:
could it be a bug in the font? i.e. a Th ligature showing up in
smallcaps? if so, then simplefonts should disable ligatures in smallcaps
I'm looking at AGaramondPro-Regular in fontforge and it has the lookup
for small caps well above the lookup for li
Hans Hagen skribis:
> could it be a bug in the font? i.e. a Th ligature showing up in
> smallcaps? if so, then simplefonts should disable ligatures in smallcaps
I'm looking at AGaramondPro-Regular in fontforge and it has the lookup
for small caps well above the lookup for ligatures. The software
Derek CORDEIRO wrote:
That does not work for me at all. The following does work with generating
the same ThOMAS
another test:
\definefontfeature[default] [default] [mode=node]
\definefontfeature[smallcaps][smallcaps][mode=node]
\definefontfeature[oldstyle] [oldstyke] [mode=node]
Hans
Derek CORDEIRO wrote:
\usemodule[simplefonts]
Question for wolfgang ... do you enable node mode?
in basemode, it might be that ligatures are loaded after smallcaps (and
base mode is static) and then it's the order of features in the font
that determines what happens,
if so, then maybe we
Derek CORDEIRO wrote:
That does not work for me at all. The following does work with generating
the same ThOMAS
can you try ..
\definefontfeature[smallcaps][smallcaps][liga=no]
\usemodule[simplefonts]
\setmainfont[A Jenson Pro Regular]
\starttext
{\sc Thomas}
\stoptext
if that works, then
On Fri, Sep 18, 2009 at 6:44 PM, Hans Hagen wrote:
> Mika Ritola wrote:
>
>> Hello all,
>>
>> For some reason, the snippet below outputs 'ThOMAS' instead of 'THOMAS.'
>> This seems to be font dependent; at least Adobe Jenson Pro and Adobe
>> Garamond Pro produce 'Th,' while the other fonts that I
Mika Ritola wrote:
Hello all,
For some reason, the snippet below outputs 'ThOMAS' instead of 'THOMAS.'
This seems to be font dependent; at least Adobe Jenson Pro and Adobe
Garamond Pro produce 'Th,' while the other fonts that I've tried produce
'TH', as expected. I don't know whether the bug exi
Hello all,
For some reason, the snippet below outputs 'ThOMAS' instead of 'THOMAS.'
This seems to be font dependent; at least Adobe Jenson Pro and Adobe
Garamond Pro produce 'Th,' while the other fonts that I've tried produce
'TH', as expected. I don't know whether the bug exists in the fonts
them
On Wed, Apr 16, 2008 at 12:34 PM, Antoine Junod <[EMAIL PROTECTED]> wrote:
> "Wolfgang Schuster" <[EMAIL PROTECTED]> writes:
>
> > On Wed, Apr 16, 2008 at 11:59 AM, Antoine Junod <[EMAIL PROTECTED]> wrote:
> >> Hi Wolfgang!
> >>
> >> "Wolfgang Schuster" <[EMAIL PROTECTED]> writes:
> >>
> >> > On Su
"Wolfgang Schuster" <[EMAIL PROTECTED]> writes:
> On Wed, Apr 16, 2008 at 11:59 AM, Antoine Junod <[EMAIL PROTECTED]> wrote:
>> Hi Wolfgang!
>>
>> "Wolfgang Schuster" <[EMAIL PROTECTED]> writes:
>>
>> > On Sun, Apr 13, 2008 at 8:39 PM, Antoine Junod <[EMAIL PROTECTED]> wrote:
>> >> Hello list,
>>
On Wed, Apr 16, 2008 at 11:59 AM, Antoine Junod <[EMAIL PROTECTED]> wrote:
> Hi Wolfgang!
>
> "Wolfgang Schuster" <[EMAIL PROTECTED]> writes:
>
> > On Sun, Apr 13, 2008 at 8:39 PM, Antoine Junod <[EMAIL PROTECTED]> wrote:
> >> Hello list,
> >>
> >> I actually use my font as simple as possible with
Hi Wolfgang!
"Wolfgang Schuster" <[EMAIL PROTECTED]> writes:
> On Sun, Apr 13, 2008 at 8:39 PM, Antoine Junod <[EMAIL PROTECTED]> wrote:
>> Hello list,
>>
>> I actually use my font as simple as possible with a
>> \definefont[boum][MyFont at 12pt]. Is it the problem?
>>
>> It the same with the \sc
Hi,
Thanks a lot for your reply :)
Henning Hraban Ramm <[EMAIL PROTECTED]> writes:
> Am 2008-04-13 um 20:39 schrieb Antoine Junod:
>> I actually use my font as simple as possible with a
>> \definefont[boum][MyFont at 12pt]. Is it the problem?
>
> Yes. You should set up your fonts with a typescri
On Sun, Apr 13, 2008 at 8:39 PM, Antoine Junod <[EMAIL PROTECTED]> wrote:
> Hello list,
>
> I'm still playing with a few otf fonts and enjoying the way ConTeXt
> works :)
>
> I'm now playing with a beautiful Garamond. I try to typeset a few
> things with old-style numbers and, well, the output cont
Am 2008-04-13 um 20:39 schrieb Antoine Junod:
> I actually use my font as simple as possible with a
> \definefont[boum][MyFont at 12pt]. Is it the problem?
Yes. You should set up your fonts with a typescript and access small
caps / oldstyle as "features".
Sorry, can't help you further at the mo
Hello list,
I'm still playing with a few otf fonts and enjoying the way ConTeXt
works :)
I'm now playing with a beautiful Garamond. I try to typeset a few
things with old-style numbers and, well, the output contains old-style
numbers but not in my Garamond (it seems to be in latin modern). What
s
Mojca Miklavec wrote:
> On 7/1/06, Taco Hoekwater wrote:
>> Mojca Miklavec wrote:
>>> On 6/29/06, Taco Hoekwater >>
{\bf A test \variant[Caps] in small caps}
>>> Does this work on your computer? (I don't get any caps here.)
>> No it doesn't, it was a leftover from a failed experiment
I did no
Mojca Miklavec wrote:
>
>
> Seems like understanding \expandafter would solve 90% of my problems.
> I tried to understand that part in TeX book, but it's so cryptic (too
> short) ... I understand the concept, but I'm not able to write the
> code for it yet :(
The trick to \expandafter is that yo
On 7/2/06, Taco Hoekwater wrote:
> Mojca Miklavec wrote:
> >
> >>>It works perfect except in a single case: \title{\molecule{SF_6}}
> >>
> >>I had seen that, but not yet bothered to fix it. Still, it is
> >>fairly easy to change the macro, try the version below.
>
> Sorry, I thought you were talkin
Mojca Miklavec wrote:
>
>>>It works perfect except in a single case: \title{\molecule{SF_6}}
>>
>>I had seen that, but not yet bothered to fix it. Still, it is
>>fairly easy to change the macro, try the version below.
Sorry, I thought you were talking about the spacing between F and 6.
> Didn't
On 7/1/06, Taco Hoekwater wrote:
> Mojca Miklavec wrote:
> > On 6/29/06, Taco Hoekwater >
> >>{\bf A test \variant[Caps] in small caps}
> >
> > Does this work on your computer? (I don't get any caps here.)
>
> No it doesn't, it was a leftover from a failed experiment
OK. I thought so :(
> >
> >
Mojca Miklavec wrote:
> On 6/29/06, Taco Hoekwater
>>{\bf A test \variant[Caps] in small caps}
>
> Does this work on your computer? (I don't get any caps here.)
No it doesn't, it was a leftover from a failed experiment
>
> Thanks for the magnificent macro! I replaced minus by $-$ and I had to
On 6/29/06, Taco Hoekwater
> {\bf A test \variant[Caps] in small caps}
Does this work on your computer? (I don't get any caps here.)
> \newbox\chemlowbox
> \def\chemlow#1%
>{\setbox\chemlowbox\hbox{{\switchtobodyfont[small]#1}}}
>
> \def\chemhigh#1%
>{\ifvoid\chemlowbox \high{{\switchtob
Taco Hoekwater wrote:
> Sorry, messed up something. New version followws:
>
> \newbox\chemlowbox
> \def\chemlow#1%
>{\setbox\chemlowbox\hbox{{\switchtobodyfont[small]#1}}}
>
> \def\chemhigh#1%
>{\ifvoid\chemlowbox \high{{\switchtobodyfont[small]#1}}%
> \else \lohi[left]{\box\chemlowbox}
Hans Hagen wrote:
>
> i didt follow this thread, so i may be wrong, but doesn't the ppchtex
> (see manuals) module does that kind of stuff?
It doesn't retain font styles (at least, I could not make it do that)
Taco
___
ntg-context mailing list
ntg-c
Sorry, messed up something. New version followws:
\newbox\chemlowbox
\def\chemlow#1%
{\setbox\chemlowbox\hbox{{\switchtobodyfont[small]#1}}}
\def\chemhigh#1%
{\ifvoid\chemlowbox \high{{\switchtobodyfont[small]#1}}%
\else \lohi[left]{\box\chemlowbox}{{\switchtobodyfont[small]#1}}\fi }
Mojca Miklavec wrote:
>>
>>It only gets the size right, not the boldnes. But it can be argued
>>that that is the correct behaviour anyways.
>
> Not so long ago you argued that \alpha-sheet, \beta-helix,
> \gamma-rays, ... should be part of text flow (a reason why the el
> companion encoding shoul
Aditya Mahajan wrote:
> Maybe what is needed is a \beforemathswitch token set. Then one could
> do
>
> \appendtoks \boldmath to \beforemathswitch
Already present: \everymathematics
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/ma
On Thu, 29 Jun 2006, Mojca Miklavec wrote:
> On 6/28/06, Taco Hoekwater wrote:
>> Aditya Mahajan wrote:
>>> Some catcode trickery might work. This is all I could manage.
>>
>> This does not work well, because
>>
>> HSO\low{4}\high{-}
>>
>> is not correct.
>
> True, but if I'm aware of it,
On 6/28/06, Taco Hoekwater wrote:
> Aditya Mahajan wrote:
> > Some catcode trickery might work. This is all I could manage.
>
> This does not work well, because
>
> HSO\low{4}\high{-}
>
> is not correct.
True, but if I'm aware of it, I can use \lohi{4}{$-$} if needed, which
works even bett
Aditya Mahajan wrote:
> On Wed, 28 Jun 2006, Mojca Miklavec wrote:
>
>
>>Hello,
>>
>>I have to tiny questions:
>>
>>1. How do I get small caps [bold] italic (except with the
>>\definedfont[ec-lmxxx])?
>
> No idea.
Same for me. I know that theoreticallu something would be possible
using \Var and
On Jun 28, 2006, at 7:44 PM, Mojca Miklavec wrote:
> Hello,
>
> I have to tiny questions:
>
> 1. How do I get small caps [bold] italic (except with the
> \definedfont[ec-lmxxx])?
>
Mojca,
this is a bit more complicated than it sounds. Have a look at Adam's
MyWay, section 4 explains how to do i
On Wed, 28 Jun 2006, Mojca Miklavec wrote:
> Hello,
>
> I have to tiny questions:
>
> 1. How do I get small caps [bold] italic (except with the
> \definedfont[ec-lmxxx])?
No idea.
> 2. I defined \molecule to be
>\def\molecule#1{$\rm#1$},
better use {\mathematics{\rm #1}} so that you can als
Hello,
I have to tiny questions:
1. How do I get small caps [bold] italic (except with the
\definedfont[ec-lmxxx])?
2. I defined \molecule to be
\def\molecule#1{$\rm#1$},
an usage example would be:
\molecule{HSO_4^{-}}
But how should I modify this it so that it would also work properly
w
Thomas A.Schmitz wrote:
For the time being, I'm thinking of a very simple list that could just
serve as a pattern for arranging the lines I get from processing the
cmap.xml. I'm just thinking, not writing code yet...
about code ... wybo dekker has cleaned up the texfont code, so that will be the
Hans Hagen said this at Wed, 2 Mar 2005 11:54:35 +0100:
>about code ... wybo dekker has cleaned up the texfont code, so that will
>be the
>starting point for extensions
Wow. Thanks, Wybo!
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Adam T. Lindsay, Computing Dept. [EMAI
On Mar 2, 2005, at 10:59 AM, Adam Lindsay wrote:
Hold on one minute... we're talking about encodings for alternate
glyphs,
right? That's orthogonal to what Unicode is about. 'a' and 'Asmall'
pretty much take up the same unicode "slot". Only 'a' appears in the
.cmap.xml file.
No, of course you're
Thomas A.Schmitz said this at Wed, 2 Mar 2005 07:18:29 +0100:
>However, your post made me think: I know nothing about XSLT, but enough
>perl to shoot myself in the foot. I guess if I had a version of
>texnansi.enc with the unicode values in addition to the names, that
>would be a good starting
Adam, I feel like a complete idiot now. I had been so proud about this
idea, but after re-reading you MyWay about OpenType, I see that I had
been reinventing the wheel: this is exactly the solution you had been
suggesting almost two years ago. Thanks for being generous about
this...
However, y
Adam Lindsay wrote:
This is good stuff. I've tried to advocate a naming convention that would
be appropriate to this. I would suggest calling this texnansi-osfsc.enc,
as baseencoding-variant.enc. This is so a modified encoding can
"masquerade" as the base encoding within ConTeXt.
i'll add the encod
Thomas A.Schmitz said this at Sun, 27 Feb 2005 08:57:36 +0100:
>I looked into it, and it turns out that Apple (?) has
>given new names even to quite "normal" characters - eacute becomes
>e_acute etc. So if you want to produce a tfm for that font, you have to
>invent a specific encoding vector.
This is good stuff. I've tried to advocate a naming convention that
would
be appropriate to this. I would suggest calling this
texnansi-osfsc.enc,
as baseencoding-variant.enc. This is so a modified encoding can
"masquerade" as the base encoding within ConTeXt.
Given this encoding with my suggest
Thomas A.Schmitz said this at Sat, 26 Feb 2005 10:13:00 +0100:
>In the last days, I played around with some truetype fonts, preparing
>them for use with ConTeXt by creating tfms via the texnansi encoding.
Hello (again) Thomas,
This is good stuff. I've tried to advocate a naming convention that
In the last days, I played around with some truetype fonts, preparing
them for use with ConTeXt by creating tfms via the texnansi encoding.
Some of these truetypes have expert features embedded into their
glyphs. texnansi automatically takes care of integrating the "ff,"
"ffi" and "ffl" ligatur
86 matches
Mail list logo
