Fonts & "esotic" languages

Fonts & "esotic" languages

[Giuseppe Bilotta (Oblomov)]

Hello,

I was browsing through the ConTeXt files, and I noticed the font-* files.
And I thus discovered ConTeXt support for "esotic" languages (Arab, Hebrew)
through ArabTeX. I wonder then if it would be possible an Omega support ...

Also, I noticed the T1 (=EC, or DC, or what you want to name it) encoding
support, but no font-* referring to the EC fonts; I saw one referring to the
CC fonts; aren't they the _old_ T1 encoded fonts? Shouldn't it be upgraded
to EC?

--
Giuseppe Bilotta

Re: Fonts & "esotic" languages

[Michal Kvasnicka]

Dear friends at Pragma,

the previous mail remind me one (maybe important) thing
I wanted to to ask you. Is there some possibility to have different
font-***.tex for different encodings?

It is a really important things for people in the Central Europe.
For example, to be able to typeset with Palatino, I must use different
.pfb files (or at least different .afm, and this way different .tfm + .vf too)
than those people using only ISO Latin 1 characters.

In LaTeX, it is solve with different .fd files. There is one .fd file for every

family and every encoding. How is it solved in the ConTeXt?

(Now I'm preparing font-***.tex file for every TeX job uniquely,
but in some time it would be better for me to solve it properly. How?)

Many thanks for your answer (and ever more thanks for you doing
the ConTeXt).

Michal Kvasnicka

--
Economics is the only field in which two people can get a Nobel Prize
for saying exactly the opposite things.

Re: Fonts & "esotic" languages

[Hans Hagen]

At 10:12 AM 9/14/00 +0200, Michal Kvasnicka wrote:
>Dear friends at Pragma,
>
>the previous mail remind me one (maybe important) thing
>I wanted to to ask you. Is there some possibility to have different
>font-***.tex for different encodings?
>
>It is a really important things for people in the Central Europe.
>For example, to be able to typeset with Palatino, I must use different
>.pfb files (or at least different .afm, and this way different .tfm + .vf
too)
>than those people using only ISO Latin 1 characters.
>
>In LaTeX, it is solve with different .fd files. There is one .fd file for
every
>
>family and every encoding. How is it solved in the ConTeXt?
>
>(Now I'm preparing font-***.tex file for every TeX job uniquely,
>but in some time it would be better for me to solve it properly. How?)

Since at pragma we use texnansi encoding while most tex users use ec, you
can imagine that this problem already solved -) 

If you look into the font files you will see that we use definitions like: 

bf = RegularBold sa 1

which means 'take the current regular font (roman, serif) in its bold
incarnation. When this font is asked for, 'RegularBold' is resolved. In
palatino, this means that 'RegularBold' becomes 'Palatino-Bold'. Now,
that's still no font file. Mapping on the filename takes place in the last
stage, and there the encoding is chosen too. That happens for instance in
font-ber.tex. So, what you should do is to make a local file [here we use
font-loc.tex] to map the names to filenames and encodings. 

So, what you can do is to make a file font-eec.tex [for easter european
countries] that lists all the fonts + names + encodings used in your
region.  There is no reason to change any font-... file, just the filename
should change. This also means that definitions like  

\definefont [VeryBig] [RegularBold at 48pt] 

will use that file and encoding [and mapping if specified]

This brings up another problem. When users are making their own font-*
files, at a certain moment we will run into naming problems. So, basically
the font-* files should be reserved for 'official' files. I'm thinking of a
way to load 'user' files. It's like the modules: s-* and m-* files are
extensions to context, users should define their files in environments! 

\environment yourfile.tex 

This fits more nicely in the project support present in context. I will
come back to that later. 

Hans 

-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re: Fonts & "esotic" languages

[Hans Hagen]

At 10:31 PM 9/13/00 +0200, Giuseppe Bilotta (Oblomov) wrote:
>Hello,
>
>I was browsing through the ConTeXt files, and I noticed the font-* files.
>And I thus discovered ConTeXt support for "esotic" languages (Arab, Hebrew)
>through ArabTeX. I wonder then if it would be possible an Omega support ...

Think so. John Plaice and I discussed it, and i think we agreed that they
make a nice couple.  You can also expect some developments in this area
next year, since omega will have new features, and all those tex's around
may even merge and grow (if pdftex and omega merge .... i will instantly
switch).  

>Also, I noticed the T1 (=EC, or DC, or what you want to name it) encoding
>support, but no font-* referring to the EC fonts; I saw one referring to the
>CC fonts; aren't they the _old_ T1 encoded fonts? Shouldn't it be upgraded
>to EC?

You should look at the enco-* files, which replaced the encoding
implementing font files.

There is an enco-ec.tex file and ec is supported. 

Hans

-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------