Hi all, After searching the archives and reading the wikis, I'm still at loss on this one. :( I installed TexLive 2007 on Ubuntu Gutsy through the repository package. All went well. However, given that I have to use XeTeX and that the ConTeXt that was installed with the package dates from May 2007, which is between January and 08.29, to be sure everything was okay I updated ConTeXt. I did it manually because ctxtools didn't work. A problem with the paths. First red flag, but I went on manually. I got the newest cont-tmf.zip and unzipped it in /usr/share/texmf and regenerated the formats by doing: texexec --make --all To check I had the correct version, I ran, on the commandline, these two: texexec --check and: ctxtools --contextversion Both gave me 2007.09.28 16:52, which seems quite correct. However, when I try to compile a document (with the --xtx option), I get the following error: ConTeXt ver: 2007.04.17 12:51 MKII fmt: 2007.11.5 int: english/english language : language en is active system : cont-new loaded (/usr/share/texmf/tex/context/base/cont-new.tex FatalError : Your format does not match the base files! FormatVersion : 2007.04.17 12:51 MKII FilesVersion : 2007.09.28 16:52 Clearly, there is something I must do that I don't know about or that I haven't found anywhere. Anyone can help? I figure it's simple -- and with all those numerous update questions around, I'm still stumped. Many thanks in advance for any help. Cheers! Jeff Smith
Hello, Most things seem to be fine, you only forgot to run texexec --xtx --make --all to make the XeTeX-specific format. Mojca On 11/6/07, Jeff Smith wrote:
Hi all,
After searching the archives and reading the wikis, I'm still at loss on this one. :(
I installed TexLive 2007 on Ubuntu Gutsy through the repository package. All went well.
However, given that I have to use XeTeX and that the ConTeXt that was installed with the package dates from May 2007, which is between January and 08.29, to be sure everything was okay I updated ConTeXt.
I did it manually because ctxtools didn't work. A problem with the paths. First red flag, but I went on manually.
I got the newest cont-tmf.zip and unzipped it in /usr/share/texmf and regenerated the formats by doing:
texexec --make --all
To check I had the correct version, I ran, on the commandline, these two:
texexec --check
and:
ctxtools --contextversion
Both gave me 2007.09.28 16:52, which seems quite correct.
However, when I try to compile a document (with the --xtx option), I get the following error:
ConTeXt ver: 2007.04.17 12:51 MKII fmt: 2007.11.5 int: english/english
language : language en is active system : cont-new loaded (/usr/share/texmf/tex/context/base/cont-new.tex
FatalError : Your format does not match the base files!
FormatVersion : 2007.04.17 12:51 MKII FilesVersion : 2007.09.28 16:52
Clearly, there is something I must do that I don't know about or that I haven't found anywhere. Anyone can help? I figure it's simple -- and with all those numerous update questions around, I'm still stumped.
Many thanks in advance for any help. Cheers! Jeff Smith ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________
On Nov 6, 2007 5:07 PM, Mojca Miklavec
Hello,
Most things seem to be fine, you only forgot to run texexec --xtx --make --all to make the XeTeX-specific format.
Mojca
Uhm, while I first reported it didn't work, it probably has, but my
installation behaves strangely and I really cannot understand why.
When I run texexec from the command line, it works -- to a point,
meaning that the error I reported does not occur (there is another one
though).
When I run texexec from inside my editor (Winefish), it still reports
the bad format files like I said earlier. I have no idea how that can
happen. Linux is really making me feel stupid (my switch from Windows
is relatively recent).
That being said, if we continue on with my running texexec from the
commandline, as I said above, something else happens.:
** WARNING ** This .map file looks like a dvips format fontmap file.
** WARNING ** -- Current input buffer is: lmbsy5
LMMathSymbols5-BoldItalic "enclmmathsy ReEncodeFont"
On 11/7/07, Jeff Smith wrote:
On Nov 6, 2007 5:07 PM, Mojca Miklavec wrote:
Hello,
Most things seem to be fine, you only forgot to run texexec --xtx --make --all to make the XeTeX-specific format.
Mojca
Uhm, while I first reported it didn't work, it probably has, but my installation behaves strangely and I really cannot understand why. When I run texexec from the command line, it works -- to a point, meaning that the error I reported does not occur (there is another one though).
When I run texexec from inside my editor (Winefish), it still reports the bad format files like I said earlier. I have no idea how that can happen. Linux is really making me feel stupid (my switch from Windows is relatively recent).
That being said, if we continue on with my running texexec from the commandline, as I said above, something else happens.:
** WARNING ** This .map file looks like a dvips format fontmap file. ** WARNING ** -- Current input buffer is: lmbsy5 LMMathSymbols5-BoldItalic "enclmmathsy ReEncodeFont"
Also, it seems I can't access my system fonts. But I did run fc-cache -f (-v). Is there something else to do? When I run fc-list, I do see my system fonts that I should be able to use...
That's a "well-known" error. (To be completely honest, I'm not sure if those files are needed at all and when/why they're needed.) You need these files: http://minimals.contextgarden.net/fonts/common/fonts/map/dvipdfm/ which can be also fetched with rsync -rvzctl rsync://contextgarden.net/minimals/fonts/common/fonts/map/dvipdfm . You need to put them to [texmf]/fonts/map/dvipdfm and run mktexlsr. I have no idea about the other error (different behaviour in shell & in text editor). How did you install TeX? Do you have any TeX-related environmental variables? Mojca
2007/11/7, Jeff Smith
When I run texexec from inside my editor (Winefish), it still reports the bad format files like I said earlier. I have no idea how that can happen. Linux is really making me feel stupid (my switch from
You probably got new formats in ~/.texlive2007/texmf-var and have old formats still under /var, and the editor only sees the formats under /var. But this shouldn't happen. You restarted your editor? :-) Check the output of "texconfig conf". Best Martin
Hi again, Sorry for the delay, I was taken with real life worries for a bit. So, I realized I did have some leftovers from an earlier installation attempt. I cleaned everything and reinstalled TeXLive from the CD, from scratch. I will wait a bit before updating ConTeXt again, because right now I just want to access my system fonts (I'm on Linux) with XeTeX and I can't seem to manage to do that anymore. Everything else works. Now I just can't remember what I did back on Ubuntu Edgy/Feisty. When I run: fc-list I do see my fonts listed (after a fc-cache -f). What do I need more? Thanks for all the help! Jeff
Jeff Smith wrote:
Hi again,
Sorry for the delay, I was taken with real life worries for a bit.
So, I realized I did have some leftovers from an earlier installation attempt. I cleaned everything and reinstalled TeXLive from the CD, from scratch. I will wait a bit before updating ConTeXt again, because right now I just want to access my system fonts (I'm on Linux) with XeTeX and I can't seem to manage to do that anymore. Everything else works. Now I just can't remember what I did back on Ubuntu Edgy/Feisty. When I run:
fc-list
I do see my fonts listed (after a fc-cache -f). What do I need more?
I guess you have to setup OSFONTDIR (in texmf.cnf). Best wishes, Taco
On 11/9/07, Jeff Smith wrote:
Hi again,
Sorry for the delay, I was taken with real life worries for a bit.
So, I realized I did have some leftovers from an earlier installation attempt. I cleaned everything and reinstalled TeXLive from the CD, from scratch. I will wait a bit before updating ConTeXt again, because right now I just want to access my system fonts (I'm on Linux) with XeTeX and I can't seem to manage to do that anymore. Everything else works. Now I just can't remember what I did back on Ubuntu Edgy/Feisty. When I run:
fc-list
I do see my fonts listed (after a fc-cache -f). What do I need more?
You can either use \definetypeface[MyFace][rm][Xserif][Font Name] \setupbodyfont[MyFace,12pt] or prepare some more complex typescript examples. Note that if you want to use automatic mapping from --/--- to endash/emdashes, syntax has changed a bit since January until now. Can you send examples that don't work any more (I could imagine that you were using the new syntax (file: or name: prefix) which wasn't available ack in January). Mojca
On Saturday 10 November 2007 06:07:39 am Mojca Miklavec wrote:
On 11/9/07, Jeff Smith wrote:
Hi again, When I run:
fc-list
I do see my fonts listed (after a fc-cache -f). What do I need more?
You can either use
\definetypeface[MyFace][rm][Xserif][Font Name] \setupbodyfont[MyFace,12pt]
Ah, interesting. And what exactly is the content of Font Name? for example if fc-list displays: Bitstream Charter:style=Regular does that whole string go into the space for "Font Name"? Here is a more complex example: DejaVu Sans,DejaVu Sans Condensed:style=Condensed Bold Oblique,Bold Oblique I assume, perhaps wrongly, that this is in lieu of creating a typescript. The whole subject raises interesting possibilities for straying off the traditional TeX reservation as far as font selection is concerned. I use the TeXLive distro, but with pdftex updated to pdfTeX 3.141592-1.40.5-2.2 (Web2C 7.5.6) -- John Culleton Precision Typesetting Able Indexers and Typesetters http://wexfordpress.com
On 11/10/07, John Culleton wrote:
On Saturday 10 November 2007 06:07:39 am Mojca Miklavec wrote:
On 11/9/07, Jeff Smith wrote:
Hi again, When I run:
fc-list
I do see my fonts listed (after a fc-cache -f). What do I need more?
You can either use
\definetypeface[MyFace][rm][Xserif][Font Name] \setupbodyfont[MyFace,12pt]
Ah, interesting. And what exactly is the content of Font Name? for example if fc-list displays: Bitstream Charter:style=Regular
does that whole string go into the space for "Font Name"?
Unless it's broken this should work: \definetypeface[MyFace][rm][Xserif][Bitstream Charter]
Here is a more complex example: DejaVu Sans,DejaVu Sans Condensed:style=Condensed Bold Oblique,Bold Oblique
I assume, perhaps wrongly, that this is in lieu of creating a typescript.
I don't know how it works in that case, I should test. Xserif uses "/B", "/I" and "/BI" to get \bf, \it and \bi working. I have no idea how XeTeX handles "condensed bold oblique", but I would guess that you can provide \definetypeface[MyFace][rm][Xserif][DejaVu Sans Condensed]
The whole subject raises interesting possibilities for straying off the traditional TeX reservation as far as font selection is concerned.
I use the TeXLive distro, but with pdftex updated to pdfTeX 3.141592-1.40.5-2.2 (Web2C 7.5.6)
But you need XeTeX for that. Mojca
On Sat, 10 Nov 2007 09:24:32 -0500
John Culleton
On Saturday 10 November 2007 06:07:39 am Mojca Miklavec wrote:
On 11/9/07, Jeff Smith wrote:
Hi again, When I run:
fc-list
I do see my fonts listed (after a fc-cache -f). What do I need more?
You can either use
\definetypeface[MyFace][rm][Xserif][Font Name] \setupbodyfont[MyFace,12pt]
Ah, interesting. And what exactly is the content of Font Name? for example if fc-list displays: Bitstream Charter:style=Regular
The font name is "Bitstream Charter", the style entry is only needed for italic or bold style and you can write "Bitstream Charter/I" for italic or "Bitstream Charter/B" for the bold style.
does that whole string go into the space for "Font Name"?
Here is a more complex example: DejaVu Sans,DejaVu Sans Condensed:style=Condensed Bold Oblique,Bold Oblique
I would say you can write "DejaVu Sans" for the normal version and "DejaVu Sans Condensed" for the narrow version. Choosing the bold and italic styles should be possible with the feature tags in ConTeXt but I never tried the new font setups for XeTeX in ConTeXt.
I assume, perhaps wrongly, that this is in lieu of creating a typescript.
The whole subject raises interesting possibilities for straying off the traditional TeX reservation as far as font selection is concerned.
I use the TeXLive distro, but with pdftex updated to pdfTeX 3.141592-1.40.5-2.2 (Web2C 7.5.6)
Wolfgang
On Nov 10, 2007 6:07 AM, Mojca Miklavec
You can either use
\definetypeface[MyFace][rm][Xserif][Font Name] \setupbodyfont[MyFace,12pt]
or prepare some more complex typescript examples. Note that if you want to use automatic mapping from --/--- to endash/emdashes, syntax has changed a bit since January until now.
Can you send examples that don't work any more (I could imagine that you were using the new syntax (file: or name: prefix) which wasn't available ack in January).
Wow. I'm the worst ConTeXt user ever. I've asked for help several times now it's mostly been because I was too careless. In this case, my document had no \setupbodyfont. I've always used the Xserif way. *reddens in shame* :-( That being said, I'm interested to know more about the new sytax. Is it documented anywhere? Thanks, and sorry! Jeff
On 11/10/07, Jeff Smith wrote:
On Nov 10, 2007 6:07 AM, Mojca Miklavec wrote:
You can either use
\definetypeface[MyFace][rm][Xserif][Font Name] \setupbodyfont[MyFace,12pt]
or prepare some more complex typescript examples. Note that if you want to use automatic mapping from --/--- to endash/emdashes, syntax has changed a bit since January until now.
Can you send examples that don't work any more (I could imagine that you were using the new syntax (file: or name: prefix) which wasn't available ack in January).
Wow. I'm the worst ConTeXt user ever. I've asked for help several times now it's mostly been because I was too careless. In this case, my document had no \setupbodyfont. I've always used the Xserif way. *reddens in shame* :-(
That being said, I'm interested to know more about the new sytax. Is it documented anywhere?
Of course not :) You can say (features=default is optional) \definefontsynonym[SomeFont][name:Font Name][features=default] which means that XeTeX will call the font \font\somefont="FontName;mapping=tex-text,..." (tex-text is implied by features=default) Back in January and before one achived the same by saying \definefontsynonym[SomeFont]['Font Name;mapping=tex-text'][encoding=uc] Now encoding=uc is not needed any more since it's implied when one runs XeTeX or LuaTeX. To be honest, it's not completely clear to me what should happen with type-xtx typescripts (how to remove uc encoding from there). The other possibility is to say \definefontsynonym[SomeFont][file:lmroman12-regular][features=default] which means that XeTeX will load the font "lmroman12-regular.otf" from texmf tree, the equivalent in plain XeTeX being \font\somefont="[lmroman12-regular];mapping=tex-text,..." When there is neither file: nor name: prefix (\definefontsynonym[SomeFont][lmr12]), it means that XeTeX will try to load a font in this order - lmr12 (good old tfm fonts) - "lmr12" - "[lmr12]" (the order might change) Mojca
When there is neither file: nor name: prefix (\definefontsynonym[SomeFont][lmr12]), it means that XeTeX will try to load a font in this order - lmr12 (good old tfm fonts) - "lmr12" - "[lmr12]"
The last two items meaning, respectively: • "lmr12" Try and load the *font name* lmr12 as an installed font (first string in the output of fc-list, Display Name in Apple Fontbook, etc.)—This is the recommended option in XeteX, by the way • "[lmr12]" Try and load the *file name* lmr12 from the texmf tree (as looked up by the kpathsea library)
On Nov 10, 2007 9:23 PM, Mojca Miklavec
Of course not :)
You can say (features=default is optional) \definefontsynonym[SomeFont][name:Font Name][features=default] which means that XeTeX will call the font \font\somefont="FontName;mapping=tex-text,..." (tex-text is implied by features=default)
Back in January and before one achived the same by saying \definefontsynonym[SomeFont]['Font Name;mapping=tex-text'][encoding=uc] Now encoding=uc is not needed any more since it's implied when one runs XeTeX or LuaTeX. To be honest, it's not completely clear to me what should happen with type-xtx typescripts (how to remove uc encoding from there).
The other possibility is to say \definefontsynonym[SomeFont][file:lmroman12-regular][features=default] which means that XeTeX will load the font "lmroman12-regular.otf" from texmf tree, the equivalent in plain XeTeX being \font\somefont="[lmroman12-regular];mapping=tex-text,..."
When there is neither file: nor name: prefix (\definefontsynonym[SomeFont][lmr12]), it means that XeTeX will try to load a font in this order - lmr12 (good old tfm fonts) - "lmr12" - "[lmr12]" (the order might change)
Hmmm.. must I use \setupbodyfont as well when using the \definefontsynonym method? Because those alternative methods don't work. This works: \definetypeface[corps][rm][Xserif][Garamond Premier Pro] \setupbodyfont[corps,12pt] But not this: \definefontsynonym[corps][name:Garamond Premier Pro][features=default] or \definefontsynonym[corps][file:GaramondPremrPro.][features=default] or \definefontsynonym[corps][Garamond Premier Pro][features=default] I see the default Times font instead (it compiles ok). Jeff
On 11/13/07, Jeff Smith wrote:
On Nov 10, 2007 9:23 PM, Mojca Miklavec wrote:
Of course not :)
You can say (features=default is optional) \definefontsynonym[SomeFont][name:Font Name][features=default] which means that XeTeX will call the font \font\somefont="FontName;mapping=tex-text,..." (tex-text is implied by features=default)
Back in January and before one achived the same by saying \definefontsynonym[SomeFont]['Font Name;mapping=tex-text'][encoding=uc] Now encoding=uc is not needed any more since it's implied when one runs XeTeX or LuaTeX. To be honest, it's not completely clear to me what should happen with type-xtx typescripts (how to remove uc encoding from there).
The other possibility is to say \definefontsynonym[SomeFont][file:lmroman12-regular][features=default] which means that XeTeX will load the font "lmroman12-regular.otf" from texmf tree, the equivalent in plain XeTeX being \font\somefont="[lmroman12-regular];mapping=tex-text,..."
When there is neither file: nor name: prefix (\definefontsynonym[SomeFont][lmr12]), it means that XeTeX will try to load a font in this order - lmr12 (good old tfm fonts) - "lmr12" - "[lmr12]" (the order might change)
Hmmm.. must I use \setupbodyfont as well when using the \definefontsynonym method? Because those alternative methods don't work. This works:
\definetypeface[corps][rm][Xserif][Garamond Premier Pro] \setupbodyfont[corps,12pt]
Oh, sorry. I should explan a bit more in detail. When you're using Xsans, you're actually using approxximately the following shortcuts (see type-xtx.tex; although what I'm sending here are the new/fixed definitions, they should work the same way): \starttypescript[Xserif][all][name] \definefontsynonym[Dummy] [name:\typescripttwo] [features=default] \definefontsynonym[DummyItalic] [name:\typescripttwo/I] [features=default] \definefontsynonym[DummyBold] [name:\typescripttwo/B] [features=default] \definefontsynonym[DummyBoldItalic][name:\typescripttwo/BI][features=default] \definefontsynonym[DummyCaps] [name:\typescripttwo] [features=smallcaps] ... \definefontsynonym[Serif] [Dummy] \definefontsynonym[SerifBold] [DummyBold] \definefontsynonym[SerifItalic] [DummyItalic] \definefontsynonym[SerifBoldItalic] [DummyBoldItalic] \definefontsynonym[SerifCaps] [DummyCaps] \stoptypescript Xserif defines the whole family, so switches like \bf, \bi, ... etc will work properly.
But not this:
\definefontsynonym[corps][name:Garamond Premier Pro][features=default] or \definefontsynonym[corps][file:GaramondPremrPro.][features=default] or \definefontsynonym[corps][Garamond Premier Pro][features=default]
That only defines a font, but doesn't switch to it. You could: 1.) use \definedfont[corps], but things like \bf for example won't work 2.) use \definefontsynonym[Serif][file:GaramondPremrPro][features=default] 3.) create a proper typescript, here's an example from type-xtx, which you can adapt for your needs: \starttypescript[serif][timesnewroman] \definefontsynonym[MSTimes] [name:Times New Roman] [features=default] \definefontsynonym[MSTimesItalic] [name:Times New Roman Italic] [features=default] \definefontsynonym[MSTimesBold] [name:Times New Roman Bold] [features=default] \definefontsynonym[MSTimesBoldItalic][name:Times New Roman Bold Italic][features=default] \stoptypescript \starttypescript[serif][timesnewroman][name] \definefontsynonym[Serif] [MSTimes] \definefontsynonym[SerifBold] [MSTimesBold] \definefontsynonym[SerifItalic] [MSTimesItalic] \definefontsynonym[SerifBoldItalic] [MSTimesBoldItalic] \definefontsynonym[SerifSlanted] [MSTimesItalic] \definefontsynonym[SerifBoldSlanted][MSTimesBoldItalic] \definefontsynonym[SerifCaps] [MSTimes] \stoptypescript \definetypeface[mytimes][rm][serif][timesnewroman] \setupbodyfont[mytimes,12pt] Mojca
participants (7)
-
Arthur Reutenauer -
Jeff Smith -
John Culleton -
Martin Schröder -
Mojca Miklavec -
Taco Hoekwater -
Wolfgang Schuster