Re: [NTG-context] Using Postscript Type 1 fonts in ConTeXt/XeTeX?
Hi Mojca,
Sorry for the late reply. I was travelling extensively. Now I am
trying to pick up this thread again -- here's the text source I used
(with your latest suggestion) and the error produced (see line 100) --
still the same problem I think :-(
1 \starttypescript[serif][eco]
2 \definefontsynonym[Serif] [Eco-Regular]
3 \definefontsynonym[SerifBold] [Eco-Bold]
4 \definefontsynonym[SerifItalic][Eco-Italic]
5 \definefontsynonym[SerifBoldItalic][Eco-BoldItalic]
6 \stoptypescript
7
8 \starttypescript[serif][eco]
9 \definefontsynonym[Eco-Regular] [name:Eco101Roman][features=default]
10 \definefontsynonym[Eco-Bold] [name:Eco301Bold][features=default]
11 \definefontsynonym[Eco-Italic][name:Eco102Italic][features=default]
12
\definefontsynonym[Eco-BoldItalic][name:Eco302BoldItalic][features=default]
13 \stoptypescript
14
15 \starttypescript[eco]
16 \definetypeface[\typescriptone][rm][serif][eco][default]
17 \stoptypescript
18
19 \usetypescript[eco]
20 \setupbodyfont[eco]
21
22 \starttext
23 normal text, {\bf bold text}, {\em italic text} and {\bi
bolditalic text}.
24 \stoptext
1 TeXExec | processing document 'hello.tex'
2 TeXExec | no ctx file found
3 TeXExec | tex processing method: context
4 TeXExec | TeX run 1
5 TeXExec | writing option file hello.top
6 TeXExec | using randomseed 13
7 TeXExec | tex engine: xetex
8 TeXExec | tex format: cont-en
9 This is XeTeXk, Version 3.141592-2.2-0.997 (Web2C 7.5.6)
10 \write18 enabled.
11 file:line:error style messages enabled.
12 entering extended mode
13 (./hello.tex
14
15 ConTeXt ver: 2008.01.16 13:49 MKII fmt: 2008.1.21 int:
english/english
16
17 language: language en is active
18 system : cont-new loaded
19 (/usr/local/context/tex/texmf-context/tex/context/base/cont-new.tex
20 systems : beware: some patches loaded from cont-new.tex
21 (/usr/local/context/tex/texmf-context/tex/context/base/cont-new.mkii)
22 (/usr/local/context/tex/texmf-context/tex/context/base/cont-mtx.tex))
23 system : cont-old loaded
24 (/usr/local/context/tex/texmf-context/tex/context/base/cont-old.tex
25 loading : Context Old Macros
26 )
27 system : cont-fil loaded
28 (/usr/local/context/tex/texmf-context/tex/context/base/cont-fil.tex
29 loading : Context File Synonyms
30 )
31 system : cont-sys.rme loaded
32 (/usr/local/context/tex/texmf-context/tex/context/user/cont-sys.rme
33 (/usr/local/context/tex/texmf-context/tex/context/base/type-tmf.tex)
34 (/usr/local/context/tex/texmf-context/tex/context/base/type-siz.tex)
35 (/usr/local/context/tex/texmf-context/tex/context/base/type-otf.tex)
36 (/usr/local/context/tex/texmf-context/tex/context/base/type-xtx.tex))
37 bodyfont: 12pt rm is loaded
38 language: patterns nl-ec:ec-1-2:3 fr-ec:ec-2-2:3
de-ec:ec-3-2:
39 3 it-ec:ec-4-2:3 pt-ec:ec-5-2:3 hr-ec:ec-6-2:3
pl-ec:ec-7-2:3 cz-e
40 c:ec-8-2:3 sk-ec:ec-9-2:3 sl-ec:ec-10-2:3
ru-ec:ec-12-2:3 en-ec:ec-
41 13-2:3 uk-ec:ec-14-2:3 us-ec:ec-15-2:3
agr-ec:ec-16-2:3 da-ec:ec-1
42 7-2:3 sv-ec:ec-18-2:3 af-ec:ec-19-2:3
no-ec:ec-20-2:3 deo-ec:ec-21-
43 2:3 es-ec:ec-25-2:3 ca-ec:ec-26-2:3 la-ec:ec-27-2:3
ro-ec:ec-28-2:
44 3 tr-ec:ec-29-2:3 fi-ec:ec-31-2:3 hu-ec:ec-32-2:3 loaded
45 specials: tex,postscript,rokicki loaded
46 system : hello.top loaded
47 (./hello.top
48 specials: loading definition file dpx
49 (/usr/local/context/tex/texmf-context/tex/context/base/spec-dpx.tex
50 specials: loading definition file fdf
51 (/usr/local/context/tex/texmf-context/tex/context/base/spec-fdf.tex
52 (/usr/local/context/tex/texmf-context/tex/context/base/spec-fdf.mkii))
53 specials: fdf loaded
54 )
55 specials: fdf,dpx loaded
56 specials: loading definition file xet
57 (/usr/local/context/tex/texmf-context/tex/context/base/spec-xet.tex)
58 specials: fdf,dpx loaded
59 ) (/usr/local/context/tex/texmf-context/tex/context/base/type-tmf.tex)
60 (/usr/local/context/tex/texmf-context/tex/context/base/type-siz.tex)
61 (/usr/local/context/tex/texmf-context/tex/context/base/type-otf.tex)
62 (/usr/local/context/tex/texmf-context/tex/context/base/type-xtx.tex)
63 (/usr/local/context/tex/texmf-context/tex/context/base/type-tmf.tex)
64 (/usr/local/context/tex/texmf-context/tex/context/base/type-siz.tex)
65 (/usr/local/context/tex/texmf-context/tex/context/base/type-otf.tex)
66 (/usr/local/context/tex/texmf-context/tex/context/base/type-xtx.tex)
67
Re: [NTG-context] Indenting (again!): a real problem in indentnext=yes
[EMAIL PROTECTED] wrote: Sorry, I wasn't precise enough: I would like to indent paragraphs inside a block created with \defineenumeration (like theorems...), not inside an itemize block. The output in this latter case is indeed quite awful. \defineenumeration[theorem][indenting=always] This is actually easier to find, because it actually is documented in texshow: http://texshow.contextgarden.net/ Every paragraph (preceded by an empty line or \par) in the text flow will get indented, independently of: * what is above (formula, float, etc) * what environment it belongs to (quote, theorem, abstract, etc.), as long as this environment doesn't need alignment (like itemize, tabular, etc.) Of course, particular objects like captions, tables, footnotes, won't be concerned by indenting. I hope my explanations were clear enough... If needed, I can write a small LaTeX example and send it to the list. The thing is that the formal specification is not clearly defined, not even if you mention all cases. _You_ may not want indented footnotes, but _I_ have typeset a book that did. And consider this: Text text text text \startquotation Quoted text quoted text \stopquotation Text text text text is the next Text indented, yes or no? Whether this is a 'display' or a standalone paragraph is very much up to the document designer. In english mathematical texts, Theorems and such are often seen as a kind of run-in header, so that Theorem 1. Text text text is not indented, but that usually does not apply to Proof. Text text text and Remark 1. Text text text: those usually _are_ indented. I am being hesitant about a 'global switch' because I fear that any automated solution only takes care of one particular set of settings, and so does will really help that much and will become a documentation nightmare. Imagine: The command \indentallparagraphs will make sure that every paragraph in the document will get indented, regardless of its surroundings, with the following exceptions: * the bodies of the predefined floating objects figures, tables, intermezzos, graphics. * the bodies of the predefined footnotes endnotes, and floating marginals * the contents of float captions * the paragraph following a \stopformula, if that formula is not preceded by \placeformula, and there is not empty line inbetween. * any itemgroups, enumerations, descriptions, floats etc. that were not predefined in the context core. * ... I hope you see the problem with that. Even a simple command like \setupindentnext[yes] does not work out-of-the-box, because you actually wanted \setupformulae[indentnext=auto] % not yes As I said before, it may be much easier to put all this in a module (by you, or someone else, but I guess you now have the list of desired commands pretty much at hand?). Then you can say \usemodule[indentall] and the context core would not have to think about all these border cases. Best wishes, Taco ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] %18 or 18% : incorrect placement of the percentage sign ?
Idris Samawi Hamid wrote: On Thu, 31 Jan 2008 15:35:35 -0700, Peter Münster [EMAIL PROTECTED] wrote: On Thu, Jan 31 2008, Steffen Wolfrum wrote: Any native arabic speaker out there? Is it %18 or 18% ?? Hello, I don't know nothing about Arabic script, but wouldn't it be logic to ask for %81 or 18% ? Hmm, this could be a long discussion... sure, but interesting (summary should be part of your arab typesetting paper) In ancient times, Arabic numerals (whence our own) were pronounced as follows (translation): 1234 = 4 and 30 and 2 hundred and a thousand aha, makes sense maybe it's also related to the fact that nowadays we see more numbers, and have learned to see them 'as a whole' and not as a systematic sequence - 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 - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Indenting (again!): a real problem in indentnext=yes
Selon Taco Hoekwater [EMAIL PROTECTED]: \defineenumeration[theorem][indenting=always] This is actually easier to find, because it actually is documented in texshow: http://texshow.contextgarden.net/ You're right. I found it there just after I sent the mail... Thank you, and sorry I didn't look at it first. The thing is that the formal specification is not clearly defined, not even if you mention all cases. _You_ may not want indented footnotes, but _I_ have typeset a book that did. It's not exactly about what _I_ want: my only wish was to recover the LaTeX specification. And actually, I don't know if it is clearly defined or not. Maybe I'm too used to LaTeX choices. And consider this: Text text text text \startquotation Quoted text quoted text \stopquotation Text text text text is the next Text indented, yes or no? Whether this is a 'display' or a standalone paragraph is very much up to the document designer. Without an empty line over it, it should not be indented. It's the rule in LaTeX, and it seems quite natural (to me). If you want it indented, you have to start a new paragraph, with an empty line or \par. All this because quotation can be part of a paragraph. Formulae, itemize, can also be part of a paragraph, that's why the rule should be the same for them. Floats, footnotes, etc. can't be part of a paragraph, that's why the rule is different for them. In english mathematical texts, Theorems and such are often seen as a kind of run-in header, so that Theorem 1. Text text text is not indented, but that usually does not apply to Proof. Text text text and Remark 1. Text text text: those usually _are_ indented. For theorem like environments, I'd follow the choices of the AMS. The text inside theorems should follow the same rule as the main text outside. The head of theorems never get indented (by default). I am being hesitant about a 'global switch' because I fear that any automated solution only takes care of one particular set of settings, and so does will really help that much and will become a documentation nightmare. Imagine: The command \indentallparagraphs will make sure that every paragraph in the document will get indented, regardless of its surroundings, with the following exceptions: * the bodies of the predefined floating objects figures, tables, intermezzos, graphics. * the bodies of the predefined footnotes endnotes, and floating marginals * the contents of float captions * the paragraph following a \stopformula, if that formula is not preceded by \placeformula, and there is not empty line inbetween. \placeformula shouldn't modify anything there... * any itemgroups, enumerations, descriptions, floats etc. that were not predefined in the context core. * ... I hope you see the problem with that. Even a simple command like \setupindentnext[yes] does not work out-of-the-box, because you actually wanted \setupformulae[indentnext=auto] % not yes auto seems indeed to be the default in LaTeX. As I said before, it may be much easier to put all this in a module (by you, or someone else, but I guess you now have the list of desired commands pretty much at hand?). Then you can say \usemodule[indentall] and the context core would not have to think about all these border cases. I understand that it's delicate to modify the core for such questions. My point is that I always found indenting clear or coherent in LaTeX: you want an indented line, then leave an empty line before. In ConTeXt, I had to fight a bit to recover this simple rule. But as I said, maybe I'm too used to LaTeX choices... As you suggest, I will put every command I used in a separate file, and try to produce a module out of it. I'm not sure I have sufficient knowledge for this yet, but I'll try. Last of all, I want to thank you for all your answers, and apologize for my poor english: I might seem a bit rude, but this is clearly not my wish. Best regards, Morgan ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] spacing problem with mvs sybols
Taco == Taco Hoekwater [EMAIL PROTECTED] writes: Hi Taco, That was quick answer. Thanks a lot. Taco \symbol[] gobbles following spaces, because it also has a second Taco argument for the symbol set. Use one of these to stop it from Taco doing so: The 2nd one looks optimal when symbol set is globally invoked. It looks like wiki need some update... Sincerely, Gour pgp866g98Xoac.pgp Description: PGP signature ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] %18 or 18% : incorrect placement of the percentage sign ?
On 1 févr. 08, at 12:15, Steffen Wolfrum wrote:
[…]
Maybe I missed the point: don't both lines produce the same output:
۱۲۳ ۴۵۶ ۷۸۹ ?
\TeXXeTstate=1
\definedfont[GeezaPro at 16pt]
\starttext
۱۲۳ ۴۵۶ ۷۸۹
\beginL
۱۲۳ ۴۵۶ ۷۸۹
\endL
\stoptext
... or was this a confusion of multi-script e-mails?
Hi Steffen,
Indeed you are right. But the point is that when writing a text in
Persian, or rather any RL text, in principle the beginning of the file
is:
\TeXXeTstate=1
\everypar={\setbox0=\lastbox \beginR \box0 }
and therefore the output is different than the one you get. If one
omits the second or both of the above two lines, again the output is
as one intends, but the difficulty comes from the fact that (at least
in Persian) when one writes some text containing a number, the digits
and the separators, which can be the comma U+002C, the space, or the
slash U+002F called Solidus (?) for writing fractions, should be
typeset Left-to-Right. In particular compare the following for writing
the number 123 456 789.01:
۱۲۳ ۴۵۶ ۷۸۹,۰۱
\beginL
۱۲۳ ۴۵۶ ۷۸۹,۰۱
\endL
Indeed the first one results in something meaningless.
Best regards: OK
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] spacing problem with mvs sybols
Gour wrote: Taco == Taco Hoekwater [EMAIL PROTECTED] writes: Hi Taco, That was quick answer. Thanks a lot. Taco \symbol[] gobbles following spaces, because it also has a second Taco argument for the symbol set. Use one of these to stop it from Taco doing so: The 2nd one looks optimal when symbol set is globally invoked. It *is* optional, that is it. Optionality implies space-eating. Best wishes, Taco ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] XeTeX vs. luatex
Hi! After moving to emacs I decided to settle on ConTeXt markup and want to use Unicode engine. Luatex is advancing very nicely and I wonder is there any reason to use XeTeX over luatex, i.e. what features are missing (if any) in regards to regarding font-handling in luatex in comparison with XeTeX? Sincerely, Gour pgp7BEib2zMxP.pgp Description: PGP signature ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
