On 10/2/2018 1:39 PM, Ulrike Fischer wrote:
Am Tue, 2 Oct 2018 11:29:46 +0200 schrieb Hans Hagen:
Can't you check for a free range instead?
sure, but then i also loose some functionality in context (unless i gho
for ugly solutions) ... as all glyphs are supposed to have a name access
by
Am Tue, 2 Oct 2018 11:29:46 +0200 schrieb Hans Hagen:
>> Can't you check for a free range instead?
> sure, but then i also loose some functionality in context (unless i gho
> for ugly solutions) ... as all glyphs are supposed to have a name access
> by name is a pretty good alternative
Well
On 10/2/2018 9:29 AM, Ulrike Fischer wrote:
Am Tue, 2 Oct 2018 06:55:02 +0200 schrieb luigi scarso:
For what do you reserve the space in the PUA?
http://www.pragma-ade.nl/general/manuals/fonts-mkiv.pdf
page 32 of the document :
As we already mentioned in a previous chapter, in ConTeXt
On 10/1/2018 11:11 PM, David Carlisle wrote:
If you need to allocate a block for internal use wouldn't it be possible
to use one of the high areas Supplementary Private Use Area-A or B
(U+F - U+F) (U+10 - U+10) ?
The BMP PUA block (U+E000 U+F8FF) just has so many documented
Am Tue, 2 Oct 2018 06:55:02 +0200 schrieb luigi scarso:
>> For what do you reserve the space in the PUA?
> http://www.pragma-ade.nl/general/manuals/fonts-mkiv.pdf
> page 32 of the document :
> As we already mentioned in a previous chapter, in ConTeXt we use
> Unicode internally. This also
On Mon, Oct 1, 2018 at 7:56 PM Ulrike Fischer wrote:
>
> For what do you reserve the space in the PUA?
>
http://www.pragma-ade.nl/general/manuals/fonts-mkiv.pdf
page 32 of the document :
As we already mentioned in a previous chapter, in ConTeXt we use Unicode
internally.
This also means that
On 10/1/2018 7:55 PM, Ulrike Fischer wrote:
Am Mon, 1 Oct 2018 19:29:40 +0200 schrieb Hans Hagen:
\DeclareTextGlyphY{LinBiolinum_K}{uniE18C}{57740}
A funny definition ... is that access by name or number?
By number, it uses \char at the end to get the glyph.
Anyway, for generic (so not
Am Mon, 1 Oct 2018 19:29:40 +0200 schrieb Hans Hagen:
>> \DeclareTextGlyphY{LinBiolinum_K}{uniE18C}{57740}
>A funny definition ... is that access by name or number?
By number, it uses \char at the end to get the glyph.
> Anyway, for generic (so not for context) I can keep these glyphs in the
On 10/1/2018 11:42 AM, Ulrike Fischer wrote:
Can you tell me when this change happend? Perhaps I can build an
older fontloader as a fall back.
no, probably a while ago when some other clash in private area use was
solved .. i'm not going to mess with the code now as 0xE000-0xEFFF is
used
On Mon, Oct 1, 2018 at 11:43 AM Ulrike Fischer wrote:
>
> I just got from Claudio Beccari (which seem to have complained to
> Luigi)
>
hm, not a complain, a simple "bug report". I always try to answer directly
to Claudio when/if I can,
but in this case, if I have understood correctly, you are
Am Mon, 1 Oct 2018 10:20:07 +0200 schrieb Hans Hagen:
> anyway, the problem, with these private areas is that they are also used
> by the loader (and context) so in order to avoid clashes we move all
> private chars in the font to a dedicated private range
This basically means that for every
On 9/30/2018 10:08 PM, Ulrike Fischer wrote:
The font Coelacanth (on CTAN) has glyphs in the private area.
Between 2/2017 (luaotfload in texlive 2017) and now the storing and
accessing of this glyphs has changed.
In the lua of the font of 2017 I find e.g.
[62860]={
12 matches
Mail list logo
