[NTG-context] m-letter stationary]

2005-02-26 Thread Rob Ermers
Hans,
Thanks again for the new code.
I tried it in my document with my stationary, but it did not work.
When I create a new test document with the code you suggested, all pages 
have VERY ODD in the upper left corner.

Kind regards,
Robert
h h extern wrote:
 \definelayer[test][doublesided=yes,state=repeat]

 \setupbackgrounds[page][background=test]

 \setlayer[test][left] []{VERY ODD}
 \setlayer[test][right][]{VERY EVEN}

 \starttext

 test \page test \page
 test \page test \page
 test \page test \page

 \stoptext

 -
   Hans Hagen | PRAGMA ADE
   Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
  | www.pragma-pod.nl
 -



---BeginMessage---
Hans,
Thanks again for the new code.
I tried it in my document with my stationary, but it did not work.
When I create a new test document with the code you suggested, all pages 
have VERY ODD in the upper left corner.

Kind regards,
Robert
h h extern wrote:
\definelayer[test][doublesided=yes,state=repeat]
\setupbackgrounds[page][background=test]
\setlayer[test][left] []{VERY ODD}
\setlayer[test][right][]{VERY EVEN}
\starttext
test \page test \page
test \page test \page
test \page test \page
\stoptext
-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-




test.pdf
Description: Adobe PDF document
---End Message---
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


[NTG-context] Installation för (complete) novices

2005-02-26 Thread Mats Broberg
Good morning,

As mentioned yesterday, I am trying to install ConTeXt on my Windows XP
machine. However, I am experiencing some problems and thought I could
get some help from someone on the list.

Bear in mind though, that my previous experience regarding installation
steps is from installing InDesign, QuarkXPress and the like, so you may
want to be a bit patient... :)

This is what I have done so far:



1: Downloaded and installed MikTeX, ver. 2.4, accepting all default
settings/suggestions.

2: Downloaded and installed WinEdt. Have run WinEdt's TeX diagnostics
and it's OK.

3: Downloaded and installed ActivePerl, ver. ActivePerl 5.8.6.811, MSI,
and accepted all default settings/suggestions.

4: Restarted.

5: In the command line window I then typed texexec --verbose and got
alot of information in return, so texexec seems to work alright.

6: Then the installation manuals says something about copying
texexec.rme to texexec.ini. Does it mean that I should delete the
.ini file and rename the .rme file, and then uncommenting the MikTeX
line (as referred in the manual)? Also, I opened the files and they are
just two chunks of unformatted ASCII texts. No linebreaks, no blank
lines etc. Is that correct? 



OK, my bloodsugar dropped a bit at that point :) and tried the
following:

I created a small file by copying Hans' sample in Sec 2.2 in the ConTeXt
manual. In the command line window I typed texexec --test and got the
reply:

unknown file type: texmfscripts

I would be very grateful if someone could hint what I have done wrong
and/or lead me through any following installation steps.

Many thanks in advance!

Best regards,
Mats Broberg

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


[NTG-context] Correction to previous e-mail

2005-02-26 Thread Mats Broberg
Listmembers,

OK, the two chunks of text I mentioned were obviously due to the kind of
ASCII text editor I use. I downloaded a different editor one and now the
.rme and the .ini files look better.

Sorry for taking up bandwidth about that specific issue.

Best regards,
Mats Broberg


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


[NTG-context] Additional steps taken since the first e-mail

2005-02-26 Thread Mats Broberg
Listmembers,

I have also done the following since the first e-mail:


- Copied the contents of texexec.rme to texexec.ini

- Uncommented the set TeXShell to miktex line in the new texexec.ini
file.

- Added the string C:\texmf\miktex\context\perltk to the PATH
(however, there is no context or perltk folder in the miktex
folder. Shouldn't there be?)


However, the problem still persists.

Best regards,
Mats Broberg

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


[NTG-context] small caps

2005-02-26 Thread Thomas A . Schmitz
In the last days, I played around with some truetype fonts, preparing 
them for use with ConTeXt by creating tfms via the texnansi encoding. 
Some of these truetypes have expert features embedded into their 
glyphs. texnansi automatically takes care of integrating the ff, 
ffi and ffl ligatures. In order to extract small caps and old-style 
numerals, I created a modified texnansi encoding. Here it comes:

/TeXnANSISCEncoding [
/.notdef % 0
/Euro % /Uni20AC 1
/.notdef % 2
/.notdef % 3
/fraction % 4
/dotaccent %5
/hungarumlaut % 6
/ogonek %   7
/fl %   8
/.notdef % /fraction %  9   not used (see 4), backward compatability only
/cwm%   10  not used, except boundary char internally maybe
/ff%11
/fi%12
/.notdef % /fl% 13  not used (see 8), backward compatability only
/ffi   %14
/ffl   %15
/dotlessi % 16
/dotlessj % 17
/grave %18
/acute %19
/caron %20
/breve %21
/macron %   22
/ring  %23
/cedilla %  24
/germandbls %   25
/AEsmall%   26
/OEsmall%   27
/Oslashsmall %  28
/AE%29
/OE%30
/Oslash %   31
/space %32  % /suppress in TeX text
/exclam %   33
/quotedbl % 34  % /quotedblright in TeX text
/numbersign %   35
/dollar %   36
/percent %  37
/ampersand %38
/quoteright %   39  % /quotesingle in ANSI
/parenleft %40
/parenright %   41
/asterisk % 42
/plus  %43
/comma %44
/hyphen %   45
/period %   46
/slash %47
/zerooldstyle  %48
/oneoldstyle   %49
/twooldstyle   %50
/threeoldstyle %51
/fouroldstyle  %52
/fiveoldstyle  %53
/sixoldstyle   %54
/sevenoldstyle %55
/eightoldstyle %56
/nineoldstyle  %57
/colon %58
/semicolon %59
/less  %60  % /exclamdown in Tex text
/equal %61
/greater %  62  % /questiondown in TeX text
/question % 63
/at %   64
/A %65
/B %66
/C %67
/D %68
/E %69
/F %70
/G %71
/H %72
/I %73
/J %74
/K %75
/L %76
/M %77
/N %78
/O %79
/P %80
/Q %81
/R %82
/S %83
/T %84
/U %85
/V %86
/W %87
/X %88
/Y %89
/Z %90
/bracketleft %  91
/backslash %92  % /quotedblleft in TeX text
/bracketright % 93
/circumflex %   94  % /asciicircum in ASCII
/underscore %   95  % /dotaccent in TeX text
/quoteleft %96  % /grave accent in ANSI
/Asmall %   97
/Bsmall %   98
/Csmall %   99
/Dsmall %   100
/Esmall %   101
/Fsmall %   102
/Gsmall %   103
/Hsmall %   104
/Ismall %   105
/Jsmall %   106
/Ksmall %   107
/Lsmall %   108
/Msmall %   109
/Nsmall %   110
/Osmall %   111
/Psmall %   112
/Qsmall %   113
/Rsmall %   114
/Ssmall %   115
/Tsmall %   116
/Usmall %   117
/Vsmall %   118
/Wsmall %   119
/Xsmall %   120
/Ysmall %   121
/Zsmall %   122
/braceleft %123 % /endash in TeX text
/bar   %124 % /emdash in TeX test
/braceright %   125 % /hungarumlaut in TeX text
/tilde %126 % /asciitilde in ASCII
/dieresis % 127 not used (see 168), use higher up instead
/Lslash %   128 this position is unfortunate, but now too late to fix
/quotesingle %  129
/quotesinglbase %   130
/florin %   131
/quotedblbase % 132
/ellipsis % 133
/dagger %   134
/daggerdbl %135
/circumflex %   136
/perthousand %  137
/Scaron %   138
/guilsinglleft %139
/OE%140
/Zcaron %   141
/asciicircum %  142
/minus %143
/lslash %   144
/quoteleft %145
/quoteright %   146
/quotedblleft % 147
/quotedblright %148
/bullet %   149
/endash %   150
/emdash %   151
/tilde %152
/trademark %153
/scaron %   154
/guilsinglright %   155
/oe%156
/zcaron %   157
/asciitilde %   158
/Ydieresis %159
/nbspace %  160 % /space (no break space)
/exclamdown %   161
/cent  %162
/sterling % 163
/currency % 164
/yen   %165
/brokenbar %166
/section %  167
/dieresis % 168
/copyright %169
/ordfeminine %  170
/guillemotleft %171
/logicalnot %   172
/sfthyphen %173 % /hyphen (hanging hyphen)
/registered %   174
/macron %   175
/degree %   176
/plusminus %177
/twosuperior %  178
/threesuperior %179
/acute %180
/mu%181
/paragraph %182
/periodcentered %   183
/cedilla %  184
/onesuperior %  185
/ordmasculine % 186
/guillemotright %   187
/onequarter %   188
/onehalf %  189
/threequarters %190
/questiondown % 191
/Agrave %   192
/Aacute %   193
/Acircumflex %  194
/Atilde %   195
/Adieresis %196
/Aring %197
/AE%198
/Ccedilla % 199
/Egrave %   200
/Eacute %   

Re: [NTG-context] lettrine.sty, but not LaTeX

2005-02-26 Thread Taco Hoekwater
David Wooten wrote:
Hmm, this is great.
However, I can't seem to get it to accept an image (Image=true or 
Image=yes). Anyone else have some luck?
It couldn't work. Here is a new version, with fixed image support,
some cleanups in the code, and support for per-argument setup
functionality as provided by \LettrineOptionsFor{...} in LaTeX
The one thing I could not/did not solve is how to make ConTeXt shut
up about 'bodyfont 112.5pt is defined (can better be done global)'.
I think I've covered all of lettrine.sty now, but I may have
overlooked a bug or two ;-)
Greetings, Taco



t-lettri.tex
Description: TeX document


drop.tex
Description: TeX document
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] Python,swig and pdftex ?

2005-02-26 Thread Janko Hauser
luigi.scarso schrieb:
 I'm try do make something useful with Python and pdftex using swig.
 Any suggestions ?

Have you looked at pytex? It does nothing with pdftex, but I do not know
what do you want to actually do.

__Janko

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


Re: [NTG-context] Additional steps taken since the first e-mail

2005-02-26 Thread Matthew Huggett
Mats Broberg wrote:
   I have also done the following since the first e-mail:


   - Copied the contents of texexec.rme to texexec.ini

OK


   - Uncommented the set TeXShell to miktex line in the new texexec.ini
   file.

   - Added the string C:\texmf\miktex\context\perltk to the PATH
   (however, there is no context or perltk folder in the miktex
   folder. Shouldn't there be?)

As far as I remember, apart from installing Perl (ActivePerl) and
adding it to PATH, I only had to add MikTeX's bin directory to
PATH.

Have you also generated the formats?  From texexec.rme:

,
| % If this file is called 'texexec.rme', copy it to 'texexec.ini',
| % check the settings above, change them according to your TeX
| % distribution, and say:
| %
| %   texexec  --verbose
| %
| % When set up properly, you should see your local settings fly by.
| % When these settings are ok, the next call should work:
| %
| %   texexec  --make
| %   ^^^
| % and you should be able to process a file by saying
| %
| %   texexec  filename
`

And then of course, be sure to run:

,
| mktexlsr
`

Regarding the files not having line breaks, I made the same mistake
when I started using ConTeXt.  The files have Unix end of line
characters, so Notepad and other Windows-only editors will just give
you a long string of garbage, as you discovered.  Hans has put a lot
of work in making Scite work nicely with ConTeXt, so you might find
that helpful.  Other users have their favorites (Emacs, jEdit, etc.).

Good luck,

Matthew

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


Re: [NTG-context] Additional steps taken since the first e-mail

2005-02-26 Thread Matthew Huggett

   Also, what does mktexlsr refer to

I don't know how it really works, so I can only explain this in
layman's terms.  If you look in your texmf directory, you should see a
ls-R file.  If you have a texmf-local tree, there should be one there
too.  These ls-R files make up a database that are used to locate
various files in a TeX system.  After you make changes, like updating
and rebuilding formats, or copying texexec.rme to texexec.ini, you
need to update the databases before TeX becomes aware of the changes.
This is what mktexlsr does.  On some systems, the command might be
texhash.


Matthew

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


[NTG-context] lack of hyphenation

2005-02-26 Thread Ciro A. Soto
The knowlegeable John Culleton said in one of the
lists that he could recognize if a book was typeset
with
MS-word by looking at the rivers and the lack of
hyphenation. I then checked my 310-page book I am
typesetting with context and not a single line had a
hyphenated word at the end.

So, my question is: Is it okay? or do I need to set
any parameter to allow hyphenation? 
I do have
\tolerance=1, because I don't like lines longer
than the rest, but I thought I could still get some
hyphenated words. Am I right?

thank you
Ciro

=
==
Ciro A. Soto
Author of
The Guitar Maker. 
An Exploration of Wisdom, Design and Love. Pub. Date: Aug. 2005.

All problems are at the interface. Each one of them has a solution.
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] lettrine.sty, but not LaTeX

2005-02-26 Thread Peter Münster
On Sat, 26 Feb 2005, Taco Hoekwater wrote:

 This is just a port of lettrine.sty, and I do not believe it should
 be part of standard ConTeXt.

Why not?

Thanks a lot for this port, Taco, it's great!
Cheers, Peter

-- 
http://pmrb.free.fr/contact/
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


RE: [NTG-context] lack of hyphenation

2005-02-26 Thread Mats Broberg
Ciro,

From a purely typographical point of view, a hyphenated word is always
better than excessive space between words in a line (which is more
discernable to the eye). 

However, depending on column width, the language the text is typeset in,
and the algorithm that is used for hyphenation  justification, some
texts can be typeset without very few hyphens. But if a text is typeset
without hyphenation - take a really good look at the word spacing.
Chances are, they are large. BTW, it's easier to see excessive
wordspacing if you hold the page upside down and squint with your eyes.

Ok, here's something for the spacing aficionados: Take a look at The
art of spacing by Bartels (Chicago, 1926). I have it at hand when I'm
writing this. Not one hyphen in the whole book, not one excessive
wordspace - and all last lines in paragraphs ending less than a one or
two ems from the right margin.

Beautiful, and probably mathematically impossible to achieve. If I don't
remember wrong, DEK writes about Bartels in one of his books and
suspects he rewrote the text while handsetting the lines. 

I would agree with that. 

Best regards,
Mats Broberg



 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of Ciro A. Soto
 Sent: den 26 februari 2005 18:08
 To: mailing list for ConTeXt users
 Subject: [NTG-context] lack of hyphenation
 
 
 The knowlegeable John Culleton said in one of the
 lists that he could recognize if a book was typeset
 with
 MS-word by looking at the rivers and the lack of
 hyphenation. I then checked my 310-page book I am
 typesetting with context and not a single line had a
 hyphenated word at the end.
 
 So, my question is: Is it okay? or do I need to set
 any parameter to allow hyphenation? 
 I do have
 \tolerance=1, because I don't like lines longer
 than the rest, but I thought I could still get some
 hyphenated words. Am I right?
 
 thank you
 Ciro
 
 =
 ==
 Ciro A. Soto
 Author of
 The Guitar Maker. 
 An Exploration of Wisdom, Design and Love. Pub. Date: Aug. 2005.
 
 All problems are at the interface. Each one of them has a 
 solution. ___
 ntg-context mailing list
 ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
 

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


Re: [NTG-context] lack of hyphenation

2005-02-26 Thread Taco Hoekwater
Ciro A. Soto wrote:
So, my question is: Is it okay? or do I need to set
any parameter to allow hyphenation? 
I do have
\tolerance=1, because I don't like lines longer
than the rest, but I thought I could still get some
hyphenated words. Am I right?
Yes, you are right. Assuming you do not have very long lines
and a small body font, it is quite possible that you are a
victim of one of the recent hyphenation-file name confusions
that have been plagueing recent TeX distributions.
Try this: \showhyphens{hyphenation}
It should print
  Underfull \hbox (badness 1) in paragraph at lines 2--2
  [] \*10ptrmtf* hy-phen-ation
on your terminal. If it doesn't, ConTeXt refuses the hyphenate
English, possibly because the patterns were not loaded in the
format (in that case, updating your ConTeXt is the easiest
solution).
Good luck, Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


[NTG-context] 4UP with no table of content - bug?

2005-02-26 Thread Ciro A. Soto
I have this 310-page book with a table of content
that is alsways fine when I use a single page layout.

When I switch to
\setuparranging [2UP,rotated,doublesided]
it also prints the table of content, however,
if I rerun the job for a second time using
the 2UP, the table of content disappears.

Is it a bug or do I need to do something special?

thank you
Ciro
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] lack of hyphenation

2005-02-26 Thread Taco Hoekwater
Ciro A. Soto wrote:
Thank you Taco,
this is what I get. I got a *similar* line
to what you sent, but not the same. Is it ok?
ciro
looks fine, so perhaps you have disabled hyphenation
by using something like \setuptolerance[verytolerant],
or they were truly unnecesary (it is possible)
Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


[NTG-context] Re: lack of hyphenation

2005-02-26 Thread Patrick Gundlach
Hello Taco,

 this is what I get. I got a *similar* line
 to what you sent, but not the same. Is it ok?

 looks fine, 

are you sure that the hyphenation configuration is the same in plain
and ConTeXt? Perhaps it is a bit late for me, but I think that the
test has to be done within ConTeXt to make sure about the correct
hyphenation.

Patrick

PS: see you in France
-- 
ConTeXt wiki: http://contextgarden.net
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] small caps

2005-02-26 Thread Adam Lindsay
Thomas A.Schmitz said this at Sat, 26 Feb 2005 10:13:00 +0100:

In the last days, I played around with some truetype fonts, preparing 
them for use with ConTeXt by creating tfms via the texnansi encoding. 

Hello (again) Thomas,

This is good stuff. I've tried to advocate a naming convention that would
be appropriate to this. I would suggest calling this texnansi-osfsc.enc,
as baseencoding-variant.enc. This is so a modified encoding can
masquerade as the base encoding within ConTeXt.

Given this encoding with my suggested name, you could therefore run
texfont as following:
 texfont --encoding=texnansi --variant=osfsc   --[other options]

Variants that select rarer features that Old Style Figures and Small Caps
may need to be given font-specific names, as rare glyph names tend to
vary wildly between fonts.

Cheers,
adam
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay, Computing Dept. [EMAIL PROTECTED]
 Lancaster University, InfoLab21+44(0)1524/510.514
 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

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


Re: [NTG-context] Additional steps taken since the first e-mail

2005-02-26 Thread Johannes Werner
newinstaller,
i struggled more than one day with installation of context. i'm using a 
different OS (redhat linux) and have a different tex-distribution on it 
(tetex), but maybe this hint is useful for you too:
in the tetex-distro there is a file .../texmf/web2c/fmtutil.cnf . in 
this file the lines for context were commented by default - you have to 
uncomment them and run fmtutil --missing afterwards (or fmtutil 
-all, if you have more time). maybe in miktex there's somthing 
similiar. at my first try i forget to run fmtutil, edited texexec.ini 
and run texexec --make which worked. but afterwards context had some 
special features.

Mats Broberg wrote:
Listmembers,
I have also done the following since the first e-mail:
- Copied the contents of texexec.rme to texexec.ini
- Uncommented the set TeXShell to miktex line in the new texexec.ini
file.
- Added the string C:\texmf\miktex\context\perltk to the PATH
(however, there is no context or perltk folder in the miktex
folder. Shouldn't there be?)
 

no context directory? maybe on a different place (c:\texmf\tex\context ?)
However, the problem still persists.
Best regards,
Mats Broberg
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
 

mfg, johannes
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] setting up even and odd pages

2005-02-26 Thread Paul Tremblay
On Fri, Feb 25, 2005 at 10:56:55AM +0100, Hans Hagen wrote:
 
 Paul Tremblay wrote:
 I'm confused on setting up even and odd pages. If I wanted to set up a
 chapter with the first page one way, and even and odd pages another way,
 how do I do this? Say the first page must start on an odd page. The
 right margin will be 1 inch. Now the each succeeding left (or
 even-numbered) page will have a left margin of 1 inch. The right margin
 (the inner part if it were in a book) should be 1/2 inch. For the right
 (odd-numbered page), the left margin (the inner part if it were a book)
 should be 1/2 inch, while the right, outer margin should be 1 inch.
 
 There are several methods, like:
 
 \setuplayout[left] []
 \setuplayout[right][]
 

This doesn't work for me. ConTeXt simply ignores the command.

Paul

-- 


*Paul Tremblay *
[EMAIL PROTECTED]*

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


Re: [NTG-context] Re: lack of hyphenation

2005-02-26 Thread Ciro A. Soto
well, I did the test running texexec on a file
containing only this line:

\showhyphens{hyphenation}

and got:

TeXExec 5.2.4 - ConTeXt / PRAGMA ADE 1997-2005

executable : pdfetex
format : cont-en
 inputfile : 4test
output : pdftex
 interface : en
  current mode : none
   TeX run : 1

This is pdfeTeXk, Version 3.141592-1.20a-2.2 (Web2C
7.5.3)
 \write18 enabled.
 %-line parsing enabled.
 (/usr/local/texlive2004/texmf/web2c/natural.tcx)
output format initialized to DVI
entering extended mode
(./4test.tex

ConTeXt  ver: 2004.11.17  fmt: 2005.1.30  int: english
 mes: english

..

Underfull \hbox (badness 1) in paragraph at lines
1--1
[] \*10ptrmtf* hyphenation
)


I suppose there is a problem then ...right?

c


--- Patrick Gundlach [EMAIL PROTECTED] wrote:

 Hello Taco,
 
  this is what I get. I got a *similar* line
  to what you sent, but not the same. Is it ok?
 
  looks fine, 
 
 are you sure that the hyphenation configuration is
 the same in plain
 and ConTeXt? Perhaps it is a bit late for me, but I
 think that the
 test has to be done within ConTeXt to make sure
 about the correct
 hyphenation.
 
 Patrick
 
 PS: see you in France
 -- 
 ConTeXt wiki: http://contextgarden.net
 ___
 ntg-context mailing list
 ntg-context@ntg.nl
 http://www.ntg.nl/mailman/listinfo/ntg-context
 

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


Re: [NTG-context] small caps

2005-02-26 Thread Thomas A . Schmitz
This is good stuff. I've tried to advocate a naming convention that 
would
be appropriate to this. I would suggest calling this 
texnansi-osfsc.enc,
as baseencoding-variant.enc. This is so a modified encoding can
masquerade as the base encoding within ConTeXt.

Given this encoding with my suggested name, you could therefore run
texfont as following:
 texfont --encoding=texnansi --variant=osfsc   --[other options]
That is by far the most elegant solution indeed! I have renamed my 
encoding file.

Variants that select rarer features that Old Style Figures and Small 
Caps
may need to be given font-specific names, as rare glyph names tend to
vary wildly between fonts.

Sadly, you are absolutely right about this. And it's not only rare 
glyphs that get wildly different names. There was some rumor on the TeX 
on OS X list that people couldn't get the beautiful HoeflerText font to 
work with TeX; it turned out that this was true for newer versions of 
the font only. I looked into it, and it turns out that Apple (?) has 
given new names even to quite normal characters - eacute becomes 
e_acute etc. So if you want to produce a tfm for that font, you have to 
invent a specific encoding vector. Once you know how this works, it's 
easy enough, but really annoying.

So, the variant scheme in texfont is at least a convenient way to 
cope with this mess.

Best
Thomas
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context