On 6 February 2016 at 00:50, Karl Berry wrote:
> I believe that it does not follow the uri in the document DOCTYPE
> definition
>
> Well, evidently not, since
> http://www.gnu.org/software/texinfo/dtd/6.0/texinfo.dtd is found just
> fine when visited directly. Unless there is an error in
On 02/05/2016 04:29 PM, Karl Berry wrote:
I can't figure it out from info info-stnd cus.
Perhaps that node should explicitly say that only keystrokes passed from
the terminal emulator can be bound, i.e., that info is not an X
application and therefore cannot see non-ASCII things like Shif
On 02/05/2016 04:50 PM, Karl Berry wrote:
I believe that it does not follow the uri in the document DOCTYPE
definition
Well, evidently not, since
http://www.gnu.org/software/texinfo/dtd/6.0/texinfo.dtd is found just
fine when visited directly. Unless there is an error in the dtd
pre
I believe that it does not follow the uri in the document DOCTYPE
definition
Well, evidently not, since
http://www.gnu.org/software/texinfo/dtd/6.0/texinfo.dtd is found just
fine when visited directly. Unless there is an error in the dtd
preventing it from being applied, which is certain
I can't figure it out from info info-stnd cus.
Perhaps that node should explicitly say that only keystrokes passed from
the terminal emulator can be bound, i.e., that info is not an X
application and therefore cannot see non-ASCII things like Shift+Space
or CTRL- or whatever. -k
On Thu, Feb 4, 2016, at 21:18, Gavin Smith wrote:
> On 4 February 2016 at 20:06, Benno Schulenberg wrote:
> > So the request is: could Shift+Space please do a backward scroll,
> > the thing that some users will expect from a text browser?
>
> I don't think it's possible. The terminal emulator wo
> Will this patch be okay to go in without the other patches? I want to
> take more time to review the encoding-related patches.
If I understand correctly, it\'s okay.
There is no problem with the us-ascii strings.
In the case of non-ascii strings, PDF outline strings are broken.
It is same behav
