Hans wrote:
chinese is not yet defined in utf so if you want that, we need to do it
...
assuming this, how about making a set of tfm,enc,map files that match
the unicode positions (volunteers ...)
I'm very willing to help, especially if there is some drudge work
involved in constructing the
sjoerd siebinga wrote:
I have made a Ruby-script (for personal use loosely based on Adam's
xsl-files) which generates all the encoding- and symbolfiles from a
given cmapfile. If someone could send me the ttf-font, I can generate
all the necessary encodingfiles for you.
the chinese fonts
Hi,
sjoerd siebinga wrote:
I have made a Ruby-script (for personal use loosely based on Adam's
xsl-files) which generates all the encoding- and symbolfiles from a
given cmapfile. If someone could send me the ttf-font, I can generate
all the necessary encodingfiles for you.
Nice! The
Thomas A. Schmitz wrote:
This last step gave and still gives me some headaches (my last
attempt was with Opensuse 10.1 alpha 4), and that's where I ask for
some elucidation: texexec does not rely on kpsewhich to locate the
directory where it dumps the
texexec useses kpse but your
Hi Thomas,
Thomas A. Schmitz wrote:
Dear all (and especially the linux heads...),
I have been playing with my linux partition lately and looking at the
linux installation section in the wiki. I see there are two approaches:
- take the minimal linux distribution that Hans prepares,
- start
I wrote:
\sc and \bf are defined at the same level in ConTeXt, so they (normally)
exclude each other. My guess is that it is very unlikely that this will
be fixed, but ...
make that
be changed, but ..
Because it is not a bug, the behaviour is intentional.
Taco
Tobias Burnus wrote:
(Hmm, I never though I would end up such deep in linguistics duing my
PhD theses in physics. But having three Chinese in the group and doing
regularily some measurements at a research centre in Taiwan - I
couldn't help picking up something.)
well, there is a certain
Taco Hoekwater wrote:
Peter M�nster wrote:
On Mon, 12 Dec 2005, Taco Hoekwater wrote:
\starttext
{\sc Normal and \bf bold Small-Caps. Accents: �}
\stoptext
Hi Peter,
And here are my problems:
1.) I get bold sc font, but the normal \sc is now the normal font.
\sc and \bf are
� wrote:
Hello,
this does not work:
\setupoutput[pdf]
\setupinteraction[state=start,focus=minwidth]
\starttext
bla
\stoptext
Solution seems to be in mult-con.tex in a \startvariables section:
minwidth: minbreedteminwidth
minbreite
On 13 Dec 2005, at 11:34, Hans Hagen wrote:
sjoerd siebinga wrote:
I have made a Ruby-script (for personal use loosely based on
Adam's xsl-files) which generates all the encoding- and
symbolfiles from a given cmapfile. If someone could send me the
ttf-font, I can generate all the
Hans Hagen wrote:
Taco Hoekwater wrote:
Peter M�nster wrote:
On Mon, 12 Dec 2005, Taco Hoekwater wrote:
\starttext
{\sc Normal and \bf bold Small-Caps. Accents: �}
\stoptext
Hi Peter,
And here are my problems:
1.) I get bold sc font, but the normal \sc is now the normal font.
Taco Hoekwater wrote:
I wrote:
\sc and \bf are defined at the same level in ConTeXt, so they (normally)
exclude each other. My guess is that it is very unlikely that this will
be fixed, but ...
make that
be changed, but ..
Because it is not a bug, the behaviour is intentional.
Yes,
Hans Hagen wrote:
what we need is a set of encoding files like
/UniEncoding52 [
/uni52DF
/uni52E0
I hate to be negative, but I have doubts about how generic this approach
may be. In some tentative experiments, I discovered that many (most?)
CJK fonts don't use traditional postscript
sjoerd siebinga wrote:
On 13 Dec 2005, at 11:34, Hans Hagen wrote:
sjoerd siebinga wrote:
I have made a Ruby-script (for personal use loosely based on
Adam's xsl-files) which generates all the encoding- and
symbolfiles from a given cmapfile. If someone could send me the
ttf-font, I
Taco, Hans,
thanks for your reactions. And I see that Taco speaks from (bad)
experience. I have always fiddled around and tried to make ConTeXt
work in the linux distros i have tried so far (since I'm on ppc,
there were four of them: gentoo, fedora, ubuntu, suse), but have
never made any
Thomas A. Schmitz wrote:
OK, will RTFM. One final thought: I remember reading an article (by
Siep? in MAPS?) that having more than one texmf.cnf wasn't too
difficult. Would that be an option I should try? Having one which
just lets all the defaults provided by the distribution and one (set
Adam Lindsay wrote:
Hans Hagen wrote:
what we need is a set of encoding files like
/UniEncoding52 [
/uni52DF
/uni52E0
I hate to be negative, but I have doubts about how generic this
approach may be. In some tentative experiments, I discovered that many
(most?) CJK fonts don't use
Richard Gabriel wrote:
Hello Hans,
quite incidentally I've found out that some of the localization files
(lang-*.tex) are incomplete.
I've filled in missing phrases in lang-ger.tex and lang-sla.tex for
the languages I speak, i.e. English, German, Czech and Slovak.
Please look at the attached
Hans Hagen wrote:
Adam Lindsay wrote:
Fortunately, ttf2tfm's -w [EMAIL PROTECTED]@ notation seems to address this
in most of the old test cases I tried.
afaik pdftex can handle the index and unic entries as
alternatives for glyphnames
Yes. Sorry I wasn't clear on that.
It's just
The manual suggests that you can put index calls between a \section
heading and its first paragraph without worry, but for me it breaks the
page-breaking mechanism, allowing the section title to end up at the
bottom of a page like this:
\starttext
\section{Tufte}
\dorecurse{4}{\input tufte \par}
I said:
Is there any workaround/fix?
I find that the addition of \dontleavehmode fixes it. Is this safe to
use in general?
\starttext
\section{Tufte}
\dorecurse{4}{\input tufte \par}
\section{Knuth}
\dontleavehmode\index{knuth}
\input knuth \par
\stoptext
Thanks,
Duncan
Am 2005-12-13 um 10:21 schrieb Taco Hoekwater:
\definebodyfont [default] [hw] [tf=Handwriting sa 1]
So, you would need something like this:
\definebodyfont [default] [hw]
[tf=Handwriting sa 1,
bf=HandwritingBold sa 1,
it=HandwritingItalic sa 1,
sl=HandwritingSlanted sa 1,
Duncan Hothersall wrote:
I said:
Is there any workaround/fix?
I find that the addition of \dontleavehmode fixes it. Is this safe to
use in general?
\starttext
\section{Tufte}
\dorecurse{4}{\input tufte \par}
\section{Knuth}
\dontleavehmode\index{knuth}
\input knuth \par
\stoptext
Hans Hagen wrote:
Duncan Hothersall wrote:
I find that the addition of \dontleavehmode fixes it. Is this safe to
use in general?
no, use \dontleavehmode instead
;-)
___
ntg-context mailing list
ntg-context@ntg.nl
Hans wrote:
Taco Hoekwater wrote:
Hans Hagen wrote:
Nicolas Grilly wrote:
There is a very little error in file
/tex/texmf-local/web2c/texmf.cnf.
This file is contained in archive justtex.zip downloaded from
Pragma web site.
It lacks a S after TEXMFPROJECT in
Hi,
Richard Gabriel wrote:
+\setuplabeltext [\s!de] [\v!appendix=Anschlu\ssharp\space] % RG
Hmm, I'd rather use Anhang.
Besides: So far I used simply 1 Title of my first chapter and A
My first appendix rather than Chapter 1 Title of my first chapter.
(It looks cute as
Chapter 1
Tobias Burnus wrote:
Hi,
Richard Gabriel wrote:
+\setuplabeltext [\s!de] [\v!appendix=Anschlu\ssharp\space] % RG
Hmm, I'd rather use Anhang.
ok, added as comment
Besides: So far I used simply 1 Title of my first chapter and A
My first appendix rather than Chapter 1 Title of my
Nicolas Grilly wrote:
The issue is one expression is singular and the other one is plural. We need
to have the same convention for each expression. So, yes, it's possible to
change the other line to singular to fix this very little bug ;-)
singular is what i want it to be (since i use it
Hmm, I'd rather use Anhang.
OK. I suppose you're a native German, I'm not...
Besides: So far I used simply 1 Title of my first chapter and
A My first appendix rather than Chapter 1 Title of my first
chapter.
Hmm, it's a question... I use exactly the variant with chapter title in
two
Duncan Hothersall wrote:
The manual suggests that you can put index calls between a \section
heading and its first paragraph without worry, but for me it breaks the
page-breaking mechanism, allowing the section title to end up at the
bottom of a page like this:
\starttext
\section{Tufte}
Richard Gabriel wrote:
Hmm, I'd rather use Anhang.
OK. I suppose you're a native German, I'm not...
Besides: So far I used simply 1 Title of my first chapter and
A My first appendix rather than Chapter 1 Title of my first
chapter.
Hmm, it's a question... I use exactly the variant
Hans Hagen wrote:
Richard Gabriel wrote:
Hello Hans,
quite incidentally I've found out that some of the localization files
(lang-*.tex) are incomplete.
I've filled in missing phrases in lang-ger.tex and lang-sla.tex for
the languages I speak, i.e. English, German, Czech and Slovak.
Hmmm.
Hi Vit,I've originally posted my updates here to the ntg-context list and asked Hans to review them and incorporate them into the distribution.Now it seems I've made something horribly bad... :-(I swear I won't be so active anymore!As one Czech proverb says: "For goodness to beggary."
Hi,
Vit Zyka wrote:
Hmmm. What about to suggest the changes first here in the list? I did
not catch the original email. It is not in the archive too. So me and
other users of these languages can not discuss the changes...
It seems Lurker doesn't keep attachments. I'm sending you off-list
34 matches
Mail list logo
