Re: proposal for html manual cross links

>     ---    corresponding utf-8 characters (hyphen) 2010
>     --     corresponding utf-8 characters (em dash) 2014
> 
> I don't see the logic to transforming -- to emdash (should be endash if
> anything), and --- to three hyphen chars.  Or is that not what you're
> suggesting?

I made 2 mistakes here. First I exchanged -- and --- and second it was
endash and not hyphen.

I should have wrote, transform
--- to em dash U+2014, and
-- to en dash U+2013.

The idea behind that was to be able to discriminate between something like
@command{---} and --- in text. But after some thinking, I agree with you 
this is unneeded, as I think we don't want to have nodes differing only 
by that. Thus in any context ---, --, `` and '' should remain as is (and 
their characters, -, ` and ' encoded as other simple characters).

> For purposes of xrefs, I think it might be simplest to just leave -
> characters as themselves, untransformed (or transformed into 002d).
> However many -'s are in the input are in the output.  Wdyt?

You are right. In the end --- -> _002d_002d_002d

> used.  (Hey, maybe we would work 2602 umbrella or 2603 snowman into
> Texinfo somehow?  They're so cute. :)

@umbrella{} and @snowman{} would be right. Would need some ascii art in
info, though...


> How about transforming each ` into 2018 (left single quotation mark) and
> each ' into 2019 (right single quotation mark)?

Why not U+0060 and U+0027 ?

> Sorry to be unsure on this, but does this mean that to follow these
> links, either (a) the output must be monolithic (everything in one html
> file), or (b) javascript is required?  Is there any other way to implement?

Yes it means that. But notice that it was you who wanted that... My first
proposal was with one file per node...

> Finally, in general, I'm afraid I'm unclear about something fundamental:
> could you discuss a bit about the relationship between utf8 and URI
> escaping and how this will all work?  Is %XX hex representation used at
> some level (and if not, why not?)?  Could you show some concrete
> examples?

It is not %XX, because % is not accepted in a= or id= in xhtml, but instead
_XXXX.
For example
@node A  node --- with  @b{@^{H} in _'%} and @TeX{} @u{B} @point{}@enddots{}

Would lead to 
A-node-_002d_002d_002d-with-_0124-in_005f_0027_0025-and-Tex-B_0028-_2605_002e_002e_002e_002e

Notice the 
@enddots{} -> .... -> _002e_002e_002e_002e
And also
_ -> _005f
- -> _002d
A  node -> A-node
@u{B} -> B( -> B_0028

The last is because there is no corresponding unicode character.

As you can see there are only [A-Za-z-_] which is right for a= or id=
attributes in xhtml.

Pat
_______________________________________________
Texinfo home page: http://www.gnu.org/software/texinfo/
[email protected]
http://ff0.org/mailman/listinfo/texinfo-pretest