[bug #57217] --disable-java and --disable-csharp have no effect

[Bruno Haible]

Follow-up Comment #3, bug #57217 (project gettext):

The options --disable-java and --disable-csharp are meant to get past possible
build hassles when you have broken Java or C# compilers or runtimes.

Their purpose is *not* to put you in a world where Java and C# don't exist.

> /usr/share/gettext/javaversion.class

This file is not built; it is already present as a binary blob in the source
tree.

> hello-java, hello-java-swing, ...

These are examples; on the same level as documentation. Just like it would be
confusing to have a documentation that mentions Java support in one place and
a documentation that doesn't mention Java support in another place of the web,
the same holds for the examples.

> I am also attaching a WIP patch which would remove CSharp and Java Support

This patch goes way off the limits of reasonable changes. Imagine a web server
that hosts a web application for translators; this web application runs
'msgfmt -c' locally on the server to check the translated PO files. With your
patch, PO files which mention Java or C# format strings could not be validated
any more - for no good reason. The Java and C# format string analyzers are
written in C; they don't run Java or C# code.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57217>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/