Thank you for your advice.
> By the way, I don't understand ChangeLog entries like this:
>
> 2016-03-23 Masamichi Hosoda
> * doc/texinfo.tex (\pdfgettoks, \pdfaddtokens, \adn, \poptoks,
> \maketoks, \makelink, \pdflink, \done): New Macro.
> Add XeTeX PD
On 26 March 2016 at 19:34, Joe Dalton wrote:
> Is there a difference between closing brace and close brace?
Forgot to answer this, there's no difference, and in my opinion we
should use "closing brace" consistently.
On 26 March 2016 at 19:34, Joe Dalton wrote:
> Hi, I have finished the Danish translation on TP for texinfo. But a few
> strings is missing clarification. I hope you can help me.
>
> It's about the term brace. A number of strings includes this term.
>
> What specific characters is the reference f
Hi, I have finished the Danish translation on TP for texinfo. But a few strings
is missing clarification. I hope you can help me.
It's about the term brace. A number of strings includes this term.
What specific characters is the reference for is it {} (or perhaps () or []).
Or perhaps a differe
On 16 June 2015 at 01:26, Gavin Smith wrote:
> On 15 June 2015 at 18:37, Gavin Smith wrote:
>> Another idea which I had while writing this email, which I haven't
>> explored yet, is for the parser to be able to return in the tree it
>> creates elements that are "free variables", which could be su
On 6 March 2016 at 09:41, Gavin Smith wrote:
> On 5 March 2016 at 17:38, Jack Howarth
> wrote:
>> When building texinfo 6.1 on x86_64-apple-darwin15, the following
>> correction is required...
>>
>> --- tp/Texinfo/Convert/XSParagraph/configure.ac.orig 2016-03-05
>> 12:31:24.0 -0500
>> ++
On 26 March 2016 at 00:50, Karl Berry wrote:
> I really don't understand the code in \pdfgettoks in texinfo.tex.
>
> Not sure if this is still relevant, but it's not just about page
> numbers, is it? I thought that crazy stuff was at least partly about
> handling brace characters that should
