inactive -- and ---

inactive -- and ---

[Henning Hraban Ramm]

[-- Attachment #1: type-sil-gentium.tex --]
[-- Type: application/octet-stream, Size: 2999 bytes --]

%
% Typescript for serif family sil gentium
% written by install-font.pl (copyleft Henning Hraban Ramm)
% adapted 2004-08-23, 2005-11-20
%
% Write in your TeX file something like:
% \usetypescriptfile	[type-sil-gentium]
% \usetypescript	[fiee][sil-gentium]
% \setupbodyfont	[sil-gentium, rm, 12pt]
% \setupbodyfontenvironment	[default]	[em=italic]
% (install-font supports no slanted fonts, but they are default in ConTeXt)

% source of the font: http://scripts.sil.org/Gentium
% the alternate font seems to change only some diacritics

% load mapfile
\starttypescript	[map]	[gentium]	[\defaultencoding]
	\loadmapfile	[\defaultencoding-sil-gentium.map]
\stoptypescript

% serif sil gentium
\starttypescript	[serif]	[gentium,gentium-alt]	[\defaultencoding]
	\definefontsynonym	[GentiumAlt-Italic]	[\defaultencoding-genai101]	[encoding=\defaultencoding]
	\definefontsynonym	[GentiumAlt]	[\defaultencoding-genar101]	[encoding=\defaultencoding]
	\definefontsynonym	[Gentium-Italic]	[\defaultencoding-geni101]	[encoding=\defaultencoding]
	\definefontsynonym	[Gentium]	[\defaultencoding-genr101]	[encoding=\defaultencoding]
\stoptypescript

% serif gentium
\starttypescript	[serif]	[gentium]	[name]
	\setups             [font:fallback:serif]
	\definefontsynonym	[Serif]		[Gentium]
	\definefontsynonym	[SerifItalic]	[Gentium-Italic]
	\definefontsynonym	[SerifBoldAlt]	[SerifItalic]
	\definefontsynonym	[SerifBoldItalic]	[SerifItalic]
	\definefontsynonym	[SerifCaps]	[SerifItalic]
	\definefontsynonym	[SerifBoldCaps]	[SerifItalic]

	\definefontsynonym	[SerifAlt]		[GentiumAlt]
	\definefontsynonym	[SerifItalicAlt]	[GentiumAlt-Italic]
	\definefontsynonym	[SerifOldstyle]	[SerifAlt]
	
	% unfortunately you need to define eight synonyms to handle the fallback cases:
	\definefontsynonym [SerifRegular]	[Serif]
	\definefontsynonym [SerifRegularAlt]	[SerifAlt]
	\definefontsynonym [SerifBoldAlt]	[SerifAlt]
	\definefontsynonym [SerifCapsAlt]	[SerifAlt]
	\definefontsynonym [SerifItalicAlt]	[SerifItalicAlt]
	\definefontsynonym [SerifSlantedAlt]	[SerifItalicAlt]
	\definefontsynonym [SerifBoldItalicAlt]	[SerifItalicAlt]
	\definefontsynonym [SerifBoldSlantedAlt]	[SerifItalicAlt]
	% markup of \Var[alt] results in a (subtle) font switch:
	\definefontvariant [Serif] [alt] [Alt]
\stoptypescript

% serif gentium
\starttypescript	[serif]	[gentium-alt]	[name]
	\setups             [font:fallback:serif]
	\usetypescript		[serif]	[gentium]	[\defaultencoding]
	\definefontsynonym	[Serif]	[GentiumAlt]
	\definefontsynonym	[SerifItalic]	[GentiumAlt-Italic]
\stoptypescript

% sample family definition
\starttypescript	[fiee]	[sil-gentium]
	\definetypeface	[sil-gentium]	[rm]	[serif]	[gentium]	[default]	[encoding=\defaultencoding]
	\definetypeface	[sil-gentium]	[ss]	[sans]	[default]	[default]	[encoding=\defaultencoding]
	\definetypeface	[sil-gentium]	[tt]	[mono]	[default]	[default]	[encoding=\defaultencoding]
	\definetypeface	[sil-gentium]	[mm]	[math]	[default]	[default]	[encoding=\defaultencoding]
\stoptypescript


[-- Attachment #2: Type: text/plain, Size: 529 bytes --]

I'm just trying to modernize and enhance my old typescripts and  
reckognized that -- and --- become inactive (i.e. don't become endash  
and emdash, but stay dashes) with the SIL Gentium font (or at least  
with my typescript).

How can that happen? And what can I do?

I'm using the latest gwTeX (ConTeXt 2005-11-17). The typescript is  
attached, but I don't think the bug is in there...


Grüßlis vom Hraban!
---
http://www.fiee.net/texnique/
http://contextgarden.net
http://www.cacert.org (I'm an assurer)


[-- Attachment #3: Type: text/plain, Size: 139 bytes --]

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: inactive -- and ---

[Thomas A. Schmitz]

Hraban,

AFAIK, -- and --- aren't active, but they (should) produce ligatures,  
so the problem is most probably at the level of the tfms you  
produced. How did you obtain them? By running texfont? Which encoding  
are you using?

Thomas

On Nov 20, 2005, at 1:12 PM, Henning Hraban Ramm wrote:

> <type-sil-gentium.tex>
> I'm just trying to modernize and enhance my old typescripts and  
> reckognized that -- and --- become inactive (i.e. don't become  
> endash and emdash, but stay dashes) with the SIL Gentium font (or  
> at least with my typescript).
>
> How can that happen? And what can I do?
>
> I'm using the latest gwTeX (ConTeXt 2005-11-17). The typescript is  
> attached, but I don't think the bug is in there...
>
>
> Grüßlis vom Hraban!
> ---
> http://www.fiee.net/texnique/
> http://contextgarden.net
> http://www.cacert.org (I'm an assurer)
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context

Re: inactive -- and ---

[Taco Hoekwater]

Thomas A. Schmitz wrote:
> Hraban,
> 
> AFAIK, -- and --- aren't active, but they (should) produce ligatures,  
> so the problem is most probably at the level of the tfms you  produced. 
> How did you obtain them? By running texfont? Which encoding  are you using?

\defaultencoding expands to 'ec' these days (used to be 'texnansi').
Perhaps that is the problem?

Taco

Re: inactive -- and ---

[Thomas A. Schmitz]

I just looked into font conversion for another project. In EC.enc,  
you have this line:

% LIGKERN hyphen hyphen =: endash ; endash hyphen =: emdash ;

so fonts converted by texfont and using --enc=ec should have the  
dashes enabled automagically. The problem I had was with the f- 
ligatures, I had to manually add these lines:

% LIGKERN f f =: ff ; f i =: fi ; f l =: fl ;
% LIGKERN ff f =: fff ; ff i =: ffi ; ff l =: ffl ;

In general, texnansi still seems to be doing a better job with this  
sort of thing. The ligkern instructions are not mentioned explicitly  
in texnansi.enc, but they are still used, so I assume texfont has  
them hardwired into its own code somewhere. May be Adam knows more  
about it?

Best

Thomas

On Nov 20, 2005, at 2:14 PM, Taco Hoekwater wrote:

> Thomas A. Schmitz wrote:
>> Hraban,
>> AFAIK, -- and --- aren't active, but they (should) produce  
>> ligatures,  so the problem is most probably at the level of the  
>> tfms you  produced. How did you obtain them? By running texfont?  
>> Which encoding  are you using?
>
> \defaultencoding expands to 'ec' these days (used to be 'texnansi').
> Perhaps that is the problem?
>
> Taco
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context

Re: inactive -- and ---

[Henning Hraban Ramm]

>>>> AFAIK, -- and --- aren't active, but they (should) produce  
>>>> ligatures,  so the problem is most probably at the level of the  
>>>> tfms you  produced. How did you obtain them? By running texfont?  
>>>> Which encoding  are you using?
>>> \defaultencoding expands to 'ec' these days (used to be 'texnansi').
>>> Perhaps that is the problem?
> so fonts converted by texfont and using --enc=ec should have the  
> dashes enabled automagically.
> ...
> In general, texnansi still seems to be doing a better job with this  
> sort of thing. The ligkern instructions are not mentioned  
> explicitly in texnansi.enc, but they are still used, so I assume  
> texfont has them hardwired into its own code somewhere. May be Adam  
> knows more about it?

Thank you.
I'm using ec, but tried also texnansi without changes.
The TFMs are generated by texfont, but long ago; I should try to re- 
generate them.
Other fonts have no problems.
endash and emdash are defined in the texfont-generated AFMs (original  
is TTF); I can't read TFM...


Grüßlis vom Hraban!
---
http://www.fiee.net/texnique/
http://contextgarden.net
http://www.cacert.org (I'm an assurer)

Re: inactive -- and ---

[Thomas A. Schmitz]

[-- Attachment #1.1: Type: text/plain, Size: 569 bytes --]

Hraban,

you can't read tfm, but have you tried converting them to pl? That's  
a format you can read... And you probably have a pair of vf and tfm  
files, so you could and should convert to vpl.

Best

Thomas

On Nov 20, 2005, at 11:43 PM, Henning Hraban Ramm wrote:

> Thank you.
> I'm using ec, but tried also texnansi without changes.
> The TFMs are generated by texfont, but long ago; I should try to re- 
> generate them.
> Other fonts have no problems.
> endash and emdash are defined in the texfont-generated AFMs  
> (original is TTF); I can't read TFM...
>


[-- Attachment #1.2: Type: text/html, Size: 1648 bytes --]

[-- Attachment #2: Type: text/plain, Size: 139 bytes --]

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context