Re: [NTG-context] updating ConTeXt to latest on openbsd-current Q #3
On 3/7/06, frantisek holop wrote: > \ohungarumlaut is the one. > > i don't specify any encodings, and i use vanilla latin2 > (il2 in context if i am not mistaken). > > should i use \enableregime[il2] ? It's called \enableregime[latin2]. Some time ago I also suggested to add some more synonyms (so that \enableregime[il2] and \enableregime[iso-8859-2] would work as well, but they weren't included [yet]). Mojca ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] updating ConTeXt to latest on openbsd-current Q #3
hmm, on Tue, Mar 07, 2006 at 11:12:18AM +0100, Mojca Miklavec said that
> On 3/6/06, frantisek holop wrote:
> > ok, the only problem i see at first glance is \"{o}
> > (long hungarian umlaut) is with a wave and not the proper umlaut.
> >
> > could this be a problem with context's encodings?
> > i presume the lm fonts contain the right character...
> > it is certainly not that special :)
>
> Which one do you have in mind? \ohungarumlaut (ő) or \odiaeresis (ö)?
> They both seem to work here, although you might have forgotten the
> magic keyword \enableregime[utf] (or whatever encoding you might want
> to use - if your favourite is not available, ask for it).
\ohungarumlaut is the one.
i don't specify any encodings, and i use vanilla latin2
(il2 in context if i am not mistaken).
should i use \enableregime[il2] ?
-f
--
the first sight of love is the last of wisdom.
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] updating ConTeXt to latest on openbsd-current Q #3
On 3/6/06, frantisek holop wrote:
> ok, the only problem i see at first glance is \"{o}
> (long hungarian umlaut) is with a wave and not the proper umlaut.
>
> could this be a problem with context's encodings?
> i presume the lm fonts contain the right character...
> it is certainly not that special :)
Which one do you have in mind? \ohungarumlaut (ő) or \odiaeresis (ö)?
They both seem to work here, although you might have forgotten the
magic keyword \enableregime[utf] (or whatever encoding you might want
to use - if your favourite is not available, ask for it).
Mojca
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] updating ConTeXt to latest on openbsd-current Q #2
frantisek holop wrote: > hmm, on Mon, Mar 06, 2006 at 10:57:57PM +0100, Taco Hoekwater said that > >>Finally, what goes wrong: unless you either delete the teTeX-supplied >>context formats or change texmf.cnf, the old formats will be found first >>by kpathsea. > > > excellent explanation. > > so is it either or? is it enough to change texmf.cnf _or_ delete the > old format files? I believe it is either or, but I am not sure any more. It's been a while since I've used a "normal" installation. Cheers, Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] updating ConTeXt to latest on openbsd-current Q #3
Hi again,
frantisek holop wrote:
>
> ok, seems like my last problem is about the fonts. i must say the
> wiki gets a bit controversial here:
[...]
> what now? i downloaded the lm.tgz package, compared files, and
> clearly, teTeX 3.0 files are old-old-old.
The wiki is right, the FAQ is wrong.
> ok, the only problem i see at first glance is \"{o}
> (long hungarian umlaut) is with a wave and not the proper umlaut.
I know not (font encoding is not my best point these days).
Cheers, Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] updating ConTeXt to latest on openbsd-current Q #2
hmm, on Mon, Mar 06, 2006 at 10:57:57PM +0100, Taco Hoekwater said that > Finally, what goes wrong: unless you either delete the teTeX-supplied > context formats or change texmf.cnf, the old formats will be found first > by kpathsea. excellent explanation. so is it either or? is it enough to change texmf.cnf _or_ delete the old format files? from the wiki: -%<-- Cleanup fmtutil Optionally, you can remove ConTeXt support from teTeX's configuration, because ConTeXt does not use fmtutil. -%<-- -f -- wasting your life is prohibited by the law ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] updating ConTeXt to latest on openbsd-current Q #3
hmm, on Mon, Mar 06, 2006 at 11:04:25PM +0100, Taco Hoekwater said that
> This is one of the latin modern fonts. ConTeXt depends on the latin
> modern package, and will not run without errors if latin modern is
> not installed.
thanks for the all the answers...
this all could be in the wiki thought, would save you/me mining the
archives :) so i'll shamefully steal and put this info into the
openbsd upgrade page i just started :)
ok, seems like my last problem is about the fonts. i must say the
wiki gets a bit controversial here:
http://wiki.contextgarden.net/TeTeX_3.0_installation says:
Install a Latin Modern font update
The Latin Modern fonts are still in development, so teTeX has a hard
time catching up. To get a stable system, you have to manually download
the [Latin Modern distribution] from ctan and install the package
according to the[instructions in the FAQ].
The ConTeXt-specific support files are included in Cont-tmf.zip, so it
is just a matter of installing the actual font files.
http://wiki.contextgarden.net/Cont-lmt.zip says:
This was the Latin Modern release from CTAN, repackaged for an easier
download.
It has disappeared since Context 2006.02.01
http://www.tex.ac.uk/cgi-bin/texfaq2html?label=uselmfonts says:
Note that teTeX distributions, from version 3.0, already have the lm
fonts: all you need do is use them.
according to the wiki, i don't need cont-lmt.zip anymore.
according to the tex faq i already have them.
what now? i downloaded the lm.tgz package, compared files, and
clearly, teTeX 3.0 files are old-old-old.
so i copied over the old files, run texhash, and lo and behold,
fonts are all right.
ok, the only problem i see at first glance is \"{o}
(long hungarian umlaut) is with a wave and not the proper umlaut.
could this be a problem with context's encodings?
i presume the lm fonts contain the right character...
it is certainly not that special :)
-f
--
part-time musicians are semiconductors.
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] updating ConTeXt to latest on openbsd-current Q #2
frantisek holop wrote: >hi there, > >my second question, is more like asking for pointers... > >where can i read more about fmtutil, and how come that >context does not use it when (i assume) pdftex does? > > > Fmtutil is used to generate the necessary format files to run tex. - Context provides this within texexec. So generating the formats becomes simply texexec --make en metafun mptopdf i.e. a list of requested formats. even shorter this is texexec --make all.. This will however generate formats which you will never use. But nowadays, where diskspace is no issue :-) Kind regards Willi >--\startquote--- >Cleanup fmtutil > >Optionally, you can remove ConTeXt support from teTeX's configuration, >because ConTeXt does not use fmtutil. > >Using > ># fmtutil-sys --edit > >you can comment out the lines for metafun,cont-en, and mptopdf > >And you can use > ># cd /usr/local/teTeX/share/texmf-var/web2c && rm -f cont-en.* metafun.* >mptopdf.* > >to remove the old (fmtutil-generated) formats. > >--\stopquote > >-f > > ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] updating ConTeXt to latest on openbsd-current
On Mar 6, 2006, at 10:17 PM, frantisek holop wrote: > hi there, > > i am a (somewhat) long time pdflatex user and i am trying to > convert to > ConTeXt. That's good, welcome to the ConTeXt community. I'm sure you'll like it around here... I'll try and answer some of your questions: > > shell_escape = t > > if it isn't already. > > --\stopquote > > in the default openbsd package this line says: > > shell_escape = f > > what is the difference? and what is it for anyway? > some external execution of the legends are true? :) > Among other things, ConTeXt has wonderful integration for an implementation of Metapost called Metafun. If you set shell escape to "t," ConTeXt will be able to compile Metafun code that is included in your documents. this is a security issue when you're on a system with many users; if you;re running it on your own personal computer, it is safe to set this to true. > kpathsea: Running mktexmf ec-lmr12 > ! I can't find file `ec-lmr12'. > <*> ...ljfour; mag:=1; nonstopmode; input ec-lmr12 This is the old Latin-Modern bug that is a recurring event on this list. Download the file cont-lmt.zip from the pragma website, unzip it in your texmf-tree, run texhash, and this should solve your problems on this front. HTH, you'll certainly receive more answers. Thomas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] updating ConTeXt to latest on openbsd-current Q #3
frantisek holop wrote: > > please consider the following minimal example: > Hi again (example snipped)! > ! Font \*12ptrmtf*=ec-lmr12 not loadable: Metric (TFM) file not found. This is one of the latin modern fonts. ConTeXt depends on the latin modern package, and will not run without errors if latin modern is not installed. Cheers, Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] updating ConTeXt to latest on openbsd-current
frantisek holop wrote: > > the first step to upgrade context is: > > --\startquote--- > Fix texmf.cnf > --\stopquote > > i deliberately skipped this one, and the new context worked without it. > what does this precisely do? See the answer to #2, already posted > but it turned out that that this new line comes up anyway. could anyone > comment on it? That line from texexec comes from paranoia in texexec, I think it is displayed always. > the next tip is to > > --\startquote--- > shell_escape = t > --\stopquote > > in the default openbsd package this line says: > > shell_escape = f > > what is the difference? and what is it for anyway? > some external execution of the legends are true? :) It allows tex to start programs on-the-fly. Most imprtantly metapost, for the creation of graphics. It works fine without, but with the 'f' setting, usually an extra tex run is needed, loosing you valuable time. Cheers, Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] updating ConTeXt to latest on openbsd-current Q #2
Hi there! frantisek holop wrote: > my second question, is more like asking for pointers... > > where can i read more about fmtutil, and how come that > context does not use it when (i assume) pdftex does? The following comes from a thread in december about this same issue. The full thread is here: http://archive.contextgarden.net/message/20051213.100910.f7bb2779.en.html Posted by Taco Hoekwater (hey, that's me!): --- Here's what happened. In the "really old" days, formats ended with .fmt, like plain.fmt. When etex and omega came around, they identified themselves by having e.g. plain.efmt (note the extra "e"), so that they could coexist happily. However, this cluttered the build system quite a bit, so recently it was decided to drop the extra characters. At that time, it was understood that there would be an extra subdirectory below texmf/web2c to differentiate between the different engines (at least, that is what Hans and I gathered from the discussion). So you would have, e.g. "web2c/pdfetex/cont-en.fmt" as well as "web2c/omega/cont-en.fmt". But it turned out that since LaTeX has separate names for the different formats anyway (Lambda etc.), ConTeXt was the only client of this new feature, and Thomas Esser decided that it was not worth the effort to support these extra directories. However, for ConText it would be very, very unwieldy to have cont-pdfetex-en.fmt, cont-xetex-en.fmt, cont-aleph-en.fmt etc., each six or seven times. And because context is always called through texexec, the latest texexec's implement this engine subdirectory functionality for you. Finally, what goes wrong: unless you either delete the teTeX-supplied context formats or change texmf.cnf, the old formats will be found first by kpathsea. ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] updating ConTeXt to latest on openbsd-current Q #3
hi there,
this (for the moment) last question is not really about the upgrade but
about context itself. this is the problem because of which i upgraded
in the first (but not the only) place.
please consider the following minimal example:
%<
\starttext
\section{Pogány köszöntő}
\startlines
Nézd! dércsipte fáink megőszült
fején ül most a szél és lengő
harangú tornyok között csak
megkondúlnak a jámbor imák!
Csorgó nyálával békés borjú
lépdel még szekerünk után, de
már nem kószál szárnyas szavakkal
szájunk körül halovány ámen!
Megmosakodtunk! tornyok között,
fákon pihenő szélben és most
megőszült fák közt csókokkal tarkán
pogány szemekkel kitavaszodtunk!
A testünket nézd! együtt fakad a
rüggyel drága hús és napbadobált
csókjaink után boldog torokkal
így, istentelenül fölsikoltunk!
1930. január 11.
\stoplines
\stoptext
%<
here's the transcript of context:
%<
amaaq> texexec --pdf file
TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005
fixing texformat path :
.:{!!/home/f/.texmf-config,!!/home/f/.texmf-var,/home/f/texmf,!!/etc/texmf,!!/var/texmf,!!/usr/local/share/texmf,!!/usr/local/share/texmf-local,!!/usr/local/share/texmf-dist}/web2c/{$engine,}{pdfetex,}
fixing engine variable : pdfetex
executable : pdfetex
format : cont-en
inputfile : hun
output : pdftex
interface : en
current mode : none
TeX run : 1
This is pdfeTeX, Version 3.141592-1.30.6-2.2 (Web2C 7.5.5)
(/usr/local/share/texmf-local/web2c/natural.tcx)
entering extended mode
(./hun.tex
ConTeXt ver: 2006.02.15 17:41 fmt: 2006.3.4 int: english mes: english
language: language en is active
system : cont-new loaded
(/usr/local/share/texmf-local/tex/context/base/cont-new.tex
systems : beware: some patches loaded from cont-new.tex
color : palette rollover is available
)
system : cont-old loaded
(/usr/local/share/texmf-local/tex/context/base/cont-old.tex
loading : Context Old Macros
)
system : cont-fil loaded
(/usr/local/share/texmf-local/tex/context/base/cont-fil.tex
loading : Context File Synonyms
)
system : cont-sys.rme loaded
(/usr/local/share/texmf-local/tex/context/user/cont-sys.rme
(/usr/local/share/texmf-local/tex/context/base/type-exa.tex)
(/usr/local/share/texmf-local/tex/context/base/type-syn.tex)
(/usr/local/share/texmf-local/tex/context/base/type-enc.tex)
(/usr/local/share/texmf-local/tex/context/base/type-siz.tex)
(/usr/local/share/texmf-local/tex/context/base/type-map.tex)
(/usr/local/share/texmf-local/tex/context/base/type-spe.tex)
(/usr/local/share/texmf-local/tex/context/base/type-akb.tex))
bodyfont: 12pt rm is loaded
kpathsea: Running mktextfm ec-lmr12
mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode;
input ec-lmr12
This is METAFONT, Version 2.71828 (Web2C 7.5.4)
kpathsea: Running mktexmf ec-lmr12
! I can't find file `ec-lmr12'.
<*> ...ljfour; mag:=1; nonstopmode; input ec-lmr12
Please type another input file name
! Emergency stop.
<*> ...ljfour; mag:=1; nonstopmode; input ec-lmr12
Transcript written on mfput.log.
grep: ec-lmr12.log: No such file or directory
mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input
ec-lmr12' failed to make ec-lmr12.tfm.
kpathsea: Appending font creation commands to missfont.log.
! Font \*12ptrmtf*=ec-lmr12 not loadable: Metric (TFM) file not found.
\relax
\xxdododefinefont ...tspec {#4}\newfontidentifier
\let \localrelativefontsiz...
\fontstrategy ...ame #1\csname #2#3#4#5\endcsname
\tryingfontfalse \fi
...yle \fontalternative \fontsize
\fi \iftryingfont \fontstr...
\synchronizefont ...strategy \the \fontstrategies
\relax \fi \ifskipfontchar...
\getvalue [EMAIL PROTECTED]@ \fontstyle }
\edef \fontstyle {\fontstyle }\if...
...
l.1
\starttext
? X
No pages of output.
Transcript written on hun.log.
return code : 256
run time : 6 seconds
total run time : 6 seconds
%<
some gurus will kill me now, because this is (for me) a simple
missfont.log case, but the truth is, that no other macro packages are
missing any fonts at all. i must also add, that i did a
amaaq> sudo updmap --enable Map lm.map
before that, my accented letters were simply ingored out from the
output, and if i changed to a well known font (charter) per
instructions, i got a missing font again.
-f
--
and the reset button lets you re-run autoexec.bat
[NTG-context] updating ConTeXt to latest on openbsd-current Q #2
hi there, my second question, is more like asking for pointers... where can i read more about fmtutil, and how come that context does not use it when (i assume) pdftex does? --\startquote--- Cleanup fmtutil Optionally, you can remove ConTeXt support from teTeX's configuration, because ConTeXt does not use fmtutil. Using # fmtutil-sys --edit you can comment out the lines for metafun,cont-en, and mptopdf And you can use # cd /usr/local/teTeX/share/texmf-var/web2c && rm -f cont-en.* metafun.* mptopdf.* to remove the old (fmtutil-generated) formats. --\stopquote -f -- the best way out of a difficulty is through it. ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] updating ConTeXt to latest on openbsd-current
hi there,
i am a (somewhat) long time pdflatex user and i am trying to convert to
ConTeXt. openbsd comes with teTeX 3.0 pre-packaged, that is with a very
old ConTeXt. the package has some openbsd specific stuff, but minimal,
and only for keeping cnf files between updates and a couple of paths are
different, but that is it.
i was (am) having font problems, so i thought an upgrade would not hurt.
the lovely guides on contextgarden.net got me started, and with minor
changes i have a fresh ConTeXt up and running, but i have some problems
still i am afraid. i am very new to ConTeXt and to TeX in general,
i was always behind the "safe" curtains of macros (like memoir, etc).
as i followed the instructions from here:
http://wiki.contextgarden.net/TeTeX_3.0_installation
my question are related to this page
i will break down my question into more mails, so it's not too long,
and so that people can answer to mails they know the answer to :)
the first one:
the first step to upgrade context is:
--\startquote---
Fix texmf.cnf
Now first you have to fix texmf.cnf as supplied with teTeX:
# vi /usr/local/teTeX/share/texmf/web2c/texmf.cnf
You have to add an engine path to the TEXFORMATS line, so that it reads:
TEXFORMATS = .;$TEXMF/web2c/{$engine,}
--\stopquote
i deliberately skipped this one, and the new context worked without it.
what does this precisely do?
when i first run the new context, a new line in the output immediately
caught my attention:
TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005
fixing texformat path : .:{!!/home/f/.texmf-config,!!/home/f/.texmf-var,/home/f
/texmf,!!/etc/texmf,!!/var/texmf,!!/usr/local/share/texmf,!!/usr/local/share/tex
mf-local,!!/usr/local/share/texmf-dist}/web2c/{$engine,}{pdfetex,}
so i thought, ok, here's the path issue. so i added "{$engine,}" as intructed,
but it turned out that that this new line comes up anyway. could anyone
comment on it?
the next tip is to
--\startquote---
While at it, you probably want to set
shell_escape = t
if it isn't already.
--\stopquote
in the default openbsd package this line says:
shell_escape = f
what is the difference? and what is it for anyway?
some external execution of the legends are true? :)
-f
--
i'm not old. i'm chronologically gifted.
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
