Re: [NTG-context] German ß
Hello, I tried following things: 1.\enableregime[win] äöü is working; ß is shown as SS 2. \enableregime \[il1] öäü and ß comes wrong 3. \enableregime[win] \definecharacter ssharp 255 äöü is working; ß is shown as SS \ssharp results in ß 4. \enableregime[il1] \definecharacter ssharp 255 äöü are wrong; ß is shown as ß 5. and completely strage: using \ss in the text changes from there on to the font LMSans12! And there ß and öäü is working. I really have to state that I don't understand the font font handling completely but I think some things changed here in the last time. I hope that anybody can give me a hint how to use fonts (especially that ones from the latex-hfbright package) Wolfgang Mojca Miklavec schrieb: Wolfgang Zillig [EMAIL PROTECTED] wrote: Hello, i have some problems with an selfcreated typescriptfile. Until one of the last context-updates everythin works fine. The font I use is from the hfbright package (the hfbright package is a free version of the cmbright font) but when I created that typescript I did't relalize that a full font package was available and I renamed the fonts (therefore I will not provide that ugly typescript file here). I don't know what has changed but the german ß is not working any more. I use as font encoding ec and as regime win. I'm a bit confused where exactly my problem lies: either the encoding is wrong, but I do't know which one is right because in the latex package hfbright the encoding is called OT1. Has anyone an idea how to fix this problem or can anyone help me to set up a context module like the hfbright-module? Many thanks Wolfgang Out of curiosity: what happens if you add the following line somewhere after the definition of encoding and after font switching? \definecharacter ssharp 25 Also try to test a word like bi\ssharp chen (this should prevent problems with input regime). If this works, it's necessary to add support for OT1 (if this is not already default), see http://source.contextgarden.net/enco-ec.tex for example. Ec is not supposed to work properly (in LaTeX it's known under the name T1), texnansi also has other character positions, but ssharp could work there. Mojca ___ 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] Modes for configuration
Alan Bowen wrote: Following the example in the ConTeXt Wiki (http:// wiki.contextgarden.net/Modes) I have defined an environment file that specifies two modes (screen, print) for the production of the same source file. This works well when the appropriate texexec commands are given at the command line. The problem is that I am trying to set this production up for users who are happier with a GUI. Is there a way to do generate diverse outputs from the same source file without resorting to the command line? I have experimented with TeXShop�the users tend to works on Macs �but without success thus far. (1) at the top of the file you can say: % modes=... i can think of a 'plugin' in texexec that pops up a menu asking what mode to use (maybe you should put it put it on the wish list in the context portal -) Hans - 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 - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Debian Install
Olivier wrote: Quoting Hans Hagen : -- was [EMAIL PROTECTED] on Oct 15, 2005 at 01:54:28 -- Olivier wrote: Actually, the file texmf.cnf should be located at /etc/texmf/ like all the config files for the tetex distrib (and I assume the /usr/share/texmf/web2c is just a link from there). actually, moving all such files to etc is a bad idea; if etc really wants that file there (maybe under /etc/web2c), best make a symlink from there to the formal place tex tree; makes updating easier; a lot of effort goes into making the tex tree clean and self contained, so moving files outside the tree is a bad idea. I understand some people may have different views. I was just trying to tell the way it is done in the Debian GNU/Linux system. There is a policy about TeX stuff location inside the system which is described in the Debian TeX policy here: http://people.debian.org/~frank/Debian-TeX-Policy This includes as you can read in the first paragraph on config: The central configuration file for TeX applications is /etc/texmf/texmf.cnf, the central font configuration file is /var/lib/texmf/web2c/updmap.cfg, the central language/hyphenation configuration /var/lib/texmf/tex/generic/config/language.dat, and format generation is determinded by /var/lib/texmf/web2c/fmtutil.cnf. All four files are generated by configuration update programs from configuration files in subdirectories of /etc/texmf. That's how it is, and was'nt involved in the making of this policy :) sure -) but it's confusing that some files end up in etc and some not; i could imagine /etc/web2c that has all config files The original poster was asking for the normal setting in his Debian system and I believe it is correct. Moreover, it is always a bad idea to move files provided by packages: I know you are providing a sync mechanism for conTeXt but you'll certainly understand that doing this for every set of program in a system is something a sysadmin does'nt want to go into, and I guess that's where packaging system originated ;) tex reads multiple texmf.cnf files, so one way of getting around it is to make sure that your texmfcnf env var is set up right; that way one can put his own copy of texmf.cnf in a known place (home path or so); Hans - 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 - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] strange (?) exporting from pdf
andrea valle wrote: Hi to all, I was trying to convert form pdf to rtf in order to share docs with non-conTeXt people. Acrobat 7.0 allows with save as to export to many formats. When I convert a pdf created with MSword (or something like: I tried also with some on-line pdfs) I have substantially no problems. But when I convert pdfs created with context or latex I have no blank spaces in the output rtf. Also, accents became autonomous ' (like in source). This seems to be systematic: same behavior with conversion to doc or html, same behavior if I use Trapeze converter instead of Acrobat. E.g.: pdf in--out (rtf, doc, ...): questo � un test -- questo`euntest I suppose it depends on pedf source generation. Any hints? tex does not have a space, and spacing ends up in skips; also, sometimes slot 32 is used for whatever char needs a slot; your problem is not related to pdftex, but a bug in the exporter which is unable to handle arbitrary encodings an option is to use texnansi encoding which is the least problematic one Hans - 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 - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] German ß
Wolfgang Zillig wrote:
Hello,
I tried following things:
1.\enableregime[win]
äöü is working; ß is shown as SS
Strange. If you take a look at enco-def.tex, you'll notice that
\Ssharp will expand into SS, but I have no idea why this would happen
with \ssharp. Where did I miss the definition?
2. \enableregime \[il1]
öäü and ß comes wrong
3. \enableregime[win]
\definecharacter ssharp 255
äöü is working; ß is shown as SS
\ssharp results in ß
4. \enableregime[il1]
\definecharacter ssharp 255
äöü are wrong; ß is shown as ß
When I take a look to regi-win.tex and regi-il1.tex, both definitions
for the character 223 appear to be OK (\defineactivetoken 223
{\ssharp}). I have no idea where the difference comes from.
You have to write
\definecharacter ssharp 25, not 225. If you look at the .enc or .afm
files of your font, there's a germandbls located on the 25th slot.
But I can't really track down your examples. They are too confusing.
5. and completely strage: using \ss in the text changes from there on to
the font LMSans12! And there ß and öäü is working.
\ss stands for sans in ConTeXt (just as if someone would try to
switch the language to Slovenian with \sl). I'm not sure about which
meaning of \ss would have the priority here, but I'm almost sure
that it won't be changed. You can use \ssharp or the proper regime.
I really have to state that I don't understand the font font handling
completely but I think some things changed here in the last time.
I hope that anybody can give me a hint how to use fonts (especially that
ones from the latex-hfbright package)
I have absolutely no idea about the fonts (I'm unable to install one),
but I can explain you a bit about the mechanism behind. It's not a
very clear way of explaining - I hope that you'll catch at least a
little bit of it.
There are (at least) two layers of encodings The first one, called
regime in ConTeXt (and inputenc in LaTeX) takes care that the bytes
in your input file transform into something meaningful for TeX and the
second layer, encoding in ConTeXt (fontenc in LaTeX) takes care that
this something meaningful chooses the proper glyph from the font you
provided.
Examples of regimes are il1 (iso latin 1), win (cp1252), utf (utf-8),
... They are pretty standard and if there's a mistake in the
regi-*.tex file, it should be removed right away.
Examples of encodings (font encodings) are OT1 (standard in TeX),
ec/cork/T1, texnansi, ... They are supposed to be standard, but it may
be that some glyphs in your font are missing, that font comes in some
obscure font encoding, that encodings themselves are buggy and
nonstandard (ec contains some glyphs with strange names and some
duplucates), that there is no standard at all (Arabic, symbol fonts)
...
TeXnansi is supposed to be somehow recommended for the usage with
ConTeXt for Western European. It may also be that it is the default
(instead of the default OT1 in TeX) and that there's no undo
texnansi except if you delete a couple of lines in ConTeXt source or
if you write your own enco-ot1.tex file. OT1 is needed for your font
(you could recode the font as well, but this requires some additional
skills and you would have to do that on every computer where you want
to compile your document then).
When you define a regime (such as il1 or win), the bytes in your input
file will turn into named glyphs. If there's a char 223 in your file
(which is defined to be ß in iso latin 1, but may be just any other
character in another regime), you'll see the definition
\defineactivetoken 223 {\ssharp}
in regi-win.tex.
Now that you have this \ssharp you have to tell TeX which glyph from
the chosen font to use. Fonts have only 256 slots and ß is located at
position 25 in OT1 (default) encoding. But you have to tell ConTeXt
about that. This happens in enco-xxx.tex when you choose an encoding.
If you had a font in ec encoding, the definition
\definecharacter ssharp 255
in enco-ec.tex would do that for you. ConTeXt processes the
enco-def.tex file first. Strange letters that are not present in your
font, but could be faked, are defined there. \Ssharp expands into SS
there, \ssharp goes into the character 25, some accents are built
there, ...
When you tell ConTeXt that you would like to use ec font encoding,
some of the definitions are replaced.
\definecharacter Thorn 222
in enco-ec.tex will explain to ConTeXt that character 222 can be used
when someone types in \Thorn or Þ in the proper encoding. In any
other encoding \Thorn would be ignored.
I don't know how you prepared your typescript file (and I guess that I
wouldn't understand it anyway), but the problem may be that you are
instructing ConTeXt to use the wrong encoding. Perhaps even if you
don't define any encoding explicitly, it perhaps defaults to texnansi.
(sorry for philosophising)
Mojca
Mojca Miklavec schrieb:
Wolfgang Zillig [EMAIL PROTECTED] wrote:
Hello,
i
Re: [NTG-context] German ß
Wolfgang Zillig said this at Sun, 16 Oct 2005 19:57:35 +0200: The font I use is from the hfbright package (the hfbright package is a free version of the cmbright font) but when I created that typescript I did't relalize that a full font package was available and I renamed the fonts (therefore I will not provide that ugly typescript file here). I don't know what has changed but the german ß is not working any more. I use as font encoding ec and as regime win. Hi. I'm just catching up with this issue. Mojca is giving you the right information. I've installed hfbright on my machine and can confirm that it is OT1 (context's `default' encoding) only. The easiest way to fix this for you is to return to the typescripts and make sure they say: [encoding=default] instead of [encoding=ec] As you are probably aware, there are issues with hyphenation and the OT1 encoding. However, the TFMs and free Type 1 glyphs for this font simply are not around. May I suggest looking at the new Latin Modern light sans fonts for text, and using hfbright for mathematics only? 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] MathML: Spacing bug
Salvete, afaics, the following three mathml snippets encode exactly the same thing: ---[1] mrow mia/mi mo::/mo mib/mi /mrow ---[2] mrow mia/mi mo::/mo mib/mi /mrow ---[3] mrow mia/mimo::/momib/mi /mrow However, I only get the expected output from the third version. Any workaround or bugfix? Regards, Christopher ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] MathML: Spacing bug
Christopher Creutzig wrote: However, I only get the expected output from the third version. Any workaround or bugfix? My bad. I forgot the math wrapper element. The spacing is perfectly ok (in this example). Christopher ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] German ß
[Wolfgang, I hope you don't mind me copying parts of your response to the list. -adam] Wolfgang Zillig said this at Mon, 17 Oct 2005 14:06:32 +0200: Hello Adam, thanks for your answer! Hi. I'm just catching up with this issue. Mojca is giving you the right information. I've installed hfbright on my machine and can confirm that it is OT1 (context's `default' encoding) only. The easiest way to fix this for you is to return to the typescripts and make sure they say: [encoding=default] instead of [encoding=ec] ok, I did not know that OT1 is equal default. It's another FAQ... As you are probably aware, there are issues with hyphenation and the OT1 encoding. However, the TFMs and free Type 1 glyphs for this font simply are not around. in the package hfbright there are pfb included (I think this are the type 1). tfms are also on my system Yes, on my system, the TFMs are actually from the CMBright package, and the map file redirects to the HFBright Type1/.pfb files. I don't know much about hyphenantion, but why are there problems? There's a little bit of explanation here: http://wiki.contextgarden.net/Encodings_and_Regimes ...but basically, TeX's hyphenation trickery doesn't know how to deal with composite characters (when it puts an atop a u [pardon my 7-bit rendition]). If a word contains a composite u as a character, it won't break. If it contains a full ü, TeX can deal with it. May I suggest looking at the new Latin Modern light sans fonts for text, and using hfbright for mathematics only? Propably you are right and I should go the easy way and simply use an other font. Do you know if there is a ready package for the Latin Modern light sans? Um, disregard that. I must have hallucinated that font. It doesn't exist. Sorry. 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] German
Adam Lindsay wrote: Propably you are right and I should go the easy way and simply use an other font. Do you know if there is a ready package for the Latin Modern light sans? Um, disregard that. I must have hallucinated that font. It doesn't exist. Sorry. well, there since the monospaces is a sans, and since there is a light monospaced in latin modern it may have been some subconscious mix up Hans - 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 - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Chinese in utf-8
Lutz Haseloff said: i prepared a small perl script to convert chinese utf-8 encoded tex-files to gbk coded tex-files. Thanks so much, I look forward to trying it out next week when I get back to work, and will let you know how I get on. Thanks for taking the time. Duncan ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Modes for configuration
Willi— Many thanks. That is helpful and much appreciated. I missed the closing remark about \enablemode on the Mode page of ConTeXt wiki (which I come to rely on extensively). The advantage of the command line/texexec approach is that one can specify the name of the output using --result xxx and so avoid clobbering files. But I suspect that the users will find it easier to play with \enablemode commands using their various editors of choice and to rename the output before recompiling the file. Alan On Oct 16, 2005, at 2:53 PM, Willi Egger wrote: Hi Alan, This is simle to solve: %\enablemode[screen] \enablemode[print] \envrionment yourenvironment Important is to enable the required mode before loading the environment file. - Dit you know that you can select multiple modes e.g. you have a print-mode and the document should be created for letter, A4 and A5. So you could define a letter-mode an A4-mode and an A5-mode. In the document you can say \enablemode[print,A4] \envrionment yourenvironment Hope that this helps Willi Alan Bowen wrote: Following the example in the ConTeXt Wiki (http:// wiki.contextgarden.net/Modes) I have defined an environment file that specifies two modes (screen, print) for the production of the same source file. This works well when the appropriate texexec commands are given at the command line. The problem is that I am trying to set this production up for users who are happier with a GUI. Is there a way to do generate diverse outputs from the same source file without resorting to the command line? I have experimented with TeXShop—the users tend to works on Macs —but without success thus far. Thanks for any suggestions. Alan ___ 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 ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Modes for configuration
Many thanks, Hans. The idea of a pop-up menu for texexec does have a peculiar charm. Best, Alan On Oct 17, 2005, at 4:21 AM, Hans Hagen wrote: Alan Bowen wrote: Following the example in the ConTeXt Wiki (http:// wiki.contextgarden.net/Modes) I have defined an environment file that specifies two modes (screen, print) for the production of the same source file. This works well when the appropriate texexec commands are given at the command line. The problem is that I am trying to set this production up for users who are happier with a GUI. Is there a way to do generate diverse outputs from the same source file without resorting to the command line? I have experimented with TeXShop�the users tend to works on Macs �but without success thus far. (1) at the top of the file you can say: % modes=... i can think of a 'plugin' in texexec that pops up a menu asking what mode to use (maybe you should put it put it on the wish list in the context portal -) Hans - 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 - ___ 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] strange (?) exporting from pdf
Am 2005-10-17 um 10:27 schrieb Hans Hagen: I was trying to convert form pdf to rtf in order to share docs with non-conTeXt people. Acrobat 7.0 allows with save as to export to many formats. When I convert a pdf created with MSword (or something like: I tried also with some on-line pdfs) I have substantially no problems. But when I convert pdfs created with context or latex I have no blank spaces in the output rtf. Also, accents became autonomous ' (like in source). This seems to be systematic: same behavior with conversion to doc or html, same behavior if I use Trapeze converter instead of Acrobat. tex does not have a space, and spacing ends up in skips; also, sometimes slot 32 is used for whatever char needs a slot; your problem is not related to pdftex, but a bug in the exporter which is unable to handle arbitrary encodings an option is to use texnansi encoding which is the least problematic one I just read that Acrobat has an export bug since 6.0 (still exists in new 7.0.5), that eats sometimes also spaces and accented characters from MSW and other sources. 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] Modes for configuration
Well, I am very glad that you said something. I was feeling unusually sheepish for having missed it! Cheers, Alan On Oct 17, 2005, at 4:45 PM, Henning Hraban Ramm wrote: Am 2005-10-17 um 19:04 schrieb Alan Bowen: Many thanks. That is helpful and much appreciated. I missed the closing remark about \enablemode on the Mode page of ConTeXt wiki That's no wonder - I added it this morning after I read Willi's mail. ;- 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 ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] def with if..else fails in TABLE
Salute wizards!
I tried to write a macro for a TABLE line:
\def\TestCmd{\dodoubleempty\doTestCmd}
\def\doTestCmd[#1][#2]#3{\bTR\bTD #3
\iffirstargument\hfill (#1)\fi
\eTD \bTD
\ifsecondargument
3: #2 and #3
\else
2: only #3
\fi
\eTD\eTR
}
But it never goes into else (if #2 is empty, I get 3: and #3)!
And it's only with the table commands around.
Why? What can I do?
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] strange (?) exporting from pdf
Thanks to all. I'm still struggling to find a way to share easily common documents with non-Context world. I thought I would have solved passing directly form the final pdf output to doc/rtf format, but it seems that I will have to give up. Best -a- On 17 Oct 2005, at 10:27, Hans Hagen wrote: andrea valle wrote: Hi to all, I was trying to convert form pdf to rtf in order to share docs with non-conTeXt people. Acrobat 7.0 allows with save as to export to many formats. When I convert a pdf created with MSword (or something like: I tried also with some on-line pdfs) I have substantially no problems. But when I convert pdfs created with context or latex I have no blank spaces in the output rtf. Also, accents became autonomous ' (like in source). This seems to be systematic: same behavior with conversion to doc or html, same behavior if I use Trapeze converter instead of Acrobat. E.g.: pdf in-->out (rtf, doc, ...): questo � un test --> questo`euntest I suppose it depends on pedf source generation. Any hints? tex does not have a space, and spacing ends up in skips; also, sometimes slot 32 is used for whatever char needs a slot; your problem is not related to pdftex, but a bug in the exporter which is unable to handle arbitrary encodings an option is to use texnansi encoding which is the least problematic one Hans - 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 - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context Andrea Valle DAMS - Facoltà di Scienze della Formazione Università degli Studi di Torino [EMAIL PROTECTED] ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
