Re: [NTG-context] Cannot access Lua function

2021-10-31 Thread kauśika cittūr via ntg-context
On Sunday, October 31, 2021 2:43:48 PM IST Hans Hagen wrote: > I bet that clever students can trace that down -) Just to clarify, I am a student at university. Have to make some documents as a teaching assistant in courses so many students use the same abbreviations. > > in that case you

Re: [NTG-context] Cannot access Lua function

2021-10-30 Thread kauśika cittūr via ntg-context
On Saturday, October 30, 2021 9:16:15 PM IST Hans Hagen wrote: > cf the pdf speca: > > Creator: If the document was converted to PDF from another format, > the name of the PDF processor that created the original document from > which it was converted. > > Producer: If the document was converted

Re: [NTG-context] Cannot access Lua function

2021-10-30 Thread kauśika cittūr via ntg-context
On Saturday, October 30, 2021 4:57:07 PM IST Hans Hagen wrote: > that function was only meant for internal (inter-lua-module > communication) usage (also because there are some expectations abotu > what is in there) > > what do you want change? Dear Hans, I want to (/used to) set the creator

[NTG-context] Cannot access Lua function

2021-10-30 Thread kauśika cittūr via ntg-context
Dear list, In one of my documents I have this lua block – \startluacode local metadata = lpdf.getmetadata(); ⋮ \stopluacode to modify some metadata fields. The file compiles with the latest LMTX (2021.10.28) without any errors but no PDF is produced. In the log, the following line is present :

Re: [NTG-context] [Solved] Line breaks, \wordright and hyphenation

2021-10-26 Thread kauśika cittūr via ntg-context
On Monday, October 25, 2021 7:34:06 AM IST kauśika cittūr wrote: > On Sunday, October 24, 2021 7:42:59 AM IST kauśika cittūr wrote: > > Dear list, > > > > In short, my question is: why does \wordright cause a line-break when the > > line preceding it breaks with hyphenation and does not

Re: [NTG-context] Line breaks, \wordright and hyphenation

2021-10-24 Thread kauśika cittūr via ntg-context
On Sunday, October 24, 2021 7:42:59 AM IST kauśika cittūr wrote: > Dear list, > > In short, my question is: why does \wordright cause a line-break when the > line preceding it breaks with hyphenation and does not otherwise? How to > avoid it (if at all possible)? > > I have this delimitedtext

Re: [NTG-context] Line breaks, \wordright and hyphenation

2021-10-24 Thread kauśika cittūr via ntg-context
On Sunday, October 24, 2021 5:31:32 PM IST Hans Hagen wrote: > On 10/24/2021 1:08 PM, Benjamin Buchmuller via ntg-context wrote: > > Maybe > > > > \hfill author > > It's anyway nicer to use > > % \definenarrower > % [amnata] > % [left=\measure{amnatamargin}, > %

Re: [NTG-context] Line breaks, \wordright and hyphenation

2021-10-24 Thread kauśika cittūr via ntg-context
On Sunday, October 24, 2021 7:42:59 AM IST kauśika cittūr wrote: > Dear list, > > In short, my question is: why does \wordright cause a line-break when the > line preceding it breaks with hyphenation and does not otherwise? How to > avoid it (if at all possible)? > > I have this delimitedtext

[NTG-context] Line breaks, \wordright and hyphenation

2021-10-23 Thread kauśika cittūr via ntg-context
Dear list, In short, my question is: why does \wordright cause a line-break when the line preceding it breaks with hyphenation and does not otherwise? How to avoid it (if at all possible)? I have this delimitedtext instance called 'amnata' defined as below: \definemeasure[amnatamargin][3cm]

Re: [NTG-context] Number conversion in btxlist and citations

2021-09-16 Thread kauśika cittūr via ntg-context
On Wednesday, September 15, 2021 8:08:59 PM IST kauśika cittūr wrote: > Dear all, > > I have a simple btx definition 'mylist' for which I have written a simple > publ-imp-mylist.lua and publ-imp-mylist-mkvi. In that latter I have > > ⋮ > \definebtx > [mylist] >

Re: [NTG-context] Number conversion in btxlist and citations

2021-09-16 Thread kauśika cittūr via ntg-context
On Wednesday, September 15, 2021 8:08:59 PM IST kauśika cittūr wrote: > Dear all, > > I have a simple btx definition 'mylist' for which I have written a simple > publ-imp-mylist.lua and publ-imp-mylist-mkvi. In that latter I have > > ⋮ > \definebtx > [mylist] >

[NTG-context] Number conversion in btxlist and citations

2021-09-15 Thread kauśika cittūr via ntg-context
Dear all, I have a simple btx definition 'mylist' for which I have written a simple publ-imp-mylist.lua and publ-imp-mylist-mkvi. In that latter I have ⋮ \definebtx [mylist] [default=default,specification=mylist] \definebtxrendering [mylist] [specification=mylist] \setupbtxlist

Re: [NTG-context] PDF metadata and pdfx keys

2021-09-15 Thread kauśika cittūr via ntg-context
On Wednesday, September 15, 2021 6:07:09 PM IST Hans Hagen wrote: > On 9/15/2021 1:27 PM, kauśika cittūr via ntg-context wrote: > > On Wednesday, September 15, 2021 8:08:34 AM IST kauśika cittūr wrote: > >> Dear all, > >> > >> In my do

Re: [NTG-context] PDF metadata and pdfx keys

2021-09-15 Thread kauśika cittūr via ntg-context
On Wednesday, September 15, 2021 8:08:34 AM IST kauśika cittūr wrote: > Dear all, > > In my documents I use > \setupinteraction > [ > author={AuthorName}, > title={MyTitle}, > subtitle={MySubtitle}, > ] > to set the document metadata. I also use > \startluacode >

[NTG-context] PDF metadata and pdfx keys

2021-09-14 Thread kauśika cittūr via ntg-context
Dear all, In my documents I use \setupinteraction [ author={AuthorName}, title={MyTitle}, subtitle={MySubtitle}, ] to set the document metadata. I also use \startluacode local metadata = lpdf.getmetadata(); metadata['producer']='author';

Re: [NTG-context] Axis macro in MetaFun

2021-09-11 Thread kauśika cittūr via ntg-context
On Saturday, September 11, 2021 10:30:25 PM IST Hans Hagen wrote: > On 9/11/2021 4:27 PM, kauśika cittūr via ntg-context wrote: > > Dear All, > > > > I am truly grateful for the new additions to MetaFun. It has greatly > > helped me in producing neat dr

[NTG-context] Axis macro in MetaFun

2021-09-11 Thread kauśika cittūr via ntg-context
Dear All, I am truly grateful for the new additions to MetaFun. It has greatly helped me in producing neat drawings for my academic work. In this connection, I have a few queries. Currently I am using PGFPlots (with ConTeXt) to draw simple plots from CSV data. I was wondering if there is any

Re: [NTG-context] Default page layout

2021-09-11 Thread kauśika cittūr via ntg-context
On Friday, September 10, 2021 2:09:29 PM IST Hans Hagen wrote: > On 9/10/2021 7:26 AM, kauśika cittūr via ntg-context wrote: > > Dear List, > > > > I am using LMTX 2021.08.30 19:56. > > > > I have the following example – > > \starttext > > \s

Re: [NTG-context] Default page layout

2021-09-09 Thread kauśika cittūr via ntg-context
On Friday, September 10, 2021 10:56:09 AM IST kauśika cittūr wrote: > Dear List, > > I am using LMTX 2021.08.30 19:56. > > I have the following example – > \starttext > \showlayout > > \input knuth > \stoptext > > which yields an output (attached here) with a "asymmetric" layout. > > Am I

[NTG-context] Default page layout

2021-09-09 Thread kauśika cittūr via ntg-context
Dear List, I am using LMTX 2021.08.30 19:56. I have the following example – \starttext \showlayout \input knuth \stoptext which yields an output (attached here) with a "asymmetric" layout. Am I doing something wrong? Or have I missed something? Please advise. Thanks, kauśika test-doc.pdf

Re: [NTG-context] Incorrect rendering in Devanagari forms in some fonts

2021-09-01 Thread kauśika cittūr via ntg-context
On Wednesday, September 1, 2021 1:43:56 PM IST kauśika cittūr wrote: > Dear All, > > I have encountered a strange problem using certain Devanagari fonts for the > Sanskrit languagein ConTeXt, wherein the rakaar ligatures are not rendered > properly in some glyphs/conjuncts. The problem is not too

[NTG-context] Incorrect rendering in Devanagari forms in some fonts

2021-09-01 Thread kauśika cittūr via ntg-context
Dear All, I have encountered a strange problem using certain Devanagari fonts for the Sanskrit languagein ConTeXt, wherein the rakaar ligatures are not rendered properly in some glyphs/conjuncts. The problem is not too easy to describe so please pardon this long email. The fonts I am using