[NTG-context] Re: Chinese
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 files. I don't know enough (yet) about the logic of it all to help with setting up the system, but if someone can supply skeleton files and/or a method for constructing the necessary files, I'm happy to do any leg-work. Duncan ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Re: Chinese
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 mentioned in the context garden qualify for such a treatment (htsong cum suis) Hans ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Re: Chinese
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 recommended (by Xiao Jianfeng) TrueType fonts are given at http://wiki.contextgarden.net/Chinese They are ftp://ftp.ctex.org/pub/tex/fonts/truetype/ttf/htfs.ttf ftp://ftp.ctex.org/pub/tex/fonts/truetype/ttf/hthei.ttf ftp://ftp.ctex.org/pub/tex/fonts/truetype/ttf/htkai.ttf ftp://ftp.ctex.org/pub/tex/fonts/truetype/ttf/htsong.ttf Richard Gabriel wrote: But yet another question: What about Japanese? I've made only small research so far, but unlike Chinese, there's almost no information about Japanese in TeX. How much of work would be to adjust the current chinese ConTeXt module for Japanese? What would you need for it? [Of course, meanwhile I'll investigate some other ways of typesetting Japanese...] (I don't know much about Japanese.) In Japanese contrary to Chinese they mix different character sets: - The Chinese characters (Kanji), which seem to make up most of the (scientific) text (I'v seen); in addition some pronouncation based characters are used: - (Kana:) Hiragana and Katagana; the former are rather round characters in Japanese texts, most prominent should be の [means something like of in English]. They are mostly used for suffixes/prefixes where no Chinese equivalent exists. Whereas Katagana is used to write words which have been taken from (mostly) European languages. For Kanji there should be no problem with the Chinese module, for Kana you need additional support for these characters. Since they are pronouncation based, they only consisted of 50 Characters each. Tobias (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.) ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] linux installations
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 texmf.cnf file may be kind of non standard; maybe you need to tweak that one formats. So what I've seen happening is that I have brandnew formats in one place, yet texexec --version will still display the old versions (or say somehting like cont-en.fmt unknown). I have often just found out where kpsewhich searches for the formats and then replaced these old formats with symlinks to the new ones, but I'm not quite sure if this is a good approach. Does anyone have more insights on this? What's with this proliferation of TEXMF-trees in recent versions of teTeX: which ones do we actually need? Which ones can be deleted safely? good point ... i lost track of that long ago; there is some info in the tex live manual about all those additional home/sys/whatever trees, maybe reading that manual helps Hans ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] linux installations
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 from TexLive Minor correction: - start from teTeX (not the same as texlive) I see why these approaches have their advantages. Nevertheless, I would want to add a further point: shouldn't we provide some hints for those who have a working TeX installation on linux and want to keep it because they are not (yet) exclusive ConTeXt users and want to be able to upgrade with their distribution's system? I believe this is quite hard, because every distribution has a slightly different teTeX setup. My view was: if you want an up-to-date ConTeXt, start out fresh. Otherwise, you can save yourself an enormous hassle by learning to live with an outdated system. If you want to spend time on this, then kudos to you, but I have given up on the distribution-supplied TeX's altogether. I have played around with several distros and think some general points could go into the wiki: 1. look at texmf.cnf; find out where TEXMFLOCAL is on your system. In most distros, the directory doesn't exist yet, create it. 2. In the definitions of texmf.cnf, make sure that TEXMFLOCAL comes before the other TEXMF trees. 3. unzip cont-tmf.zip into this directory, run mktexlsr or texhash 4. run texexec --make --al Now you often still have a broken ConTeXt distribution, even if you can get 4. to work, because you also need the latest latin-modern font distribution. And for that, you have to make another set of changes to texmf.cnf because the older latin-moderns used different paths and filenames for just about everything, and you have to make sure the new ones are found. And don't forget that you probably have to fix updmap's config file as well to make sure dvips remains working. You'll also still have a rather outdated pdftex and metapost, but I guess that is not really a big deal for most people. 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 formats. So what I've seen happening is that I have brandnew formats in one place, yet texexec --version will still display the old versions (or say somehting like cont-en.fmt unknown). I have often just found out where kpsewhich searches for the formats and then replaced these old formats with symlinks to the new ones, but I'm not quite sure if this is a good approach. Does anyone have more insights That solution is fine. 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. on this? What's with this proliferation of TEXMF-trees in recent versions of teTeX: which ones do we actually need? Which ones can be deleted safely? The strangest ones are the ~/.texmf-var ones, where fmtutil and updmap dump their stuff. They are documented in /usr/local/teTeX/share/texmf/web2c/texmf.cnf if you use Thomas' distribution. Cheers and good luck! Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] problems with bold small caps
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 ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Re: Chinese
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 charm in those characters, even if you cannot read them (during a 2*10 hour trip in a chinese bus during the last tug conference one quickly learns to recognize the symbols for gas stations and such -) browsing a chinese-english dictionary is also fun (i have a small one on my desk; some day i should start collecting dictionaries of all languages that context supports -); with a bit of puzzling one can find out the system behind the way words are made up Hans ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] problems with bold small caps
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 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 I assume it would be possible to do something using the
\variants mechanism (note: I am not sure and would not know how)
thi sis an option indeed; the other method is just to define an
additional typeface
\definetypeface[mainface].
\definetypeface[smallface].
\definetypeface[osface].
andthen do things like \smallface\bf
typeface switching is rather efficient
Hans
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] focus=minwidth,minheight
� 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 minsirka ampiezzamin latimeminima % TB TH minheight: minhoogte minheight minhoehe minvyska altezzamininaltimeminima ok, added Hans ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Re: Chinese
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 necessary encodingfiles for you. the chinese fonts mentioned in the context garden qualify for such a treatment (htsong cum suis) Ok. Where can I send the chinese encodingfiles? ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] problems with bold small caps
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.
\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 I assume it would be possible to do something using the
\variants mechanism (note: I am not sure and would not know how)
thi sis an option indeed;
This is implemented at http://wiki.contextgarden.net/Pseudo_Small_Caps
(links to files on typokvitek.com has to be retyped, sorry)
Vit
the other method is just to define an
additional typeface
\definetypeface[mainface].
\definetypeface[smallface].
\definetypeface[osface].
andthen do things like \smallface\bf
typeface switching is rather efficient
Hans
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
--
===
Ing. Vít Zýka, Ph.D. TYPOkvítek
database publishing databazove publikovani
data maintaining and typesetting in typographic quality
priprava dat a jejich sazba v typograficke kvalite
tel.: (+420) 777 198 189 www: http://typokvitek.com
===
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] problems with bold small caps
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, and it's what variants were intended to address, to stack font switching behaviour on top of known shapes and weights. Old Style sometimes exists in more than regular shapes. Small Caps appear in bold and sometimes even italics versions. (Variants were also to get at fonts that wouldn't normally have a style associated with them, as well.) 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] Re: Chinese
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 names, but rather map from unicode to an indexed glyph number. Fortunately, ttf2tfm's -w [EMAIL PROTECTED]@ notation seems to address this in most of the old test cases I tried. 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
[NTG-context] your mails at go
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 can generate all the necessary encodingfiles for you. the chinese fonts mentioned in the context garden qualify for such a treatment (htsong cum suis) Ok. Where can I send the chinese encodingfiles? you can send me a zip maybe we should start thinking on how to set up a repository at https://foundry.supelec.fr/ taco and patrick have more experience in this area than i have so maybe they have some ideas on how to organize this Hans ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] linux installations
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 systematic approach. I'm really grateful for Taco's explanations; this helps me a lot. On Dec 13, 2005, at 11:55 AM, Taco Hoekwater wrote: I believe this is quite hard, because every distribution has a slightly different teTeX setup. My view was: if you want an up-to-date ConTeXt, start out fresh. Otherwise, you can save yourself an enormous hassle by learning to live with an outdated system. :-) If you want to spend time on this, then kudos to you, but I have given up on the distribution-supplied TeX's altogether. Now you often still have a broken ConTeXt distribution, even if you can get 4. to work, because you also need the latest latin-modern font distribution. And for that, you have to make another set of changes to texmf.cnf because the older latin-moderns used different paths and filenames for just about everything, and you have to make sure the new ones are found. And don't forget that you probably have to fix updmap's config file as well to make sure dvips remains working. You'll also still have a rather outdated pdftex and metapost, but I guess that is not really a big deal for most people. OK, what about that: my aim would be to have one up-to-date ConTeXt installation in TEXMFLOCAL and leave everything else pretty much untouched. One could easily add a step to unzip cont-lmt.zip into TEXMFLOCAL as well. I've done it and it doesn't appear to break things with other TeX programs (disclaimer: I use pdf*tex exclusively, so I don't know about dvips). That solution is fine. 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. OK, then one step would be: find the old .fmt files and delete them. The strangest ones are the ~/.texmf-var ones, where fmtutil and updmap dump their stuff. They are documented in /usr/local/teTeX/share/texmf/web2c/texmf.cnf 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 via an environment variable) which will put TEXMLOCAL before anything else? Thanks, and best Thomas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] linux installations
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 via an environment variable) which will put TEXMLOCAL before anything else? make an .../texmf-mine and $TEXMFMINE and put that one first in the $TEXMF list; just make sure that your own stuff is found first Hans ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Re: Chinese
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 traditional postscript names, but rather map from unicode to an indexed glyph number. 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 Hans ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Some localizations
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 files and if you consider them OK (they really should be! :-) ), please add them to the distribution. ok, patched (i made the section related labels comments since we default no nothing) btw, your lang-ger had no patch (apart from some AA change) Hans ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Re: Chinese
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 that ttf2tfm is the tool that does a good job at extracting those entries when other tools fail. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 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
[NTG-context] Index entries messing up page breaks
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}
\section{Knuth}
\index{Knuth}
\input knuth \par
\stoptext
Is there any workaround/fix?
Thanks very much,
Duncan
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Index entries messing up page breaks
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
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] typescript problem (hw variants)
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, bi=HandwritingBoldItalic sa 1, bs=HandwritingBoldSlanted sa 1, sc=HandwritingCaps sa 1] Thank you, that works. And I think that really belongs in font-unk. Now we must find a solution for the small caps problem... 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: [NTG-context] Index entries messing up page breaks
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
no, use \dontleavehmode instead
if you see a tex file on the web and wonder why the spacing is messed up
... it's probably because of abundant use of \leavemode
(recent versions of pdftex provide \quitvmode which is equivalent to
\dontleavehmode; taco wrote that patch a while ago)
Hans
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Index entries messing up page breaks
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 http://www.ntg.nl/mailman/listinfo/ntg-context
RE: [NTG-context] A very little error in texmf.cnf
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 definition of TEXMF :
TEXMF =
{!!$TEXMFPROJECTS,!!$TEXMFFONTS,!!$TEXMFLOCAL,!!$TEXMFEXTRA,!!$TEXMF
MAIN}
eh ... why should that be plural?
It should agree with this line, surely:
TEXMFPROJECTS = $SELFAUTOPARENT/texmf-projects
ah, then that one should be singular (i always set that one
in other setup scripts)
TEXMFPROJECT = $SELFAUTOPARENT/texmf-project
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 ;-)
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Some localizations
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
Title of my first chapter
with the first line differently styled as the second, but this is rarely
used.)
One probably should add them -- as comment after the actual empty label.
Next question: Why are you changing the Å into a + ?
-% \defineactivecharacter Å {\AA{}}
+% \defineactivecharacter + {\AA{}}
Tobias
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Some localizations
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 first chapter.
(It looks cute as
Chapter 1
Title of my first chapter
with the first line differently styled as the second, but this is
rarely used.)
One probably should add them -- as comment after the actual empty label.
indeed i made them comments, all sectioning labels are empty by default
(but it does not hurt to show them as comment)
Next question: Why are you changing the � into a + ?
-% \defineactivecharacter � {\AA{}}
+% \defineactivecharacter + {\AA{}}
actually. those chars are ansi chars and show up as a real \AA in my
editor so i kept the old one
Hans
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] A very little error in texmf.cnf
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 at all our machines) Hans ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Some localizations
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 lines as you mention in the parenthesis.
Sorry if I did something wrong. It really wasn't my intention to make
problems to other users... :-(
Next question: Why are you changing the Å into a + ?
It's NOT my work. :-(
I didn't change any other things than headtexts/labeltexts!
-Richard
Tobias Burnus wrote:
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
Title of my first chapter
with the first line differently styled as the second, but this is
rarely used.)
One probably should add them -- as comment after the actual empty label.
Next question: Why are you changing the Å into a + ?
-% \defineactivecharacter Å {\AA{}}
+% \defineactivecharacter + {\AA{}}
Tobias
___
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] Index entries messing up page breaks
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}
\dorecurse{4}{\input tufte \par}
\section{Knuth}
\index{Knuth}
\input knuth \par
\stoptext
Is there any workaround/fix?
can you try (test extensively):
\def\dodoregister[#1]#2#3%
{\dogotopar{\dontleavehmode\doprocesspageregister[#1]{#2}{#3}}}
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Some localizations
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 with chapter title in two lines as you mention in the parenthesis. Sorry if I did something wrong. It really wasn't my intention to make problems to other users... :-( Next question: Why are you changing the � into a + ? It's NOT my work. :-( I didn't change any other things than headtexts/labeltexts! maybe th eeditor is messing up (can happen with cut and paste), it's an 8 bit char; anyhow, this is what checking is for -) Hans ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Some localizations
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. 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... Vit Please look at the attached files and if you consider them OK (they really should be! :-) ), please add them to the distribution. ok, patched (i made the section related labels comments since we default no nothing) btw, your lang-ger had no patch (apart from some AA change) Hans ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Some localizations
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." ;-)-RichardFrom: Vit Zyka [mailto:[EMAIL PROTECTED]To: mailing list for ConTeXt users [mailto:[EMAIL PROTECTED]Sent: Wed, 14 Dec 2005 00:56:40 +0100Subject: Re: [NTG-context] Some localizationsHans 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. 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...Vit Please look at the attached files and if you consider them OK (they really should be! :-) ), please add them to the distribution. ok, patched (i made the section related labels comments since we default no nothing) btw, your lang-ger had no patch (apart from some AA change) Hans___ntg-context mailing listntg-context@ntg.nlhttp://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] Some localizations
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 the files Gabriel sent to the mailing list as attachment to his messages : http://archive.contextgarden.net/message/20051213.124612.61dd4755.en.html http://archive.contextgarden.net/message/20051213.153042.f1ff0de0.en.html Cheers, Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
