Re: [NTG-context] Separation of delimited text symbol
On 2013–03–08 Wolfgang Schuster wrote: The following change in typo-del.mkiv prevents the line break. […] Thanks Wolfgang for the code and thanks to Hans for incorporating this into the core. Marco signature.asc Description: Digital 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] width=local broken?
On 3/12/2013 1:32 AM, revic...@caesar.elte.hu wrote:
Hi,
I'm trying to use width=local in an enumartion, but the width is the
same for hsize, broad and local.
Example from the wiki
(http://wiki.contextgarden.net/Framed#Width_broad_and_local):
\setuppapersize[A5]
\setuppapersize[A7,landscape][A7,landscape]
\setupbodyfont[8pt,ss]
\setupcolors[state=start]
\setupframed[framecolor=blue]
\showframe
\starttext
\framed[width=\hsize,align=middle]{width=hsize}
\startitemize
\setlocalhsize
\item \framed[width=\hsize,align=middle] {width=hsize}
\item \framed[width=broad,align=middle] {width=broad}
\item \framed[width=local,align=middle] {width=local}
\stopitemize
\stoptext
Compare the above example with the picture from the wiki.
Did something changed around local?
tricky ... you can play with (in pack-rul.mkiv) a changed order:
% 2013/03/12: a change of order (sizes before align
\csname\??framedoffsetalternative
\ifcsname\??framedoffsetalternative\localoffset\endcsname
\localoffset
\else
\s!unknown
\fi
\endcsname
\csname\??framedwidthalternative
\ifcsname\??framedwidthalternative\localwidth\endcsname
\localwidth
\else
\s!unknown
\fi
\endcsname
\csname\??framedheightalternative
\ifcsname\??framedheightalternative\localheight\endcsname
\localheight
\else
\s!unknown
\fi
\endcsname
%
\forgetall % should happen after \localwidth but before align
%
\ifx\localformat\empty
\setfalse\c_framed_has_format
\else
\settrue\c_framed_has_format
\dosetraggedcommand\localformat % not that fast
\fi
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] Reusing MP graphics
On 3/11/2013 8:20 PM, Marco Patzer wrote:
Hi,
I have two questions concerning MP graphics.
What's going on here? The “abcdefghi” text is not displayed in the second
graphic and the “A” is stretched to match the size of the first graphic. Can
someone explain why this happens and if this is expected?
\startreusableMPgraphic{foo}
draw textext(abcdefghi);
picture p; p := currentpicture;
\stopreusableMPgraphic
\startreusableMPgraphic{bar}
addto currentpicture also p; %% not printed
draw textext(A); %% distorted
\stopreusableMPgraphic
\starttext
\reuseMPgraphic{foo}
\reuseMPgraphic{bar}
\stoptext
Does \includeMPgraphic only work with useMPgraphics (in contrast to
reusableMPgraphic)?
%% works with useMPgraphics, though
\startreusableMPgraphic{alpha}
draw textext(abcdefghi);
\stopreusableMPgraphic
\startreusableMPgraphic{beta}
\includeMPgraphic{alpha}
draw textext(A); %% not printed
\stopreusableMPgraphic
\starttext
\reuseMPgraphic{alpha}
\reuseMPgraphic{beta}
\stoptext
For each graphic context will remember the text picture. so, in your
case, the stored p in the first graphic has a reference to a text
picture (index 1) but it's the one created in the second graphic (also
index 1). There are no persistent text pictures (yet).
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] TOC: Chapters with and without page-numbers
Hello there, normally I use \setuplist[chapter][pagenumber=no] to prevent pages for chapters in the TOC, because normally (!) after every chapter-titel comes a section-title, directly, without text between the two titles. And so it is in this case enough to give the page-number for the section-titles only. But now I have an book with one single chapter, which do not have sections. So with \setuplist[chapter][pagenumber=no] it has no page-number in the TOC. I want to have the page-number for this single chapter-title only, but for the other chapter-titles (which have section-titles after them) I want still the above setting. How to do that? Thank you! Huseyin PS.: Sorry for sending this question with the wrong email-adress one minute before, it awaits moderation, but can be deleted, of course. ___ 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] garden example at fault
Hello Hans,
I think \setupbackgrounds now requires you to specify both the
column(s) *and* the row(s) you want to fill in.
% does not work
\setupbackgrounds[header][background=color, backgroundcolor=blue]
% does not work
\setupbackgrounds[header][][background=color, backgroundcolor=blue]
% this works
\setupbackgrounds[header][leftedge,leftmargin,text,rightmargin,rightedge][background=color,
backgroundcolor=blue]
(Also, just in case you didn't know: remember than any \showframe must
come before \setupbackgrounds, or it will 'overwrite' your settings.)
Cheers,
Sietse
On 11 March 2013 21:38, H. van der Meer h.vanderm...@uva.nl wrote:
I tried this sample from the garden to look at the top and bottom, see
Command/setuplayout.
Below a copy of the garden page (pagesize changed from A10 to A6):
\setuppapersize[A6]
%% This is an example for showing the effect of the vertical parameters
%% top, topdistance, bottom, bottomdistance and topspace.
%% Just play around with these parameters.
\showframe
%% Show the top and the bottom with blue color:
\setupbackgrounds[header, footer][background=color, backgroundcolor=blue]
\def\MyLength{10pt}
\setuplayout[
top=\MyLength,
topdistance=\MyLength,
bottom=\MyLength,
bottomdistance=\MyLength,
topspace=\dimexpr(\topheight + \topdistance),
height=fit]
\starttext
\input thuan
\stoptext
This is LuaTeX, Version beta-0.75.0-2013030308 (rev 4589)
ConTeXt ver: 2013.03.04 18:28 MKIV fmt: 2013.3.4 int: english/english
The top and bottom should have been blue as in the screenshot from the garden
(figure to the left). The reality however is no blue sections at all (figure
at right). What is wrong: the (fairly recent) context or the example in the
garden?
Hans van der Meer
___
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] reStructuredText module
Philipp Gesang wrote: Hi Bill. ···date: 2013-03-11, Monday···from: Bill Meahan··· Am I correct in thinking the rst module does not process the class and container directives? When I wrote the module I was working with the reST spec [0] and the syntax reference [1]. It’s been a while, but afair I implemented the spec completely (with the limitations described in the manual). It does not, to my knowledge, define the directives you mention and I don’t know what they’re supposed to do. (Btw. like much of the spec, “container” and “class” sound suspiciously HTML-specific. If that is true, they address one output markup which happens to be -- not Context! I might find the time to add a simple wrapper for the container thingy (to boxes or framed?). However, I doubt that it’s possible to replicate the behavior of HTML divs + CSS without a larger effort [2]. In this case it might be preferable to have docutils generate some XML and directly typeset the result with Context.) Best regards Philipp Hi Philip The .class and .container direectives are certainly there with *ML in mind but I think there might be analog situatins in ConTeXt. .. class:: classname blah, blah, blah exists to stick a class name on the following element for styling with an external stylesheet of some sort. CSS/CSS3 are probably the primary examles but other XML-bases markus apply just as well .. class::classname blab, blab, blab could yield p class=classnameblab, blab, blab/p h2 class=classnameblab. blab, blab/h2 or anything else that can take a class name attribute. .. container:: containername Foo, bar, baz bunch of stuff yields div class=containername foo, bar, baz bunch of stuff /div I would think ,, class:: ought to map quite well in ConTeXt: \setupsomething [classname] [attributelist] \startclassname Whatever \stopclassname for suitable values of something .. container:: probably maps to something like \frame[containername] although frames as such cannot cross page boundaries. Perhaps there is (or could be) a more suitable construct. I'm trying to be exemplary not directive. :) ConTeXt environment files are certainly analogus to CSS files and are used with the same end goals in mind. styling markup elements through class= or equivalent is rapidly becoming the order of the day for a wide variety of documents. Certainly (X)HTML, epub2, epub3, ODT, DOCX and an increasing horde of others are either there or heading there very soon. Am I way off base here? -- Bill Meahan Westland, Michigan USA ___ 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] reStructuredText module
···date: 2013-03-12, Tuesday···from: Bill Meahan···
Philipp Gesang wrote:
···date: 2013-03-11, Monday···from: Bill Meahan···
Am I correct in thinking the rst module does not process the class
and container directives?
When I wrote the module I was working with the reST spec [0] and
the syntax reference [1]. It’s been a while, but afair I
implemented the spec completely (with the limitations described
in the manual). It does not, to my knowledge, define the
directives you mention and I don’t know what they’re supposed to
do.
(Btw. like much of the spec, “container” and “class” sound
suspiciously HTML-specific. If that is true, they address one
output markup which happens to be -- not Context! I might find
the time to add a simple wrapper for the container thingy (to
boxes or framed?). However, I doubt that it’s possible to
replicate the behavior of HTML divs + CSS without a larger effort
[2]. In this case it might be preferable to have docutils
generate some XML and directly typeset the result with Context.)
Best regards
Philipp
The .class and .container direectives are certainly there with *ML in mind
but I think there might be analog situatins in ConTeXt.
.. class:: classname
blah, blah, blah
exists to stick a class name on the following element for styling with an
external stylesheet of some sort. CSS/CSS3 are probably the primary examles
but other XML-bases markus apply just as well
.. class::classname
blab, blab, blab
could yield
p class=classnameblab, blab, blab/p
h2 class=classnameblab. blab, blab/h2
or anything else that can take a class name attribute.
From its description [0], the “class” directive appears to be
next to meaningless outside an HTML context. It’s supposed to set
“classes”. The doctree spec [1] explicitly states that “The
classes attribute's contents should be ignorable.”
To my knowledge, the closest thing in Context to CSS classes is
the “setups=” parameter. All macros don’t accept it, though, so
I can’t think of a general way of handling it. The list of macros
where it applies would have to be hardcoded ...
Docutils’ latex2 writer -- the reference implementation, mind
you -- btw. doesn’t take the “class” directive seriously at all:
it handles paragraphs but ignores it e.g. for section heads.
.. container:: containername
Foo, bar, baz
bunch of stuff
yields
div class=containername
foo, bar, baz
bunch of stuff
/div
.. container:: probably maps to something like
\frame[containername]
although frames as such cannot cross page boundaries. Perhaps
there is (or could be) a more suitable construct. I'm trying to
be exemplary not directive. :)
Fyi [2]: “container” is docutils for “div”. How’s a “div”
supposed to look? That depends on your browser (not the spec!),
and the HTML version being used (XHTML 1.1 for python2-docutils).
What does that mean for non-HTML targets? Apparently nothing:
again, docutils ignore the directive when writing LaTeX (and man
pages, for that matter).
Nevertheless, I added some code to handle container directives:
at the moment they simply map to macros of the same name.
Existence of the macro is tested for at runtime, so you can place
the definitions in your preamble. Example:
·
This is a paragraph.
.. container:: xyzzy
whatever
foo **bar** baz
This is another paragraph.
·
This will generate the output:
·
\startparagraph
This is a paragraph.
\stopparagraph
\ifcsname xyzzy\endcsname%
\csname xyzzy\endcsname%
{whatever foo {\sc bar} baz}%
\else
{whatever foo {\sc bar} baz}%
\fi
\startparagraph
This is another paragraph.
\stopparagraph
·
So if there’s no \xyzzy, the contents are treated as a simple
group. Unnamed containers default to \framed. Let me know what
you think. The code is at:
https://bitbucket.org/phg/context-rst/get/0df50df9c8fb.zip
ConTeXt environment files are certainly analogus to CSS files and are used
with the same end goals in mind.
styling markup elements through class= or equivalent is
rapidly becoming the order of the day for a wide variety of
documents. Certainly (X)HTML, epub2, epub3, ODT, DOCX and an
increasing horde of others are either there or heading there very
soon.
Sure. I have no problem with that as long as it stays
implementation-agnostic.
Thanks for the feedback.
Philipp
[0] http://docutils.sourceforge.net/docs/ref/rst/directives.html#class
[1] http://docutils.sourceforge.net/docs/ref/doctree.html#classes
[2] http://docutils.sourceforge.net/docs/ref/rst/directives.html#container
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
Re: [NTG-context] reStructuredText module
On Tue, 12 Mar 2013, Philipp Gesang wrote:
Nevertheless, I added some code to handle container directives:
at the moment they simply map to macros of the same name.
Existence of the macro is tested for at runtime, so you can place
the definitions in your preamble. Example:
·
This is a paragraph.
.. container:: xyzzy
whatever
foo **bar** baz
This is another paragraph.
·
This will generate the output:
·
\startparagraph
This is a paragraph.
\stopparagraph
\ifcsname xyzzy\endcsname%
\csname xyzzy\endcsname%
{whatever foo {\sc bar} baz}%
\else
{whatever foo {\sc bar} baz}%
\fi
\startparagraph
This is another paragraph.
\stopparagraph
·
A better way to handle this is to provide macros \startRSTcontainer ...
\stopRSTcontainer and translate the above to
\startRSTcontainer[xyzzy][...settings ]
\stopRSTcontainer
It should be responsiblility of the document author to make sure that the
containers work correctly.
Depending on what containers are supposed to do (I have not read the links
posted in this thread), providing such a container might be as simple as
\let\startRSTcontainer=\startframedtext
\let\stopRSTcontainer=\stopframedtext
or
\let\startRSTcontainer=\startparagraph
\let\stopRSTcontainer=\stopparagraph
Aditya___
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] reStructuredText module
···date: 2013-03-12, Tuesday···from: Aditya Mahajan··· On Tue, 12 Mar 2013, Philipp Gesang wrote: A better way to handle this is to provide macros \startRSTcontainer ... \stopRSTcontainer and translate the above to I considered adding a generator \defineRSTcontainer with the usual interface (e.g. [command=\framed,frame=on]). This won’t work because the output is supposed to be a self-contained document. The goal is for the output to consist of ordinary Context macros only so it can be imported without loading further code. (I’m undecided regarding the requirement of the “\RST...” prefix, though.) \startRSTcontainer[xyzzy][...settings ] \stopRSTcontainer It should be responsiblility of the document author to make sure that the containers work correctly. Depending on what containers are supposed to do (I have not read the links posted in this thread), They are defined as HTML div’s. providing such a container might be as simple as \let\startRSTcontainer=\startframedtext \let\stopRSTcontainer=\stopframedtext or \let\startRSTcontainer=\startparagraph \let\stopRSTcontainer=\stopparagraph Honestly, I have no idea. Depending on the style sheet a div can be a float or aligned or have a shaded background. The current approach leaves the implementation to the user. Philipp -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments pgp0UMQM9mQ0z.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] reStructuredText module
On Tue, 12 Mar 2013, Philipp Gesang wrote:
···date: 2013-03-12, Tuesday···from: Aditya Mahajan···
On Tue, 12 Mar 2013, Philipp Gesang wrote:
A better way to handle this is to provide macros \startRSTcontainer
... \stopRSTcontainer and translate the above to
I considered adding a generator \defineRSTcontainer with the
usual interface (e.g. [command=\framed,frame=on]). This won’t
work because the output is supposed to be a self-contained
document. The goal is for the output to consist of ordinary
Context macros only so it can be imported without loading further
code. (I’m undecided regarding the requirement of the “\RST...”
prefix, though.)
Personally, I think that it is reasonable to expect the users to import a
module.
Honestly, I have no idea. Depending on the style sheet a div can
be a float or aligned or have a shaded background. The current
approach leaves the implementation to the user.
Another option is to change the generated output to
\start[xyzzy]
\stop
When the environment xyzzy exists, this is (supposed to be, see below)
equivalent to
\startxyzzy
\stopxyzzy
otherwise, this is equivalent to
\bgroup
\egroup
This way, you maintain your goal of having output that runs out of the
box, but at the same time generate readable code. It can then be left upto
the user to define the xyzzy environment (Of course, this method does not
support passing arguments to environment, but then neither does your
proposed solution).
@Hans, there is a bug in core-sys.mkiv: There is a missing \expandafter, and
currentstartstop should be changed to m_syst_start_stop.
\def\syst_start_yes[#1]%
{\edef\m_syst_start_stop{#1}%
\ifx\m_syst_start_stop\empty
\let\syst_stop_indeed\donothing
\else\ifcsname\e!start\m_syst_start_stop\endcsname
\expandafter\let\expandafter\syst_stop_indeed\csname\e!stop\m_syst_start_stop\endcsname
\csname\e!start\m_syst_start_stop\expandafter\expandafter\expandafter\endcsname
\else
\let\syst_stop_indeed\donothing
\fi\fi}
Aditya___
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] beta
Hi, I uploaded a beta. Quite some files were touched as I went over all messages at the Lua end (simplified using the formatter, more consistent, etc). It might be that I made mistakes which then will show up when tracing options are enabled or error messages are issued. 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] setups within typescripts: can it be done?
On 3/11/2013 5:51 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:
Dear gang,
Here is the situation: For an upcoming book project I may use a set of
proprietary fonts whose license that does not allow modification even
for personal, private use. Some characters I need are absent, but the
I'd choose another font.
components I need are there (macrons, dots, etc). So I can conceivably
use \defineactivecharacter to map each needed unicode char to a \def
made of glyph components in the font.
there is a 'compose' feature that does some virtual magic ... it's also
possible to specify things in a lfg file .. here is a copy from an
upcoming manual:
Yet another demonstration of manipulation is the following. Not all
fonts come
with all combined glyphs. Although we have an auto|-|compose feature in
\CONTEXT\
it sometimes helps to be specific with respect to some combinations. This is
where the \type {compositions} goodie kicks in:
\starttyping
local compose = {
[0x1E02] = {
anchored = top,
},
[0x1E04] = {
anchored = bottom,
},
[0x0042] = { -- B
anchors = {
top = {
x = 300,
y = 700,
},
bottom = {
x = 300,
y = -30,
},
},
},
[0x0307] = {
anchors = {
top = {
x = -250,
y = 550,
},
},
},
[0x0323] = {
anchors = {
bottom = {
x = -250,
y = -80,
},
},
},
}
return {
name = lm-compose-test,
version = 1.00,
comment = Goodies that demonstrate composition.,
author = Hans and Mojca,
copyright = ConTeXt development team,
compositions = {
[lmroman12-regular] = compose,
}
}
\stoptyping
Of course this assumes some knowledge of the font metrics (in base
points) and
\UNICODE\ slots, but it might be worth the trouble. After all, one only
needs to
figure it out once. But keep in mind that it will always be a kludge.
A slightly different way to define such compositions is the following:
\starttyping
local defaultunits = 193 - 30
local compose = {
DY = defaultunits,
-- [0x010C] = { DY = defaultunits }, -- Ccaron
-- [0x02C7] = { DY = defaultunits }, -- textcaron
}
-- fractions relative to delta(X_height - x_height)
local defaultfraction = 0.85
local compose = {
DY = defaultfraction, -- uppercase compensation
}
return {
name = lucida-one,
version = 1.00,
comment = Goodies that complement lucida.,
author = Hans and Mojca,
copyright = ConTeXt development team,
compositions = {
[lbr] = compose,
[lbi] = compose,
[lbd] = compose,
[lbdi] = compose,
}
}
\stoptyping
Of course no one really needs this because \OPENTYPE\ Lucida fonts
have replaced the \TYPEONE\ versions.
-
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] setups within typescripts: can it be done?
Hi Hans, Thanks for the reply: On Tue, 12 Mar 2013 19:01:30 -0600, Hans Hagen pra...@wxs.nl wrote: On 3/11/2013 5:51 PM, Idris Samawi Hamid ادريس سماوي حامد wrote: Dear gang, Here is the situation: For an upcoming book project I may use a set of proprietary fonts whose license that does not allow modification even for personal, private use. Some characters I need are absent, but the I'd choose another font. LOL. If you're referring to the private-use restriction: Adobe allows private/personal modifications for most fonts, so I could get away with making small fallbacks, etc. In the end, I may very well go with a company like Adobe for just this reason. (On the other hand, all of their optical sized book fonts are made by the same designer and have the same feel ... I'd like to try something different if I can find it). If you're referring to finding a font that has all the requisite characters: Hardly any HQ commercial text font for books has the requisite characters (mostly but not all in the Latin Extended Additional block). TeX-Gyre has the chars (I lobbied for them some years ago) but for the current project T-G is not really an option. components I need are there (macrons, dots, etc). So I can conceivably use \defineactivecharacter to map each needed unicode char to a \def made of glyph components in the font. there is a 'compose' feature that does some virtual magic ... Yes, I tried that a long time ago; will try again, though more precision will be needed, especially for italic etc.. it's also possible to specify things in a lfg file .. here is a copy from an upcoming manual: snip Yaay, I look forward to reading that! I was thinking that the goodies file would be the ideal place to put the specs. Of course this assumes some knowledge of the font metrics (in base points) and \UNICODE\ slots, but it might be worth the trouble. After all, one only needs to figure it out once. But keep in mind that it will always be a kludge. A slightly different way to define such compositions is the following: snip Ok, I'll study that as well Of course no one really needs this because \OPENTYPE\ Lucida fonts have replaced the \TYPEONE\ versions. Indeed. OTOH, I just found this wonderful (+very-expensive) Dutch typeface that is still(!) only available in Type1/ttf format. Thanks again and Best wishes Idris -- Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523 ___ 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] beta
2013/3/13 Hans Hagen pra...@wxs.nl: Hi, I uploaded a beta. Quite some files were touched as I went over all messages at the Lua end (simplified using the formatter, more consistent, etc). It might be that I made mistakes which then will show up when tracing options are enabled or error messages are issued. fails to define fonts. See this example: \definefontsynonym[song][name:adobesongstd] \definefontfallback[hereos][name:texgyreherosregular][0x-0x0400] \definefontsynonym[fbsong][song][fallbacks=hereos] \definefont[newsong][fbsong] \starttext \newsong 夹杂 English 的中文文本 \stoptext I get the error: ! LuaTeX error .../context/tex/texmf-context/tex/context/base/font-col.lua:90: attempt to get length of local 'd' (a nil value) stack traceback: .../context/tex/texmf-context/tex/context/base/font-col.lua:90: in function 'fontcollectiondefine' [string \directlua ]:1: in main chunk. -- Best regards, Li Yanrui (李延瑞) ___ 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 ___
