Re: [NTG-context] Using metapost figures in context
Aditya Mahajan wrote: I have right now kept the command as MPfigure. grep MPfigure in meta-fig -) 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] [XeTeX] XeTeX, ConTeXt, and utf-8 hyphenation patterns.
On 13 Jun 2006, at 8:25 am, Hans Hagen wrote: On a more general level, if both ConTeXt and XeTeX are engaged in converting legacy TeX hyphenation patterns to utf-8, should they be coordinated in order to avoid duplication of effort? anyone can use the patterns; of course bugs need to be sorted out, but given my experiences with pattern maintainance i will not drop them from context; too much has gone wrong in the past; but you can consider them to be generic so indeed we can avoid duplication of work. Indeed I have no desire to duplicate work. :) My main concern at this point relates to packaging and co-ordination between the different macro packages that load patterns; we can't expect latex users to be dependent on having context installed, or vice versa. Patterns belong in a base tex installation, where they can be available to any higher-level macro package. This needs to be sorted out among a wider group than this mailing list JK ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] [XeTeX] XeTeX, ConTeXt, and utf-8 hyphenation patterns.
Peter Heslin wrote: A little while ago, I said that I hoped to convert Dimitrios Filippou's ancient Greek hyphenation patterns (the elhyphen package) to utf-8, in order to use them with xetex. Before thinking about starting this work, I decided to look to see if anyone else had done it, and I came across something interesting in ConTeXt, which is not a package I normally use. There appears to be a whole subdirectory in the ConTeXt distribution that is full of utf-8 hyphenation patterns, including Filippou's ancient Greek ones, but also including German, French, etc. They are in the file: http://www.pragma-ade.com/context/current/cont-tmf.zip, in the tex/context/patterns directory. Can anyone who knows about ConTeXt explain about where these patterns come from and how it is that context manages to use these patterns? (I thought that non-xetex TeX could only use single-byte encoded patterns.) some time ago i decided to ship patterns with context because (1) there is no sound infrastructure in the tex world for managin gpatterns (2) i need encoding neutral patterns [most patterns are ec only] (3) i want control over what gets loaded in context (4) i wanted to get rid of every year's disappearing, renamed, changed patterns (5) apart from the fact that i wanted patterns that were not in a sense hard wired latex patterns If there is a script that was used to convert these from the source to utf-8, is it available? A quick glance at the ancient greek patterns (in the file lang-agr.pat) shows that there is a bug in the conversion that I'd like to report and fix. ctxtools --pat [en nl agr ...] ctxtools --pat --utf[en nl agr ...] the greek conversions were done with the help of a greek language users on the context list, so in case of troubles, so i cc there; bugs need to be fixed indeed in ctxtools.rb you can grep for 'agr' and see what conversions takes place for greek more info can be found in: http://www.pragma-ade.com/general/manuals/mpattern.pdf (also published in tugboat) there is a file lang-all.xml in the context distribution On a more general level, if both ConTeXt and XeTeX are engaged in converting legacy TeX hyphenation patterns to utf-8, should they be coordinated in order to avoid duplication of effort? anyone can use the patterns; of course bugs need to be sorted out, but given my experiences with pattern maintainance i will not drop them from context; too much has gone wrong in the past; but you can consider them to be generic so indeed we can avoid duplication of work. 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] # in MPinclusions
Aditya Mahajan wrote: Hi, How can I make MPinclusions consider # as a normal character. try \string# (or \#) 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] Using metapost figures in context
Aditya Mahajan wrote: n lines deleted I added to texexec: texexec --mpgraphic somefile.mp which will run mp and make a pdf file. when more graphics are in the file, names become somefile-1.pdf etc one can always say: \useexternalfigure[whatever][somefile-123.pdf] to have more symbolic names 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] [XeTeX] XeTeX, ConTeXt, and utf-8 hyphenation patterns.
Jonathan Kew wrote: On 13 Jun 2006, at 8:25 am, Hans Hagen wrote: On a more general level, if both ConTeXt and XeTeX are engaged in converting legacy TeX hyphenation patterns to utf-8, should they be coordinated in order to avoid duplication of effort? anyone can use the patterns; of course bugs need to be sorted out, but given my experiences with pattern maintainance i will not drop them from context; too much has gone wrong in the past; but you can consider them to be generic so indeed we can avoid duplication of work. Indeed I have no desire to duplicate work. :) My main concern at this point relates to packaging and co-ordination between the different macro packages that load patterns; we can't expect latex users to be dependent on having context installed, or vice versa. Patterns belong in a base tex installation, where they can be available to any higher-level macro package. well, the problem is that until now, most pattern files were basically latex oriented files; the same is kind of true with fonts: changes in related files and names take place, and are synced with latex and then bites contex users; i've kind of given up on that This needs to be sorted out among a wider group than this mailing list well, installing the lang-* pat files only is an option, as is adding tex/context/patterns to the xetex input path in the xetex input path variable (although i believe that the tree is searched anyway); also, given what people have to install nowadays, installing the context ipackage is not that big a burden (xetex binaries and associated libs are pretty big themselves anyway) 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] extra white in framedtext
On Jun 12, 2006, at 23:31, Hans Hagen wrote:
Hans van der Meer wrote:
I did want to typeset material within framedtext with some white
before and after each line.
Appropriate for this seems to me: \null\quad material \quad\null\crlf
etc.; the preceding \null preventing disappearence of the first
\quad.
The strange thing is that the \null in the first line induces an
extra
vertical whitespace between the top of the frame and the first line
inside the frame.
An impression of the result:
---
|� �� �� �� �� �� �� �|� with \null
in first line
|� �� �first line� � �|
|� �� �second line � �|
---
---
|� �� �first line� � �|� without \null in first line
|� �� �second line � �|
---
It seems counterintuitive to withhold the \null in the first line in
order to have the framing correct.
A minimal example on which I encountered this follows:
\setupbodyfont[cmr]
interesting, cmr
Yes, my default font setup sometimes seems to play havoc with me.
It turns automagically into lm.
As for the above problem, my brains were a bit rusty I think.
Just a leavevmode did the trick:
\startframedtext[middle][width=fit]
\leavevmode % = the solution
\null\quad\type{with leavevmode: no more extra vertical space}\quad
\null\crlf
\null\quad\type{normal vertical space}\quad\null
\stopframedtext
Hans van der Meer
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] extra white in framedtext
Hans van der Meer wrote:
On Jun 12, 2006, at 23:31, Hans Hagen wrote:
Hans van der Meer wrote:
I did want to typeset material within framedtext with some white
before and after each line.
Appropriate for this seems to me: \null\quad material \quad\null\crlf
etc.; the preceding \null preventing disappearence of the first
\quad.
The strange thing is that the \null in the first line induces an
extra
vertical whitespace between the top of the frame and the first line
inside the frame.
An impression of the result:
---
|� �� �� �� �� �� �� �|� with \null
in first line
|� �� �first line� � �|
|� �� �second line � �|
---
---
|� �� �first line� � �|� without \null in first line
|� �� �second line � �|
---
It seems counterintuitive to withhold the \null in the first line in
order to have the framing correct.
A minimal example on which I encountered this follows:
\setupbodyfont[cmr]
interesting, cmr
Yes, my default font setup sometimes seems to play havoc with me.
It turns automagically into lm.
As for the above problem, my brains were a bit rusty I think.
Just a leavevmode did the trick:
\startframedtext[middle][width=fit]
\leavevmode % = the solution
\null\quad\type{with leavevmode: no more extra vertical space}\quad
\null\crlf
\null\quad\type{normal vertical space}\quad\null
\stopframedtext
in general \dontleavehmode is better since \leavevmode may introduce unwanted
whitespace sometimes
(i try to avoid \leavevmode whenever possible)
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
