July 2015 - ntg-context - NTG Mailing Lists

bug with bookmarks?
by Pablo Rodriguez 05 Jul '15

05 Jul '15

Dear list, I have the following sample: \setupinteraction[state=start] \placebookmarks [part,chapter,section,subsection,subsubsection] [part,chapter] \starttext \placelist[part,chapter] \startfrontmatter \chapter{Introduction} \stopfrontmatter \startbodymatter \dorecurse{2}{\part{Part} \dorecurse{3}{\chapter{Chapter} \dorecurse{5}{\section{Section}}}} \stopbodymatter \stoptext For some strange reason, with front and body matters the bookmarks for parts don’t contain bookmarks for chapters (although chapter bookmarks do contain section bookmarks). Removing \placelist[part,chapter] shows the same issue (part bookmarks not containing chapter bookmarks). And replacing \placelist[part,chapter] with \completecontent places bookmarks from front matter after the ones from the body matter. (Besides the fact that I don’t want to have sections in the TOC.) I suspect this may be a bug. Could you confirm it or explain me what I’m missing? Many thanks for your help, Pablo -- http://www.ousia.tk

1 0

conTeXt Mkiv: the number of parameters can not be more than 9?
by 土卜皿 04 Jul '15

04 Jul '15

hi, all For testing, I have a definition: \define[9]\DEFINETEST{#1,#2,#3,#4,#5,#6,#7,#8,#9} context test can work fine, when I modify the above into: \define[10]\DEFINETEST{#1,#2,#3,#4,#5,#6,#7,#8,#9,#10} I got a error: test.tex: ! Illegal parameter number in definition of \DEFINETEST >From StackExchange, I got a answer: Since ConTeXt is based on TeX, the maximum number of 9 parameters is inherited So, in Context mkiv, what should I do for more than 9 parameters? Thanks! Best Regards Dillon

3 3

How to implement a head like this?
by 土卜皿 04 Jul '15

04 Jul '15

hi, all I want to use context for writing my resume, I found the head like the attached file's very awesome, but I don't know how to implement it, or what elements I should use to do it? please any one help me, Thanks in advance! Best Regards Dillon Peng

3 4

issues with xtable
by Pablo Rodriguez 04 Jul '15

04 Jul '15

Dear list, I have the following sample: \setupxtable[frame=on, option=stretch] \setupxtable[name][foregroundstyle=\bfc, ny=3, align=lohi] \setupxtable[cv][foregroundstyle=\em, ny=2, align=bottom] \setupxtable[contact][foregroundstyle=\em, align=flushright] \starttext \startxtable \startxrow \startxcell[name][ny=3]Some Name\stopxcell \startxcell[contact]Some Address Here\stopxcell \stopxrow \startxrow \startxcell[cv][ny=2]Curriculum vitae\stopxcell \startxcell[contact]City, State, 55555\stopxcell \stopxrow \startxrow \startxcell[contact](000) 111-3333\stopxcell \stopxrow \startxrow \startxcell[contact]user(a)domain.level\stopxcell \stopxrow \startxrow \startxcell[contact]http://contextgarden.net\stopxcell \stopxrow \stopxtable \stoptext And I experiencing three issues. The first issue is I don’t know why there is a third column at all. I may be dowing something wrong, but where does ConTeXt read that there is a third xcell on any xrow? (I guess this might be a bug.) The second issue is that align=lohi doesn’t center vertically the cell contents. There is slightly less vertical space before the text than before it. The third issue is that spanning information isn’t read from \setupxtable, but I thas to be added at the xcell itself. Wouldn’t it be possible to read it from \setupxtable also? Many thanks for your help, Pablo -- http://www.ousia.tk

1 0

Re: [NTG-context] Accessibility and Tagged PDFs: Bugs and Feature Requests
by Christoph Reller 03 Jul '15

03 Jul '15

On Wed, 01 Jul 2015 19:02:08 +0200 Hans Hagen <pragma(a)wxs.nl> wrote: > So, it's not that difficult to add features, more a matter of priorities > and motivation (apart from the fact that my acrobat is a bit old by now > so I cannot really test). > Dear Hans, You can use the PDF Accessibility Checker for Testing (this might be even better than Acrobat): http://www.access-for-all.ch/en/pdf-lab/pdf-accessibility-checker-pac.html And to add to your motivation ;-) : Google ranks tagged PDFs higher than non-tagged PDFs. For those moving from MS Word to ConTeXt this is a must. Thank you for all your effort! Christoph

2 1

newbie - scite and context standalone
by Florian Rudt 03 Jul '15

03 Jul '15

Dear List, I tried to install ConTeXt Suite with SciTe on Windows with this manual: http://wiki.contextgarden.net/Windows_Installation:_ConTeXt_Suite_with_SciTe Installing ConTeXt was no problem and it works. For SciTe I took Troy Simpson's Windows installer (version 3.5.7) and downloaded scintillua_3.5.7-1 from http://foicica.com/scintillua/download. I installed SciTe as the installer suggests and copied all from the scintillua_3.5.7-1-folder to the SciTe-folder. Then I copied everything from C:\context\tex\texmf-context\context\data\scite\context to the same folder. In SciTe I added "import scite-context-user" to the Global Options File. I thought that this would be all to get SciTe with ConTeXt working, but when I press Ctrl+F12 nothing happens. Have I forgotten something or is there something new? All I want is a more sophisticated editor than Texworks/Texshop, preferably a cross-platform one. SciTe looks nice and tidy so I can concentrate on my code and text. An alternative for all OSes would be emacs/AUCtex, but coming from the DTP-side, this one scares me. My main machine is a Macmini (or: two of them), but I want to get away (after 25 years) from this Apple and DTP things. My preferred OS for the future would be Linux Mint Debian Edition (LMDE), because it was the fastest and clearest form me after testing several OSes in VirtualBox. Thanks for Your help Florian

2 1

\footnote and \note with \setupnotation[way=bypage], but it does not work with XML processing
by mf 02 Jul '15

02 Jul '15

Hello list, I have a text with footnotes that get referenced more than once. No problem for ConTeXt, since it has \footnote and \note for that. Resetting the footnote counter every page with \setupnotation[way=bypage] complicates the problem, because when you call \note on the next page, it prints the value of the counter that the footnote had in the previous page, when it should produce a new \footnote instead for the new page. Running this example should show the problem more clearly: \setupnotation[way=bypage] \def\showcountersinmargin#1{% \inmargin{\rawcountervalue[contapag#1].\rawcountervalue[#1]}% } \def\showidinmargin#1{% \inrightmargin{ #1}% } \def\mynotelabel#1{#1pag\rawcountervalue[contapag#1]} \def\myfootnote#1#2{% \definenumber[contapag#1][prefix=no]% \incrementcounter[contapag#1]% \definenumber[#1][way=bypage,prefix=no]% \incrementcounter[#1]% \footnote[\mynotelabel{#1}]{#2}% \showcountersinmargin{#1}% \showidinmargin{\mynotelabel{#1}}% } \def\mynote#1#2{% \incrementcounter[#1]% \doifelse{\rawcountervalue[#1]}{1}{% \incrementcounter[contapag#1]% \footnote[\mynotelabel{#1}]{#2}% \showcountersinmargin{#1}% \showidinmargin{\mynotelabel{#1}}% }{% \note[\mynotelabel{#1}]% \showcountersinmargin{#1}% \showidinmargin{\mynotelabel{#1}}% }% } \starttext \def\fnid{id1} \def\fntext{Text of the recurring footnote} Using just \verbatim{\footnote}\footnote[\fnid]{\fntext} and than \verbatim{\note}\note[\fnid] even in... \page ... the new page\footnote[otherid]{another footnote} does not work\note[\fnid](here different footnotes are referred with the same number because I used \verbatim{\note} to reference a footnote of the previous page). {\bf The text above should have been like this:}\par ... the new page\note[otherid] does not work\footnote{\fntext}. \page Using \verbatim{\myfootnote} and \verbatim{\mynote} it works as expected: Some text before the first occurrence of my recurring footnote\myfootnote{\fnid}{\fntext}. Some other text, with a new occurrence of my recurring footnote\mynote{\fnid}{\fntext}. \dorecurse{5}{ \page[yes] % new page \getrandomnumber \n {1} {7} \dorecurse{\n}{ Other text\footnote{other disturbing footnote}.\par } A new occurrence of the previous footnote\mynote{\fnid}{\fntext}. \getrandomnumber \n {1} {7} \dorecurse{\n}{ Other text\footnote{other disturbing footnote}.\par } Another occurrence of the previous footnote\mynote{\fnid}{\fntext}, to see if it gets referenced right.% } \stoptext My functions (\myfootnote and \mynote) solve the problem, at least with version 2014.05.21 of ConTeXt (recent versions seem to have this bug: http://www.ntg.nl/pipermail/ntg-context/2015/082498.html) Now my problem is that I can't get the same code working in XML(XHTML) processing. Here's a recurring footnote in XHTML: Text of the recurring footnote for the first occurrence, and Text of the recurring footnote for all the other occurrences of the same footnote. These are my corresponding XML setups in ConTeXt: \startxmlsetups xml:span:footnote:id \myfootnote{\xmlatt{#1}{id}}{\xmlflush{#1}} \stopxmlsetups \startxmlsetups xml:span:footnote:idref \mynote{\xmlatt{#1}{idref}}{\xmlflush{#1}} \stopxmlsetups Used in XML processing, the counters "go crazy" and I get "??" instead of the right footnote numbers in the text. Any hints? Thanks in advance, MF

1 0

Accessibility and Tagged PDFs: Bugs and Feature Requests
by Dr. Dominik Klein 01 Jul '15

01 Jul '15

Context is the only Tex-based system that allows to properly tag a pdf. Tagged PDFs are one major requirement for accessibility. Indeed, in several large organizations/universities, accessibility is mandated by law, and this is a major obstacle for using Tex. In practice compliance is often assessed with Acrobat Pro's accessibility checker. Context produces a nice tag-structure, but there are some minor issues that prevent compliance to [1], and hence Acrobat Pro complains during the check. The main issues are: 1.) Elements that are not contained in the structure tree are not marked as an artifact. Consider this example: ------------------------------- \setuptagging[state=start] \setuppagenumbering [location=, alternative=doublesided] \setupheadertexts [{Chapter~\getmarking[chapternumber]\hskip1em\getmarking[chapter]}] [{Header Right}] [{Header Left}] [{Chapter~\getmarking[chapternumber]\hskip1em\getmarking[chapter]}] \setupfootertexts [Organization Name] [pagenumber] [pagenumber] [Organization Name] \starttext \startfrontmatter something \stopfrontmatter \startbodymatter some more text here \stopbodymatter \stoptext ------------------------------- Header, footer, pagenumber etc. will not be included in the tag structure. Of course this makes absolutely sense and is correct, however according to Section 14.8.2.2.2 of [1], then this content that is not in the structure tree should be marked as an artifact, i.e. /Artifact BMC .. EMC or in an advanced way with /Artifact PropertyList where the type of Artifact can be defined. It would be nice if those elements that are not included in the tag tree would be marked as artifacts by default. The same holds for \startelement[ignore] when one wants to explicitly remove something from the structure tree. 2.) Images without alternate text: According to Section 14.9.3 of [1], alternate descriptions in human readable text should be provided for images. It would be really helpful, if these could be defined in the source tex file, and then automatically added when creating the object in the structure tree. I.e. it would be nice to have something like: \placefigure[top][Image Reference]{Caption}{ \externalfigure[cow.pdf][width=10cm][alternate text = "This images shows a beautiful cow."] } The same holds for formulas: Whereas the mathml-like tagging of Context is very advanced, sometimes it might be still helpful to supply a textual description (alt-text ="The definition of the Pythagorean theorem: a^2 + b^2 = c^2") 3.) Tag names of the resulting tag structure: Section 14.8.4 of [1] defines standard structure types, such as <H>, , <Sect> etc. Context creates a tag-tree that uses names directly representing the structure names of the context laguage, such as <sectiontitle>. This should however be mapped to something standard, such as <H>. Interestingly these mappings seem to have been considered in strc-tag.mkiv but I was unable to generate such a tagged pdf. Editing/Outcommenting things in strc-tag.mkiv didn't work for me. It would be nice if there was a switch somewhere, i.e. \setuptagging[state=start,tagnames=pdf17] - or maybe I overlooked something? 4.) Acrobat Pro always complains that the language for the whole document is not set. 5.) Tables The generated structure looks something like this: <table> <tablerow> <tablecell> ... <tablerow> <tablecell> ... Here, not only are the tag names non-compliant, also the tag structure should distinguish between the table header (THead), and table rows (TBody), c.f. Section 14.8.4.3.1 of [1]. A simple heuristic would be to always put the first line into THead tags, and the rest of the able into TBody. 6.) It would be nice if a flat tag structure could be created optionally. This is not a required feature according to [1], and in fact a properly nested structure is surely preferable for the final output; for debugging or checking during document creation however, a flat structure tree sometimes is easier to browse through. All in all, these seem to be the only issues that prevent accessible PDF documents with context. For those within an organization where accessibility is required legally for all publications, compliance to at least Acrobat Pro's checks is a huge issue. I do not know how difficult these things are to implement in Context (personally I am just lost in the code), but looking at e.g. tex.stackexchange for question related to accessibility, this is indeed a major obstacle for several people. cheers - Dominik [1] ISO 32000-1:2008, available at http://www.adobe.com/devnet/pdf/pdf_reference.html

5 7

Re: [NTG-context] Accessibility and Tagged PDFs: Bugs and Feature Requests
by Christoph Reller 01 Jul '15

01 Jul '15

On Tue, Jun 30, 2015 at 10:33 AM,luigi scarso <luigi.scarso(a)gmail.com> wrote: > On Sun, Jun 28, 2015 at 12:59 PM, Dr. Dominik Klein < > Dominik.Klein(a)outlook.com> wrote: > > > Context is the only Tex-based system that allows to properly tag a pdf. > > Tagged PDFs are one major requirement for accessibility. > > > > Indeed, in several large organizations/universities, accessibility is > > mandated by law, and this is a major obstacle for using Tex. In practice > > compliance is often assessed with Acrobat Pro's > > accessibility checker. > > > > Context produces a nice tag-structure, but there are some minor issues > > that prevent compliance to [1], and hence Acrobat Pro complains during > the > > check. > > Thank you for the report . > It would be nice to have a pdf made by context using \nopdfcompression > that have all these issues together with the report emitted by acrobat. > Last time I have checked a pfd/a-1a made by context it was all ok, but it > was time ago and maybe not > all the features were tested deeply. > > -- > luigi > Hello and thank you for raising these issues. Note that there is a free and very good PDF accessibility checker: http://www.access-for-all.ch/en/pdf-lab/pdf-accessibility-checker-pac.html You can easily generate a detailed report with this tool. It does, however, not check for PDF/A-1a conformance. Cheers, Christoph

1 0