[NTG-context] Increase textbackground page break white space
Hey list,
Some of my textbackgrounds occupy more than one page and break part way
through them, as expected. Where their containing text is split at the
page break, I am finding that the frame is too close to the contents. So
I'd like to increase the white space of the bottom and top of the
textbackground's frame and content where it splits across a page.
This is what I have been using so far:
\definetextbackground[SomeTextBackground]
[location=paragraph,
color=color_text,
background=color,
backgroundcolor=colour_text_background_shaded,
frame=on,
framecolor=colour_text,
topoffset=0.5cm,
bottomoffset=0.5cm,
leftoffset=0.5cm,
rightoffset=0.5cm,
before={
\blank[2*big]
},
after={
\blank[2*big]
},
style=smalltype,
corner=round]
I've been trying to solve this problem for months without any luck.
--
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com
signature.asc
Description: This is a digitally signed message part
___
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] wrong footnote number in beta from today
On 8-5-2012 16:25, Pablo Rodríguez wrote:
Hi there,
I'm afraid that footnote numbering in body text is wrong in latest beta
(the bug was also in the two previous betas).
Here you have a sample that shows the bug:
\setupnotation[footnote][number=no]
\setuphead[chapter][number=no]
\starttext
\chapter{First chapter}
one\footnote{two}
\section{First section}
three\footnote{four}
\stoptext
There should be no note footnote numbering, but the body text takes the
sectioning command number for the footnote references (which is
obviously wrong).
Many thanks for your help,
fixed in next beta
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] greek items broken:
Am 08.05.2012 um 19:32 schrieb Meer, H. van der: > I do not get lowercase greek letters on the itemize as should happen with > symbol setup g. > A minimal example, showing the demise of lowercase greek against succes for > uppercase. It’s a font problem because MkII took the greek letters from the math font but MkIV takes them from the text font and Latin Modern doesn’t have lower case greek letters. Wolfgang___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Font for MetaPost graphics
On 2012-05-08 Hans Hagen wrote:
> ok, can you add this to cont-new.mkiv (after \unprotect):
>
> \def\m_meta_colo_initializations{%
> vardef OverlayLineColor=\MPcolor{\overlaylinecolor} enddef;
> vardef OverlayColor=\MPcolor{\overlaycolor} enddef;
> }
That works.
> As I've used that patch for quite a while now I could probably
> move it to the core.
Since you use it for a while it seems to work ⇒ into the core
Thanks a lot Hans for implementing this.
Wikified:
http://wiki.contextgarden.net/Command/defineMPinstance
http://wiki.contextgarden.net/Command/setupMPinstance
Best wishes
Marco
___
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Font for MetaPost graphics
On 8-5-2012 19:19, Marco wrote:
On 2012-05-08 Hans Hagen wrote:
On 8-5-2012 19:01, Marco wrote:
On 2012-05-05 Hans Hagen wrote:
Did I?
My bad ;)
This code fails:
\defineMPinstance [mympinstance] [metafun] [textcolor=red]
\starttext
\startMPcode
draw textext("some text") ;
\stopMPcode
\startMPcode{mympinstance}
draw textext("some text") ;
\stopMPcode
\stoptext
Marco
It works here.
Fails here, source and log are attached.
ok, can you add this to cont-new.mkiv (after \unprotect):
\def\m_meta_colo_initializations{%
vardef OverlayLineColor=\MPcolor{\overlaylinecolor} enddef;
vardef OverlayColor=\MPcolor{\overlaycolor} enddef;
}
I have that in my local experimental code. It has to do with the fact
that mp's color spaces are not compatible with each other. As I've used
that patch for quite a while now I could probably move it to the core.
Maybe more users can test this.
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
[NTG-context] greek items broken:
I do not get lowercase greek letters on the itemize as should happen with symbol setup g. A minimal example, showing the demise of lowercase greek against succes for uppercase. \starttext \startitemize[g] \startitem nr 1\stopitem \startitem nr 2\stopitem \startitem nr 3\stopitem \startitem nr 4\stopitem \stopitemize \startitemize[G] \startitem nr 1\stopitem \startitem nr 2\stopitem \startitem nr 3\stopitem \startitem nr 4\stopitem \stopitemize \stoptext Hans van der Meer itemsym.pdf Description: itemsym.pdf ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Font for MetaPost graphics
On 2012-05-08 Hans Hagen wrote:
> On 8-5-2012 19:01, Marco wrote:
> > On 2012-05-05 Hans Hagen wrote:
>
> Did I?
My bad ;)
> > This code fails:
> >
> > \defineMPinstance [mympinstance] [metafun] [textcolor=red]
> >
> > \starttext
> >
> > \startMPcode
> > draw textext("some text") ;
> > \stopMPcode
> >
> > \startMPcode{mympinstance}
> > draw textext("some text") ;
> > \stopMPcode
> >
> > \stoptext
> >
> > Marco
>
> It works here.
Fails here, source and log are attached.
current version: 2012.05.08 13:45
Marco
\defineMPinstance [mympinstance] [metafun] [textcolor=red]
\starttext
\startMPcode
draw textext("some text") ;
\stopMPcode
\startMPcode{mympinstance}
draw textext("some text") ;
\stopMPcode
\stoptext
(g.tex
ConTeXt ver: 2012.05.08 13:45 MKIV fmt: 2012.5.8 int: english/english
system > cont-new.mkiv loaded
(/home/zewz/context/tex/texmf-context/tex/context/base/cont-new.mkiv
system > beware: some patches loaded from cont-new.mkiv
)
system > g.top loaded
system > options > start used options
used options> % runtime options files (command line driven)
used options> \unprotect
used options> % feedback and basic job control
used options> % handy for special styles
used options> \startluacode
used options> document = document or { }
used options> document.arguments={
used options> ["once"]=true,
used options> }
used options> document.files={
used options> "g",
used options> }
used options> \stopluacode
used options> % process info
used options> \setupsystem[inputfile=g]
used options> \setupsystem[\c!n=3,\c!m=1]
used options> \enabledirectives[system.runonce]
used options> % modes
used options> % options (not that important)
used options> \startsetups *runtime:options
used options> \stopsetups
used options> % styles and modules
used options> \startsetups *runtime:modules
used options> \stopsetups
used options> % done
used options> \protect \endinput
system > options > stop used options
(g.top)
fonts > latin modern fonts are not preloaded
languages > language en is active
{/home/zewz/context/tex/texmf-context/fonts/map/pdftex/context/mkiv-base.map}
fonts > preloading latin modern fonts (second stage)
fonts > typescripts > unknown: library 'loc'
{/home/zewz/context/tex/texmf/fonts/map/dvips/lm/lm-math.map}{/home/zewz/context/tex/texmf/fonts/map/dvips/lm/lm-rm.map}
fonts > virtual math > unable to resolve name mapsfromchar
fonts > fallback modern rm 12pt is loaded
metapost> initializing instance 'metafun' using format 'metafun'
metapost> loading 'metafun': /home/zewz/context/tex/texmf-context/metapost/context/base/metafun.mpiv
metapost> initializing instance 'mympinstance' using format 'metafun'
metapost> loading 'metafun': /home/zewz/context/tex/texmf-context/metapost/context/base/metafun.mpiv
! terminal: >> OverlayLineColor
>> (0,0,0)
! Equation cannot be performed (numeric=color).
;
<*> ...ineWidth:=0pt ; OverlayLineColor:=(0,0,0);
OverlayColor:=(0,0,0); Ba...
>> OverlayColor
>> (0,0,0)
! Equation cannot be performed (numeric=color).
;
<*> ...yLineColor:=(0,0,0); OverlayColor:=(0,0,0);
BaseLineSkip:=14.4816pt; ...
.
system > tex > error on line 11 in file g.tex: terminal: >> OverlayLineColor
>> (0,0,0)
! Equation cannot be performed (numeric=color).
;
<*> ...ineWidth:=0pt ; OverlayLineColor:=(0,0,0);
OverlayColor:=(0,0,0); Ba...
>> OverlayColor
>> (0,0,0)
! Equation cannot be performed (numeric=color).
;
<*> ...yLineColor:=(0,0,0); OverlayColor:=(0,0,0);
BaseLineSkip:=14.4816pt; ...
...
1 \defineMPinstance [mympinstance] [metafun] [textcolor=red]
2
3 \starttext
4
5 \startMPcode
6 draw textext("some text") ;
7 \stopMPcode
8
9 \startMPcode{mympinstance}
10 draw textext("some text") ;
11 >> \stopMPcode
12
13 \stoptext
14
...0;;]===], [===[;;]===], false)}
\meta_process_graphic ...!!es , \MPaskedfigure )}}
\egroup \placeMPgraphic \m...
\meta_start_code_instance ..._process_graphic {#2}
\meta_end_graphic_group
l.11 \stopMPcode
? x
system > files > start used files
used files >1: filename=g | filetype=tex | foundname=g.tex | usedmethod=filesystem
used files >2: filename=cont-new.mkiv | filetype=tex | foundname=/home/zewz/context/tex/texmf-context/tex/context/base/cont-new.mkiv | used
Re: [NTG-context] Font for MetaPost graphics
On 8-5-2012 19:01, Marco wrote:
On 2012-05-05 Hans Hagen wrote:
Did I?
This code fails:
\defineMPinstance [mympinstance] [metafun] [textcolor=red]
\starttext
\startMPcode
draw textext("some text") ;
\stopMPcode
\startMPcode{mympinstance}
draw textext("some text") ;
\stopMPcode
\stoptext
Marco
It works here.
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
[NTG-context] fonts
Hi,
A nice candidate for wikification:
\setupbodyfont[dejavu]
\setupbodyfontenvironment
[default]
[smallsized=1.25,
mediumsized=1.5,
largesized=2.0]
\definefontsize[smallsized]
\definefontsize[mediumsized]
\definefontsize[largesized]
\starttext
\setuphead[chapter] [style=\bflargesized]
\setuphead[section] [style=\bfmediumsized]
\setuphead[subsection][style=\bfsmallsized]
\chapter {Whatever $x-1$}
\section {Whatever $x-1$}
\subsection{Whatever $x-1$}
\input ward
\stoptext
--
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Font for MetaPost graphics
On 2012-05-05 Hans Hagen wrote:
This code fails:
\defineMPinstance [mympinstance] [metafun] [textcolor=red]
\starttext
\startMPcode
draw textext("some text") ;
\stopMPcode
\startMPcode{mympinstance}
draw textext("some text") ;
\stopMPcode
\stoptext
Marco
___
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Asian Language Support
Hi Yusuke > A question for Yusuke: what script name should we use? It is a difficult question. In Chinese or Korean case, what they have chosen? In Japanese, we need to prepare a lot of characters for font set if they complete Adobe-Japan-1.5 or something. So, some font vendors publish the font sets including only kana-region and latin/number-region (and elementary school level kanjis). In this case, script=kana might be ok, but if the font set has all the characters of Adobe-Japan-1.5 region, then script=kana is too impolite. Moreover, in pTeX world, we use 'kanji' for this kind, but we need to rethink 'kanji' is most appreciate or not. we use hangul for korean and hanzi for chinese so kanji sounds ok to me but in fact there a bit more to it, currently we have \definescript[hangul] [method=hangul] \definescript[hanzi] [method=hanzi] \definescript[nihongo] [method=nihongo] and these use default presets but as there can be be variants in spacing one can also define for instance \definescript [myhangul] [hangul] [preset=mypreferences] (not that there are such preferences defined now) and more key/values will be supported some day so, shall we go for 'kanji' for the default setup? but 'japanese' could do as well as well because we can define synonyms Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Asian Language Support
Abe-san, thanks for the suggestion. I will do the reading as you suggested. It's always good to have backup for now, in case a clean method can't be worked out with Mark IV right away. Regards ABE Noriyuki wrote: > Dear Henman-san, > > > So a question might be can ptex be used with ConTeXt? as the the engine? > > Would this wowrk? > With ConTeXt mark II (not mark IV), you can use ptex as the engine. Such > support is included in W32TeX. (I don't know whether TeXLive 2011 > supports it.) You can type `texexec --eptex foo'. > > If you want to try it, please read share/texmf/doc/context/context-w32. > txt and test-eptex.tex. (It is written in Japanese, but I think it does > not matter for you.) > > 2012/05/07(Mon) 22:54:47, "d.henman" : > > > > Yusuke-san, > >Thank you too for writing. It seems like one or the other so far, > > platex > > does not give good western style characters but is great for Japanese, > > which > > the other option, simplefonts gives good western characters and according > > to > > you bad Japanese charac > > ters. Is it the font or the spacing that is bad in simplefont? > > > > So a question might be can ptex be used with ConTeXt? as the the engine? > > Would this wowrk? > > > > ___ > > 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 : http://foundry.supelec.fr/projects/contextrev/ > > wiki : http://contextgarden.net > > > > ___ > > > Sincerely, > Noriyuki Abe > ___ > 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 : http://foundry.supelec.fr/projects/contextrev/ > wiki : http://contextgarden.net > ___ ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Asian Language Support
Hi, Hans,
> A question for Yusuke: what script name should we use?
It is a difficult question. In Chinese or Korean case,
what they have chosen? In Japanese, we need to prepare a
lot of characters for font set if they complete Adobe-Japan-1.5
or something. So, some font vendors publish the font sets
including only kana-region and latin/number-region (and
elementary school level kanjis). In this case, script=kana
might be ok, but if the font set has all the characters
of Adobe-Japan-1.5 region, then script=kana is too impolite.
Moreover, in pTeX world, we use 'kanji' for this kind, but
we need to rethink 'kanji' is most appreciate or not.
Thanks,
-- Yusuke.
(2012/05/08 7:07), Hans Hagen wrote:
On 7-5-2012 15:12, S Barmeier wrote:
I am writing documents in English/Japanese.
If you want to include English text, you probably need to define your
own typescript (or use simplefonts), because most Japanese fonts have
terrible Latin fonts...
I can probably help you, if you tell me what exactly you need.
If you're just typesetting Japanese text, you will need
\setscript[hanzi] to enable linebreaks...
And the rest is done by Unicode magic: just type away between \starttext
and \stoptext
I uploaded a beta with preliminary Japanese script support.
\enabletrackers[scripts.analyzing]
% \enabletrackers[scripts.injections]
\enabletrackers[scripts.details]
% \definefont[testfont][heiseikakugostd-w5][script=kana,language=jan]
\definefont[testfont][heiseiminstd-w3] [script=kana,language=jan]
\testfont
\starttext
\startscript[nihongo]
\startlines
国、『国』、『国』、『国』、『国』、『国』、
\hbox to 3em{国、『国』、『国』、『国』、『国』、『国』、}
国：国：国：国：国：国：国：国：国：国
\hbox to 3em{国：国：国：国：国：国：国：国：国：国}
\stoplines
\stopscript
\stoptext
A question for Yusuke: what script name should we use?
More (simple) examples are needed in order to get all relations between
categories done (so, currently we still use a copy of chinese but with already
a few japanese specific inter-character issues done).
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
--
黒木 裕介 (KUROKI Yusuke)
kuroky(at)users.sourceforge.jp
http://ptetexwin.sourceforge.jp/
___
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
[NTG-context] wrong footnote number in beta from today
Hi there,
I'm afraid that footnote numbering in body text is wrong in latest beta
(the bug was also in the two previous betas).
Here you have a sample that shows the bug:
\setupnotation[footnote][number=no]
\setuphead[chapter][number=no]
\starttext
\chapter{First chapter}
one\footnote{two}
\section{First section}
three\footnote{four}
\stoptext
There should be no note footnote numbering, but the body text takes the
sectioning command number for the footnote references (which is
obviously wrong).
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Asian Language Support
> > Just a remark: for cjk one can best use the mkiv feature to combine > fonts; there are probably some examples of korean fonts mixed with e.g. > palatino or times in the email archive. Here is a sample typescript file for mixed Korean and English fonts suggested by Hans. Using this file, I can use Korean font for Korean and Palatino for English. It works well. You can modify this file for your purpose. Good luck! Best regards, Dalyoung type-imp-unfonts.mkiv Description: Binary data ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] \definehighlight + \words | \WORDS
On 8-5-2012 13:28, Wolfgang Schuster wrote:
The next version will support named casing:
WORD
word
Word
Words
capitals cap
Capitals Cap
none
random
It would be also useful to change the following line in font-pre.mkiv to use
\setcharacterchasing instead of \WORD (won’t work anymore when you remove
\groupedcommand from the \WORD as written in the comments in typo-cap.mkiv)
\definealternativestyle [\v!WORD] [\WORD][\WORD]
Additional entries for \word, Words etc. in font-pre.mkvi are useful as well
because “style=word” looks better than “style={\setcharacterchasing[word]}”.
I had been thinking about a 'vector' key (in addition to style) but
that's a bit of work as we then need to provide some *vectore variants
as well and integrate it in the style/color switching helpers which is
ab it of work
but anyhow, it doesn't hurt to have them as alternative styles so you
can test it later today (making a beta)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] \definehighlight + \words | \WORDS
On 2012-05-08 13:28, Wolfgang Schuster wrote:
>
> It would be also useful to change the following line in font-pre.mkiv to use
> \setcharacterchasing instead of \WORD (won’t work anymore when you remove
> \groupedcommand from the \WORD as written in the comments in typo-cap.mkiv)
>
> \definealternativestyle [\v!WORD] [\WORD][\WORD]
>
> Additional entries for \word, Words etc. in font-pre.mkvi are useful as well
> because “style=word” looks better than “style={\setcharacterchasing[word]}”.
Seconded. That would be of great value and at least I will use it
very often.
philipp
>
> Wolfgang
> ___
> 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 : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
pgpLbnSpVMsYk.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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] \definehighlight + \words | \WORDS
Am 08.05.2012 um 13:17 schrieb Hans Hagen:
> On 8-5-2012 11:18, Philipp Gesang wrote:
>> On 2012-05-08 11:07, Wolfgang Schuster wrote:
>>>
>>> Am 08.05.2012 um 10:35 schrieb Philipp Gesang:
>>>
Dear listmates,
I rely on automated uppercasing and lowercasing a lot and I’m
very happy with the \words and \WORD macros. But I can’t find a
way to properly combine them with the “style” parameter of
highlights: it breaks frames and enumerations. Example:
\definehighlight [tolower] [style=\words,] %%% This is problematic.
\def\mylower#1{\bgroup\words#1\egroup} %%% The command itself
%%% works, though.
\starttext
FOO \tolower{FOO} FOO\par %%% Works.
\framed{BAR \mylower{BAR} BAR}%%% Works.
\framed{BAR \tolower{BAR} BAR}%%% Fails.
\startitemize %%% Enumerations don’t work either.
\item FOO \mylower{FOO} FOO %%% Works.
\item FOO \tolower{FOO} FOO %%% Fails.
\stopitemize
\stoptext
In short: while I can always wrap it in a \def, the more elegant
doesn’t work in all cases. Is there anything wrong with my
approach?
>>>
>>> You can use
>>>
>>> \definehighlight [tolower] [style={\setcharactercasing[2]}]
>>>
>>> to create the \tolower command.
>>
>> Perfect, thanks a lot. So it was caused by the \groupedcommand in
>> the definition of \word.
>
> The next version will support named casing:
>
> WORD
> word
> Word
> Words
> capitals cap
> Capitals Cap
> none
> random
It would be also useful to change the following line in font-pre.mkiv to use
\setcharacterchasing instead of \WORD (won’t work anymore when you remove
\groupedcommand from the \WORD as written in the comments in typo-cap.mkiv)
\definealternativestyle [\v!WORD] [\WORD][\WORD]
Additional entries for \word, Words etc. in font-pre.mkvi are useful as well
because “style=word” looks better than “style={\setcharacterchasing[word]}”.
Wolfgang
___
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] \definehighlight + \words | \WORDS
On 8-5-2012 11:18, Philipp Gesang wrote:
On 2012-05-08 11:07, Wolfgang Schuster wrote:
Am 08.05.2012 um 10:35 schrieb Philipp Gesang:
Dear listmates,
I rely on automated uppercasing and lowercasing a lot and I’m
very happy with the \words and \WORD macros. But I can’t find a
way to properly combine them with the “style” parameter of
highlights: it breaks frames and enumerations. Example:
\definehighlight [tolower] [style=\words,] %%% This is problematic.
\def\mylower#1{\bgroup\words#1\egroup} %%% The command itself
%%% works, though.
\starttext
FOO \tolower{FOO} FOO\par %%% Works.
\framed{BAR \mylower{BAR} BAR}%%% Works.
\framed{BAR \tolower{BAR} BAR}%%% Fails.
\startitemize %%% Enumerations don’t work either.
\item FOO \mylower{FOO} FOO %%% Works.
\item FOO \tolower{FOO} FOO %%% Fails.
\stopitemize
\stoptext
In short: while I can always wrap it in a \def, the more elegant
doesn’t work in all cases. Is there anything wrong with my
approach?
You can use
\definehighlight [tolower] [style={\setcharactercasing[2]}]
to create the \tolower command.
Perfect, thanks a lot. So it was caused by the \groupedcommand in
the definition of \word.
The next version will support named casing:
WORD
word
Word
Words
capitals cap
Capitals Cap
none
random
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Asian Language Support
I am attaching five test files including Fig. 3.1, 3.2, 3.3 in http://www.w3.org/TR/jlreq/ . All files but Fig3_1-different-linebreaks.txt, the positions of linebreaks are the same as the examples. In writing a manuscript, we will make linebreaks depending on its context, then the same results are required from the different sources, Fig3_1.txt and Fig3_1-different-linebreaks.txt . Yusuke. (2012/05/08 0:54), Hans Hagen wrote: On 7-5-2012 15:17, KUROKI Yusuke wrote: What the timing you choose to post this message! Several days ago, I, Japanese, firstly met Hans and had a lecture about Japanese typography and typesetting. Now it is the duration to prepare to think about Japanese typesetting in ConTeXt. It is note that hanzi option of ConTeXt is ugly for Japanese typesetting, it must come from some Chinese typesetting custom. We need to define a handler similar to chinese and korean, but with japanese rules etc. I will make a basic setup so that we have a starting point. It would be handy to have some test files. For instance, in http://www.w3.org/TR/jlreq/ the text in fig 3.1, 3.2, 3.3 which has mixed punctuation etc. Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - -- 黒木 裕介 (KUROKI Yusuke) kuroky(at)users.sourceforge.jp http://ptetexwin.sourceforge.jp/ 日本語の表記においては，漢字や仮名だけで なく，ローマ字やアラビア数字，さらに句読 点や括弧類などの記述記号を用いる．これら を組み合わせて表す日本語の文章では，表記 上における種々の問題がある． 日本語の表記においては，漢字や仮名だけでなく， ローマ字やアラビア数字，さらに句読点や括弧類などの 記述記号を用いる． これらを組み合わせて表す日本語の文章では，表記上に おける種々の問題がある． 日本語の表記においては，漢字や仮名だけで なく，ローマ字やアラビア数字，さらに句読 点や括弧類などの記述記号を用いる。これら を組み合わせて表す日本語の文章では，表記 上における種々の問題がある。 日本語の表記においては、漢字や仮名だけで なく、ローマ字やアラビア数字、さらに句読 点や括弧類などの記述記号を用いる。これら を組み合わせて表す日本語の文章では、表記 上における種々の問題がある。 日本語の表記では“漢字”や”仮名”だけで なく，“ローマ字”や“アラビア数字”，さら に“句読点”や“括弧類”などの記述記号を 用いる． ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] \definehighlight + \words | \WORDS
On 2012-05-08 11:07, Wolfgang Schuster wrote:
>
> Am 08.05.2012 um 10:35 schrieb Philipp Gesang:
>
> > Dear listmates,
> >
> > I rely on automated uppercasing and lowercasing a lot and I’m
> > very happy with the \words and \WORD macros. But I can’t find a
> > way to properly combine them with the “style” parameter of
> > highlights: it breaks frames and enumerations. Example:
> >
> >
> >
> > \definehighlight [tolower] [style=\words,] %%% This is problematic.
> > \def\mylower#1{\bgroup\words#1\egroup} %%% The command itself
> >%%% works, though.
> >
> > \starttext
> >
> > FOO \tolower{FOO} FOO\par %%% Works.
> > \framed{BAR \mylower{BAR} BAR}%%% Works.
> > \framed{BAR \tolower{BAR} BAR}%%% Fails.
> > \startitemize %%% Enumerations don’t work either.
> > \item FOO \mylower{FOO} FOO %%% Works.
> > \item FOO \tolower{FOO} FOO %%% Fails.
> > \stopitemize
> >
> > \stoptext
> >
> >
> >
> > In short: while I can always wrap it in a \def, the more elegant
> > doesn’t work in all cases. Is there anything wrong with my
> > approach?
>
> You can use
>
> \definehighlight [tolower] [style={\setcharactercasing[2]}]
>
> to create the \tolower command.
Perfect, thanks a lot. So it was caused by the \groupedcommand in
the definition of \word.
Philipp
>
> Wolfgang
> ___
> 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 : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
pgpM5YJabR3Ne.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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] [***SPAM***] Re: Asian Language Support
On 7-5-2012 14:54, d.henman wrote: Yusuke-san, Thank you too for writing. It seems like one or the other so far, platex does not give good western style characters but is great for Japanese, which the other option, simplefonts gives good western characters and according to you bad Japanese charac ters. Is it the font or the spacing that is bad in simplefont? Just a remark: for cjk one can best use the mkiv feature to combine fonts; there are probably some examples of korean fonts mixed with e.g. palatino or times in the email archive Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] \definehighlight + \words | \WORDS
Am 08.05.2012 um 10:35 schrieb Philipp Gesang:
> Dear listmates,
>
> I rely on automated uppercasing and lowercasing a lot and I’m
> very happy with the \words and \WORD macros. But I can’t find a
> way to properly combine them with the “style” parameter of
> highlights: it breaks frames and enumerations. Example:
>
>
>
> \definehighlight [tolower] [style=\words,] %%% This is problematic.
> \def\mylower#1{\bgroup\words#1\egroup} %%% The command itself
>%%% works, though.
>
> \starttext
>
> FOO \tolower{FOO} FOO\par %%% Works.
> \framed{BAR \mylower{BAR} BAR}%%% Works.
> \framed{BAR \tolower{BAR} BAR}%%% Fails.
> \startitemize %%% Enumerations don’t work either.
> \item FOO \mylower{FOO} FOO %%% Works.
> \item FOO \tolower{FOO} FOO %%% Fails.
> \stopitemize
>
> \stoptext
>
>
>
> In short: while I can always wrap it in a \def, the more elegant
> doesn’t work in all cases. Is there anything wrong with my
> approach?
You can use
\definehighlight [tolower] [style={\setcharactercasing[2]}]
to create the \tolower command.
Wolfgang
___
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Asian Language Support
Dear Henman-san, > So a question might be can ptex be used with ConTeXt? as the the engine? > Would this wowrk? With ConTeXt mark II (not mark IV), you can use ptex as the engine. Such support is included in W32TeX. (I don't know whether TeXLive 2011 supports it.) You can type `texexec --eptex foo'. If you want to try it, please read share/texmf/doc/context/context-w32. txt and test-eptex.tex. (It is written in Japanese, but I think it does not matter for you.) 2012/05/07(Mon) 22:54:47, "d.henman" : > > Yusuke-san, >Thank you too for writing. It seems like one or the other so far, platex > does not give good western style characters but is great for Japanese, which > the other option, simplefonts gives good western characters and according to > you bad Japanese charac > ters. Is it the font or the spacing that is bad in simplefont? > > So a question might be can ptex be used with ConTeXt? as the the engine? > Would this wowrk? > > ___ > 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 : http://foundry.supelec.fr/projects/contextrev/ > wiki : http://contextgarden.net > > ___ Sincerely, Noriyuki Abe ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] \definehighlight + \words | \WORDS
Dear listmates,
I rely on automated uppercasing and lowercasing a lot and I’m
very happy with the \words and \WORD macros. But I can’t find a
way to properly combine them with the “style” parameter of
highlights: it breaks frames and enumerations. Example:
\definehighlight [tolower] [style=\words,] %%% This is problematic.
\def\mylower#1{\bgroup\words#1\egroup} %%% The command itself
%%% works, though.
\starttext
FOO \tolower{FOO} FOO\par %%% Works.
\framed{BAR \mylower{BAR} BAR}%%% Works.
\framed{BAR \tolower{BAR} BAR}%%% Fails.
\startitemize %%% Enumerations don’t work either.
\item FOO \mylower{FOO} FOO %%% Works.
\item FOO \tolower{FOO} FOO %%% Fails.
\stopitemize
\stoptext
In short: while I can always wrap it in a \def, the more elegant
doesn’t work in all cases. Is there anything wrong with my
approach?
Best regards
Philipp
pgpNgAKRut2wp.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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
[NTG-context] [***SPAM***] Re: Asian Language Support
Yusuke-san, Thank you too for writing. It seems like one or the other so far, platex does not give good western style characters but is great for Japanese, which the other option, simplefonts gives good western characters and according to you bad Japanese charac ters. Is it the font or the spacing that is bad in simplefont? So a question might be can ptex be used with ConTeXt? as the the engine? Would this wowrk? ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] FLOWcharts - connector line length?
On 8-5-2012 08:20, Mari Voipio wrote:
Now, to implementing all this new knowledge in Chart 2.
and after that comes chart 3:
\usemodule[chart]
\startFLOWchart[ABC]
\startFLOWcell
\name{A}
\location{1,1}
\destination{whatever:A}
\text{A}
\connection[bt]{B}
\stopFLOWcell
\startFLOWcell
\name{B}
\location{1,2}
\destination{whatever:B}
\text{B}
\connection[bt]{C}
\stopFLOWcell
\startFLOWcell
\name{C}
\location{1,3}
\destination{whatever:C}
\text{C}
\connection[bt]{A}
\stopFLOWcell
\stopFLOWchart
\setupinteraction[state=start]
\starttext
\FLOWchart[ABC]
\startchapter[title=We're at A,reference=whatever:A] \input ward
\stopchapter
\startchapter[title=We're at B,reference=whatever:B] \input tufte
\stopchapter
\startchapter[title=We're at C,reference=whatever:C] \input zapf
\stopchapter
\stoptext
(One reason why the chart module exists is that it can be used for
online qa manuals and such where one can jump from cells to explanation.)
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
