Re: [NTG-context] follow up

2019-04-03 Thread Hans Hagen

On 4/3/2019 7:58 AM, Christoph Reller wrote:

My two cents:

I don't believe that it is the CIDSet. Both fun.pdf and fun1.pdf have no 
CIDSet (which is good).

The (relevant) differences between the two PDFs are:
- Different ToUnicode
- Different embedded font stream
- Minor differences in the font descriptor
It could be the ToUnicode: If preview is not able to parse the last 
entry in the ToUnicode table then it may also drop this glyph in its 
display, although ToUnicode is only relevant for text extraction.


indeed and only very few viewers do that right

It could be the font stream: In the CFF font file there is a CharSet 
table that maps character-IDs to glyph-IDs. If preview cannot read the 
last entry in this table (or the last glyph, glyph nr. 10) then it might 
drop it.


coul dbe but acrobat is very picky on that as is ghostscript and they work

By bet is on the ToUnicode, because, usually, if viewers fail to read a 
font file then they drop the entire font file and not single glyphs.


hm, but i don't think it's different from non lmtx .. i need to check it

Anyway, both PDFs seem to be valid. But I wonder if the differences in 
the font descriptor are legitimate (especially StemV):
Object 9 <-> 7: Different entry Ascent integer value: 1127 <-> 806 in 
font descriptor dictionary.
Object 9 <-> 7: Different entry Descent integer value: -280 <-> -194 in 
font descriptor dictionary.
Object 9 <-> 7: Different entry StemV integer value: 91 <-> 0 in font 
descriptor dictionary.


yes, but most of these are bogus and heuristically derived (could be the 
subset or whole font) and quite certainly not used in rendering 
(positioning happens at the pdf level)


we'll see what magic taco has embrained ... he knows apple pdf handling 
in detail so ...



Cheers,
Christoph

On Tue, Apr 2, 2019 at 10:16 PM Hans Hagen > wrote:


On 4/2/2019 8:38 PM, Taco Hoekwater wrote:
 >
 >
 >> On 2 Apr 2019, at 17:11, Hans Hagen mailto:j.ha...@xs4all.nl>> wrote:
 >>
 >> On 4/2/2019 4:18 PM, Ulrike Fischer wrote:
 >>> Am Tue, 2 Apr 2019 15:58:18 +0200 schrieb Floris van Manen:
 > indeed on preview no x shows up but it does in other viewers
 >
 
  Not just the x.
  In the second example the s will disappear, be shows up if you
add some extra digits, and then dropping the 2
 >>> I don't have a mac and can't reproduce the problem. But the missing
 >>> char seems to be always the last one in the beginbfchar/endbfchar
 >>> list.
  The OSX preview is flaky but i’d assume the output of both
context version would be similar (enough)
 >>> The new context adds new lines inside the beginbfchar/endbfchar
 >>> block. Perhaps this confuses preview and it drops the last entry.
 >> it is indeed the last one that is the issue but changing spacing
or adding dummies doesn't help
 >
 > More likely the problem it has is due to the omitted /CIDSet in
the font descriptor.
 >
 > The error is in the display engine, not the text extractor (since
cut work ok).
 > And that means the problem is almost certainly not the cmap. The
only other non-trivial
 > difference I saw in the old vs. new pdf was that no longer
present /CIDSet.
 >
 > Unf., generating one in the text editor is bit beyond
me-on-the-could mode, so I can
 > not be certain of that although it seems likely (I checked with
FF that the two glyphs
 > are indeed in the embedded font subset and in the exact slots the
pdf says they have, so
 > that is also unlikely to be the problem.)
ok, i'll check that tomorrow ... (cidsets are actually obsolete)

Hans

-
                                            Hans Hagen | PRAGMA ADE
                Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
         tel: 038 477 53 69 | www.pragma-ade.nl
 | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
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  : 

Re: [NTG-context] index "compress" option / collapsing of page numbers

2019-04-03 Thread Henning Hraban Ramm
Am 2019-04-02 um 18:53 schrieb Hans Hagen :

> On 4/2/2019 11:54 AM, Henning Hraban Ramm wrote:
>> Ahoi,
>> with \setupregister[compress=yes], index entries 1,2,3,4 become 1–4. That’s 
>> great.
>> But (at least in German publications) it’s usual that 1,2 becomes 1f. and 
>> 1,2,3 becomes 1ff.
>> Is it possible to configure it that way?
> it should not be too hard to program but, it being german problem:
> 
> - you have to come up with an example
> - wolfgang has to come up with a proper keyword (compress=?)
> 

Thank you – it’s not only a German habit, even if we pronounce it “folgende”, 
“f.” stems from Latin “folio”, and “ff.” is a duplicated abbreviation, as was 
usual in mediaeval Latin.
So, this is at least used in English, German, Norwegian and Swedish, as far as 
I could find. In French they seem to use “sq.” and “sqq.” (sequens).

https://de.wiktionary.org/wiki/ff.
https://en.wiktionary.org/wiki/ff.
https://fr.wiktionary.org/wiki/sq.

I suggest the following setup options:

compress = no  —> don’t collapse (as now)
compress = yes —> always use – (as now)

compresssymbols={\,f.,\,ff.} (or how can you setup a list?)
compress = symbols —> use first symbol for one other page, second for more pages
if there’s only one symbol, more than one sequential page should use – 
(like “yes”)

Is this feasible?

As far as I see, we need this only for index entries, i.e. \setupregister, 
since there’s no command like \at for more than one page anyway; or is there a 
need to collapse pages in bibliographies?


Test case:


\usemodule[visual]
\setuppapersize[A6]

\setupregister[index][
  compress=yes,
  %compresssymbols={\,f.,\,ff.},
  %compress=symbols,
]

\starttext
\placeindex\index{nonsense}
\page

\strut\index{something}\page
\strut\index{something}\page

\dorecurse{7}{
\fakewords{10}{100}\index{something}\par
\fakewords{20}{200}\index{other}\par
\fakewords{10}{100}\index{something}\par
}
\index{finis} % not flushed?

\stoptext



Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD

___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] Announcing Season of Docs 2019

2019-04-03 Thread Henning Hraban Ramm
Am 2019-04-02 um 22:47 schrieb Mojca Miklavec :

> Hi,
> 
> This is just to let you know that Google started accepting applications for 
> organisations that want to participate in "Google season of docs", offering 
> stipends to technical writers to work full time on improving documentation of 
> open source projects.
> 
> See also a list of sample ideas:
> https://developers.google.com/season-of-docs/docs/project-ideas
> (but maybe some improvement of the writing tools could also count, I don't 
> know).
> 
> Participation is not limited to students this time.
> 
> Is any of the TeX user groups interested in participating?

Would it make sense to make the ongoing ConTeXt book projects (Alan’s, mine, 
other?) "season of docs" projects?

I’d love to get a mentor. Even better if there’s money involved. ;)

Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD

___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] index "compress" option / collapsing of page numbers

2019-04-03 Thread Herbert Voss



Am 03.04.19 um 11:41 schrieb Thomas A. Schmitz:




On 3. Apr 2019, at 10:56, Henning Hraban Ramm  wrote:

Thank you – it’s not only a German habit, even if we pronounce it “folgende”, 
“f.” stems from Latin “folio”, and “ff.” is a duplicated abbreviation, as was 
usual in mediaeval Latin.
So, this is at least used in English, German, Norwegian and Swedish, as far as 
I could find. In French they seem to use “sq.” and “sqq.” (sequens).


I’m not sure the abbreviation for “folio” has anything to do with our German 
“folgende”; if you have a link for this, I would like to know. And for the 
record: “ff.” for page ranges is now discouraged in most scholarly 
publications; journals and publishers now say f. for x - x+1, or exact page 
numbers.


it has nothing do do with "folgende", but it is often used because it 
means nearly the same.



folium = {
  de = {”f”, ”ff”},
  en = {”f”, ”ff”},
  fr = {”\,sq”,”\,sqq”},
  jp = {”シンボル”,”番号”},
}

Herbert
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] index "compress" option / collapsing of page numbers

2019-04-03 Thread Ulrike Fischer
Am Wed, 3 Apr 2019 10:56:21 +0200 schrieb Henning Hraban Ramm:

>  or is there a need to collapse pages in bibliographies?

there can be such page ranges with ff both in the bibliography and
the citation. But normally you input them hard coded as you know it
in advance (in biblatex as 1\psq or 1\psqq). 
But biblatex has options to recreate them on-the-fly for backref
lists in the bib (and could use the code in more places if needed). 
 
-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/

___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] index "compress" option / collapsing of page numbers

2019-04-03 Thread Thomas A. Schmitz


> On 3. Apr 2019, at 10:56, Henning Hraban Ramm  wrote:
> 
> Thank you – it’s not only a German habit, even if we pronounce it “folgende”, 
> “f.” stems from Latin “folio”, and “ff.” is a duplicated abbreviation, as was 
> usual in mediaeval Latin.
> So, this is at least used in English, German, Norwegian and Swedish, as far 
> as I could find. In French they seem to use “sq.” and “sqq.” (sequens).

I’m not sure the abbreviation for “folio” has anything to do with our German 
“folgende”; if you have a link for this, I would like to know. And for the 
record: “ff.” for page ranges is now discouraged in most scholarly 
publications; journals and publishers now say f. for x - x+1, or exact page 
numbers.

Thomas
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] Luametatex

2019-04-03 Thread Hans Hagen

On 4/3/2019 12:06 PM, Dmitry Starostin wrote:
To sum up problems of setting up after installing context-lmtx (context 
mkiv on my machine is gone, so these are quite pressing questions):


how gone ... all can live alongside


Some were addressed, but I cannot resolve them

1. luametatex: works as intended from within TexShop, but 'command not 
found' from terminal $CONTEXTHOME/tex/texmf-osx-64/bin/even after 
chmod 755.


What to source?


is there a

luametatex
mtxrun -> luametatex
context -> luametatex


2. ./luametatex 'no format given'


indeed, when called directly without any argument


3. there used to be context --run, now there isn't.

there should be a binary or link to binary

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] index "compress" option / collapsing of page numbers

2019-04-03 Thread Hans Hagen

On 4/3/2019 10:56 AM, Henning Hraban Ramm wrote:

Am 2019-04-02 um 18:53 schrieb Hans Hagen :


On 4/2/2019 11:54 AM, Henning Hraban Ramm wrote:

Ahoi,
with \setupregister[compress=yes], index entries 1,2,3,4 become 1–4. That’s 
great.
But (at least in German publications) it’s usual that 1,2 becomes 1f. and 1,2,3 
becomes 1ff.
Is it possible to configure it that way?

it should not be too hard to program but, it being german problem:

- you have to come up with an example
- wolfgang has to come up with a proper keyword (compress=?)



Thank you – it’s not only a German habit, even if we pronounce it “folgende”, 
“f.” stems from Latin “folio”, and “ff.” is a duplicated abbreviation, as was 
usual in mediaeval Latin.
So, this is at least used in English, German, Norwegian and Swedish, as far as 
I could find. In French they seem to use “sq.” and “sqq.” (sequens).

https://de.wiktionary.org/wiki/ff.
https://en.wiktionary.org/wiki/ff.
https://fr.wiktionary.org/wiki/sq.

I suggest the following setup options:

compress = no  —> don’t collapse (as now)
compress = yes —> always use – (as now)

compresssymbols={\,f.,\,ff.} (or how can you setup a list?)
compress = symbols —> use first symbol for one other page, second for more pages
if there’s only one symbol, more than one sequential page should use – 
(like “yes”)

Is this feasible?


i'll add

\setuplabeltext % predefined
  [en]
  [following:singular=f.,
   following:plural=ff.]

\setupregister[index][compress=text]

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] Luametatex

2019-04-03 Thread Dmitry Starostin
To sum up problems of setting up after installing context-lmtx (context
mkiv on my machine is gone, so these are quite pressing questions):

Some were addressed, but I cannot resolve them

1. luametatex: works as intended from within TexShop, but 'command not
found' from terminal $CONTEXTHOME/tex/texmf-osx-64/bin/even after
chmod 755.

What to source?

2. ./luametatex 'no format given'

3. there used to be context --run, now there isn't.
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] Announcing Season of Docs 2019

2019-04-03 Thread juh
Am Wed, Apr 03, 2019 at 11:17:22AM +0200 schrieb Henning Hraban Ramm:
 > 
> > Is any of the TeX user groups interested in participating?
> 
> Would it make sense to make the ongoing ConTeXt book projects (Alan’s, mine, 
> other?) "season of docs" projects?
> 
> I’d love to get a mentor. Even better if there’s money involved. ;)

I would be happy to see these projects funded, but I am not sure whether a book
is open enough. AFAIK Google is addressing open source communities.

But why not try to get it?

juh

-- 
Autoren-Homepage: . http://literatur.hasecke.com
Satiren & Essays: . http://www.sudelbuch.de
Privater Blog:  http://www.hasecke.eu
Netzliteratur-Projekt:  http://www.generationenprojekt.de




signature.asc
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] optional hyphenation patterns in ancient Greek

2019-04-03 Thread Arthur Reutenauer
Pablo,

On Sun, Mar 31, 2019 at 10:55:18PM +0200, Pablo Rodriguez wrote:
> Since this isn’t about myself or my documents, I guess it is worth to
> provide the optional hyphenation set to all TeX users, not only the ones
> who use ConTeXt.

  You’re making it impossible to help you.  Whatever anyone says, you
dismiss it with various excuses: you already knew that, you read the
email but needed half a year to tell it wasn’t useful, you want to have
the discussion in another forum.  Right now it’s imaginary users that
prop your demand for a different solution because it “isn’t about
yourself or your documents” -- even though it clearly is.  No one else
here has expressed interest in what you’re asking for.

  There’s worse, though.  Your original request revealed that some
consonant pairs could be treated differently when hyphenating Ancient
Greek.  Which are they?  Determining that was clearly on you, and would
have brought at least a modicum of substance to the discussion.  Having
however more or less lost hope that you ever will, I did that job myself
and now think that

βμ βν γμ θμ πμ τν φμ χμ

are the only consonant pairs that require a different treatment.  Would
you please confirm?

Best,

Arthur
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] index "compress" option / collapsing of page numbers

2019-04-03 Thread Henning Hraban Ramm
Am 2019-04-03 um 13:30 schrieb Hans Hagen :

> On 4/3/2019 10:56 AM, Henning Hraban Ramm wrote:
>> Am 2019-04-02 um 18:53 schrieb Hans Hagen :
>>> On 4/2/2019 11:54 AM, Henning Hraban Ramm wrote:
 Ahoi,
 with \setupregister[compress=yes], index entries 1,2,3,4 become 1–4. 
 That’s great.
 But (at least in German publications) it’s usual that 1,2 becomes 1f. and 
 1,2,3 becomes 1ff.
 Is it possible to configure it that way?
>>> it should not be too hard to program but, it being german problem:
>>> 
>>> - you have to come up with an example
>>> - wolfgang has to come up with a proper keyword (compress=?)
>>> 
>> Thank you – it’s not only a German habit, even if we pronounce it 
>> “folgende”, “f.” stems from Latin “folio”, and “ff.” is a duplicated 
>> abbreviation, as was usual in mediaeval Latin.
>> So, this is at least used in English, German, Norwegian and Swedish, as far 
>> as I could find. In French they seem to use “sq.” and “sqq.” (sequens).
>> https://de.wiktionary.org/wiki/ff.
>> https://en.wiktionary.org/wiki/ff.
>> https://fr.wiktionary.org/wiki/sq.
>> I suggest the following setup options:
>> compress = no  —> don’t collapse (as now)
>> compress = yes —> always use – (as now)
>> compresssymbols={\,f.,\,ff.} (or how can you setup a list?)
>> compress = symbols —> use first symbol for one other page, second for more 
>> pages
>>  if there’s only one symbol, more than one sequential page should use – 
>> (like “yes”)
>> Is this feasible?
> 
> i'll add
> 
> \setuplabeltext % predefined
>  [en]
>  [following:singular=f.,
>   following:plural=ff.]
> 
> \setupregister[index][compress=text]


Great! Thank you!
I’ll document it.

Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD

___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___