Hello Justin, Justin B Rye schrieb am 13. Nov 2014 um 14:01
> > One possibility I see would be omitting the three options in the > > manpage as it suffices to find them additional documention which is > > delivered with the programm, i.e. MANUAL.html and README-files - which > > would need to a revision as well, by the way. > Actually I was just looking at the main README (datestamped only a > couple of years ago) and wondering what it means by > # * You can change URL description like 'http://hogege.net' in plain text > # into link to that URL. There is a function MARK_URL prepared for this conversion 1. Load plain text with an URL-like string $echo "abc http://debian.org xyz" | w3m 2. Press Esc-C to make w3m expect the command for this function (See README.func) 3. Type in MARK_URL <Enter> All URL-like strings in the buffer appear coloured and got anchor properties > Is that talking about "-o mark_all_pages=1" AKA "Treat URL-like > strings as links in all pages"? For me it has no apparent effect; if > we could work it out, it would be worth a mention in EXAMPLES (and if > not, it's one for reportbug). Yes, I think the function MARK_URL and mark_all_pages aim at the same goal. But, like you, I do not see any difference between mark_all_pages=0 and mark_all_pages=1. (There is as well a boolean configuration variable display_link, but it makes w3m showing target addresses in the status line of the program window as soon a the cursor touches a link.) > [...] > > a possible target would be > > > > nntp://news.aioe.org/comp.os.linux.networking > Yes, that's the server I was using to check the newsgroup really > existed, now that news.demon.co.uk is gone! I replaced the variable $NEWSSERVER with this concrete server name. By the way. Option -m works as described in the README you mentioned. "It has 'internet message mode', which determines the type of document from header. If the Content-Type: field of the document is text/html, that document is displayed as HTML document." I updated the explanation to option -m, erased "Implementation not verified" > >> What happened to the URL there? (Checks) Oh, it doesn't wrap it in > >> <plain ASCII angles>, it uses exotic ???mathematical ones???! > > These exotic parenthesis are a product of the groff-man-module and > > they are triggered by .UR. Shall I return to elements within the plain > > ascii character set? > "zgrep '\.UR' /usr/share/man/man*/*.gz" shows plenty of other > respectable man pages using it (often for email addresses too). I was > just surprised groff would bother for something like this when it's > quite happy to use ASCII apostrophes and so on. I should perhaps also > have highlighted the way groff handles quotes: apparently on your > system it respects the locale and renders \(lq \(rq as « » rather than > as ??? ???. In fact, here, these quotes are rendered as » «. That's fine. The german language team expects this type of quotation marks to be used. With respect to URLs, I still do not know whether I should use .UR and .UE. po4a accepts these codes for layout macros. With respect to addresses, I eliminated .MT and .ME macro codes as they caused troubles with po4a that shall deliver the template file for translations afterwards A version _6 is prepared here. Best regards Markus -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/20141113205506.GA3721@lune
