[NTG-context] website updates
Hi, Quick note: yesterday during the NTG meeting, we agreed that from now on, I will send a message to the mailing list if something new has been uploaded to the pragma ade website. Best wishes, Taco ___ 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] hyphenated url
On Thu, Oct 28 2010, Steffen Wolfrum wrote: > > > \startuseURL[anotherurl][urldescription] > > http://test%it.example.com > > \stopuseURL > > this doesn't work ... the address gets corrupt! > > Just run it, open the PDF in Acrobat and test the link: > > "Acrobat is attempting to connect to > http://test%25it.example.com"; This is normal behaviour of Acrobat, see also: http://archive.contextgarden.net/message/20101027.213001.ba65dced.en.html "it" is not hexadecimal. Peter -- Contact information: http://pmrb.free.fr/contact/ ___ 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 link with url + footnote
Hello,
Minimal example:
\setupinteraction[state=start]
\starttext
\hyphenatedurl{www.test.com}\footnote{a footnote}
Problem: the link is \quote{www.test.com1}.
\stoptext
Cheers, Peter
--
Contact information: http://pmrb.free.fr/contact/
___
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] ConText, TikZ and definecolor: undefined control sequence
On Wed, Oct 27, 2010 at 22:08, Michael Murphy wrote:
> On 27/10/2010 19:18, Marius wrote:
>>
>> Hello,
>> I had the same problem, so I desided to define colors by hand.
>>
>> \definecolor [lightgray] [h=D3D3D3]
>>
>> \usemodule[tikz]
>>
>> \unprotect
>> \pgfu...@definecolor{black}{gray}{0}
>> \pgfu...@definecolor{gray}{gray}{0.5}
>> \pgfu...@definecolor{lightgray}{gray}{0.9}
>> \pgfu...@definecolor{white}{gray}{1}
>> \protect
>
> Yes, this is what I've resorted to. But it would be nice to define things
> properly.
>
>> If you want to fix script, you need to change line:
>>
>> local cv = colors.value(attributes)
The table "colors" is expected to have a function named "value" that
take the "attributes" parameter as its sole parameter itself. It then
assigns the result to the local variable cv. After some research,
adding "local colors = global.attributes.colors" below the line
"local prtcatcodes = tex.prtcatcodes" works. There is a catch however,
you can't use opacity on these colors. I suppose we have to generate
all the transparency level by using spot colors or something like
that.
However, I still need to
add"\let\appendtoPDFdocumentcolorspaces\gobbleoneargument"
"\let\appendtoPDFdocumentextgstates\gobbleoneargument" and
"\let\PDFcolor\gobbleoneargument" before loading the TikZ module in
order for my documents to build without errors. These macros used to
be defined in mkii (spec-fdf.mkii) and TikZ relies on them
(tex/generic/pgf/utilities/pgfutil-context.def) but not anymore in
mkiv since the color support has changed between mkii and mkiv. I
suppose they had to do with the color support for PDF files, but
letting them gobble their argument still seems to work. On what side
should this problem be looked into: ConTeXt or TikZ?
Regards.
-- Cédric
>>
>> into
>>
>> local cv = attributes.colors.values
>>
>> Just guess, untested.
>
> Nope, doesn't work. Using
>
> local colors = colors or { }
>
> gets me a little further, but then complains that 'value' is a nil value. I
> don't know enough Lua to fix this either. Strangely, it seems to work on
> some older MkIV versions of ConTeXt...
>
> Michael.
> ___
> 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] hyphenated url
On 2010-10-28 <08:46:55>, Steffen Wolfrum wrote:
>
> Am 28.10.2010 um 00:05 schrieb Philipp Gesang:
>
> > % Usage example here:
> >
> > \startuseURL[anotherurl][urldescription]
> > http://test%it.example.com
> > \stopuseURL
> >
> > \starttext
> >
> > \from[anotherurl]\par
> > \url[anotherurl]\par
> >
> > Test.\footnote{\url[anotherurl]}
> >
> > \stoptext
>
>
>
> Hi Philipp,
>
> this doesn't work ... the address gets corrupt!
>
> Just run it, open the PDF in Acrobat and test the link:
>
> "Acrobat is attempting to connect to
> http://test%25it.example.com";
This can’t get corrupted any more because it’s illegal. From
RFC 1738:
···8<
hostname = *[ domainlabel "." ] toplabel
domainlabel= alphadigit | alphadigit *[ alphadigit | "-" ] alphadigit
···8<
No percent signs allowed in the hostname. Put your test percent
sign somewhere else and it will work (don’t know about acrobat,
but okular cooperates):
http://testit.example.com/%25
http://www.google.com/search?q=L%C3%A4rmbel%C3%A4stigung
Hth, Philipp
>
>
> Steffen
> ___
> 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
pgpc5MfIUuZdd.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] space breaks url-links
Hello,
Minimal example:
\setupinteraction[state=start]
\useURL[test][http://test.com/space space/]
\starttext
url: \url[test]
hyphenatedurl: \hyphenatedurl{http://test.com/space space/}
\stoptext
Cheers, Peter
--
Contact information: http://pmrb.free.fr/contact/
___
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] ConText, TikZ and definecolor: undefined control sequence
Actually, the opacity works great!
-- Cédric
On Thu, Oct 28, 2010 at 09:54, Cedric Mauclair
wrote:
> On Wed, Oct 27, 2010 at 22:08, Michael Murphy
> wrote:
>> On 27/10/2010 19:18, Marius wrote:
>>>
>>> Hello,
>>> I had the same problem, so I desided to define colors by hand.
>>>
>>> \definecolor [lightgray] [h=D3D3D3]
>>>
>>> \usemodule[tikz]
>>>
>>> \unprotect
>>> \pgfu...@definecolor{black}{gray}{0}
>>> \pgfu...@definecolor{gray}{gray}{0.5}
>>> \pgfu...@definecolor{lightgray}{gray}{0.9}
>>> \pgfu...@definecolor{white}{gray}{1}
>>> \protect
>>
>> Yes, this is what I've resorted to. But it would be nice to define things
>> properly.
>>
>>> If you want to fix script, you need to change line:
>>>
>>> local cv = colors.value(attributes)
> The table "colors" is expected to have a function named "value" that
> take the "attributes" parameter as its sole parameter itself. It then
> assigns the result to the local variable cv. After some research,
> adding "local colors = global.attributes.colors" below the line
> "local prtcatcodes = tex.prtcatcodes" works. There is a catch however,
> you can't use opacity on these colors. I suppose we have to generate
> all the transparency level by using spot colors or something like
> that.
>
> However, I still need to
> add"\let\appendtoPDFdocumentcolorspaces\gobbleoneargument"
> "\let\appendtoPDFdocumentextgstates\gobbleoneargument" and
> "\let\PDFcolor\gobbleoneargument" before loading the TikZ module in
> order for my documents to build without errors. These macros used to
> be defined in mkii (spec-fdf.mkii) and TikZ relies on them
> (tex/generic/pgf/utilities/pgfutil-context.def) but not anymore in
> mkiv since the color support has changed between mkii and mkiv. I
> suppose they had to do with the color support for PDF files, but
> letting them gobble their argument still seems to work. On what side
> should this problem be looked into: ConTeXt or TikZ?
>
> Regards.
>
> -- Cédric
>
>>>
>>> into
>>>
>>> local cv = attributes.colors.values
>>>
>>> Just guess, untested.
>>
>> Nope, doesn't work. Using
>>
>> local colors = colors or { }
>>
>> gets me a little further, but then complains that 'value' is a nil value. I
>> don't know enough Lua to fix this either. Strangely, it seems to work on
>> some older MkIV versions of ConTeXt...
>>
>> Michael.
>> ___
>> 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] manipulate ttf-fonts loaded with luatex
Am Wed, 27 Oct 2010 17:32:21 -0400 (EDT) schrieb Aditya Mahajan: > On Wed, 27 Oct 2010, Ulrike Fischer wrote: > >> Am Wed, 27 Oct 2010 14:35:46 -0400 (EDT) schrieb Aditya Mahajan: >> >>> On Wed, 27 Oct 2010, Ulrike Fischer wrote: >>> Hello, I'm currently a bit playing around with the idea to add some support in the (LaTeX) package "chessfss" (which handle chess fonts) for fonts loaded with the luaotfload package. As luaotfload use the context code to load the font I'm hoping that someone here can help me with some of my problems. Chess fonts are highly unstandard. The different authors of the fonts did put the chars quite randomly in the character table and also used various glyphs name. So in the psfonts.map almost every font has its own encoding vector: >>> >>> What is the unicode support for chess fonts. Are there unicode glyphs for >>> each symbol (just like card suits, I guess)? >> >> There are unicode code points only for a part of the symbols. > > I checked the unicode list. The codepoints 0x2654 to 0x365F cover all the > chess pieces. All the fonts in enpassent.dk and chessfss_gallery.pdf show > only these symbols. So what is missing? Most of the symbols needed/used by chessfss to construct boards: WhiteKingOnBlack, BlackQueenOnBlack etc, piecemasks and fieldmasks. Also a lot of so-called "informator symbols" used to comment chess games. If you want to see the whole range of symbol look in the skaknew-fonts on CTAN. They are quite complete. > I am guessing that the problem is not as simple as just mapping a > font glyph to the corresponding unicode codepoint. Even if unicode would have a code point for every symbol: At first my problem is not _where_ to map a glyph but _how_ to do it. And at second: Chess games and boards are typeset with commands so it doesn't matter much where a glyph is in a font as long as all chess fonts use the same standard so that you can switch fonts without problems. The standard used by chessfss is (for historical reasons) the font chart of the skak/skaknew fonts. -- Ulrike Fischer ___ 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] hyphenated url
On 27-10-2010 7:08, Peter Münster wrote:
On Wed, Oct 27 2010, Wolfgang Schuster wrote:
He wants perhaps:
\starthyphenatedurl
www.%.com
\stophyphenatedurl
No, he wants
\footnote{...\hyphenatedurl{...%...}...}
Yes. But if I understand TeX right, then there will be only 2 possibilities:
1.)
\footnote{bla
\starthyphenatedurl
www.%.com
\stophyphenatedurl
bla bla}
\asciimode \catcode`\% = \othercatcode
\footnote{bla \hyphenatedurl{www.%.com} bla bla}
\stoptext
If we can agree that asciimode also makes % a characters I can add that
preset. In that case one should mark comments differently, although when
one wants % to be % comments are not in the picture anyway.
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] ConText, TikZ and definecolor: undefined control sequence
Here is the fixed script.
On 27 October 2010 23:08, Michael Murphy wrote:
> On 27/10/2010 19:18, Marius wrote:
>>
>> Hello,
>> I had the same problem, so I desided to define colors by hand.
>>
>> \definecolor [lightgray] [h=D3D3D3]
>>
>> \usemodule[tikz]
>>
>> \unprotect
>> \pgfu...@definecolor{black}{gray}{0}
>> \pgfu...@definecolor{gray}{gray}{0.5}
>> \pgfu...@definecolor{lightgray}{gray}{0.9}
>> \pgfu...@definecolor{white}{gray}{1}
>> \protect
>
> Yes, this is what I've resorted to. But it would be nice to define things
> properly.
>
>> If you want to fix script, you need to change line:
>>
>> local cv = colors.value(attributes)
>>
>> into
>>
>> local cv = attributes.colors.values
>>
>> Just guess, untested.
>
> Nope, doesn't work. Using
>
> local colors = colors or { }
>
> gets me a little further, but then complains that 'value' is a nil value. I
> don't know enough Lua to fix this either. Strangely, it seems to work on
> some older MkIV versions of ConTeXt...
>
> Michael.
> ___
> 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
> ___
>
colorfix.tex
Description: TeX document
___
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] hyphenated url
On Thu, Oct 28 2010, Hans Hagen wrote: > If we can agree that asciimode also makes % a characters I can add > that preset. I agree. It's more consistent. Peter -- Contact information: http://pmrb.free.fr/contact/ ___ 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] improper sizes with pixel unit in MPinitialisation
Hi,
I started using 'MPinitialisation' to store some global variables. Much
easier than passing them over and over again to MP macros. Sadly this
way is inaccurate with the unit 'px' (no such problems with 'pt').
See attached example. The frame gives the exact size, showing that the
MP graphic is 'out of bounds'.
MTXrun | current version: 2010.10.22 16:46
same result for both marks
Peter
\setuppagenumber[state=stop]
\pdfpxdimen49336sp
\startMPinitializations
px:= .7528125;
fooWidth := 600px;
fooHeight := 400px;
\stopMPinitializations
\startuniqueMPgraphic{foo}
fill unitsquare xyscaled(fooWidth,fooHeight) withcolor
transparent(1,0.2,blue);
\stopuniqueMPgraphic
\starttext
\framed[offset=overlay,width=600px,height=400px,framecolor=darkblue]{\uniqueMPgraphic{foo}}
\stoptext
pixel.pdf
Description: Adobe PDF document
___
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] improper sizes with pixel unit in MPinitialisation
On 10/28/2010 12:12 PM, Peter Rolf wrote: Hi, I started using 'MPinitialisation' to store some global variables. Much easier than passing them over and over again to MP macros. Sadly this way is inaccurate with the unit 'px' (no such problems with 'pt'). See attached example. The frame gives the exact size, showing that the MP graphic is 'out of bounds'. Probably because metapost calculates in printer points of 72pt/in, instead of tex's 72.27pt/in. So your mp scale factor is likely to be a little off. Best wishes, Taco ___ 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] hyphenated url
On Thu, Oct 28, 2010 at 11:53:52AM +0200, Peter Münster wrote: > On Thu, Oct 28 2010, Hans Hagen wrote: > > > If we can agree that asciimode also makes % a characters I can add > > that preset. > > I agree. It's more consistent. Me too :) We just need some other way to put inline comments. Regards, Khaled -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer ___ 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] ConText, TikZ and definecolor: undefined control sequence
On 28-10-2010 9:54, Cedric Mauclair wrote:
On Wed, Oct 27, 2010 at 22:08, Michael Murphy wrote:
On 27/10/2010 19:18, Marius wrote:
Hello,
I had the same problem, so I desided to define colors by hand.
\definecolor [lightgray] [h=D3D3D3]
\usemodule[tikz]
\unprotect
\pgfu...@definecolor{black}{gray}{0}
\pgfu...@definecolor{gray}{gray}{0.5}
\pgfu...@definecolor{lightgray}{gray}{0.9}
\pgfu...@definecolor{white}{gray}{1}
\protect
Yes, this is what I've resorted to. But it would be nice to define things
properly.
If you want to fix script, you need to change line:
local cv = colors.value(attributes)
The table "colors" is expected to have a function named "value" that
take the "attributes" parameter as its sole parameter itself. It then
assigns the result to the local variable cv. After some research,
adding "local colors = global.attributes.colors" below the line
"local prtcatcodes = tex.prtcatcodes" works. There is a catch however,
you can't use opacity on these colors. I suppose we have to generate
all the transparency level by using spot colors or something like
that.
There are several solutions to the problem.
\usemodule[tikz]
\startmode[mkiv]
\startluacode
thirddata = thirddata or { }
thirddata.pgf = thirddata.pgf or { }
local texsprint, prtcatcodes, format = tex.sprint, tex.prtcatcodes,
string.format
local function unsupported_color(name)
texsprint(prtcatcodes,format("\\PackageError{pgf}{color %s has
unsupported model}{}", name))
texsprint(prtcatcodes,format("\\pgfu...@definecolor{%s}{gray}{0}",
name))
end
local colors = attributes.colors
function thirddata.pgf.registercolor(name,attribute) -- solution 1
local cv = colors.value(attribute)
if cv then
local model = colors.forcedmodel(cv[1])
if model > 3 then
model = 3 -- no cmyk or spot or multitone
end
if model == 2 then
texsprint(prtcatcodes,format("\\pgfu...@definecolor{%s}{gray}{%1.3f}",
name, cv[2]))
elseif model == 3 then
texsprint(prtcatcodes,format("\\pgfu...@definecolor{%s}{rgb}{%1.3f,%1.3f,%1.3f}",
name, cv[3], cv[4], cv[5]))
else
unsupported_color(name)
end
else
unsupported_color(name)
end
end
function lpdf.pdfcolor(attribute)
context(lpdf.color(1,attribute))
end
\stopluacode
\stopmode
\unprotect
% solution 1 (also fallback when cmyk is used):
% \def\PDFcolor#1%
% {\ctxlua{thirddata.pgf.pdfcolor(\thecolorattribute{#1})}}
% solution 2 (faster as less parsing at the tex end):
% \def\pgfu...@registercolor#1%
% {\ctxlua{thirddata.pgf.registercolor("#1",\thecolorattribute{#1})}}
% solution 3 (backward compatible):
\def\PDFcolor#1%
{\ctxlua{lpdf.pdfcolor(\thecolorattribute{#1})}}
\protect
\definecolor[mycolora][r=1,g=0,b=1]
\definecolor[mycolorb][m=1]
\starttext
\starttikzpicture
\fill[mycolora] (0,0) circle (2);
\fill[mycolorb] (0,0) circle (1);
\stoptikzpicture
\stoptext
I'll define \pdfcolor for this purpose as that's what tikz expects.
However, I still need to
add"\let\appendtoPDFdocumentcolorspaces\gobbleoneargument"
"\let\appendtoPDFdocumentextgstates\gobbleoneargument" and
"\let\PDFcolor\gobbleoneargument" before loading the TikZ module in
order for my documents to build without errors. These macros used to
be defined in mkii (spec-fdf.mkii) and TikZ relies on them
(tex/generic/pgf/utilities/pgfutil-context.def) but not anymore in
mkiv since the color support has changed between mkii and mkiv. I
suppose they had to do with the color support for PDF files, but
letting them gobble their argument still seems to work. On what side
should this problem be looked into: ConTeXt or TikZ?
In pgfutil-context.def there should be no such commands called when mkiv
is used. Isn't there a
\doifmodeelse {mkiv} { ...
section? anyhow, in that section one can add
\ifdefined\PDFcolor \else
\ctxlua{function lpdf.pdfcolor(attribute)
context(lpdf.color(1,attribute)) end}
\def\PDFcolor#1{\ctxlua{lpdf.pdfcolor(\thecolorattribute{#1})}}
\fi
(in the next beta this is not needed as \PDFcolor is defined then)
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
-
% Copyright 2006 by Till Tantau
%
% This file may be distributed and/or modified
%
% 1. under the LaTeX Project Public License and/or
% 2. under the GNU Public License.
%
% See the file doc/generic/pgf/licenses/LICENSE for more details.
% The aux files, needed for reading back coordinates
\def\pgfu...@aux@r...@hook{
\pgfu...@iffileexists{\jobname.pgf}{\input \jobname.pgf\relax}{}
\csname newwrite\endcsname\pgfu...@auxout
\csname openout\endcsname\pgf
Re: [NTG-context] ConText, TikZ and definecolor: undefined control sequence
On 28-10-2010 10:24, Cedric Mauclair wrote: Actually, the opacity works great! Officially it could hook into the context transparency model but I guess that that is too much hassle. 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] hyphenated url
On Thu, Oct 28 2010, Khaled Hosny wrote: > Me too :) We just need some other way to put inline comments. I don't know, if it's possible, but \% could be nice. Peter -- Contact information: http://pmrb.free.fr/contact/ ___ 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 link with url + footnote
On 28-10-2010 9:49, Peter Münster wrote:
Hello,
Minimal example:
\setupinteraction[state=start]
\starttext
\hyphenatedurl{www.test.com}\footnote{a footnote}
Problem: the link is \quote{www.test.com1}.
\stoptext
\goto{wherever}[url(www.test.com)]\footnote{a footnote}
--
-
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] hyphenated url (SOLVED)
Am 28.10.2010 um 08:53 schrieb Taco Hoekwater:
> This works:
>
> \startbuffer [comurl] \catcode`\%=12
> \hyphenatedurl{...
If I didn't overlook something, then this must be finally the solution:
\startbuffer [comurl] \catcode`\%=12
\useURL[test][http://www.kommers.se/upload/Analysarkiv/In%20English/Analyses/Woolcock%20paper%20on%20impact%20of%20Lisbontreaty%20on%20tradepolicy.pdf][]
[http://www.kommers.se/upload/Analysarkiv/In%20English/\crlf
Analyses/Woolcock%20paper%20on%20impact%20of%20Lisb\crlf
ontreaty%20on%20tradepolicy.pdf]\from[test]
\stopbuffer
\setupinteraction
[state=start]
\starttext
test {\getbuffer[comurl]} text.% HEY!
test
\startfootnote
test \getbuffer[comurl]\ text.% HEY!
\stopfootnote{} text.% HEY!
\stoptext
Here, the "%" character can be used for URL, both in bodytext and footnote, but
works as "comment", too.
And we can at the same time manually break long URLs that are too weird for
hyphenation by \hyphenatedurl.
Thank you Taco, Peter, Philipp and Hans for your efforts ...
and eventually getting all the pieces for this solution together!!!
Steffen
___
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] ConText, TikZ and definecolor: undefined control sequence
Sadly no. I once tried to modify it to make it work and I ended up
with what I proposed. Not very nice, but worked for me.
Thanks for your solution.
-- Cédric
On Thu, Oct 28, 2010 at 13:46, Hans Hagen wrote:
>
> \ifdefined\PDFcolor \else
>
> \ctxlua{function lpdf.pdfcolor(attribute) context(lpdf.color(1,attribute))
> end}
>
> \def\PDFcolor#1{\ctxlua{lpdf.pdfcolor(\thecolorattribute{#1})}}
>
> \fi
>
___
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] NTG Meeting October 27, 2010
On Wed, Oct 20, 2010 at 5:59 PM, Taco Hoekwater wrote: > Dear TeXies! > > > The autumn meeting of the NTG will take place on October 27, 2010, > from 10:00 until 16:30. > > We will meet at one of the locations of the Netherlands Defence Academy: > complex 'Kasteel van Breda', Kasteelplein 10, 4811 XC Breda. The > meeting will take place in building "'t Uiltje". > > The program is as follows: > : > * Discussion topic: The rise of e-readers: will this be the end > of typesetting or will we manage to survive? So, should we start to manage our survive ? -- luigi ___ 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] manipulate ttf-fonts loaded with luatex
On 28-10-2010 10:34, Ulrike Fischer wrote:
Even if unicode would have a code point for every symbol: At first
my problem is not _where_ to map a glyph but _how_ to do it. And at
second: Chess games and boards are typeset with commands so it
doesn't matter much where a glyph is in a font as long as all chess
fonts use the same standard so that you can switch fonts without
problems. The standard used by chessfss is (for historical reasons)
the font chart of the skak/skaknew fonts.
\directlua{fonts.otf.char("glyphname")}
Should work.
-
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] NTG Meeting October 27, 2010
On 28-10-2010 2:17, luigi scarso wrote: * Discussion topic: The rise of e-readers: will this be the end of typesetting or will we manage to survive? So, should we start to manage our survive ? Frans G decided never to print again. 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] Using fourier-GUT as math font
On 27-10-2010 3:49, nitralime wrote:
I have made a mistake in my typescript. Here is the corrected version:
%%
..
\starttypescript [math] [fourier][texnansi]
\definefontsynonym [Fourier-Math-Letters] [name:fouriermathletters]
\definefontsynonym [Fourier-Math-Letters-Italic]
[name:fouriermathlettersitalic]
\definefontsynonym [Fourier-Math-Letters-Bold]
[name:fouriermathlettersbold]
\definefontsynonym [Fourier-Math-Letters-BoldItalic]
[name:fouriermathlettersbolditalic]
\definefontsynonym [Fourier-Math-Blackboard] [name:fouriermathblackboard]
\definefontsynonym [Fourier-Math-Calligraphic] [name:fouriermathcal]
\definefontsynonym [Fourier-Math-Symbols] [name:fouriermathsymbols]
\definefontsynonym [Fourier-Math-Extension] [name:fouriermathextension]
%---
\definefontsynonym [Euler-Fraktur] [name:eufm10]
\definefontsynonym [Euler-Fraktur-Bold] [name:eufb10]
%---
\stoptypescript
..
%%
However, this correction has not affected the final result. The same
problem as before:-(
It does not work that way in mkiv.
(1) you need a proper serif definition:
\starttypescript [serif] [utopia] [name]
\definefontsynonym [Serif][file:whatever.afm]
\definefontsynonym [SerifItalic] [file:...]
\definefontsynonym [SerifBold][file:...]
\definefontsynonym [SerifBoldItalic] [file:...]
\definefontsynonym [SerifSlanted] [file:...]
\definefontsynonym [SerifBoldSlanted] [file:...]
\stoptypescript
(2) you need a math definition:
\starttypescript [math] [fourier]
\loadfontgoodies[fourier-math]
\definefontsynonym[mathroman][four...@fourier-math]
\stoptypescript
(3) now you can define a typeface:
\definetypeface[whatever][rm][serif][utopia] [default]
\definetypeface[whatever][mm][math] [fourier][default]
\setupbodyfont[whatever]
However, first you need to figure out the right names for the utopia
files. Next you need to make a file fourier-math.lfg, like:
return {
name = "fourier-math",
version = "1.00",
comment = "Goodies that complement fourier math.",
author = "Hans",
copyright = "ConTeXt development team",
mathematics = {
mapfiles = {
"fourier.map",
},
virtuals = {
["fourier-math"] = {
{ name = "futmi.tfm", vector = "tex-mi" },
{ name = "futmii.tfm", vector = "tex-it" },
{ name = "futsy.tfm", vector = "lbr-sy", skewchar=0x7F,
parameters = true },
{ name = "fourier-mex.tfm", vector = "tex-ex",
extension = true },
}
}
}
}
This does not work at my end as the names of the files are wrong. Also,
more entries are needed (see for instance lucida-math.lfg). I have no
time to figure out these names.
(btw, there is already some math utopia support)
-
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] manipulate ttf-fonts loaded with luatex
Am Thu, 28 Oct 2010 14:33:03 +0200 schrieb Hans Hagen:
> On 28-10-2010 10:34, Ulrike Fischer wrote:
>
>> Even if unicode would have a code point for every symbol: At first
>> my problem is not _where_ to map a glyph but _how_ to do it. And at
>> second: Chess games and boards are typeset with commands so it
>> doesn't matter much where a glyph is in a font as long as all chess
>> fonts use the same standard so that you can switch fonts without
>> problems. The standard used by chessfss is (for historical reasons)
>> the font chart of the skak/skaknew fonts.
>>
>
> \directlua{fonts.otf.char("glyphname")}
>
> Should work.
No, it doesn't work.
\directlua{fonts.otf.char("c140")} doesn't give the King ("c140",
\char140) but an "aring" due to the entry
unicodes={...,c140={ 229, 140 },...}
in temp-pirat.lua generated by luaoftload.
\documentclass{article}
\usepackage{luaotfload}
\pagestyle{empty}
\begin{document}
\font\test={name:Chess Figurine Pirat}
\test
\char140 \directlua{fonts.otf.char("c140")}
\end{document}
So how can I change the fontdata so that
\directlua{fonts.otf.char("c140")} gives the correct glyph?
And when I have corrected the fontdata, is there a way (besides
using a fea-file) to manipulate the fontdata so that the input "K"
outputs the glyph "c140"?
--
Ulrike Fischer
___
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] hyphenated url
Am 28.10.2010 um 08:53 schrieb Taco Hoekwater:
> On 10/27/2010 02:43 PM, Wolfgang Schuster wrote:
>>
>> Am 27.10.2010 um 12:35 schrieb Steffen Wolfrum:
>>
>>> Hi Hans and other catcode wizards,
>>>
>>> isn't there a way to make this kind of catcode trickery only be available
>>> *inside* \hyphenatedurl{} environment?
>>
>> It’s useless in this case because the „%“ is read from the footnote before
>> \hyphenatedurl can see it and any local catcode changes have therefore no
>> effect.
>
> This works:
>
> \startbuffer [comurl] \catcode`\%=12
> \hyphenatedurl{http://www.kommers.se/upload/Analysarkiv/In%20English/Analyses/Woolcock%20paper%20on%20impact%20of%20Lisbontreaty%20on%20tradepolicy.pdf}
> \stopbuffer
>
> \setupinteraction
> [state=start]
>
> \starttext
>
> test\footnote{test \getbuffer[comurl] text.} text.
>
> \stoptext
Sure but \getbuffer isn’t expanded when the footnote text is read by tex, when
you look at the tuc file you can see the entry for the footnote is:
titledata={
title="test \\getbuffer [comurl] text.",
},
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] hyphenated url
Am 28.10.2010 um 13:02 schrieb Khaled Hosny:
> On Thu, Oct 28, 2010 at 11:53:52AM +0200, Peter Münster wrote:
>> On Thu, Oct 28 2010, Hans Hagen wrote:
>>
>>> If we can agree that asciimode also makes % a characters I can add
>>> that preset.
>>
>> I agree. It's more consistent.
>
> Me too :) We just need some other way to put inline comments.
\bgroup \obeylines
\gdef\hide%
{\begingroup%
\obeylines%
\dohide}
\gdef\dohide#1
{\endgroup}
\egroup
\starttext
Auf% ligature
lage
Auf\hide ligature
lage
\stoptext
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] manipulate ttf-fonts loaded with luatex
On 10/28/2010 02:57 PM, Ulrike Fischer wrote: And when I have corrected the fontdata, is there a way (besides using a fea-file) to manipulate the fontdata so that the input "K" outputs the glyph "c140"? I have not followed this closely, bit it seems to me that the problem is more likely caused by a fea file than that it is cured by it. ___ 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] NTG Meeting October 27, 2010
On Thu, Oct 28, 2010 at 2:35 PM, Hans Hagen wrote: > On 28-10-2010 2:17, luigi scarso wrote: > >>> * Discussion topic: The rise of e-readers: will this be the end >>> of typesetting or will we manage to survive? >> >> So, should we start to manage our survive ? > > Frans G decided never to print again. hm, not a good sign then. -- luigi ___ 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] manipulate ttf-fonts loaded with luatex
On 28-10-2010 2:57, Ulrike Fischer wrote:
Am Thu, 28 Oct 2010 14:33:03 +0200 schrieb Hans Hagen:
On 28-10-2010 10:34, Ulrike Fischer wrote:
Even if unicode would have a code point for every symbol: At first
my problem is not _where_ to map a glyph but _how_ to do it. And at
second: Chess games and boards are typeset with commands so it
doesn't matter much where a glyph is in a font as long as all chess
fonts use the same standard so that you can switch fonts without
problems. The standard used by chessfss is (for historical reasons)
the font chart of the skak/skaknew fonts.
\directlua{fonts.otf.char("glyphname")}
Should work.
No, it doesn't work.
\directlua{fonts.otf.char("c140")} doesn't give the King ("c140",
\char140) but an "aring" due to the entry
unicodes={...,c140={ 229, 140 },...}
in temp-pirat.lua generated by luaoftload.
\documentclass{article}
\usepackage{luaotfload}
\pagestyle{empty}
\begin{document}
\font\test={name:Chess Figurine Pirat}
\test
\char140 \directlua{fonts.otf.char("c140")}
\end{document}
So how can I change the fontdata so that
\directlua{fonts.otf.char("c140")} gives the correct glyph?
And when I have corrected the fontdata, is there a way (besides
using a fea-file) to manipulate the fontdata so that the input "K"
outputs the glyph "c140"?
I can't speak for latex so if you want an answer then I need the font in
order to see what happens in context as that is the reference.
-
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] manipulate ttf-fonts loaded with luatex
Am Thu, 28 Oct 2010 15:08:09 +0200 schrieb Taco Hoekwater:
>> And when I have corrected the fontdata, is there a way (besides
>> using a fea-file) to manipulate the fontdata so that the input "K"
>> outputs the glyph "c140"?
> I have not followed this closely, bit it seems to me that the problem
> is more likely caused by a fea file than that it is cured by it.
The problem is that I have some highly non-standard (mostly
ttf-)fonts with glyphs with non-standard names ordered in
non-standard ways. The problem exists without using fea-files at
all!
I will ask the other way round: If you have a font loaded with e.g.
\font\test={name:Arial) in context. Can you manipulate the fontdata
so that when you use this font ABC outputs the glyphs CDE? If yes
how do you do it? If no: can I define a virtual font which does the
task? I naturally don't want to disturb the font loading system of
luaotfload. Or to write a font loader. I don't have enough knowledge
to do this.
--
Ulrike Fischer
___
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] manipulate ttf-fonts loaded with luatex
Am Thu, 28 Oct 2010 15:10:20 +0200 schrieb Hans Hagen: > I can't speak for latex so if you want an answer then I need the font in > order to see what happens in context as that is the reference. The font is here: http://www.enpassant.dk/chess/downl/pirat.zip (I'm not expecting context or luaotfload to handle such a non-standard font automatically. I'm only trying to find out how to write the code needed to adjust the font.) -- Ulrike Fischer ___ 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] manipulate ttf-fonts loaded with luatex
On Thu, Oct 28, 2010 at 03:08:09PM +0200, Taco Hoekwater wrote: > On 10/28/2010 02:57 PM, Ulrike Fischer wrote: > > > >And when I have corrected the fontdata, is there a way (besides > >using a fea-file) to manipulate the fontdata so that the input "K" > >outputs the glyph "c140"? > > I have not followed this closely, bit it seems to me that the problem > is more likely caused by a fea file than that it is cured by it. It seems like the font is using that multiple code points for the same glyph some thing of TrueType, I'm not sure, but I recall FF documentation recommending against using it. Regards, Khaled -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer ___ 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] Using fourier-GUT as math font
Thank you very much for this info! As a beginner I must first figure out (resp. digest) what you have written:-) My intention was to create a typescript for the combination Baskerville (serif) + GillSans(sans) + Consolas(mono) + FourierGUT(math) The typescript included in my original posting contains the relevant definitions for all of these parts (serif, sans etc.). I have added the output of "mtxrun ..." on my pc below. Hopefully somebody else on this list can give me some tips! *[...@hilbert ~]$* *mtxrun --script fonts --list --all --pattern=*fourier** fourieralternateblack fourieralternateblack /home/nik/.fonts/MathFonts/FourierGUT/fourier-alt-black.afm fourieralternateblackblack fourieralternateblack /home/nik/.fonts/MathFonts/FourierGUT/fourier-alt-black.afm fourieralternateboldfourieralternatebold /home/nik/.fonts/MathFonts/FourierGUT/fourier-alt-bold.afm fourieralternateboldboldfourieralternatebold /home/nik/.fonts/MathFonts/FourierGUT/fourier-alt-bold.afm fourieralternatebolditalic fourieralternatebolditalic /home/nik/.fonts/MathFonts/FourierGUT/fourier-alt-boldita.afm fourieralternatebolditalicbold fourieralternatebolditalic /home/nik/.fonts/MathFonts/FourierGUT/fourier-alt-boldita.afm fourieralternateitalic fourieralternateitalic /home/nik/.fonts/MathFonts/FourierGUT/fourier-alt-ita.afm fourieralternateitalicnormalfourieralternateitalic /home/nik/.fonts/MathFonts/FourierGUT/fourier-alt-ita.afm fourieralternateroman fourieralternateroman /home/nik/.fonts/MathFonts/FourierGUT/fourier-alt.afm fourieralternateromannormal fourieralternateroman /home/nik/.fonts/MathFonts/FourierGUT/fourier-alt.afm fourieralternatesemiboldfourieralternatesemibold /home/nik/.fonts/MathFonts/FourierGUT/fourier-alt-semi.afm fourieralternatesemiboldsemiboldfourieralternatesemibold /home/nik/.fonts/MathFonts/FourierGUT/fourier-alt-semi.afm fourieralternatesemitalic fourieralternatesemitalic /home/nik/.fonts/MathFonts/FourierGUT/fourier-alt-semiita.afm fourieralternatesemitalicsemibold fourieralternatesemitalic /home/nik/.fonts/MathFonts/FourierGUT/fourier-alt-semiita.afm *fouriermathblackboard fouriermathblackboard /home/nik/.fonts/MathFonts/FourierGUT/fourier-bb.afm fouriermathblackboardblack fouriermathblackboard /home/nik/.fonts/MathFonts/FourierGUT/fourier-bb.afm fouriermathcal fouriermathcal /home/nik/.fonts/MathFonts/FourierGUT/fourier-mcl.afm fouriermathcalnormalfouriermathcal /home/nik/.fonts/MathFonts/FourierGUT/fourier-mcl.afm fouriermathextensionfouriermathextension /home/nik/.fonts/MathFonts/FourierGUT/fourier-mex.afm fouriermathextensionmedium fouriermathextension /home/nik/.fonts/MathFonts/FourierGUT/fourier-mex.afm fouriermathletters fouriermathletters /home/nik/.fonts/MathFonts/FourierGUT/fourier-ml.afm fouriermathlettersbold fouriermathlettersbold /home/nik/.fonts/MathFonts/FourierGUT/fourier-mlb.afm fouriermathlettersbolditalicfouriermathlettersbolditalic /home/nik/.fonts/MathFonts/FourierGUT/fourier-mlitb.afm fouriermathlettersitalicfouriermathlettersitalic /home/nik/.fonts/MathFonts/FourierGUT/fourier-mlit.afm fouriermathlettersnormalfouriermathletters /home/nik/.fonts/MathFonts/FourierGUT/fourier-ml.afm fouriermathsymbols fouriermathsymbols /home/nik/.fonts/MathFonts/FourierGUT/fourier-ms.afm fouriermathsymbolsnormalfouriermathsymbols /home/nik/.fonts/MathFonts/FourierGUT/fourier-ms.afm* fourierorns fourierorns /home/nik/.fonts/MathFonts/FourierGUT/fourier-orns.afm fourierornsnormal fourierorns /home/nik/.fonts/MathFonts/FourierGUT/fourier-orns.afm Kind regards Nik On 10/28/2010 02:57 PM, Hans Hagen wrote: On 27-10-2010 3:49, nitralime wrote: I have made a mistake in my typescript. Here is the corrected version: %% .. \starttypescript [math] [fourier][texnansi] \definefontsynonym [Fourier-Math-Letters] [name:fouriermathletters] \definefontsynonym [Fourier-Math-Letters-Italic] [name:fouriermathlettersitalic] \definefontsynonym [Fourier-Math-Letters-Bold] [name:fouriermathlettersbold] \definefontsynonym [Fourier-Math-Letters-BoldItalic] [name:fouriermathlettersbolditalic] \definefontsynonym [Fourier-Math-Blackboard] [name:fouriermathblackboard] \definefontsynonym [Fourier-Math-Calligraphic] [name:fouriermathcal] \definefontsynonym [Fourier-Math-Symbols] [name:fouri
[NTG-context] interaction in included pdfs
Hi all,
what happened with the "experimental support for keeping links in included
pdfs"?
\setupinteraction[state=start]
\starttext
\externalfigure[cow.pdf][interaction=yes]
\stoptext
gives an error:
\@@su:epdf-overlay ...oodies("\@@efinteraction ")}
\reference [\figurereferen...
\executedefinedoverlay ...x {\the \everyoverlay #2
}}\setbox \scratchbox \hbo...
\dodobackgroundbox ...urrentbackground \endcsname
}}}\wd \extraframebox \zer...
\dododobackgroundbox ... \else \dodobackgroundbox
\expandafter \dododobackgr...
\dobackedbox ...box \framedbackground ,\s!unknown
,\relax \box \framebox \hs...
\stoplocalframed ...und \empty \else \dobackedbox
\fi \handleframedlocator \...
...
l.6 \stoptext
Greeting
Andreas
___
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] manipulate ttf-fonts loaded with luatex
On 28-10-2010 3:33, Khaled Hosny wrote: On Thu, Oct 28, 2010 at 03:08:09PM +0200, Taco Hoekwater wrote: On 10/28/2010 02:57 PM, Ulrike Fischer wrote: And when I have corrected the fontdata, is there a way (besides using a fea-file) to manipulate the fontdata so that the input "K" outputs the glyph "c140"? I have not followed this closely, bit it seems to me that the problem is more likely caused by a fea file than that it is cured by it. It seems like the font is using that multiple code points for the same glyph some thing of TrueType, I'm not sure, but I recall FF documentation recommending against using it. indeed there is some multiple mapping going on and as we're dealing with sparse tables and loops over a hash we get a bit arbitrary matches when there are multiple ... there is also some pretty high altuni field present if I look at the font in fontforge the chess symbols sit in latin slots so it's in the font if the font is okay, accessing by glyph name will work ok 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] manipulate ttf-fonts loaded with luatex
Am Thu, 28 Oct 2010 16:59:34 +0200 schrieb Hans Hagen: And when I have corrected the fontdata, is there a way (besides using a fea-file) to manipulate the fontdata so that the input "K" outputs the glyph "c140"? >>> >>> I have not followed this closely, bit it seems to me that the problem >>> is more likely caused by a fea file than that it is cured by it. >> >> It seems like the font is using that multiple code points for the same >> glyph some thing of TrueType, I'm not sure, but I recall FF >> documentation recommending against using it. > > indeed there is some multiple mapping going on and as we're dealing with > sparse tables and loops over a hash we get a bit arbitrary matches when > there are multiple ... > > there is also some pretty high altuni field present > > if I look at the font in fontforge the chess symbols sit in latin slots > so it's in the font Yes, I know that the font is a bit dubious. That's the case for quite a lot of the free chessfonts. The question I have: How can I correct the fontdata after I have loaded the font? -- Ulrike Fischer ___ 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] manipulate ttf-fonts loaded with luatex
On 10/28/2010 04:59 PM, Hans Hagen wrote:
if the font is okay, accessing by glyph name will work ok
The font is an 8-bit encoding-indexed Macintosh Roman font
presenting itself as TrueType, and that is why it is so
confusing.
Because the font says it is in MacRoman encoding, and the glyph
names are pointless affairs like /c140 (which is the king symbol)
instead of sane names, fontforge takes that the '140' part of
the name is a decimal code point in MacRoman encoding.
This is correct behavior on fontforge's part, but it means that
the Unicode remap becomes slightly messy, as /c140 maps to
'LATIN SMALL LETTER A WITH RING ABOVE'., and the glyph named
/c229 (which is in fact the aring symbol) maps to 'LATIN CAPITAL A
WITH CIRCUMFLEX', and /194 (which is the Acirc) maps to 'NOT SIGN',
etc. etc. In short: the font's glyph naming is anemic.
Now, it appears that luaotfload produces a rubbish .lua file, probably
because it dumps both the MacRoman and the Unicode assignment at the
same time as a merged table. That is a bug, but that is an issue for
the luaotfload maintainers, not something for the context mailing list.
In context itself, \char140 actually and correctly produces the king
symbol.
Incidentally, in context, you can get a dump of the actually used
unicode slots by running:
\starttext
\showfont[PIRAT.TTF][all] % grid table
\stoptext
or
\usemodule[fnt-10]
\starttext
\ShowCompleteFont{PIRAT.TTF}{12pt}{1} % number&names table
\stoptext
Now, about fixing it: I don't think there is much you can do with
a feature file in this case. If you want to make glyph (name) changes,
it is better to do so in the actual font file, because the fea file
will get hopelessly confusing. (and it will be specific to this
particular font file anyway), and more importantly: if you use a fea
file, you will keep hitting that luaotfload bug. So either clean up
the font yourself, or report a luaotfload bug and wait for it to be
fixed ...
Best wishes,
Taco
___
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] kerncharacters
Hi Wolfgang,
how can I get negative character kerning?
(\kerncharacters only seems to work with values <0)
\starttext
{\kerncharacters[0.02]include/inc-archive/materials/archive-material-newWind.asp?textPath=/documents/}
{include/inc-archive/materials/archive-material-newWind.asp?textPath=/documents/}
{\kerncharacters[-0.2]include/inc-archive/materials/archive-material-newWind.asp?textPath=/documents/}
\stoptext
Best regards,
Steffen
___
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] manipulate ttf-fonts loaded with luatex
On Thu, Oct 28, 2010 at 05:48:12PM +0200, Taco Hoekwater wrote: > On 10/28/2010 04:59 PM, Hans Hagen wrote: > > > >if the font is okay, accessing by glyph name will work ok > > The font is an 8-bit encoding-indexed Macintosh Roman font > presenting itself as TrueType, and that is why it is so > confusing. > > Because the font says it is in MacRoman encoding, and the glyph > names are pointless affairs like /c140 (which is the king symbol) > instead of sane names, fontforge takes that the '140' part of > the name is a decimal code point in MacRoman encoding. > > This is correct behavior on fontforge's part, but it means that > the Unicode remap becomes slightly messy, as /c140 maps to > 'LATIN SMALL LETTER A WITH RING ABOVE'., and the glyph named > /c229 (which is in fact the aring symbol) maps to 'LATIN CAPITAL A > WITH CIRCUMFLEX', and /194 (which is the Acirc) maps to 'NOT SIGN', > etc. etc. In short: the font's glyph naming is anemic. > > Now, it appears that luaotfload produces a rubbish .lua file, probably > because it dumps both the MacRoman and the Unicode assignment at the > same time as a merged table. That is a bug, but that is an issue for > the luaotfload maintainers, not something for the context mailing list. As one of the luaotfload maintainers, I assure you that we never touch such low level code :) at least to stay compatible with ConTeXt (I really really have no interest in two incompatible OpenType implementations, so in regard to that luaotfload is not a real fork but ConTeXt code wrapped in some LaTeX palatable sweetener). > In context itself, \char140 actually and correctly produces the king > symbol. This either means it was fixed in later version of ConTeXt (our code is derived from the texlive version), or the ConTeXt variant is doing more stuff than what the plain one does. Regards, Khaled -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer ___ 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] manipulate ttf-fonts loaded with luatex
On 28-10-2010 5:37, Ulrike Fischer wrote: The question I have: How can I correct the fontdata after I have loaded the font? in context it is possible to 'patch' a font before it gets cached but that's just a hack; in luaotf I can imagine that you intercept the font just before it gets passed to tex, but anyway, it's asking for problems with respect to future proof processing 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] manipulate ttf-fonts loaded with luatex
On 28-10-2010 5:59, Khaled Hosny wrote: As one of the luaotfload maintainers, I assure you that we never touch such low level code :) at least to stay compatible with ConTeXt (I really really have no interest in two incompatible OpenType implementations, so in regard to that luaotfload is not a real fork but ConTeXt code wrapped in some LaTeX palatable sweetener). in that case it's fontforge that merges the two vectors (technically we can have one glyph name representing two unicode points) using the /C logic that taco mentions; the best solution is to have sane glyph names This either means it was fixed in later version of ConTeXt (our code is derived from the texlive version), or the ConTeXt variant is doing more stuff than what the plain one does. it also relates to looping over the sparse tables ... sort of arbitrary what comes first but, as taco mentions, \char140 does give a king here; doesn't it in latex? - 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] manipulate ttf-fonts loaded with luatex
On 28-10-2010 5:59, Khaled Hosny wrote: This either means it was fixed in later version of ConTeXt (our code is derived from the texlive version), or the ConTeXt variant is doing more stuff than what the plain one does. probably the only way out of this font mess is to have extra hash table (could be a feature like : namehash=yes) although it obscures the fact that there is a problem in the font which a few years from now makes debugging user problems a pain as no one is going to remember 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 ___
Re: [NTG-context] manipulate ttf-fonts loaded with luatex
Am Thu, 28 Oct 2010 17:48:12 +0200 schrieb Taco Hoekwater:
> Now, it appears that luaotfload produces a rubbish .lua file, probably
> because it dumps both the MacRoman and the Unicode assignment at the
> same time as a merged table. That is a bug, but that is an issue for
> the luaotfload maintainers, not something for the context mailing list.
>
> In context itself, \char140 actually and correctly produces the king
> symbol.
Well miktex has again a working context.
ConTeXt ver: 2010.05.24 13:05 MKIV fmt: 2010.10.28 int:
english/english
So I tried the following example (I had to copy the font in document
folder, context didn't find it in the system folder):
\starttext
hello
\font\test={file:PIRAT.TTF}
\test
\char140 \directlua{fonts.otf.char("c140")}
\stoptext
This example gave exactly the same output as the comparable latex
example with luaotfload: \char140 gives the king, the
\directlua-command gives the aring.
I also compared the font files generated by both systems:
temp-pirat.lua from luaotfload and pirat.tma from context. Both are
nearly identical. They differ only in some boundingbox settings,
versions and a kern setting. Both contain in the unicodes table the
settingc140={ 229, 140 }.
I changed this setting in pirat.tma to c140=140 and deletec
pirat.tmc and recompiled my document: Now
\directlua{fonts.otf.char("c140")} gave as wanted the king.
So please tell me how can I make the change in my document. What
code should I insert here:
\starttext
\font\test={file:PIRAT.TTF}
\test
\char140 \directlua{fonts.otf.char("c140")}
\stoptext
--
Ulrike Fischer
___
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] manipulate ttf-fonts loaded with luatex
Ulrike Fischer wrote: This example gave exactly the same output as the comparable latex example with luaotfload: \char140 gives the king, the \directlua-command gives the aring. My apologies to Khaled Hosny, I was wrong. It is still a bug though, that '140' has no business being in the unicodes table. Hans and I will do some further debugging. Best wishes, Taco ___ 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] letter module, backaddress placement
Dear Wolfgang,
the default vertical placement of the backaddress is to high in dinb.nls.
When I change the offset from
\c!voffset=\dimexpr\letterstylevalue{\v!address\v!layer}\c!voffset-\letterstylevalue{\v!backaddress\v!frame}\c!height\relax]
to
\c!voffset=\dimexpr\letterstylevalue{\v!address\v!layer}\c!voffset+\letterstylevalue{\v!backaddress\v!frame}\c!height\relax]
(addition instead of subtraction) everything is fine.
Best wishes,
Florian
___
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] manipulate ttf-fonts loaded with luatex
Am Thu, 28 Oct 2010 18:01:07 +0200 schrieb Hans Hagen: >> The question I have: How can I correct the fontdata after I have >> loaded the font? > > in context it is possible to 'patch' a font before it gets cached but > that's just a hack; in luaotf I can imagine that you intercept the font > just before it gets passed to tex, but anyway, it's asking for problems > with respect to future proof processing Well I don't want to patch the font system. But why can't I change the font data after the \font\test=... line? Is the data somewhere in the memory where it can't be touched? If yes is it possible to copy the data, change it and then use the changed data to define a new font \testb? -- Ulrike Fischer ___ 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] manipulate ttf-fonts loaded with luatex
On 28-10-2010 7:08, Ulrike Fischer wrote: Am Thu, 28 Oct 2010 18:01:07 +0200 schrieb Hans Hagen: The question I have: How can I correct the fontdata after I have loaded the font? in context it is possible to 'patch' a font before it gets cached but that's just a hack; in luaotf I can imagine that you intercept the font just before it gets passed to tex, but anyway, it's asking for problems with respect to future proof processing Well I don't want to patch the font system. But why can't I change the font data after the \font\test=... line? Is the data somewhere in the memory where it can't be touched? If yes is it possible to copy the data, change it and then use the changed data to define a new font \testb? as direct manipulation at that level is doomed to fail in the future (nothing is written in stone till we have luatex 1.0) the best I can think of is to provide a function that does the job i.e. stupify the mapping, something fonts.otf.simplifynamemapping or so, or better provide that as feature so that one can enable it; really this is the only robust way 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] manipulate ttf-fonts loaded with luatex
Am Thu, 28 Oct 2010 19:17:19 +0200 schrieb Hans Hagen: The question I have: How can I correct the fontdata after I have loaded the font? >>> >>> in context it is possible to 'patch' a font before it gets cached but >>> that's just a hack; in luaotf I can imagine that you intercept the font >>> just before it gets passed to tex, but anyway, it's asking for problems >>> with respect to future proof processing >> >> Well I don't want to patch the font system. But why can't I change >> the font data after the \font\test=... line? Is the data somewhere >> in the memory where it can't be touched? If yes is it possible to >> copy the data, change it and then use the changed data to define a >> new font \testb? > > as direct manipulation at that level is doomed to fail in the future > (nothing is written in stone till we have luatex 1.0) the best I can > think of is to provide a function that does the job Hm. I do have a bit the impression as if we have here a context and latex philosophy clash. I'm not asking you to provide a funktion incorporated in the context code which does the job. _I_ want to write support files for the chess ttf-fonts. If I get something working I will perhaps add it to my package. And if something changes in luatex or the underlying luaotfload/context code, well then I will have to adjust my code. Couldn't you give some examples how to manipulate a font after it has been defined with \font\test (if it is possible) and then let me play around? -- Ulrike Fischer ___ 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] manipulate ttf-fonts loaded with luatex
On 28-10-2010 7:48, Ulrike Fischer wrote:
Hm. I do have a bit the impression as if we have here a context and
latex philosophy clash. I'm not asking you to provide a funktion
Huh? I'm not sure what philosophy refers to, as I'm not refering to
context but to the otf loading code; so it would be a function in the
lua code base (it would not even be interfaced to context as it would
invalidate most of the characters in a font).
incorporated in the context code which does the job. _I_ want to
write support files for the chess ttf-fonts. If I get something
working I will perhaps add it to my package. And if something
changes in luatex or the underlying luaotfload/context code, well
then I will have to adjust my code.
Sure, but the first complaints would end up in khaleds, tacos or my
mailbox unless your package is private and never ends up in tex
distributions). The fact that it's custom in latex to overload code and
thus create a maintaince depency does not mean that I want such a
dependency on my code. The context philosophy is to provide hooks and
ignore all compliants about other usage cq. don't care about usage of
code that is not meant to be accesses directly. (Also, Khaled then
provides the interface to the latex packages.)
Couldn't you give some examples how to manipulate a font after it
has been defined with \font\test (if it is possible) and then let me
play around?
I have no clue about the lualatex interface i.e. at what point you can
hook in code. Keep in mind that messing around with a font before or
during loading can influence other instances of that font as some data
is shared. Also, once the font lives at the tex end, some data is
frozen. Because some of the font's metadata is used in otf processing
one cannot change that data without keeping that in mind.
Anyhow, you can access some font data afterwards. In context form:
\startluacode
function Whatever(name)
for k, v in pairs(fonts.ids[font.current()].descriptions) do
if v.name == name then
tex.sprint("\\char"..k.."\\relax")
break
end
end
end
\stopluacode
\font\test=file:pirat.ttf
\def\MyChessChar#1{{\test\directlua{Whatever("#1")}}}
\MyChessChar{c160}
This is dead slow and inefficient but as you don't want a proper
function for it I don't care too much. Interesting is that it does not
work out (as wis to be expected as the normal glyph access function does
something similar).
Btw, a bit of testing at my end shows that there is something fishy with
the font with respect to inclusion in the pdf so it can well be that the
accessor is ok and something else is the problem.
As taco mentioned in an earlier mail, we will look into it (even it
makes not much sense).
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] letter module, backaddress placement
Am 28.10.2010 um 19:04 schrieb Florian Wobbe: > Dear Wolfgang, > > the default vertical placement of the backaddress is to high in dinb.nls. The position of the backaddress os correct but i think you don’t like the large gap between the backaddress and the address. The gap is there because it’s specified in the german din layout where the address field has nine lines with the first three lines reserved for dispatch information, a easy way to get rid of this space is to disable the dispatch field with \setupletterstyle[dispatch=no] 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] manipulate ttf-fonts loaded with luatex
Hi Khaled, In a next version of the oft code I do a bit more strict encoding test; not that it matters much but we need to keen an eye on fonts that have multiple code points mapped onto the same glyph. It does not solve the chess problem (something taco and I will look into tomorrow). 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] manipulate ttf-fonts loaded with luatex
On Thu, Oct 28, 2010 at 09:35:08PM +0200, Hans Hagen wrote: > Hi Khaled, > > In a next version of the oft code I do a bit more strict encoding > test; not that it matters much but we need to keen an eye on fonts > that have multiple code points mapped onto the same glyph. I'm syncing luaotfload with latest context code and many of my tests are broken, I think I'll wait for the next update to do another sync before debugging (for some reason node mode ceased to work). Regards, Khaled -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer ___ 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] manipulate ttf-fonts loaded with luatex
On Thu, Oct 28, 2010 at 07:03:14PM +0200, taco wrote: > Ulrike Fischer wrote: > > > >This example gave exactly the same output as the comparable latex > >example with luaotfload: \char140 gives the king, the > >\directlua-command gives the aring. > > My apologies to Khaled Hosny, I was wrong. No need for apology (if it were my fault life would have been easier, now I have to sync with context which is tricky since lots of things changed since my last sync). Regards, Khaled -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer ___ 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] letter module, backaddress placement
On Oct 28, 2010, at 21:11 , Wolfgang Schuster wrote: > > Am 28.10.2010 um 19:04 schrieb Florian Wobbe: > >> Dear Wolfgang, >> >> the default vertical placement of the backaddress is to high in dinb.nls. > > The position of the backaddress os correct but i think you don’t like the > large gap between the backaddress and the address. The gap is there because > it’s specified in the german din layout where the address field has nine > lines with the first three lines reserved for dispatch information, a easy > way to get rid of this space is to disable the dispatch field with > > \setupletterstyle[dispatch=no] Nice to know! Actually it was not the gap that bothered me. You are right, DIN 676 B says 45mm. But this seems to be useless as all window envelopes (that I possess) have their window at 50mm. It defeats the purpose of the backaddress field, which is hidden by the DIN layout. Shouldn't they be able to read it in the Post office in case the addressee is wrong? Puzzled, Florian ___ 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] manipulate ttf-fonts loaded with luatex
On 28-10-2010 9:46, Khaled Hosny wrote: On Thu, Oct 28, 2010 at 09:35:08PM +0200, Hans Hagen wrote: Hi Khaled, In a next version of the oft code I do a bit more strict encoding test; not that it matters much but we need to keen an eye on fonts that have multiple code points mapped onto the same glyph. I'm syncing luaotfload with latest context code and many of my tests are broken, I think I'll wait for the next update to do another sync before debugging (for some reason node mode ceased to work). I'm in the process of cleaning up some code so that could interfere with your end, although I didn't change much in that code, normally I keep an eye on the generic code. 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] interaction in included pdfs
On 28-10-2010 4:43, Andreas Harder wrote: Hi all, what happened with the "experimental support for keeping links in included pdfs"? \setupinteraction[state=start] \starttext \externalfigure[cow.pdf][interaction=yes] \stoptext fixed in next beta (I needed to catch a border case) 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] Scaling of setminus in xits
Hi, \setminus does not scale properly in xits. I am not sure if it is a bug in the font or in ConTeXt. \setupbodyfont[xits] \starttext $A \setminus B$ \stoptext 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] Footnotes in MkIV and MkII
Hullo, from what I can understand I'm using \footnote correctly (i.e. as on wiki), but if I generate the document with 'context' every footnote instance is just a direct copy of the first footnote. If I generate it with 'texexec' though, the footnotes are generated as expected. Is that a MkIV bug, feature or just me being stupid? Cheers, Matija -- gsm:+386 41 849 552 www:http://matija.suklje.name xmpp: matija.suk...@gabbler.org 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] Scaling of setminus in xits
On Thu, Oct 28, 2010 at 06:12:10PM -0400, Aditya Mahajan wrote: > Hi, > > \setminus does not scale properly in xits. I am not sure if it is a > bug in the font or in ConTeXt. > > \setupbodyfont[xits] > \starttext > $A \setminus B$ > \stoptext I don't have larger variants of that glyph, so it is not set to scale. If you can find larger glyphs in STIX, I'll use that, but right now all those slash/backslash-like glyphs confuse me (and STIX seems to have wired shapes compared to similar glyphs in other fonts). Regards, Khaled -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer ___ 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] Footnotes in MkIV and MkII
On 29-10-2010 12:17, Matija Šuklje wrote: Hullo, from what I can understand I'm using \footnote correctly (i.e. as on wiki), but if I generate the document with 'context' every footnote instance is just a direct copy of the first footnote. If I generate it with 'texexec' though, the footnotes are generated as expected. Is that a MkIV bug, feature or just me being stupid? sounds like a but or maybe a side effect of how you use the footnote; in mkiv footnotes are stored differently (and can actually be accessed in many ways) .. so a small test file is needed that shows the problem - 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] Footnotes in MkIV and MkII
Dne petek 29. oktobra 2010 ob 00:42:20 je Hans Hagen napisal(a):
> On 29-10-2010 12:17, Matija Šuklje wrote:
> > Hullo,
> >
> > from what I can understand I'm using \footnote correctly (i.e. as on
> > wiki), but if I generate the document with 'context' every footnote
> > instance is just a direct copy of the first footnote.
> >
> > If I generate it with 'texexec' though, the footnotes are generated as
> > expected.
> >
> > Is that a MkIV bug, feature or just me being stupid?
>
> sounds like a but or maybe a side effect of how you use the footnote; in
> mkiv footnotes are stored differently (and can actually be accessed in
> many ways) .. so a small test file is needed that shows the problem
\starttext
Something something\footnote{dark side}
Something something\footnote{complete}
\stoptext
Something as simple as that already triggers it in my case.
I'm using minimals from 2010.06.18 11:26.
Cheers,
Matija
--
gsm:+386 41 849 552
www:http://matija.suklje.name
xmpp: matija.suk...@gabbler.org
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] Scaling of setminus in xits
On Fri, 29 Oct 2010, Khaled Hosny wrote: On Thu, Oct 28, 2010 at 06:12:10PM -0400, Aditya Mahajan wrote: Hi, \setminus does not scale properly in xits. I am not sure if it is a bug in the font or in ConTeXt. \setupbodyfont[xits] \starttext $A \setminus B$ \stoptext I don't have larger variants of that glyph, so it is not set to scale. If you can find larger glyphs in STIX, I'll use that, but right now all those slash/backslash-like glyphs confuse me (and STIX seems to have wired shapes compared to similar glyphs in other fonts). It should not scale, but the default size is too small. Compare the size of \setminus in xtis from that in cambria or even LM. Just going by the glyph table at stix site, set minus should correspond to glyph 3991 in STIXGeneral.otf. I do not know how to view that glyph, so do not know if xtis uses the right glyph or not. 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] Scaling of setminus in xits
On Thu, Oct 28, 2010 at 07:09:45PM -0400, Aditya Mahajan wrote: > On Fri, 29 Oct 2010, Khaled Hosny wrote: > > >On Thu, Oct 28, 2010 at 06:12:10PM -0400, Aditya Mahajan wrote: > >>Hi, > >> > >>\setminus does not scale properly in xits. I am not sure if it is a > >>bug in the font or in ConTeXt. > >> > >>\setupbodyfont[xits] > >>\starttext > >>$A \setminus B$ > >>\stoptext > > > >I don't have larger variants of that glyph, so it is not set to scale. > >If you can find larger glyphs in STIX, I'll use that, but right now all > >those slash/backslash-like glyphs confuse me (and STIX seems to have > >wired shapes compared to similar glyphs in other fonts). > > It should not scale, but the default size is too small. Compare the > size of \setminus in xtis from that in cambria or even LM. Yes, that what I meant by wired shapes (the slants are sometimes different from similar slashes in other fonts). > Just > going by the glyph table at stix site, set minus should correspond > to glyph 3991 in STIXGeneral.otf. I do not know how to view that > glyph, so do not know if xtis uses the right glyph or not. If you search for 02216 glyph, you will see there is a variant glyph in STIXVar.otf, if you think that variant should be the default I can do that and make the current one available as an optional glyph variant (I think I should check the rest of the STIXVar.otf font too, it was on my todo for a while now). Regards, Khaled -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer ___ 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] Scaling of setminus in xits
On Fri, 29 Oct 2010, Khaled Hosny wrote:
Just
going by the glyph table at stix site, set minus should correspond
to glyph 3991 in STIXGeneral.otf. I do not know how to view that
glyph, so do not know if xtis uses the right glyph or not.
If you search for 02216 glyph, you will see there is a variant glyph in
STIXVar.otf, if you think that variant should be the default I can do
that and make the current one available as an optional glyph variant (I
think I should check the rest of the STIXVar.otf font too, it was on my
todo for a while now).
Dumb question, but how do I check a specific glyph in a font. I tried
\getglyph{STIXGeneral.otf}{\char2216}
and
\font\STIX=STIXGeneral.otf
\STIX \char2216
but both of them give a blank character.
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] wrong link with url + footnote
On Thu, Oct 28 2010, Hans Hagen wrote:
> >\setupinteraction[state=start]
> >\starttext
> >\hyphenatedurl{www.test.com}\footnote{a footnote}
> >Problem: the link is \quote{www.test.com1}.
> >\stoptext
>
> \goto{wherever}[url(www.test.com)]\footnote{a footnote}
Now I understand: it's not ConTeXt that creates the wrong link, but Acroread!
Cheers, Peter
--
Contact information: http://pmrb.free.fr/contact/
___
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] sorttype for bibtex
Hi, IIUC, the bib module manual says that \setuppublications[sorttype=bbl] will print the publications in the order in which they appear in the bbl file. However, one needs \setupbibtex[sorttype=bbl] \setuppublications[sorttype=bbl] to get that behavior (took forever to debug). Minimal example: \setupbibtex[sorttype=bbl] \setuppublications[sorttype=bbl] \unprotect \show\@@pbsorttype \protect %\tracingall \starttext \unprotect \show\@@pbsorttype \protect \stoptext (Try commenting on the of the \setup lines) 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 ___
