Re: [NTG-context] ec encoding and tcaron
Vit Zyka wrote:
All right, thanks Hans, I will try new alpha, but what about
texfont-pseudocaps-problem? Is it relevat to this one? I turn to thing
it is different and much simpler problem...
i think that they are not loaded at all, adam may know (in a few weeks
i'll pick up a thread about this var stuff since we have some ideas on
how to make in more convenient)
anyhow, there is no need to redefine all mappings, sinc ethe existing
typescripts will be taken as well, so:
\starttypescript [all] [latin-modern] [texnansi,ec,qx,pl0,il2,t5]
\definefontsynonym [cmcsci10] [\typescriptthree-lmri10-capitalized-800]
[encoding=\typescriptthree]
\definefontsynonym [cmcscbx10] [\typescriptthree-lmbx10-capitalized-800]
[encoding=\typescriptthree]
\definefontsynonym [cmcscbxi10] [\typescriptthree-lmbxi10-capitalized-800]
[encoding=\typescriptthree]
\definefontsynonym [cmcscro10] [\typescriptthree-lmro10-capitalized-800]
[encoding=\typescriptthree]
\definefontsynonym [cmcsctti10] [\typescriptthree-lmtti10-capitalized-800]
[encoding=\typescriptthree]
\definefontsynonym [cmcsctto10] [\typescriptthree-lmtto10-capitalized-800]
[encoding=\typescriptthree]
\definefontsynonym [cmcscss10] [\typescriptthree-lmss10-capitalized-800]
[encoding=\typescriptthree]
\definefontsynonym
[cmcscssbx10][\typescriptthree-lmssbx10-capitalized-800][encoding=\typescriptthree]
\definefontsynonym [cmcscssi10] [\typescriptthree-lmsso10-capitalized-800]
[encoding=\typescriptthree]
\stoptypescript
\starttypescript [serif] [latin-modern] [default]
\definefontsynonym [SerifSmallCaps] [ComputerModern-Caps]
\definefontsynonym [SerifItalicSmallCaps][cmcsci10]
\definefontsynonym [SerifBoldSmallCaps] [cmcscbx10]
\definefontsynonym [SerifBoldItalicSmallCaps][cmcscbxi10]
\definefontsynonym [SerifSlantedSmallCaps] [cmcscro10]
\stoptypescript
\starttypescript [sans] [latin-modern] [default]
\definefontsynonym [SansSmallCaps] [cmcscss10]
\definefontsynonym [SansItalicSmallCaps] [cmcscssi10]
\definefontsynonym [SansBoldSmallCaps] [cmcscssbx10]
\definefontsynonym [SansSlantedSmallCaps][cmcscssi10]
\stoptypescript
\starttypescript [mono] [latin-modern] [default]
\definefontsynonym [MonoSmallCaps] [ComputerModernMono-Caps]
\definefontsynonym [MonoItalicSmallCaps][cmcsctti10]
\stoptypescript
(you can now add these typescripts to the main file, no need for a separate typescript file)
another approach is:
\starttypescript [all] [latin-modern-sc] [texnansi,ec,qx,pl0,il2,t5]
\definefontsynonym [cmcsci10] [\typescriptthree-lmri10-capitalized-800]
[encoding=\typescriptthree]
\definefontsynonym [cmcscbx10] [\typescriptthree-lmbx10-capitalized-800]
[encoding=\typescriptthree]
\definefontsynonym [cmcscbxi10] [\typescriptthree-lmbxi10-capitalized-800]
[encoding=\typescriptthree]
\definefontsynonym [cmcscro10] [\typescriptthree-lmro10-capitalized-800]
[encoding=\typescriptthree]
\definefontsynonym [cmcsctti10] [\typescriptthree-lmtti10-capitalized-800]
[encoding=\typescriptthree]
\definefontsynonym [cmcsctto10] [\typescriptthree-lmtto10-capitalized-800]
[encoding=\typescriptthree]
\definefontsynonym [cmcscss10] [\typescriptthree-lmss10-capitalized-800]
[encoding=\typescriptthree]
\definefontsynonym
[cmcscssbx10][\typescriptthree-lmssbx10-capitalized-800][encoding=\typescriptthree]
\definefontsynonym [cmcscssi10] [\typescriptthree-lmsso10-capitalized-800]
[encoding=\typescriptthree]
\stoptypescript
\starttypescript [serif] [latin-modern-sc] [name]
\definefontsynonym [Serif] [ComputerModern-Caps]
\definefontsynonym [SerifItalic][cmcsci10]
\definefontsynonym [SerifBold] [cmcscbx10]
\definefontsynonym [SerifBoldItalic][cmcscbxi10]
\definefontsynonym [SerifSlanted] [cmcscro10]
\stoptypescript
\starttypescript [sans] [latin-modern-sc] [name]
\definefontsynonym [Sans] [cmcscss10]
\definefontsynonym [SansItalic] [cmcscssi10]
\definefontsynonym [SansBold] [cmcscssbx10]
\definefontsynonym [SansSlanted][cmcscssi10]
\stoptypescript
\starttypescript [mono] [latin-modern-sc] [name]
\definefontsynonym [Mono] [ComputerModernMono-Caps]
\definefontsynonym [MonoItalic] [cmcsctti10]
\stoptypescript
\starttypescript[map][latin-modern-sc][all]
...
\stoptypescript
\definetypeface[modernsc][rm][serif][latin-modern-sc][default]
.
{\modernsc test}
-
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/l
Re: [NTG-context] Problems with Natural Tables
Eckhart Guthöhrlein <[EMAIL PROTECTED]> writes:
> Am Sonntag, den 14.08.2005, 17:17 +0200 schrieb Adam Duck:
>
>> - how do I set the spacing between a vertical line (between two
>> columns) and the text inside that columns? I already used
>> "framedoffest=-3pt", but the output is unacceptable.
>
> Spacing is a weak point of natural tables. Afaik, there is no good way
> to tune spacing. I would try using dummy colums like
> \bTD[width=1em]\eTD.
OK, That sounds reasonable. I'll try that. On the other hand this
means many \bTD\eTD ... but one can write a macro for that,
I think.
>> - how do I center the whole table? This one is really crucial: my GF
>> also accepts hacks ;).
>
> \midaligned{..} works
Yep, but only if I don't split the table:
bin1Po1GsCz4s.bin
Description: application/tex
gives
ERROR: Missing } inserted.
--- TeX said ---
}
\unvcopy
\splittblboxa ...p \page \egroup \fi \fi \unvcopy
2 \ifcase \noftblnextlines...
\splittblbox ...tblsplitmethod }\splittblboxa {#1}
\fi
\eTABLE ...}}\eTBL }\removeunwantedspaces \endTBL
\stopTBLprocessing \egroup...
l.11 \eTABLE
}
and \startalignment[middle]...\stopalignment doesn't seem to do
anything in that case.
>> - why doesn't \splitfloat{\placetable...} work with Natural Tables?
>> (They won't get splitted at all, but with tables and linetables it
>> works...)
>
> \setupTABLE[split=yes] or \setupTABLE[split=repeat]
That's not what I meant:
bin66p3Vl615t.bin
Description: application/tex
doesn't split the table. The output looks exactly like the
\midaligned{} one.
bye, Adam.
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] ec encoding and tcaron
Hans Hagen wrote:
Vit Zyka wrote:
Hans, did you think about Petr Olsak's enc-tex? I believe it is much
straight-forward solution that solve input enco, output to files and
output to log (utf8 works too). And it should be much quicker than
macros. I am not sure, but perhaps there is no patch to aleph now...
i took a look at it when it came around but it's not flexible enough; it
deals with the input and part of the output; i asked the author to
consider some extensions that would it make possible to deal with
multiple output variants (keep in mind that some input data may need to
be fed into pdf specific data structures, in different encodings, with
different kind of escapes etc) and that in for instance buffers,
verbatim, multi-pass data and other situations one may need the original
input; it all depends on how a macro package is build and deals with
data and also with the complexity of the applications. Live is simply
not simple. What works for latex or plain tex may not work for context
and vise versa.
So, when i noticed the 'just use it and don't ask' attitude i gave up on
I think I undestand...
enctex or at least decided to postpone support till i ran into a
Of course anyone is free to overload the relevant pieces of the regime
handler. I suppose that putting some enctex mapper in front of it works
ok (i.e. as long as one either expands to raw characters in the current
encoding or to named glyphs.
now back to the issue:
I uploaded a new version (while crossing my fingers); the problem with
this uppercasing is that handling (font) characters is one thing,
handling inputs another oif not to speak of commands, and other things
that can end up inside WORD and then be subjected to uppercasing
\def\Vit{Vit} \WORD{\Vit} -> VIT
\def\Vit{whatever} \WORD{\Vit} -> WHATEVER
\startencoding[ec]
\defineuppercasecom \Vit {nothing}
\stopencoding
\def\Vit{whatever} \WORD{\Vit} -> nothing
so, there is much more involved; i change a few things (i fear that taco
is the only one who now understand what's going on but you may give it a
try -)
(\chardef\uppercasemode\plusone gives the old behaviour)
The problem with this kind of things is that it will not become esier to
solve when we have a different tex or so ... there are simply too many
variants / usages / ...)
All right, thanks Hans, I will try new alpha, but what about
texfont-pseudocaps-problem? Is it relevat to this one? I turn to thing
it is different and much simpler problem...
vit
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Problems with Natural Tables
Vit Zyka wrote: Eckhart Guthöhrlein wrote: Am Sonntag, den 14.08.2005, 17:17 +0200 schrieb Adam Duck: - how do I set the spacing between a vertical line (between two columns) and the text inside that columns? I already used "framedoffest=-3pt", but the output is unacceptable. Spacing is a weak point of natural tables. Afaik, there is no good way to tune spacing. I would try using dummy colums like \bTD[width=1em]\eTD. Yes, I was also thinking about that. Perhaps adding lefttext= and righttext= params to \framed (since table cell is framed) solves some problem. Imagine: \setupTABLE[column][1,2][align=right,lefttext=\hskip.5em] or \setupTABLE[column][3][align=left,righttext=\hskip5pt$\bullet$] ... \bTABLE \eTABLE probably a distance parameter then (unrelated to framed); it's slightly more complex than you think because we need to take spans into account (so it shows up in prerolls etc) but it's doable 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] Problems with Natural Tables
Eckhart Guthöhrlein wrote: Am Sonntag, den 14.08.2005, 17:17 +0200 schrieb Adam Duck: - how do I set the spacing between a vertical line (between two columns) and the text inside that columns? I already used "framedoffest=-3pt", but the output is unacceptable. Spacing is a weak point of natural tables. Afaik, there is no good way to tune spacing. I would try using dummy colums like \bTD[width=1em]\eTD. Yes, I was also thinking about that. Perhaps adding lefttext= and righttext= params to \framed (since table cell is framed) solves some problem. Imagine: \setupTABLE[column][1,2][align=right,lefttext=\hskip.5em] or \setupTABLE[column][3][align=left,righttext=\hskip5pt$\bullet$] ... \bTABLE \eTABLE vit ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] ec encoding and tcaron
Vit Zyka wrote:
Hans, did you think about Petr Olsak's enc-tex? I believe it is much
straight-forward solution that solve input enco, output to files and
output to log (utf8 works too). And it should be much quicker than
macros. I am not sure, but perhaps there is no patch to aleph now...
i took a look at it when it came around but it's not flexible enough; it deals with the input and part of the output; i asked the author to consider some extensions that would it make possible to deal with multiple output variants (keep in mind that some input data may need to be fed into pdf specific data structures, in different encodings, with different kind of escapes etc) and that in for instance buffers, verbatim, multi-pass data and other situations one may need the original input; it all depends on how a macro package is build and deals with data and also with the complexity of the applications. Live is simply not simple. What works for latex or plain tex may not work for context and vise versa.
So, when i noticed the 'just use it and don't ask' attitude i gave up on enctex or at least decided to postpone support till i ran into a
Of course anyone is free to overload the relevant pieces of the regime handler. I suppose that putting some enctex mapper in front of it works ok (i.e. as long as one either expands to raw characters in the current encoding or to named glyphs.
now back to the issue:
I uploaded a new version (while crossing my fingers); the problem with this uppercasing is that handling (font) characters is one thing, handling inputs another oif not to speak of commands, and other things that can end up inside WORD and then be subjected to uppercasing
\def\Vit{Vit} \WORD{\Vit} -> VIT
\def\Vit{whatever} \WORD{\Vit} -> WHATEVER
\startencoding[ec]
\defineuppercasecom \Vit {nothing}
\stopencoding
\def\Vit{whatever} \WORD{\Vit} -> nothing
so, there is much more involved; i change a few things (i fear that taco is the only one who now understand what's going on but you may give it a try -)
(\chardef\uppercasemode\plusone gives the old behaviour)
The problem with this kind of things is that it will not become esier to solve when we have a different tex or so ... there are simply too many variants / usages / ...)
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] Problems with Natural Tables
Adam Duck wrote:
Hello ConTeXters,
my girlfriend writes her dimploma thesis now and I talked her into
using ConTeXt, but now I'm not sure anymore that this was the right
thing to do. So, the problems are numerous and some of them are:
- how do I set the spacing between a vertical line (between two
columns) and the text inside that columns? I already used
"framedoffest=-3pt", but the output is unacceptable.
- how do I center the whole table? This one is really crucial: my GF
also accepts hacks ;).
- why doesn't \splitfloat{\placetable...} work with Natural Tables?
(They won't get splitted at all, but with tables and linetables it
works...)
- how do I refer to tables then?
I have chosen Natural Tables because they were the only one that
splitted correctly (tables and linetables let out 2/3 of a page). So,
that's all for now.
we need small examples showing/solving the problems
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] Problems with Natural Tables
Am Sonntag, den 14.08.2005, 17:17 +0200 schrieb Adam Duck:
> - how do I set the spacing between a vertical line (between two
> columns) and the text inside that columns? I already used
> "framedoffest=-3pt", but the output is unacceptable.
Spacing is a weak point of natural tables. Afaik, there is no good way
to tune spacing. I would try using dummy colums like
\bTD[width=1em]\eTD.
> - how do I center the whole table? This one is really crucial: my GF
> also accepts hacks ;).
\midaligned{..} works
> - why doesn't \splitfloat{\placetable...} work with Natural Tables?
> (They won't get splitted at all, but with tables and linetables it
> works...)
\setupTABLE[split=yes] or \setupTABLE[split=repeat]
> - how do I refer to tables then?
If you don't put them in \placetable -- I don't know.
--
Eckhart
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] ec encoding and tcaron
Mojca Miklavec wrote: (Would it be very expensive to add this feature to the ec encoding automatically?) no, quite cheap; i'll cut you a deal ... make me the texnansi and qx variants and i'll enable all of it automatically 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] ec encoding and tcaron
Taco Hoekwater wrote: Vit Zyka wrote: Just comment: There should be CMAP resouce in the PDF for that maps font encoding to unicode. Then search and copying works. ConTeXt supports CMAP but IFAIK only il2 encoding! CMAP resources for the rest encoding are missing. Just see enco-pfr.tex From the Release notes: Context 2005.07.27 This version of ConTeXt was uploaded on July 28, 2005. * . * optionally make ec-encoded pdfs better searchable in Acrobat5 and lower See also this thread, only a few weeks ago: http://archive.contextgarden.net/message/20050727.073731.41799d96.html Cheers, Taco Thank you both! I remember the thread, but at that time searching for letters in ligatures worked for me and I have never noticed that anything was wrong with texnansi until a week ago :) as Hans's tricks made the letters look all-right. So I didn't understand the point of that hack. I added the comment about pfr to the Wiki (encodings and regimes). (Would it be very expensive to add this feature to the ec encoding automatically?) Thanks, Mojca ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Problems with Natural Tables
Hello ConTeXters,
my girlfriend writes her dimploma thesis now and I talked her into
using ConTeXt, but now I'm not sure anymore that this was the right
thing to do. So, the problems are numerous and some of them are:
- how do I set the spacing between a vertical line (between two
columns) and the text inside that columns? I already used
"framedoffest=-3pt", but the output is unacceptable.
- how do I center the whole table? This one is really crucial: my GF
also accepts hacks ;).
- why doesn't \splitfloat{\placetable...} work with Natural Tables?
(They won't get splitted at all, but with tables and linetables it
works...)
- how do I refer to tables then?
I have chosen Natural Tables because they were the only one that
splitted correctly (tables and linetables let out 2/3 of a page). So,
that's all for now.
bye, Adam.
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] ec encoding and tcaron
Vit Zyka wrote: Just comment: There should be CMAP resouce in the PDF for that maps font encoding to unicode. Then search and copying works. ConTeXt supports CMAP but IFAIK only il2 encoding! CMAP resources for the rest encoding are missing. Just see enco-pfr.tex From the Release notes: Context 2005.07.27 This version of ConTeXt was uploaded on July 28, 2005. * . * optionally make ec-encoded pdfs better searchable in Acrobat5 and lower See also this thread, only a few weeks ago: http://archive.contextgarden.net/message/20050727.073731.41799d96.html Cheers, Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] ec encoding and tcaron
Mojca Miklavec wrote:
Vit Zyka wrote:
Actually I discovered the source of the problem with \tcaron!
There exists enco-ecm.tex file with some exceptions. And there is
\definecharacter tcaron {\buildtextaccent\textcaron t}
If I comment this line, expansion is not needed. I suggest to omit it
since \tcaron is now present in lm.
If and only if you work with lm & ec. Otherwise building of accents is
quite useful.
(How can I get ec in Antiqwa?)
But \WORD I do not use (it was only product of my debugging) I use
pseudo caps and there the problem preserves. Files attached and
texfont --fontroot=X: --en=ec --ve=public --co=lm --source=auto
--ca=0.8 lmbx10
Another *extremely* strange observation.
In a document with ec encoding and some accented characters, searching
for 'č' simply doesn't work. I don't understand why. I know very
little about PDF, but in the resulting document there was this line
present:
/CharSet (/breve/one/D/U/Y/u/Ccaron/Scaron/Tcaron/Zcaron/ccaron/tcaron)
with more or less only the characters I used. The line seems to be OK,
ccaron seems to be present. Searching for 'š' works as expected (even
lower/uppercase is recognised), but at the place of 'č' only c is
recognised (if I copy-pase, only c remains at that place).
I thought that it was only Acrobat's fault, but searching for the same
letter in another document worked OK (documentation for Antiqwa for
example).
Minimal example:
\usetypescript[modern][ec]
\setupbodyfont[10pt,rm]
\starttext
\ccaron\scaron
\stoptext
Just comment:
There should be CMAP resouce in the PDF for that maps font encoding to
unicode. Then search and copying works. ConTeXt supports CMAP but IFAIK
only il2 encoding! CMAP resources for the rest encoding are missing.
Just see enco-pfr.tex
vit
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Problem installing ConTeXt jedit syntax mode
Hi, I've added the context jedit mode files to the modes directory inside my jedit settings directory, and appended the mode to the catalogue. I get XML validation errors that state the various DELEGATEs are invalid. The external files (*-en, *-de, etc...) do not import. Why? What am I doing wrong? Elliot ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] ec encoding and tcaron
Vit Zyka wrote:
> Actually I discovered the source of the problem with \tcaron!
> There exists enco-ecm.tex file with some exceptions. And there is
>
>\definecharacter tcaron {\buildtextaccent\textcaron t}
>
> If I comment this line, expansion is not needed. I suggest to omit it
> since \tcaron is now present in lm.
If and only if you work with lm & ec. Otherwise building of accents is
quite useful.
(How can I get ec in Antiqwa?)
> But \WORD I do not use (it was only product of my debugging) I use
> pseudo caps and there the problem preserves. Files attached and
>texfont --fontroot=X: --en=ec --ve=public --co=lm --source=auto
> --ca=0.8 lmbx10
Another *extremely* strange observation.
In a document with ec encoding and some accented characters, searching
for 'č' simply doesn't work. I don't understand why. I know very
little about PDF, but in the resulting document there was this line
present:
/CharSet (/breve/one/D/U/Y/u/Ccaron/Scaron/Tcaron/Zcaron/ccaron/tcaron)
with more or less only the characters I used. The line seems to be OK,
ccaron seems to be present. Searching for 'š' works as expected (even
lower/uppercase is recognised), but at the place of 'č' only c is
recognised (if I copy-pase, only c remains at that place).
I thought that it was only Acrobat's fault, but searching for the same
letter in another document worked OK (documentation for Antiqwa for
example).
Minimal example:
\usetypescript[modern][ec]
\setupbodyfont[10pt,rm]
\starttext
\ccaron\scaron
\stoptext
and then either searching or converting to plain text.
Mojca
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
