Force protocol.http.compression = 1 again?

Kalle Olavi Niemitalo <[email protected]>
Newsgroups gmane.comp.web.links
Message-ID <[email protected]>
Commit d4cec950ecadb0c19206f28b0bf9c6d8992bc1e7 added
to src/protocol/http/http.c:

#if !(defined(CONFIG_GZIP) || defined(CONFIG_BZIP2))
#define COMP_NOTE "\nNote that this ELinks version has been compiled without compression\n" \
		"support anyway. This option will have no effect.\n"
#else
#define COMP_NOTE
#endif
	INIT_OPT_BOOL("protocol.http", N_("Enable on-the-fly compression (experimental)"),
		"compression", 0, 1,
		N_("If enabled, the capability to receive compressed content (gzip and/or\n"
		"bzip2) is announced to the server, which usually sends the reply\n"
		"compressed, thus saving some bandwidth at slight CPU expense.\n"
		"HOWEVER, please note that the ELinks implementation is unfortunately very\n"
		"buggy and you may see incomplete pages, pages with garbage instead of\n"
		"content, etc.!" COMP_NOTE)),

The xgettext program of GNU Gettext 0.16.1 does not understand
that COMP_NOTE is a macro, and ignores it.  Only the variant
where COMP_NOTE is empty ends up in po/elinks.pot.  So if ELinks
is compiled without decompression support, it always describes
the option in English because this description will not have been
translated.

Anyway, instead of putting the both versions of the whole string
inside #if, I'd like to revert this commit altogether.
With Witek's latest changes, compression is not so experimental
any more, I think.  Can you find any site where it still fails?

_______________________________________________
elinks-dev mailing list
[email protected]
http://linuxfromscratch.org/mailman/listinfo/elinks-dev
signature.asc (application/pgp-signature, 188 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHwehPHm9IGt60eMgRAg1FAJ0R44fi88nwJ6wpDQs69wybR3syZACg12lA
rbUBRoJNJVjoHyf+M/ceUWo=
=136x
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.