[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fop-dev
Subject:    [jira] [Created] (FOP-2493) Fails to compile on non-utf8 locale with "error: unmappable character fo
From:       "Pawel Kraszewski (JIRA)" <jira () apache ! org>
Date:       2015-06-29 5:27:05
Message-ID: JIRA.12841243.1435555622000.40908.1435555625895 () Atlassian ! JIRA
[Download RAW message or body]

Pawel Kraszewski created FOP-2493:
-------------------------------------

             Summary: Fails to compile on non-utf8 locale with "error: unmappable \
character for encoding ASCII"  Key: FOP-2493
                 URL: https://issues.apache.org/jira/browse/FOP-2493
             Project: FOP
          Issue Type: Improvement
          Components: unqualified
    Affects Versions: 2.0
         Environment: Gentoo Linux, compilation environment has unset LC_ALL, LANG \
and LANGUAGE variables to force native (English) error messages during compilations  \
Reporter: Pawel Kraszewski  Priority: Minor


Compilation of FOP terminates with load of "error: unmappable character for encoding \
ASCII" caused by UTF-8 comments in the enironment with non-UTF8 locale.

My standard env for compiling (/etc/portage/bashrc) unsets LC_ALL, LANG and LANGUAGE \
variables, forcing a special POSIX locale (which is more or less equiv to \
en_US.iso8859-1). This is intentional, as my daily locale is pl_PL.utf8 and thus \
causes Polish error messages during compilation - which is very annoying when you \
need to report a bug on non-Polish bugtracker.

As FOP is the _only_ Java package bailing out due to this problem on my system, I \
guess other packages either don't use UTF8 comments or set some flag for Java \
compiler to ignore them.

Compilation completes with en_US.utf8 locale, yet some systems (eg OpenBSD) still \
don't widely use UTF8.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[prev in list] [next in list] [prev in thread] [next in thread]