September 2023 - ntg-context - NTG Mailing Lists

(feature proposal) link to attachments: /GoToE
by Pablo Rodriguez 03 Sep '23

03 Sep '23

Hi Hans, having attachments in PDF is very useful, but the vast majority of people don’t know how to handle them (even with the attachment pane displayed when Acrobat opens the document, or with file annotation). It would be really useful to have a link with destination that it would open the embedded document (when clicked). Since in its basic functionality, this is very similar to links to external documents (GoToR), I wonder whether it would be possible to implement links to embedded documents (GoToE, https://opensource.adobe.com/dc-acrobat-sdk-docs/pdfstandards/PDF32000_2008…) At least to begin with, only links to embedded children documents would be required. If this GoToR is generated by ConTeXt from "\goto{whatever}[destination-doc::page(15)]": 17 0 obj << /D [ 14 /Fit ] /F (destination-doc.pdf) /NewWindow true /S /GoToR >> endobj A GoToE destination for "\attachment[file=destination-doc.pdf, method=hidden]" would read: 1 0 obj << /S /GoToE /D [ 14 /Fit ] /NewWindow true /T << /R /C /N (destination-doc.pdf) >> >> endobj With EmbeddedFiles, the F entry from GoToR is a target dictionary (T key) in GoToE. The T dictionary contains the relation (R key) to the destination file (only C, child, needed) and the name (N) from EmbeddedFiles/Names for the attachment. This is the most basic implementation that allows to link to an attachment. What the spec describes as “a complete facility for linking between a file in a hierarchy of nested embedded files and another file in the same or different hierarchy” is probably unnecesarily complex (even to use). With file annotations, instead of the name from EmbeddedFiles/Names in the target dictionary, it requires the keys P and A (as numbers or strings). P gives the page number which contains the file annotation: zero-based as number, or named destination as string. A gives the annotation: zero-based index of the annotation in the Annots array, or NM entry value from the annotation object. As for the interface, it would be great that GoToR links could be converted automatically in "\goto{some text}[file::page(number)]" for attached files. This basic implementation of GoToE links would be extremely helpful to access embedded documents (believe it or not, this is something I explain almost every week at work). I would be happy to provide the code to implement this, but I’m afraid this is way beyond my knowledge. Many thanks for your help, Pablo

3 4

list of modules: need changes/testing/response
by Henning Hraban Ramm 03 Sep '23

03 Sep '23

Hi all, esp. module authors! I went through the list of modules on https://modules.contextgarden.net/ (dl/) and the list that controls module installation for “--script install-modules". I removed all font-related modules from the list (not yet from the garden), since they’re probably all obsolete & outdated. Consider publishing typescripts in the wiki. The following modules don’t adhere to the necessary structure and need changes: * t-handlecsv (2023, Pablo) * metaducks (2021, Jairo) * presvoz (2023, Pablo) All of them have a name directory on top of the TDS (tex, doc). If you used a git checkout URL, please try again, for me it worked today. Several modules need testing if they still work and make sense. If their authors are present, I’d appreciate a comment if we should keep them. I’d like to delete at least everything older than 10 years. * grph-downsample.lua (2019) is known to fail in current LMTX (I hope for an integrated solution during the meeting.) t-degrade (2018) is AFAIK an older version of it – delete? * high (2018) and pret-c (2018) are syntax highlighters. Are they better than the vim and scite modules? Does it make sense to keep/update them? * karnaugh (2021, VicSanRoPe; probably OK, I just don’t understand it) * t-account (2009, Wolfgang) * t-algorithmic (2013, Wolfgang) * t-animation (2013, Wolfgang) * t-annotation (2013, Wolfgang) * t-bnf (2006, Now) * t-chromato (2008, Peter) * t-construction-plan (2008, Peter) * t-crossref (2016, Zenlima) * t-cyrillicnumbers (2016, Philipp) * t-fancybreak (2015, Wolfgang) * t-french (2011, Peter) * t-fullpage (2017, Wolfgang) * t-gantt (2012, Adam) * t-gm (2015, Luigi) * t-gnuplot (2013, Mojca) * t-greek (2013, Thomas – is this more than fonts?) * t-gs (2015, Luigi) * t-inifile (2008, Peter) * t-layout (2007, Patrick) * t-letterspace (2016, Philipp) * t-mathsets (2011, Aditya) * t-rst (2016, Philipp) * t-rsteps (2006, David) * t-simplebib (2016, Zenlima) * t-taspresent (2008, Thomas – AFAIK an old version of simpleslides) * t-title (2017, Wolfgang) * t-transliterator (2021, Philipp) * t-typearea (2008, Peter) * t-visualcounter (2018, Aditya, isn’t there a newer version?) Modules not mentioned are probably fine. Hraban

7 14

Building luametatex with Lua symbols exposed
by Jairo A. del Rio 02 Sep '23

02 Sep '23

Hi, beloved list. Since sources are in the distribution, I've tried compiling luametatex by setting LMT_STRIP in CMakeLists.txt to 0, yet the resulting binary still warns about undefined symbols, such as lua_gettop, when an external library is loaded in Lua. Any ideas on how to solve it? Thank you in advance. Best regards, Jairo

2 1

slanted font feature: LMTX vs. MkIV
by Pablo Rodriguez 02 Sep '23

02 Sep '23

Dear list, I have the following sample (using current latest from 2023.08.27 13:48): \setupinteractionscreen[option=max] \definefontfamily[maf][rm][DejaVu Sans] [sl={style:tf, features:{default,slanted}}] \setupbodyfont[maf, 8pt] \setupfittingpage[offset=1ex] \starttext \startTEXpage a {\em b} \stopTEXpage \startTEXpage[foregroundstyle={\setupbodyfont[100pt]}] a {\em b} \stopTEXpage \stoptext Using LMTX higher font size gives less slanted text (or not at all). Using MkIV text is slanted fine, independent from font size. Could anyone confirm the issue? Many thanks for your help, Pablo

3 6