On Thu, Jul 17, 2008 at 1:14 AM, Diego Depaoli wrote:

2008/7/16 Alan Stone : [snip]

...

Many thanks in advance for your enlightening help.

For some obscure reason right fontnames are linked with wrong filenames. This is the output of mtxrun --script fonts --list on my system [...] times new roman Times New Roman Times_New_Roman.ttf (real filename times.ttf) times new roman bold Times New Roman Bold Times_New_Roman_Bold.ttf (real filename timesbd.ttf) and so on...

You must rename the files (tested, it works) or change [name:Times New Roman] with [file:times] in your typescript (untested) Cheers

Hi Diego, Alans entries for the font names are correct because the files have different names on Mac with spaces in them. Wolfgang

On Thu, Jul 17, 2008 at 5:39 PM, Diego Depaoli wrote:

2008/7/17 Wolfgang Schuster :

...

On Thu, Jul 17, 2008 at 1:14 AM, Diego Depaoli wrote:

...

2008/7/16 Alan Stone : [snip]

...

Many thanks in advance for your enlightening help.

For some obscure reason right fontnames are linked with wrong filenames. This is the output of mtxrun --script fonts --list on my system [...] times new roman Times New Roman Times_New_Roman.ttf (real filename times.ttf) times new roman bold Times New Roman Bold Times_New_Roman_Bold.ttf (real filename timesbd.ttf) and so on... Hi Diego,

Alans entries for the font names are correct because the files have different names on Mac with spaces in them. Understood... but this issue still exists in Ubuntu with such fonts imported from Windows. Where mtxrun catches fonts filenames?

Hi Diego, we are talking about two differents things, what you mean is the filename of the fonts you could access with [file:...] in typescripts and which is different on Windows (and all other where the core font packages are used) and on Mac. The font name is another thing and can be different from the file name, you could access fonts by font name with [name:...] in MkIV and this name should (not sure if this is so) be the same on both systems. Regards, Wolfgang

With Ubuntu and fonts there are several things going on. Generally, the system-wide fonts are kept under /usr/share/fonts An alternate place could be /usr/local/fonts That, however, is usually empty because packages put fonts in named directories, e.g., in the ttf dir in /usr/share/fonts TeX-related fonts basically sit in the texmf tree, usually in /usr/share/texmf-texlive/fonts You can also add your own into /usr/share/texmf/fonts Or you can put fonts into ~/.fonts and into your (correct me if I err) ~/.texmf-var/fonts THEN there's defoma, the Debian Font Manager, and I am not sure what ramifications exist there. There is a way to make things like otf fonts in your texmf trees visible to defoma, but I have yet to RTFMP, except to install the cm-super XII package. HTH Charles On Fri, 2008-07-18 at 23:22 +0200, Diego Depaoli wrote:

2008/7/18 Wolfgang Schuster :

...

...

but this issue still exists in Ubuntu with such fonts imported from Windows. Where mtxrun catches fonts filenames?

Hi Diego, Hello Wolfgang,

we are talking about two differents things, what you mean is the filename of the fonts you could access with [file:...] in typescripts and which is different on Windows (and all other where the core font packages are used) and on Mac. The font name is another thing and can be different from the file name, you could access fonts by font name with [name:...] in MkIV and this name should (not sure if this is so) be the same on both systems.

That's clear to me, but my question was about the wrong correspondence between font names and filename. As I wrote mtxrun --script fonts --lists showed filenames which I didn't find anywhere, so I thought mtxrun rewrote them. Repeating the same procedure under FreeBSD all goes right. Perhaps in my Ubuntu system there is more than one Times New Roman, Arial..., (even I don't know where they live) and this confused ConTeXt. Next time I boot Ubuntu, I'll search in the whole filesystem. Thanks for the answer and sorry for the noise.

On Saturday 19 July 2008 06:03:43 am Alan Stone wrote:

On Sat, Jul 19, 2008 at 6:49 AM, Charles P. Schaum

wrote:

...

With Ubuntu and fonts there are several things going on.

Which begets the question...

Regarding font installation, detection and other (non font related) issues which occur recurrently when working with (Con)TeX(t), which GNU/Linux distribution(s) is(/are) most user-friendly ?

Alan

I just avoid font miseries by relying mostly on the \font primitive. The complexities of creating and using typescripts etc. take too much time and too much head scratching. I do use the Texfont utility to create the necessary font bits and pieces when I buy a new type 1 font. All the aliases etc. in Context don't help me much. I simply define the needed fonts in the sizes I will use. If I need another size I just copy the \font statement, change the font name and change the size parameter. For nimbus bold condensed I end up with fonts named numbux nimbuy nimbua etc. This is of course not the Context way, but it saves me time and grief. I depend on texlive in my Slackware 12.1 distro. Slack comes with tetex but AFAIK that is no longer updated. Therefore I don't bother to include it when building Slack. I install texlive from the cdr and then modify /etc/profile by adding /usr/local/texlive/2007/bin/i386-linux: to the PATH= string. Thus far the versions of Context (mkii) and pdftex etc. found on texlive have been stable and reliable. -- John Culleton Resources for every author and publisher: http://wexfordpress.com/tex/shortlist.pdf http://wexfordpress.com/tex/packagers.pdf http://www.creativemindspress.com/newbiefaq.htm http://www.gropenassoc.com/TopLevelPages/reference%20desk.htm

On Thu, Jul 17, 2008 at 5:00 PM, Alan Stone wrote:

Thanks Wolfgang.

...

calm down.

Done.

I've let some steam off earlier on. OoOo<:O)

...

\setuphead[chapter][style=\

...

myHeadingsFont\myChapterFont]

You have to load 'myHeadingsfont' typescript before you can use them because they are not available on outer level, only fonts used as bodyfont can be accesed without this selection.

That works indeed.

...

I found the information to solve your problem in the fonts manual and you should read it if you need more information.

Oh, the number of times I read it. One more time a moment ago.

Sooo... the Da Fonti Code is hidden in there. In which section of the manual did you find the clue ?

I found at page 9 and 9 what I needed.

In my quest to further understand how this stuff works, I've been testing the following...

\setuppapersize [A4][A4]

\starttypescript [serif] [mySerifFont] \definefontsynonym [mySerifFontRegular] [name:Times New Roman] [features=default] \definefontsynonym [mySerifFontItalic] [name:Times New Roman Italic] [features=default] \definefontsynonym [mySerifFontBold] [name:Times New Roman Bold] [features=default] \definefontsynonym [mySerifFontBoldItalic] [name:Times New Roman Bold Italic] [features=default] \stoptypescript \starttypescript [serif] [mySerifFont] \setups[font:fallback:serif] \definefontsynonym [Serif] [mySerifFontRegular] \definefontsynonym [SerifItalic] [mySerifFontItalic] \definefontsynonym [SerifBold] [mySerifFontBold] \definefontsynonym [SerifBoldItalic] [mySerifFontBoldItalic] \stoptypescript %\starttypescript [mySerifFont] % \definetypeface [mySerifFont] [rm] [serif] [mySerifFont] [default] %\stoptypescript

\starttypescript [sans] [mySansFont] \definefontsynonym [mySansFontRegular] [name:Arial] [features=default] \definefontsynonym [mySansFontItalic] [name:Arial Italic] [features=default] \definefontsynonym [mySansFontBold] [name:Arial Bold] [features=default] \definefontsynonym [mySansFontBoldItalic] [name:Arial Bold Italic] [features=default] \stoptypescript \starttypescript [sans] [mySansFont] \setups[font:fallback:sans] \definefontsynonym [Sans] [mySansFontRegular] \definefontsynonym [SansItalic] [mySansFontItalic] \definefontsynonym [SansBold] [mySansFontBold] \definefontsynonym [SansBoldItalic] [mySansFontBoldItalic] \stoptypescript %\starttypescript [mySansFont] % \definetypeface [mySansFont] [ss] [sans] [mySansFont] [default] %\stoptypescript

\starttypescript[myFonts] \definetypeface [mySerifFont] [rm] [serif] [mySerifFont] [default] \definetypeface [mySansFont] [ss] [sans] [mySansFont] [default] \stoptypescript

\starttypescript[myFonts] \definetypeface [myFonts] [rm] [serif] [mySerifFont] [default] \definetypeface [myFonts] [ss] [sans] [mySansFont] [default] \stoptypescript You need the same name for both typefaces.

\usetypescript[myFonts]

\setupbodyfont[mySerifFont,12pt] % this displays the correct font %\setupbodyfont[mySansFont,12pt] % this displays the correct font

\setupbodyfont[myFonts]

\definefont[myChapterFont][mySansFont sa 1.728] % compile error at line 57 with (2) [and (1)] %\definefont[myChapterFont][Arial sa 1.728] % this works with (1), compile error at line 57 with (2) %\definefont[myChapterFont][Sans sa 1.728] % defaults to LM font with (1), compile error at line 57 with (2)

%\setuphead[chapter][style=\myChapterFont] % (1) %\setuphead[chapter][style=\myFonts\myChapterFont] % (2) %\setuphead[chapter][style=\tfc\mySansFont] % (3) this works

\starttext

\chapter{chapter test} % line 57

\section{section test}

text test

\stoptext

Looking for further clues.

Alan

P.S. Resistance is futile Fontzi...I will assimilate you!

I will add to my todo list "Write a few lines about font installation for XeTeX and LuaTeX and how to use them in style keys". Regards, Wolfgang

Thanks a lot for your helpful comments Wolfgang. I will add to my todo list "Write a few lines about font installation

for XeTeX and LuaTeX and how to use them in style keys".

With the bits and pieces of information ( current and outdated ) about these matters presently being scattered all over the place, an updated guide will definitely be very useful for newbies ( and oldies ? ), speeding up their comprehension and enabling them to focus on what's important, i.e. productive issues, using ConText with LuaTeX/XeTeX. Have a great weekend, Alan