A new practical problem with invariant sections?
- To: email@example.com
- Cc: firstname.lastname@example.org
- Subject: A new practical problem with invariant sections?
- From: Anthony DeRobertis <email@example.com>
- Date: Sun, 12 Feb 2006 19:31:20 -0500
- Message-id: <[🔎] 43EFD358.firstname.lastname@example.org>
- In-reply-to: <20060209214821.GA5978@debian.inet>
- References: <E1F518q-0000M8email@example.com> <20060203151624.GJ4325@debian.inet> <20060207170452.GF7950@debian.inet> <firstname.lastname@example.org> <20060208085908.GA10240@debian.inet> <email@example.com> <20060208223330.GA10870@debian.inet> <firstname.lastname@example.org> <20060209211845.GC5830@debian.inet> <email@example.com> <20060209214821.GA5978@debian.inet>
Anton Zinoviev wrote:
> On Thu, Feb 09, 2006 at 01:19:58PM -0800, Thomas Bushnell BSG wrote:
> We have already discussed many examples, if you have some new example
> you are welcome to share it with us. :-)
I don't recall the following example being brought up.
Let's assume a manual, written by in Japanese, with Japanese invariant
sections. Someone translates this manual to English. The translator, of
course, leaves the Japanese invariant section intact.
Now, I'd like to download this (translated) manual and place it on a
portable device I own, so I can easily read it without killing a bunch
of trees. I think this is clearly a useful modification, and I think
that I should be able to do this for a DFSG-free work.
But, there is a problem: My portable device understands only ASCII, or
maybe ISO-8859-1 if I'm lucky (at least in the US, this is pretty
common). It doesn't understand UTF-8, Shift-JIS, etc. It is not
technically possible to keep the Japanese invariant section.
I believe this gives a notable, practicle reason why invariant sections
are not free.