Re[2]: [NTG-context] Re: CJK support in ConTeXt
Wednesday, August 27, 2003 Tim 't Hart wrote: > I agree that there should be another list for e-Omega (Aleph) where we can > discuss implementing multilingual code for ConTeXt, because I think it's a > bit off-topic for the regular ConTeXt list. > But on the other hand, I also support Hong Feng when he wants to create a > mailing list just for the developers of the CJK package. Or maybe just a > temporary list, just for organizational reasons. > Also a reason is that it's not already sure if e-Omega is the best option > for this (although after using Giuseppe's latest e-Omega version, I think it > is the best option) and that the creation of the CJK module will need > discussions that have nothing to do with e-Omega, like implementing CJK > chapter headings, East Asian line breaking and numbering systems. Although > some of these are ConTeXt related problems, it's a bit off-topic for the > general ConTeXt list, but also off-topic for the e-Omega list. (Of course, > when the developers of the CJK module decide to use e-Omega to implement > their outcome of the discussions, they can use the e-Omega list) > Anyway, these are my thoughts about it, and it's getting past my bedtime. > I'm sure that someone can persuade me to think otherwise! :-) While I agree that the CJK module is specialized, I'm not sure the discussion should necessarily take place somewhere else. After all, it's most definitely a ConTeXt-specific thing. Maybe you should go the same route as the other "external" modules? I don't know, where do the other ConTeXt module get discussed? Does DocbookInConTeXt have its own mailing list? Anyway, I'm glad to hear that the latest e-Omega is working for you too :) these news are the best ones me and the others of the e-Omega task force can receive :) But, if you find a way to support CJK *without* e-Omega, you should also try that route; there already is some support for Chinese, AFAIK, in ConTeXt, so maybe something else can be done without making use of Omega-specific features (you're welcome to make use of e-TeX features, which are now almost universally available). In any case, good luck with your project, -- Giuseppe "Oblomov" Bilotta ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Sidebar
Dear ConTeXt hackers, Is is possible (simple) to do a "sidebar" in Context ? Sidebar is an insert on a page, that stands out, in general to the sides, not following the normal justication of the paragraphs around it, and containing a completely separate paragraph structure like in example below: Paulo Ney de Souza --- | | | . | | . | | . | | ..|--|| | ..| || | ..|xx|| | ..|xx|| | ..|x || | ..| || | ..|xx|| | ..|xx|| | ..| || | ..|xx|| | ..|xx|| | ..|xx|| | ..|--|| | . | | . | | | --- ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] strange itemize
Dear ConTeXt hackers, I try such a simple itemize, but I do get a warning: check : missing or ungrouped '=' after 'serried' in line 6 (@@opitemiz but the documentation says: \startitemgroup[...][...,...,...][...,...=...,...] ... \stopitemgroup [...] [...,...,...] a A KA n N m r R KR continue standard broad serried packed stopper joinedup atmargin inmargin intro columns [...,...=...,...] see \setupitemgroup (1) And this is what I try: \starttext \defineconversion[patrick][\numbers] \startitemize[patrick][serried] \item item \item item \item item \item item \item item \item item \item item \item item \item item \item item \item item \stopitemize \stoptext Patrick -- Silent is the goldfish in its bowl ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Re: parameter mechanism
Hello Simon, Simon Pepping <[EMAIL PROTECTED]> writes: > There is a translation step for the keywords. For example, if a user > would say \ShowLayout[command=\xxx], you would have to retrieve it as Oh, I am lucky that this did not hit me yet. Now I'll be careful. Thanks for the information. Patrick -- Silent is the goldfish in its bowl ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
RE: [NTG-context] Re: CJK support in ConTeXt
Idris S Hamid wrote: > The aleph list may be able to serve as an appropriate place for many > questions > related to multidirectional or multilingual typesetting under ConTeXt, if > it > seems that the regular ConTeXt list is getting clogged. Put another way, > these > two lists will probably suffice. For example, some of u mentioned a > possible > CJK module for e-Omega; details of that might seem appropriate for the > aleph > list. As Arabic, Hebrew, and CJK modules are built for ConTeXt the aleph > list > may come in handy to share and/or consolidate ideas, with a view to > helping the > future multilingual development of ConTeXt remain consistent. I agree that there should be another list for e-Omega (Aleph) where we can discuss implementing multilingual code for ConTeXt, because I think it's a bit off-topic for the regular ConTeXt list. But on the other hand, I also support Hong Feng when he wants to create a mailing list just for the developers of the CJK package. Or maybe just a temporary list, just for organizational reasons. Also a reason is that it's not already sure if e-Omega is the best option for this (although after using Giuseppe's latest e-Omega version, I think it is the best option) and that the creation of the CJK module will need discussions that have nothing to do with e-Omega, like implementing CJK chapter headings, East Asian line breaking and numbering systems. Although some of these are ConTeXt related problems, it's a bit off-topic for the general ConTeXt list, but also off-topic for the e-Omega list. (Of course, when the developers of the CJK module decide to use e-Omega to implement their outcome of the discussions, they can use the e-Omega list) Anyway, these are my thoughts about it, and it's getting past my bedtime. I'm sure that someone can persuade me to think otherwise! :-) Sleep well, Tim ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Re: parameter mechanism
On Wed, Aug 27, 2003 at 06:55:05PM +0200, Patrick Gundlach wrote:
> Hello Peter,
>
> I am not so sure if I can help you, but I'll give it a try.
>
> The examples are taken from my t-layout module.
>
> I wanted to have
>
> \ShowLayout[a=b,c=d]
>
> but with the possibility to say \ShowLayout without [ ]. So I define
> \ShowLayout as
>
> \def\ShowLayout{\dosingleempty\doShowLayout}
>
> and \doShowLayout as
>
> \def\doShowLayout[#1]{%
>\getparameters[ShowLayout][#1]
>
>(some not important stuff)
>
> }
>
> to access a value, just use \getvalue{ShowLayout} where ... is
> your keyword.
>
> I hope I did not forget anything.
There is a translation step for the keywords. For example, if a user
would say \ShowLayout[command=\xxx], you would have to retrieve it as
\getvalue{ShowLayoutcommando} (note the Dutch translation
commando). Translation is done for all keywords that are used in
Context's core; language variants are mapped to a canonical value,
often but not always the Dutch form of the keyword. I do not remember
where to look this up; usually I just look into the trace log to find
out.
Regards, Simon
--
Simon Pepping
email: [EMAIL PROTECTED]
home page: scaprea.hobby.nl
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] naming and distribution of typescripts
Am Dienstag, 26.08.03, um 22:13 Uhr (Europe/Zurich) schrieb Jens-Uwe Morawski: Is there some standard how to name typescripts and locate them in a texmf-tree, so that distribution of typescripts is possible in a controled way? I always name them "type-vendor-collection.tex" (e.g. "type-adobe-palatino.tex") and put them into mytexmf/tex/context/user Typescripts are simply TeX files -- you could put the commands even in your environment file or like that -- so they should stay with "tex" instead of inventing something new that nobody (and noproggy) understands. BTW: My typescripts files are updated, and my site finally shows file dates. Grüßlis vom Hraban! -- http://www.fiee.net/texnique/ (material/typescripts.zip) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re[4]: [NTG-context] CJK support in ConTeXt
Wednesday, August 27, 2003 Tim 't Hart wrote: > I first started to use e-Omega and ConTeXt with the fpTeX > distribution, which had e-Omega 1.15 installed. Later I > switched to W32TeX (a Japanese distribution) which had > version 1.23. I just saw that a few days ago, the maintainer > of W32TeX stopped including version 1.23 and he is now using > 1.15--2.1-RC1. Is that the newest version? Yes, that's the most recent version. It addresses the bug that causes the previous version to bomb out each time an overfull or underfull box was met. > I'll give that version a try. I have good hopes for this > version since I've heard you removed some bugs from it. I'm > sure that everything will go fine now. Please give me some > time to dig up my old e-Omega code from a dark corner of my > HDD and I'll let you know how everything worked out! Take your time. I really hope the latest release helps you. I'm also pleased to know that there are other, less widespread, distributions which include the program :) > By the way, what is the best way to use e-Omega with ConTeXt? > Is there anything I have to keep in mind? The last time I > used e-Omega with ConTeXt, I made the format with 'texexec > --make --alone --tex=eomega en'. And then use 'texexec > --tex=eomega ' to make output. Is this still the > correct way? Yes. Of course, you can also make eomega your standard engine (in texexec.ini) and then forget about the --tex= option :) > Anyway, thank you for keeping Omega alive. I always thought that Omega was a > great idea, but that the lack of a stable version ruined everything. But now > it appears that you have made it useable. That's precisely why I made it :) Omega will continue its development, maintained by John and Yannis, and I will maintain e-Omega (in the future to be renamed to Aleph) as a stable, usable alternative for those who don't need the "latest and greatest". > Well, if my first tests work out great, then I'll know what I'll be doing > this coming weekend! :-) Keep us informed! :) -- Giuseppe "Oblomov" Bilotta ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
RE: Re[2]: [NTG-context] CJK support in ConTeXt
Giuseppe Bilotta wrote: > I happen to be in the e-Omega task force, so I'm extremely > interested in any bug report you may have on it. For the > moment, let's stick to the 1.15 version, which is the official > version. > > First of all, which TeX distribution are you using, and what > does the e-Omega banner say? I know there are people using > e-Omega for production use, so you might want to see if there > is an upgrade available for your distribution. I first started to use e-Omega and ConTeXt with the fpTeX distribution, which had e-Omega 1.15 installed. Later I switched to W32TeX (a Japanese distribution) which had version 1.23. I just saw that a few days ago, the maintainer of W32TeX stopped including version 1.23 and he is now using 1.15--2.1-RC1. Is that the newest version? I'll give that version a try. I have good hopes for this version since I've heard you removed some bugs from it. I'm sure that everything will go fine now. Please give me some time to dig up my old e-Omega code from a dark corner of my HDD and I'll let you know how everything worked out! By the way, what is the best way to use e-Omega with ConTeXt? Is there anything I have to keep in mind? The last time I used e-Omega with ConTeXt, I made the format with 'texexec --make --alone --tex=eomega en'. And then use 'texexec --tex=eomega ' to make output. Is this still the correct way? Anyway, thank you for keeping Omega alive. I always thought that Omega was a great idea, but that the lack of a stable version ruined everything. But now it appears that you have made it useable. Well, if my first tests work out great, then I'll know what I'll be doing this coming weekend! :-) My best, Tim ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] MPtoPDF problem: metafun.mem error
Andreas Steiger <[EMAIL PROTECTED]> writes: Hello, > Well, after about a minute of tons of lines i get another error > message :(. could you please run texexec --make --alone mptopdf and post the resulting logfile? [...] > I can't find neither cont-en.efmt nor metafun.mem on my harddisk, > might it be there went something wrong during the installation? cont-en.efmt and metafun.mem are not shipped with ConTeXt. These should be generated during installation. How did you install ConTeXt? Patrick -- Silent is the goldfish in its bowl ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re[2]: [NTG-context] Re: CJK support in ConTeXt
Wednesday, August 27, 2003 Idris S Hamid wrote: > Since > 1. the aleph list is going to be low-traffic; > 2. eomega (soon-to-be-Aleph) is geared towards multidirectional/ TeX (CJK, > Arabic, Hebrew, etc.); > The aleph list may be able to serve as an appropriate place for many questions > related to multidirectional or multilingual typesetting under ConTeXt, if it > seems that the regular ConTeXt list is getting clogged. Put another way, these > two lists will probably suffice. For example, some of u mentioned a possible > CJK module for e-Omega; details of that might seem appropriate for the aleph > list. As Arabic, Hebrew, and CJK modules are built for ConTeXt the aleph list > may come in handy to share and/or consolidate ideas, with a view to helping the > future multilingual development of ConTeXt remain consistent. I like the idea, especially since Hans is *very* likely to follow the Aleph list (I mean, is there a TeX-related mailing list he doesn't follow? ) I'll wait a little to see if Willi Egger sees the request, then I'll send him a private message to ask for the creation of the mailing list. -- Giuseppe "Oblomov" Bilotta ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re[3]: [NTG-context] parameter mechanism
Wednesday, August 27, 2003 Giuseppe Bilotta wrote:
GB> Wednesday, August 27, 2003 Hans Hagen wrote:
HH>> At 16:56 27/08/2003 +0200, you wrote:
>>>The trick is in mult-ini.tex, which redefines dosetvalue & co
>>>to support the multilingual interface; this is a problem when
>>>you want to get raw (unconverted) keyword/value sets, which is
>>>why it fails. ConTeXt used to have "raw" version of the
>>>do..value commands, but they disappeared at one point. Yes,
>>>they should be re-introduced.
HH>> i dunno what grep you have but mine gives:
HH>> syst-new.tex:\def\getrawparameters
HH>> {\dogetparameters\dosetrawvalue }
HH>> syst-new.tex:\def\getraweparameters
HH>> {\dogetparameters\dosetrawevalue}
HH>> syst-new.tex:\def\getrawgparameters
HH>> {\dogetparameters\dosetrawgvalue}
HH>> syst-new.tex:\def\getrawxparameters
HH>> {\dogetparameters\dosetrawxvalue}
GB> I can't believe I missed them! What was I looking for?
BTW is there any difference between this and the variables
system?
--
Giuseppe "Oblomov" Bilotta
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Re: CJK support in ConTeXt
Giuseppe Bilotta wrote: > Wednesday, August 27, 2003 Hong Feng wrote: > > >> It's time to discuss the topic "CJK support in ConTeXt" in a more public > >> place. > > HF> I can support this idea! I can build a mailing list with > HF> GNU Mailman on my upcoming server. > > Isn't this a good enough place? Since 1. the aleph list is going to be low-traffic; 2. eomega (soon-to-be-Aleph) is geared towards multidirectional/ TeX (CJK, Arabic, Hebrew, etc.); The aleph list may be able to serve as an appropriate place for many questions related to multidirectional or multilingual typesetting under ConTeXt, if it seems that the regular ConTeXt list is getting clogged. Put another way, these two lists will probably suffice. For example, some of u mentioned a possible CJK module for e-Omega; details of that might seem appropriate for the aleph list. As Arabic, Hebrew, and CJK modules are built for ConTeXt the aleph list may come in handy to share and/or consolidate ideas, with a view to helping the future multilingual development of ConTeXt remain consistent. Best Idris ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re[2]: [NTG-context] parameter mechanism
Wednesday, August 27, 2003 Hans Hagen wrote:
HH> At 16:56 27/08/2003 +0200, you wrote:
>>The trick is in mult-ini.tex, which redefines dosetvalue & co
>>to support the multilingual interface; this is a problem when
>>you want to get raw (unconverted) keyword/value sets, which is
>>why it fails. ConTeXt used to have "raw" version of the
>>do..value commands, but they disappeared at one point. Yes,
>>they should be re-introduced.
HH> i dunno what grep you have but mine gives:
HH> syst-new.tex:\def\getrawparameters
HH> {\dogetparameters\dosetrawvalue }
HH> syst-new.tex:\def\getraweparameters
HH> {\dogetparameters\dosetrawevalue}
HH> syst-new.tex:\def\getrawgparameters
HH> {\dogetparameters\dosetrawgvalue}
HH> syst-new.tex:\def\getrawxparameters
HH> {\dogetparameters\dosetrawxvalue}
I can't believe I missed them! What was I looking for?
--
Giuseppe "Oblomov" Bilotta
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Re: parameter mechanism
Hello Peter,
I am not so sure if I can help you, but I'll give it a try.
The examples are taken from my t-layout module.
I wanted to have
\ShowLayout[a=b,c=d]
but with the possibility to say \ShowLayout without [ ]. So I define
\ShowLayout as
\def\ShowLayout{\dosingleempty\doShowLayout}
and \doShowLayout as
\def\doShowLayout[#1]{%
\getparameters[ShowLayout][#1]
(some not important stuff)
}
to access a value, just use \getvalue{ShowLayout} where ... is
your keyword.
I hope I did not forget anything.
Patrick
--
Silent is the goldfish in its bowl
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] parameter mechanism
At 15:32 27/08/2003 +0200, you wrote:
Hello all,
I have problems to understand the command (parameter) mechanism of context.
My experiments with \getparameters didn't work, so I used \xdescgetparameters
from Giuseppe Bilotta (t-xdesc.tex).
In my eyes they look the same, but \xdescgetparameters works with my sample
code, \getparameters don't. Mhhh
% t-xdesc.tex
\def\xdescsetvalue#1#2{\expandafter\def\csname#1#2\endcsname}
\def\xdescgetparameters{\dogetparameters\xdescsetvalue}
% syst-gen.tex
\def\dosetvalue#1#2% #3
[EMAIL PROTECTED] % {#3}}
\def\getparameters {\dogetparameters\dosetvalue}
This leads me to my two questions:
What must I change, to make my test example run with \getparameters?
Where is the error in my \docommand? All parameters but [height] work and
the tracing output at this parameter (\OTRSETshowstatus) says nothing to me.
for that purpose there is:
\setvariables[namespace][key=value,...]
along with the nicely expandable
\getvariable{namespace}{key}
that's the one i use in styles.
Hans
-
Hans Hagen | PRAGMA ADE | [EMAIL PROTECTED]
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] parameter mechanism
At 16:56 27/08/2003 +0200, you wrote:
The trick is in mult-ini.tex, which redefines dosetvalue & co
to support the multilingual interface; this is a problem when
you want to get raw (unconverted) keyword/value sets, which is
why it fails. ConTeXt used to have "raw" version of the
do..value commands, but they disappeared at one point. Yes,
they should be re-introduced.
i dunno what grep you have but mine gives:
syst-new.tex:\def\getrawparameters {\dogetparameters\dosetrawvalue }
syst-new.tex:\def\getraweparameters {\dogetparameters\dosetrawevalue}
syst-new.tex:\def\getrawgparameters {\dogetparameters\dosetrawgvalue}
syst-new.tex:\def\getrawxparameters {\dogetparameters\dosetrawxvalue}
Hans
-
Hans Hagen | PRAGMA ADE | [EMAIL PROTECTED]
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Re: CJK support in ConTeXt
Wednesday, August 27, 2003 Hong Feng wrote: >> It's time to discuss the topic "CJK support in ConTeXt" in a more public >> place. HF> I can support this idea! I can build a mailing list with HF> GNU Mailman on my upcoming server. Isn't this a good enough place? -- Giuseppe "Oblomov" Bilotta ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re[2]: [NTG-context] CJK support in ConTeXt
Wednesday, August 27, 2003 Idris S Hamid wrote: ISH> FWIW, I think that one list is certainly enough. ISH> Looking at the Omega list I'm ISH> not sure there was any real benefit in having two ISH> lists; we certainly don't need ISH> to divide energies at this stage with two low-traffic lists. ISH> Now when eOmega becomes a hit, we can adjust accordingly. I fully agree. >> Given the ideas on the name change (which will be factual with >> the first officially "stable" release, that is the one >> following RC2, probably) it's probably better to use aleph in >> the mailing list name. So: ISH> BTW, since u and Hans seem to like my idea (and I'm ISH> cc'ing the others to see if ISH> they object), is it official? Are we going with Aleph? Yes, but only at freeze-time for the first "stable" release. That is, it'll still be e-Omega RC until it seems to have been fixed and cleaned up enough. My guess is that this will take one or two Release Candidates more (RC2 at least, maybe RC3 if some other important bug pops up). Then I'll make the switch, and we'll start with $\Aleph_0$ (first stable release); we'll then go for $\Aleph_0+1$, +2, +3 for bugfix releases, and $\Aleph_1$ ($\Aleph_2$, etc) for major releases. -- Giuseppe "Oblomov" Bilotta ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Re: CJK support in ConTeXt
> It's time to discuss the topic "CJK support in ConTeXt" in a more public > place. I can support this idea! I can build a mailing list with GNU Mailman on my upcoming server. Rgds, Hong _ Do You Yahoo!? 启用电邮帐号，领会雅虎通[身临其境聊电影]的动感魅力，还有网络摄像头+雅虎通收音机等你来拿 http://cn.rd.yahoo.com/mail_cn/tag/?http://cn.messenger.yahoo.com ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] CJK support in ConTeXt
Giuseppe Bilotta wrote: > Wednesday, August 27, 2003 Hans Hagen wrote: > > HH> At 12:37 27/08/2003 +0200, you wrote: > >>(I hate replying to myself, but ...) > >> > >>Ok, since it seems that e-Omega is starting to get some "mass" > >>interest, I'm thinking about setting up a mailing list for it. > >>Maybe two, one for users and one for developers. Any > >>suggestions on the listserver to use? > > HH> i can ask the ntg, since they host more lists, ok? you can mnage the list > HH> with mailmanager > > AFAIK, the two "biggest" TeX mailing lists holders are ntg and > tug; either is fine for me. Should I create two lists, or do > you think that one list is enough? FWIW, I think that one list is certainly enough. Looking at the Omega list I'm not sure there was any real benefit in having two lists; we certainly don't need to divide energies at this stage with two low-traffic lists. Now when eOmega becomes a hit, we can adjust accordingly. > Given the ideas on the name change (which will be factual with > the first officially "stable" release, that is the one > following RC2, probably) it's probably better to use aleph in > the mailing list name. So: BTW, since u and Hans seem to like my idea (and I'm cc'ing the others to see if they object), is it official? Are we going with Aleph? Best wishes Idris ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] \footnote and \note-FIXED
On Tuesday 26 August 2003 06:53, John Culleton wrote:
> I do
> \footnote[bene]{Here is a footnote}
>
> and later,
>
> Mumble mumble\note[bene]
>
> The \footnote works OK but \note does nothing. What am I doing
> wrong?
The TeXLive 8 beta was again the culprit. I also had problems with TOC
that went away when I reverted to the TeXLive 7 release. So that is
three defects so far with Context and TeXLive 8. Earlier I reported
that the /bin/i386//texexec script was missing.
When TeXLive 8 is formally released I will put it through the wringer
looking for these issues. Is there a Context test suite somewhere?
--
John Culleton
Able Indexers and Typesetters
http://wexfordpress.com
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Re: CJK support in ConTeXt
Hans Hagen wrote: > Hi Chof, > > So, alternative way is to use ASCII pTeX for Japanese. Basically looks no > >problem > >but I worry eTeX extension features. Is it possible to run ConTeXt without > >eTeX > >extension features, Hans? > > in principle yes, but you loose xml handling and a few other things. And you never know where those "few other things" are going to pop up, as I painfully learned before eOmega came along. eTeX's use in ConTeXt is by no means restricted to esoteric areas... Best Idris ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re[5]: [NTG-context] CJK support in ConTeXt
Wednesday, August 27, 2003 Hans Hagen wrote: HH> At 13:38 27/08/2003 +0200, you wrote: >>Is there some form to fill up to request the creation of the >>[EMAIL PROTECTED] mailing list? HH> just ask the ntg secretary Willy Egger (on this list -) Wow, this world is great! To Willy Egger: would it be possible to setup a mailing list at ntg.nl, named 'aleph'? -- Giuseppe "Oblomov" Bilotta ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] parameter mechanism
Wednesday, August 27, 2003 Peter Rolf wrote:
PR> Hello all,
PR> I have problems to understand the command (parameter) mechanism of context.
PR> My experiments with \getparameters didn't work, so I used
PR> \xdescgetparameters
PR> from Giuseppe Bilotta (t-xdesc.tex).
PR> In my eyes they look the same, but \xdescgetparameters works with my sample
PR> code, \getparameters don't. Mhhh
PR> % t-xdesc.tex
PR> \def\xdescsetvalue#1#2{\expandafter\def\csname#1#2\endcsname}
PR> \def\xdescgetparameters{\dogetparameters\xdescsetvalue}
PR> % syst-gen.tex
PR> \def\dosetvalue#1#2% #3
PR> [EMAIL PROTECTED] % {#3}}
PR> \def\getparameters {\dogetparameters\dosetvalue}
PR> This leads me to my two questions:
PR> What must I change, to make my test example run with \getparameters?
The trick is in mult-ini.tex, which redefines dosetvalue & co
to support the multilingual interface; this is a problem when
you want to get raw (unconverted) keyword/value sets, which is
why it fails. ConTeXt used to have "raw" version of the
do..value commands, but they disappeared at one point. Yes,
they should be re-introduced.
--
Giuseppe "Oblomov" Bilotta
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
Re[4]: [NTG-context] CJK support in ConTeXt
At 13:38 27/08/2003 +0200, you wrote: Is there some form to fill up to request the creation of the [EMAIL PROTECTED] mailing list? just ask the ntg secretary Willy Egger (on this list -) Hans - Hans Hagen | PRAGMA ADE | [EMAIL PROTECTED] Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com - information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf - ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] parameter mechanism
Hello all,
I have problems to understand the command (parameter) mechanism of context.
My experiments with \getparameters didn't work, so I used
\xdescgetparameters
from Giuseppe Bilotta (t-xdesc.tex).
In my eyes they look the same, but \xdescgetparameters works with my sample
code, \getparameters don't. Mhhh
% t-xdesc.tex
\def\xdescsetvalue#1#2{\expandafter\def\csname#1#2\endcsname}
\def\xdescgetparameters{\dogetparameters\xdescsetvalue}
% syst-gen.tex
\def\dosetvalue#1#2% #3
[EMAIL PROTECTED] % {#3}}
\def\getparameters {\dogetparameters\dosetvalue}
This leads me to my two questions:
What must I change, to make my test example run with \getparameters?
Where is the error in my \docommand? All parameters but [height] work and
the tracing output at this parameter (\OTRSETshowstatus) says nothing to me.
Thanks for any help,
Peter
P.S.: using miktex 2.3, context version 21.08.2003
Cmd.tex
Description: TeX document
Re[4]: [NTG-context] CJK support in ConTeXt
Wednesday, August 27, 2003 Hans Hagen wrote: HH> At 12:37 27/08/2003 +0200, you wrote: >>(I hate replying to myself, but ...) >> >>Ok, since it seems that e-Omega is starting to get some "mass" >>interest, I'm thinking about setting up a mailing list for it. >>Maybe two, one for users and one for developers. Any >>suggestions on the listserver to use? HH> i can ask the ntg, since they host more lists, ok? you can mnage the list HH> with mailmanager AFAIK, the two "biggest" TeX mailing lists holders are ntg and tug; either is fine for me. Should I create two lists, or do you think that one list is enough? Given the ideas on the name change (which will be factual with the first officially "stable" release, that is the one following RC2, probably) it's probably better to use aleph in the mailing list name. So: * if we go for one list, would it be [EMAIL PROTECTED] ? * if we go for multiple lists, what about [EMAIL PROTECTED] and [EMAIL PROTECTED] ? Or maybe we just start with [EMAIL PROTECTED], and the create [EMAIL PROTECTED] if there is any need to detach technical discussions from "user" discussion. Yes, let's make it this way. Is there some form to fill up to request the creation of the [EMAIL PROTECTED] mailing list? -- Giuseppe "Oblomov" Bilotta ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re[3]: [NTG-context] CJK support in ConTeXt
At 12:37 27/08/2003 +0200, you wrote: (I hate replying to myself, but ...) Ok, since it seems that e-Omega is starting to get some "mass" interest, I'm thinking about setting up a mailing list for it. Maybe two, one for users and one for developers. Any suggestions on the listserver to use? i can ask the ntg, since they host more lists, ok? you can mnage the list with mailmanager Hans - Hans Hagen | PRAGMA ADE | [EMAIL PROTECTED] Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com - information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf - ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re[3]: [NTG-context] CJK support in ConTeXt
(I hate replying to myself, but ...) Ok, since it seems that e-Omega is starting to get some "mass" interest, I'm thinking about setting up a mailing list for it. Maybe two, one for users and one for developers. Any suggestions on the listserver to use? Wednesday, August 27, 2003 Giuseppe Bilotta wrote: GB> Wednesday, August 27, 2003 Tim 't Hart wrote: TtH>> Jin-Hwan Cho wrote: >>>My suggestion for supporting CJK characters in ConTeXt is to write a >>>new module using e-Omega. Even though e-Omega does not produce PDF >>>format directly, there are not much problem with DVIPDFMx. TtH>> When I first tried to use Japanese with ConTeXt, I first looked at TtH>> e-Omega. The reason I gave up and tried to adapt the Chinese module TtH>> was that e-Omega was unstable on my machine. Version 1.23 crashed TtH>> immediately (got stuck in a loop producing [] characters). I tried TtH>> 1.15 because I heard that was more stable. I got some Japanese TtH>> output with this version, but when I tried creating more than a TtH>> paragraph, it locked as well. But this was all a few months ago. TtH>> Does anybody know if things with e-Omega have improved recently? GB> I happen to be in the e-Omega task force, so I'm extremely GB> interested in any bug report you may have on it. For the GB> moment, let's stick to the 1.15 version, which is the official GB> version. GB> First of all, which TeX distribution are you using, and what GB> does the e-Omega banner say? I know there are people using GB> e-Omega for production use, so you might want to see if there GB> is an upgrade available for your distribution. GB> Secondly, do you have a test file I could give a look at? If it GB> needs any nonstandard extra files/fonts/metrics/packages, GB> please give me pointers to these as well. ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re[2]: [NTG-context] CJK support in ConTeXt
Wednesday, August 27, 2003 Tim 't Hart wrote: TtH> Jin-Hwan Cho wrote: >>My suggestion for supporting CJK characters in ConTeXt is to write a >>new module using e-Omega. Even though e-Omega does not produce PDF >>format directly, there are not much problem with DVIPDFMx. TtH> When I first tried to use Japanese with ConTeXt, I first looked at TtH> e-Omega. The reason I gave up and tried to adapt the Chinese module TtH> was that e-Omega was unstable on my machine. Version 1.23 crashed TtH> immediately (got stuck in a loop producing [] characters). I tried TtH> 1.15 because I heard that was more stable. I got some Japanese TtH> output with this version, but when I tried creating more than a TtH> paragraph, it locked as well. But this was all a few months ago. TtH> Does anybody know if things with e-Omega have improved recently? I happen to be in the e-Omega task force, so I'm extremely interested in any bug report you may have on it. For the moment, let's stick to the 1.15 version, which is the official version. First of all, which TeX distribution are you using, and what does the e-Omega banner say? I know there are people using e-Omega for production use, so you might want to see if there is an upgrade available for your distribution. Secondly, do you have a test file I could give a look at? If it needs any nonstandard extra files/fonts/metrics/packages, please give me pointers to these as well. -- Giuseppe "Oblomov" Bilotta ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Newbie: referencing and Page numbers
Hello all,
a basic question: I have a document with three parts. The pagenumbers
display correctly like 1-2, 2-2, 3-2 etc. But referencing Chapter 2 from
Part 1 in Part 3 with
See \in{chapter}[colours] on \at{page}[colors] ...
results in
See chapter 2 on page 3 ...
I want: See chapter 2 on page 1-3 ...
How to achieve this?
Thanks and greetings
--
Dierk Höppner
Technische Informationsbibliothek
Universitätsbibliothek Hannover (TIB/UB)
EDV
Welfengarten 1b
D-30167 Hannover
Tel.: 0511 / 762 - 4067, Fax: 0511 / 762 - 5881
http://www.tib.uni-hannover.de
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] CJK support in ConTeXt
Jin-Hwan Cho wrote: >It's time to discuss the topic "CJK support in ConTeXt" in a more >public place. I couldn't agree more! :-) >The current version of ConTeXt supports Chinese only. But the same >mechasism enables Korean too. The remaining language is Japanese. >In some sense, it is possible to support Japanese in the current >subfont mechanism. But several issues (e.g. Japanese kerning system >as explained by Okumura) may occur. Could you explain what these issues are? For the past couple of months I've been busy writing Japanese support for ConTeXt, based on the Chinese module. I'm not an expert in this, so I'm sure the method I used for writing Japanese support is wrong and can be improved. But for my own personal use it has already proven to be quite useable. If anyone else is interested in what I've produced so far, please let me know. I would like to know what the issues with Japanese kerning are. I do not know a lot about Japanese typography and would like to know what the limitations of code based on the Chinese module are. >My suggestion for supporting CJK characters in ConTeXt is to write a >new module using e-Omega. Even though e-Omega does not produce PDF >format directly, there are not much problem with DVIPDFMx. When I first tried to use Japanese with ConTeXt, I first looked at e-Omega. The reason I gave up and tried to adapt the Chinese module was that e-Omega was unstable on my machine. Version 1.23 crashed immediately (got stuck in a loop producing [] characters). I tried 1.15 because I heard that was more stable. I got some Japanese output with this version, but when I tried creating more than a paragraph, it locked as well. But this was all a few months ago. Does anybody know if things with e-Omega have improved recently? Anyway, I would like to see a common CJK module for ConTeXt, where Chinese, Korean and Japanese are based on the same base code. It doesn't matter to me if it's implemented using subfonts or on using e-Omega, as long as it's stable and useable. Therefore, I would like to offer my help in creating CJK support. My best, Tim ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Re: CJK support in ConTeXt
Hi Chof, So, alternative way is to use ASCII pTeX for Japanese. Basically looks no problem but I worry eTeX extension features. Is it possible to run ConTeXt without eTeX extension features, Hans? in principle yes, but you loose xml handling and a few other things. My suggestion for supporting CJK characters in ConTeXt is to write a new module using e-Omega. Even though e-Omega does not produce PDF format directly, there are not much problem with DVIPDFMx. sounds ok to me Hans - Hans Hagen | PRAGMA ADE | [EMAIL PROTECTED] Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com - information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf - ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] \dosetupsystem ????!
At 13:32 27/08/2003 +0900, you wrote:
Hans Hagen wrote:
sounds like you set the directory string to some \setupsystem command,
are you sure that your file is ok?
I get the error even on a simple file like:
\setupoutput[pdftex]
\starttext
This is a test.
\stoptext
If I insert a } when tex reports the error, it runs to the end and
produces a good pdf. However,
it does say "Don't change language in unprotected mode!" My log file is
attached.
(./test.top)
it seems that something is happening in the top file (the option file
writtemn by texexec); did you change something in texexec.ini? is there
some magic in your local cont-sys.tex? can you grep you system for
{\setupsystem ?
Hans
-
Hans Hagen | PRAGMA ADE | [EMAIL PROTECTED]
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] \dosetupsystem ????!
Hans Hagen wrote:
sounds like you set the directory string to some \setupsystem command,
are you sure that your file is ok?
I get the error even on a simple file like:
\setupoutput[pdftex]
\starttext
This is a test.
\stoptext
If I insert a } when tex reports the error, it runs to the end and
produces a good pdf. However,
it does say "Don't change language in unprotected mode!" My log file
is attached.
Any ideas?
Thanks,
Matt
This is pdfeTeX, Version 3.14159-1.00b-pretest-20020211-2.1 (Web2c 7.3.7x)
(format=cont-en 2003.8.27) 27 AUG 2003 13:27
entering extended mode
**&cont-en test.tex
(./test.tex{c:/tex/texmf-var/pdftex/config/pdftex.cfg}
ConTeXt ver: 2003.8.21 fmt: 2003.8.27 int: english mes: english
language : language en is active
system : cont-new loaded
(c:/tex/texmf/tex/context/base/cont-new.tex
systems: beware: some patches loaded from cont-new.tex!
)
system : cont-old loaded
(c:/tex/texmf/tex/context/base/cont-old.tex
loading: Context Old Macros
)
system : cont-fil loaded
(c:/tex/texmf/tex/context/base/cont-fil.tex
loading: Context File Synonyms
)
system : cont-sys loaded
(c:/tex/texmf/tex/context/user/cont-sys.tex)
bodyfont : 12pt rm is loaded
language : patterns 2:2-en-2 loaded
specials : tex,postscript,rokicki loaded
\openout2 = `test.tui'.
system : test.top loaded
(./test.top)
Runaway argument?
\c!gebied ={\setupsystem [inputfile=test.tex] \protect
! File ended while scanning use of \dosetupsystem.
\par
\relax
\dodoreadfile ...normalinput \readfilename \relax
\the \everyafterreadfile
...file \openutilities \loadoptionfile
\checknotes \initializeMPg...
l.1
\setupoutput[pdftex]
? i
insert>}
\openout0 = `test-mpgraph.mp'.
\openout0 = `test-mprun.mp'.
\openout0 = `mpgraph.mp'.
\openout0 = `mprun.mp'.
specials : loading definition file tpd
(c:/tex/texmf/tex/context/base/spec-tpd.tex
specials : loading definition file fdf
(c:/tex/texmf/tex/context/base/spec-fdf.tex
system (E-TEX) : [line 1907] \ifcsname
)
specials : fdf loaded
)
specials : fdf,tpd loaded
systems: don't change language in unprotected mode!
pdftex : using map file: original-context-symbol.map
pdftex : using map file: pl0-ams-cmr.map
pdftex : using map file: original-vogel-symbol.map
systems: begin file test at line 2
[1.1{c:/tex/texmf-var/dvips/config/pdftex.map
Warning: pdfetex.exe (file c:/tex/texmf-var/dvips/config/pdftex.map): entry for
`cmssbxo10' already exists, duplicates ignored
}{c:/tex/texmf/pdftex/config/context/original-context-symbol.map
Warning: pdfetex.exe (file c:/tex/texmf/pdftex/config/context/original-context-
symbol.map): entry for `contnav' already exists, duplicates ignored
}{c:/tex/texmf/pdftex/config/context/pl0-ams-cmr.map}{c:/tex/texmf/pdftex/confi
g/context/original-vogel-symbol.map
Warning: pdfetex.exe (file c:/tex/texmf/pdftex/config/context/original-vogel-sy
mbol.map): entry for `fmvr8x' already exists, duplicates ignored
}]
systems: end file test at line 6
)
Here is how much of TeX's memory you used:
777 strings out of 33069
11779 string characters out of 745237
4414755 words of memory out of 5520935
31128 multiletter control sequences out of 1+5
10284 words of font info for 34 fonts, out of 50 for 1000
14 hyphenation exceptions out of 1000
45i,16n,49p,166b,246s stack positions out of 5000i,500n,5000p,20b,4s
7 PDF objects out of 30
0 named destinations out of 131072
0 words of extra memory for PDF output out of 65536
Output written on test.pdf (1 page, 4750 bytes).
[NTG-context] CJK support in ConTeXt
It's time to discuss the topic "CJK support in ConTeXt" in a more public place. The current version of ConTeXt supports Chinese only. But the same mechasism enables Korean too. The remaining language is Japanese. In some sense, it is possible to support Japanese in the current subfont mechanism. But several issues (e.g. Japanese kerning system as explained by Okumura) may occur. So, alternative way is to use ASCII pTeX for Japanese. Basically looks no problem but I worry eTeX extension features. Is it possible to run ConTeXt without eTeX extension features, Hans? My suggestion for supporting CJK characters in ConTeXt is to write a new module using e-Omega. Even though e-Omega does not produce PDF format directly, there are not much problem with DVIPDFMx. Best, ChoF. -- ~ *** | Cho, Jin-Hwan == ChoF | ^ ^ ~ o | Research Fellow | ~~~ | School of Mathematics ~~ | Korea Institute for Advanced Study | ~~ | [EMAIL PROTECTED]| | http://free.kaist.ac.kr/ChoF/ | ~~ ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
