ELinks source code defines options like this:

        INIT_OPT_BOOL("protocol.http", N_("Use UI language as Accept-Language"),
                "accept_ui_language", 0, 1,
                N_("Request localised versions of documents from web-servers 
(using the\n"
                "Accept-Language header) using the language you have configured 
for\n"
                "ELinks' user-interface (this also affects navigator.language 
ECMAScript\n"
                "value available to scripts). Note that some see this as a 
potential\n"
                "security risk because it tells web-masters and the FBI 
sniffers about\n"
                "your language preference.")),

In the description of this option, the longest line is 71
characters.  However, when ELinks runs on a 80-column terminal,
with the standard src/setup.h, it apparently wraps option
descriptions to 60 columns.  The description then looks a bit
silly and consumes more vertical space than necessary:

|  Request localised versions of documents from web-servers      |
|  (using the                                                    |
|  Accept-Language header) using the language you have           |
|  configured for                                                |
|  ELinks' user-interface (this also affects navigator.language  |
|  ECMAScript                                                    |
|  value available to scripts). Note that some see this as a     |
|  potential                                                     |
|  security risk because it tells web-masters and the FBI        |
|  sniffers about                                                |
|  your language preference.                                     |
 
I propose we change most newlines to spaces in the option.desc strings:

        INIT_OPT_BOOL("protocol.http", N_("Use UI language as Accept-Language"),
                "accept_ui_language", 0, 1,
                N_("Request localised versions of documents from web-servers 
(using the "
                "Accept-Language header) using the language you have configured 
for "
                "ELinks' user-interface (this also affects navigator.language 
ECMAScript "
                "value available to scripts). Note that some see this as a 
potential "
                "security risk because it tells web-masters and the FBI 
sniffers about "
                "your language preference.")),

Of course, newlines that delimit paragraphs or list items would
be left in.  Then, the description would instead look like this:

|  Request localised versions of documents from web-servers      |
|  (using the Accept-Language header) using the language you     |
|  have configured for ELinks' user-interface (this also         |
|  affects navigator.language ECMAScript value available to      |
|  scripts). Note that some see this as a potential security     |
|  risk because it tells web-masters and the FBI sniffers about  |
|  your language preference.                                     |

This change would require rewriting the translations in po/
though, so I don't know whether it is appropriate for 0.12.GIT.
Currently, 0.12.GIT and 0.11.4rc0.GIT are very compatible with
respect to po files, and this in principle allows 0.11.* to
benefit from po/perl/msgaccel-check in 0.12.GIT.

Attachment: pgpxbAqqVZmNH.pgp
Description: PGP signature

_______________________________________________
elinks-dev mailing list
[email protected]
http://linuxfromscratch.org/mailman/listinfo/elinks-dev

Reply via email to