From: Jonny Grant <jg-hus3n9K41k0@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Non utf8 characters in page standards.7
Date: Sun, 12 Apr 2015 10:44:49 +0100 [thread overview]
Message-ID: <552A3E91.2000204@jguk.org> (raw)
In-Reply-To: <CAKgNAkhQKtQ-hDyi2NzWZ-icWwVP3ECc-NBXPy89Lu-UY=2a-w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 12/04/15 08:22, Michael Kerrisk (man-pages) wrote:
> On 9 October 2014 at 13:24, Jonny Grant <jg-hus3n9K41k0@public.gmane.org> wrote:
>> http://man7.org/linux/man-pages/man7/standards.7.html
>>
>> Hello
>> I noticed this page has come corrupt bytes in HTML source:
>>
>> under the auspices of the Austin group
>> ??<a href="http://www.opengroup.org/austin/">http://www.opengroup.org/austin/</a>??.
>>
>>
>> See ?? in my quote above.
>>
>> In hex, the bytes are E2 9F A8 and E2 9F A9
>>
>> Any ideas?
>>
>> There are other occurances with other links too. may affect other pages too
>
> These are the characters generated to the .UR/.UE macro pair (see groff_man(7)).
>
> Cheers,
>
> Michael
>
Hello Michael
Thank you for your reply.
Perhaps the .UR/.UE characters could be taken out?
⟨http://www.opengroup.org/austin/⟩
The COLOPHON URL link doesn't have them. Ideally IMHO English man pages
would have only ASCII characters
Of course, could use the regular < > characters
Regards, Jonny
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-04-12 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 11:24 Non utf8 characters in page standards.7 Jonny Grant
[not found] ` <CAGc9EveXMqUoTRDtjWE0h6rqXNcchdxghJZ9DMd0xR399aZMBQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-12 7:22 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkhQKtQ-hDyi2NzWZ-icWwVP3ECc-NBXPy89Lu-UY=2a-w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-12 9:44 ` Jonny Grant [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=552A3E91.2000204@jguk.org \
--to=jg-hus3n9k41k0@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.