Re: [NTG-context] OSFONTDIR
> Am 2019-08-15 um 23:57 schrieb Hans Hagen : > > On 8/15/2019 11:06 PM, Henning Hraban Ramm wrote: >>> Am 2019-08-15 um 08:08 schrieb Huseyin Özoguz : >>> >>> I just moved to Win 10 (coming from Win 7) with a fresh system and >>> installed Context. >>> >>> My problem: The manual installed fonts are not stored in "Windows/Font" >>> like before, but in "AppData/Local/Microsoft/Windows/Fonts" – the default >>> Fonts, which came with windows, are still there in Windows/Font. >>> >>> If I change OSFONTDIR to the new path and execute "mtxrun --script font >>> --reload" after that, the new fonts are found by Context, but that seems no >>> good way, because now the default-fonts are not found. >>> >>> How to solve this situation? How can I prevent Win10 from installing manual >>> installed fonts into this other path and instead install it into >>> "Windows/Font"directly? (Other programs like Corel etc. have no problems >>> finding those other fonts, regardles of there location or OSFONTDIR.) >>> >>> Another solution: Give Context two pathes to look for fonts, is that >>> possible? >> OSFONTDIR is like other PATH variables, it can contain several paths, >> separated by ; (at least on Linux and OSX, maybe it’s : on Windows). My >> OSFONTDIR is rather lengthy to include my collections of commercial and free >> fonts (beware, that makes ConTeXt slow). > in what sense slow ... more fonts means of course a longer identification > time when the database is made but that happen seldom (unless you refer to an > unknown font in your document in which case a scan happens, but that should > then be fixed in the style) It’s been a while since I had my whole collection of literally thousands of fonts in OSFONTDIR, but re-scanning happens quite often – yes, probably something’s wrong in my typescripts, or I call for an invalid combination somewhere. At the moment I just get this error message on every run: resolvers | globbing | confusing filename, name: 'SourceSansPro-SemiBold.ttf', lower: 'sourcesanspro-semibold.ttf', already: 'SourceSansPro-Semibold.ttf' I don’t understand what’s wrong with that font. 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] Fwd: OSFONTDIR and Windows 10
On 8/15/2019 11:06 PM, Henning Hraban Ramm wrote: Am 2019-08-15 um 08:08 schrieb Huseyin Özoguz : I just moved to Win 10 (coming from Win 7) with a fresh system and installed Context. My problem: The manual installed fonts are not stored in "Windows/Font" like before, but in "AppData/Local/Microsoft/Windows/Fonts" – the default Fonts, which came with windows, are still there in Windows/Font. If I change OSFONTDIR to the new path and execute "mtxrun --script font --reload" after that, the new fonts are found by Context, but that seems no good way, because now the default-fonts are not found. How to solve this situation? How can I prevent Win10 from installing manual installed fonts into this other path and instead install it into "Windows/Font"directly? (Other programs like Corel etc. have no problems finding those other fonts, regardles of there location or OSFONTDIR.) Another solution: Give Context two pathes to look for fonts, is that possible? OSFONTDIR is like other PATH variables, it can contain several paths, separated by ; (at least on Linux and OSX, maybe it’s : on Windows). My OSFONTDIR is rather lengthy to include my collections of commercial and free fonts (beware, that makes ConTeXt slow). in what sense slow ... more fonts means of course a longer identification time when the database is made but that happen seldom (unless you refer to an unknown font in your document in which case a scan happens, but that should then be fixed in the style) - 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] Fwd: OSFONTDIR and Windows 10
> Am 2019-08-15 um 08:08 schrieb Huseyin Özoguz : > > I just moved to Win 10 (coming from Win 7) with a fresh system and installed > Context. > > My problem: The manual installed fonts are not stored in "Windows/Font" like > before, but in "AppData/Local/Microsoft/Windows/Fonts" – the default Fonts, > which came with windows, are still there in Windows/Font. > > If I change OSFONTDIR to the new path and execute "mtxrun --script font > --reload" after that, the new fonts are found by Context, but that seems no > good way, because now the default-fonts are not found. > > How to solve this situation? How can I prevent Win10 from installing manual > installed fonts into this other path and instead install it into > "Windows/Font"directly? (Other programs like Corel etc. have no problems > finding those other fonts, regardles of there location or OSFONTDIR.) > > Another solution: Give Context two pathes to look for fonts, is that possible? OSFONTDIR is like other PATH variables, it can contain several paths, separated by ; (at least on Linux and OSX, maybe it’s : on Windows). My OSFONTDIR is rather lengthy to include my collections of commercial and free fonts (beware, that makes ConTeXt slow). 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] Fwd: ConTeXt Group Newsletter August 2019
Thank you, Taco! > = ConTeXt Meeting blurb = > > If you have not registered yet, please consider joining us at YES, register NOW if you didn’t already! > = Chaos Communication Camp = > > CG Board member Henning Hraban Ramm is representing the ConTeXt community > at the Chaos Communication Camp 2019 in the 'LaTeX Village’ (set up in > conjunction with Dante e.V.) > > https://events.ccc.de/camp/2019/wiki/Village:LaTeX > > If any of you are in the neighbourhood of Ziegeleipark Mildenberg, Zehdenick, > Germany between August 21 and 25, I am sure he would love to see some visitors > (Zehdenick is about 60km north of Berlin). No, sorry, that won’t work – tickets are sold out. Of course I’d be glad to meet other ConTeXt users in our lovely LaTeX lab ;) BTW our neighbours are the latex loving Kinky Geeks - no coincidence… :D There will be 5 kids in our village, I’m curious what questions they’ll bring up… 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] radiobuttons
> Am 2019-08-14 um 22:09 schrieb Wolfgang Schuster > : > Use (with "framed" in the second optional argument) > > \setupfield [MMradio] [framed] [..,..=..,..] > > to get normal framed fields. I already had "framed=on" as part of my setup. *** I found a ConTeXt beta from February 2019 on my laptop, and there it works as it should. i.e. frames are there, and radiobuttons are single-select. *** > Am 2019-08-14 um 19:20 schrieb Hans Hagen : > > On 8/13/2019 8:01 PM, Henning Hraban Ramm wrote: >> Regardless of my other mails, I’d appreciate to have this bug fixed. > > Last time I checked this (widget crap) there was an issue with acrobat and > apearances ... I think that this model of parents and kids never really > worked well and when one switches a page existing renderings get messed up. > Irr some of these widgets (check boxes?) can't even have a custom > visualization any more that is kept when one goes through pages. > > I also have no clue to what extend all this is part of the 'standard'. > > Anyway, if you can make a working example (uncompressed pdf) in official > acrobat (not some other tool) that works in acrobat reader we can maybe > figure out what todays demands are. Implementing stuff like this is trivial > but the trial and error is painful. > > Hans > > (I only have acrobat X and reader for checking this.) I can understand your annoyance about Adobe – I recently switched Acrobat Pro with Qoppa PDF Studio Pro that contains most of AcroPro’s functions (including PDF/X and PDF/A check), since my Acrobat Pro 9 doesn’t work on OSX Mojave any more (it starts, but a lot of features won’t work), and I don’t want to pay monthly for their bloated crap. PDF Studio lacks LiveCycle forms support (unfortunately those are used by some German authority bodies), and it can’t display CropBox, TrimBox etc outside of the cropping tool; I placed a feature request, maybe they’ll implement it; their email support was very quick, friendly and helpful. Neither Acrobat (Pro 9) nor PDF Studio can save uncompressed PDFs. (I know old versions of AcroPro could.) I "customized" the checkbox as it was possible within Acrobat; I found no options to use custom symbols (I know it worked in Acrobat 5-7). Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD radiobuttons_pdfstudio.pdf Description: Adobe PDF document radiobuttons_acrobat.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 ___
Re: [NTG-context] radiobuttons
On 8/13/2019 8:01 PM, Henning Hraban Ramm wrote:
Regardless of my other mails, I’d appreciate to have this bug fixed.
I wasted the whole day on trying all kind of tricks and comparing pdf's
made with acronbat and context etc etc just to find out that the
preference is the problem ...
forms -> highlight color -> show border hover color
it badly interfering with these widgets ... there seems to be no way to
turn that off (forms made with acrobat suffer a bit less because they
use a funny mix of appearances and border settings and ... because they
make these buttons from dingbats (i think)
anyway, it's bad in the latest reader as well as in acrobat x which
shows it's an old issue and as it's that old one can fear it has become
a feature ... (of that no one cares)
so, the only solution seems to be to check the prefs
(mupdf is doing it right)
Hans
--- test file ---
\setupinteraction
[state=start]
\definesymbol[yes][1]
\definesymbol[nop][0]
\setupfield[whatever][width=20mm,height=20mm,frame=off]
\definefield[what][radio][whatever][whatone,whattwo][whatone]
\definesubfield[whatone][][yes,nop]
\definesubfield[whattwo][][yes,nop]
\startuniqueMPgraphic{0}
fill fullcircle scaled 1cm withcolor red ;
\stopuniqueMPgraphic
\startuniqueMPgraphic{1}
fill fullcircle scaled 1cm withcolor green ;
\stopuniqueMPgraphic
\definesymbol[YES][\uniqueMPgraphic{1}]
\definesymbol[NOP][\uniqueMPgraphic{0}]
\setupfield[WHATEVER][width=20mm,height=20mm,frame=off]
\definefield[WHAT][radio][WHATEVER][WHATONE,WHATTWO][WHATONE]
\definesubfield[WHATONE][][YES,NOP]
\definesubfield[WHATTWO][][YES,NOP]
\starttext
\startTEXpage[offset=2cm]
\field[whatone]\space\field[whattwo]
\field[WHATONE]\space\field[WHATTWO]
\field[WHATONE]\space\field[WHATTWO]
\stopTEXpage
\startTEXpage[offset=2cm]
\field[whatone]\space\field[whattwo]
\field[WHATONE]\space\field[WHATTWO]
\field[WHATONE]\space\field[WHATTWO]
\stopTEXpage
\stoptext
-
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] metafun 2
On Wed, Aug 14, 2019 at 10:18:19PM +1200, Henri Menke wrote: > I just wanted to ask, will LMTX and MetaFun remain valid implementations > of TeX and MetaPost or do we have to expect incompatibilities? If you mean “will luametatex pass the trip test”, the answer is probably no: LuaTeX already diverged from Knuth’s TeX in small ways, for example by allowing the first word of a paragraph to be hyphenated. 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] OSFONTDIR and Windows 10
Ok, solved. The problem was that Windows 10 by default installs new fonts only for the current User, not for all. I changed that, now everything is back to normal. Huseyin Özoguz Schilfweg 52a 27751 Delmenhorst E-Mail: h.oezo...@mmnetz.de Tel.: 0176/20203416 Am 15.08.2019 um 08:08 schrieb Huseyin Özoguz: Hello, I just moved to Win 10 (coming from Win 7) with a fresh system and installed Context. My problem: The manual installed fonts are not stored in "Windows/Font" like before, but in "AppData/Local/Microsoft/Windows/Fonts" – the default Fonts, which came with windows, are still there in Windows/Font. If I change OSFONTDIR to the new path and execute "mtxrun --script font --reload" after that, the new fonts are found by Context, but that seems no good way, because now the default-fonts are not found. How to solve this situation? How can I prevent Win10 from installing manual installed fonts into this other path and instead install it into "Windows/Font"directly? (Other programs like Corel etc. have no problems finding those other fonts, regardles of there location or OSFONTDIR.) Another solution: Give Context two pathes to look for fonts, is that possible? Thank you. ___ 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] OSFONTDIR and Windows 10
Hello, I just moved to Win 10 (coming from Win 7) with a fresh system and installed Context. My problem: The manual installed fonts are not stored in "Windows/Font" like before, but in "AppData/Local/Microsoft/Windows/Fonts" – the default Fonts, which came with windows, are still there in Windows/Font. If I change OSFONTDIR to the new path and execute "mtxrun --script font --reload" after that, the new fonts are found by Context, but that seems no good way, because now the default-fonts are not found. How to solve this situation? How can I prevent Win10 from installing manual installed fonts into this other path and instead install it into "Windows/Font"directly? (Other programs like Corel etc. have no problems finding those other fonts, regardles of there location or OSFONTDIR.) Another solution: Give Context two pathes to look for fonts, is that possible? Thank you. -- Huseyin Özoguz Schilfweg 52a 27751 Delmenhorst E-Mail: h.oezo...@mmnetz.de Tel.: 0176/20203416 ___ 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 ___
