[NTG-context] Graphics gets extra indent if hanging in list

2018-06-11 Thread Mikael P. Sundqvist
Hi!

Please look at the example below. I wish the red rectangle to be located as
the green one aligned with text to the right, but it gets pushed a bit (the
space to the left in the list?). Am I doing things wrongly? Is it possible
to fix easily?

/Mikael

\setuppapersize[A6]

\starttext

\starthanging[location=right]{\blackrule[color=darkgreen,width=1in,height=0.5in]}
\input ward
\stophanging

\startitemize[n]
\item
\starthanging[location=right]{\blackrule[color=darkred,width=1in,height=0.5in]}
\input ward
\stophanging
\stopitemize

\stoptext


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

[NTG-context] error in seeindex sorting

2018-06-11 Thread Henning Hraban Ramm
Me again on registers.

If you have an entry with just subentries and a reference (seeindex) from the 
main entry to an *existing* other entry, the reference is sorted at one of the 
subentries.
I.e. in the MWE we get

Fun
  games 1, see sample
  stuff 1

instead of

Fun see sample
  games 1
  stuff 1


\starttext
\index{sample}
\index{Fun+games}\index{Fun+stuff}
\seeindex{Fun}{sample}
\placeindex[n=1]
\stoptext


This prevents the completion of a scientific tome, so would be really nice if 
this could be fixed.


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
___

[NTG-context] highlighting in registers (index)

2018-06-11 Thread Henning Hraban Ramm
According to http://wiki.contextgarden.net/Registers#Processors, processors are 
the MkIV way of highlighting within index entries.

If there are highlighted and not-highlighted entries, the normal version wins.
If there is a highlighted version with subentry, the subentry becomes 
highlighted and is sorted unter the normal main entry, if there doesn’t exist a 
normal entry with the same subentry.
(These are just observations, I wouldn’t know how it should be different.)

But: Is there a way to highlight just subentries?
e.g. \index{Sun+emph->rays}


"""
\defineprocessor[emph][style=italic]

\starttext
\index{Sun}
\index{Sun->rays}
\index{emph->Sun}
\index{Sun+emph->rays} % doesn’t work
\index{emph->Sun+rays} % rays upright
\index{emph->Sun+beams} % beams italic

\placeindex[n=1]
\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
___

[NTG-context] issue with hyphenation patterns

2018-06-11 Thread Pablo Rodriguez
Dear list,

I have the following sample:

\setuplanguage[agr][patterns={agr, en}]
\setuplanguage[en][patterns={en, agr}]
\starttext
\hyphenatedword{judgmental}
\agr \hyphenatedword{judgmental}
\stoptext

I wonder why \en hyphenates the word and \agr doesn’t.

I mean, both languages have the same patterns loaded.

Using \de or \es, hyphenation works fine in both cases:

\setuplanguage[agr][patterns={agr, deo}]
\setuplanguage[deo][patterns={de, agr}]
\mainlanguage[de]
\starttext
\hyphenatedword{Klugheit}
\agr \hyphenatedword{Klugheit}
\stoptext

\setuplanguage[agr][patterns={agr, deo}]
\setuplanguage[es][patterns={es, agr}]
\mainlanguage[es]
\starttext
\hyphenatedword{experimentado}
\agr \hyphenatedword{experimentado}
\stoptext

If this isn’t a bug, what am I missing?

Many thanks for your help,

Pablo
-- 
http://www.ousia.tk
___
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] font pathes with colons

2018-06-11 Thread Ulrike Fischer
Am Sun, 10 Jun 2018 13:24:40 +0200 schrieb Hans Hagen:

> i changed the parser for generic a bit so you need to check careful next 
> beta as i'm only testing some basic plain loading

It broke ;-(

luaotfload complained about a missing registersplit,
then about a missing addspecifier, so I reinserted from the previous
version (from UF to /UF) (around line 32865)

local resolvefile=fontgoodies and fontgoodies.filenames and
fontgoodies.filenames.resolve or function(s) return s end
-- UF
local splitter,splitspecifiers=nil,""
local P,C,S,Cc,Cs=lpeg.P,lpeg.C,lpeg.S,lpeg.Cc,lpeg.Cs
local left=P("(")
local right=P(")")
local colon=P(":")
local space=P(" ")
local lbrace=P("{")
local rbrace=P("}")
definers.defaultlookup="file"
local prefixpattern=P(false)
local function addspecifier(symbol)
  splitspecifiers=splitspecifiers..symbol
  local method=S(splitspecifiers)
  local lookup=C(prefixpattern)*colon
  local sub=left*C(P(1-left-right-method)^1)*right
  local specification=C(method)*C(P(1)^1)
  local
name=Cs((lbrace/"")*(1-rbrace)^1*(rbrace/"")+(1-sub-specification)^1)

splitter=P((lookup+Cc(""))*name*(sub+Cc(""))*(specification+Cc("")))
end
local function addlookup(str,default)
  prefixpattern=prefixpattern+P(str)
end
definers.addlookup=addlookup
addlookup("file")
addlookup("name")
addlookup("spec")
local function getspecification(str)
  return lpegmatch(splitter,str or "")
end
definers.getspecification=getspecification
function definers.registersplit(symbol,action,verbosename)
  addspecifier(symbol)
  variants[symbol]=action
  if verbosename then
variants[verbosename]=action
  end
end
-- /UF


Then it complained about a missing upvalue getthreshold so I
reinserted:

local getthreshold
--UF
injections.threshold=0
getthreshold=function(font)
local p=fontdata[font].parameters
local f=p.factor
local s=p.spacing
local t=injections.threshold*(s and s.width or p.space or 0)-2
return t>0 and t or 0,f
end
--/UF


Now it works again and also the "unknown option" warning is gone. 


> i have no clue how otfload locates files but maybe you need to add an 
> entry to
> 
> local remapper = {
>  otf= "opentype fonts",
>  ttf= "truetype fonts",
>  ttc= "truetype fonts",
>  cid= "cid maps",
>  cidmap = "cid maps",
>   -- fea= "font feature files", -- no longer supported
>  pfb= "type1 fonts",-- needed for vector loading
>  afm= "afm",
>  enc= "enc files",
>  lua= "tex", -- LIKE THIS
> }

 lua= "misc fonts", 
would be better (then one can put the fonts in fonts/misc. 

But it doesn't help with the main problem that luaotfload calls
resolvers.findfile first for "basename + otf, tfm, ofm", then
triggers a rebuild of the database and only then calls
resolvers.findfile again with the fullname.

Also I really want to avoid to patch the merged code. I'm regularly
getting the newest version from context and try out if it still
works and prefer if I can use them unchanged.  

-- 
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
___

[NTG-context] OT: Pexeso (one missing rule)

2018-06-11 Thread Procházka Lukáš Ing .

Hello,

there is a card game called "Pexeso".

It is played by two or more players with pairs of cards of identical pictures.
Initially, cards are spread regularly and are turned upside down.
The first player turns two cards; if they are identical, he picks them and 
continues turning two more cards.
If both cards do not show the same picture,
--->THEY ARE TURNED BACK UPSIDE DOWN
and the next payer follows.
(So the game is about to remember as many cards as possible which have been 
turned/shown.)
The game stops when there are no more cards to turn.
Who collects more pairs of cards is winner.

Usually, you can buy Pexeso of Barbies, princesses, road signs, castles, ...

My little son (of nearly 4 years) ignores all above as he is interested (or 
even fascinated) by construction machinery and woodworking tools.

So I decided to create a Pexeso of woodworking tools for him with the following 
points:

- Pictures to be processed are placed in the subdirectory called "1" (may be 
changed).

- Pictures whose name do not start by "-" have the first letter uppercased shown on the 
card ("education" for letters).

- You may simply change the text or MP code to draw the card back.

- Backs of cards are intentionally a bit randomized (I am curious how quickly 
children are able to recognize some cards by their backs).

- When the number of cards is not multiple of two (also my case), two more 
backs of cards will be drawn.
This is intended and it comes due to some simplicity of the code; and 
it doesn't matter to anything.

- Source uses UTF-8 coding.

- There are no dependencies to external files (excluding pictures).

- The source file is attached.
Due to the size (~2.3 MB), all data including the result and source 
pictures are available for download here:

http://leteckaposta.cz/611754576

(The link will be valid for ~27 days from now.)

Enjoy!

Best regards,

Lukas


--
Ing. Lukáš Procházka | mailto:l...@pontex.cz
Pontex s. r. o.  | mailto:pon...@pontex.cz | http://www.pontex.cz | 
IDDS:nrpt3sn
Bezová 1658
147 14 Praha 4

Mob.: +420 702 033 396

Pexeso2.mkiv
Description: Binary data
___
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] Export to xml no longer works

2018-06-11 Thread Hans Hagen

On 6/11/2018 4:31 AM, Rik Kabel wrote:

With TL18, the following produces the expected xml and associated files.

\setupbackend [export=yes]
\starttext
\input knuth
\stoptext

With current betas, the xhtml file contains:

invalid xml file - parsed text

and the other files have similar content.

Can anyone reproduce the error or offer a workaround?

fixed in next beta



-
  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] OT: Pexeso

2018-06-11 Thread Procházka Lukáš Ing .

Hello,

there is a card game called "Pexeso".

It is played by two or more players with pairs of cards of identical pictures.
Initially, cards are spread regularly and are turned upside down.
The first player turns two cards; if they are identical, he picks them and 
continues turning two more cards.
Once both cards do not show the same picture, the next payer follows.
The game stops when there are no more cards to turn.
Who collects more pairs of cards is winner.

Usually, you can buy Pexeso of Barbies, princesses, road signs, castles, ...

My little son (of nearly 4 years) ignores all above as he is interested (or 
even fascinated) by construction machinery and woodworking tools.

So I decided to create a Pexeso of woodworking tools for him with the following 
points:

- Pictures to be processed are placed in the subdirectory called "1" (may be 
changed).

- Pictures whose name do not start by "-" have the first letter uppercased shown on the 
card ("education" for letters).

- You may simply change the text or MP code to draw the card back.

- Backs of cards are intentionally a bit randomized (I am curious how quickly 
children are able to recognize some cards by their backs).

- When the number of cards is not multiple of two (also my case), two more 
backs of cards will be drawn.
This is intended and it comes due to some simplicity of the code; and 
it doesn't matter to anything.

- Source uses UTF-8 coding.

- There are no dependencies to external files (excluding pictures).

- The source file is attached.
Due to the size (~2.3 MB), all data including the result and source 
pictures are available for download here:

http://leteckaposta.cz/611754576

(The link will be valid for ~27 days from now.)

Enjoy!

Best regards,

Lukas


--
Ing. Lukáš Procházka | mailto:l...@pontex.cz
Pontex s. r. o.  | mailto:pon...@pontex.cz | http://www.pontex.cz | 
IDDS:nrpt3sn
Bezová 1658
147 14 Praha 4

Mob.: +420 702 033 396

Pexeso2.mkiv
Description: Binary data
___
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
___