[
https://issues.apache.org/jira/browse/FELIX-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922466#comment-13922466
]
Alexandre Cartapanis edited comment on FELIX-4416 at 3/6/14 1:05 PM:
---------------------------------------------------------------------
Yes, but in this case, it will use the system.fileEncoding properties, wich i
can specify at startup...
Or even through a specific karaf properties, something like
"felix.fileinstall.encoding", and still use ISO-9885 as default
was (Author: acartapanis):
Yes, but in this case, it will use the system.fileEncoding properties, wich i
can specify at startup...
> CFG file encoding
> -----------------
>
> Key: FELIX-4416
> URL: https://issues.apache.org/jira/browse/FELIX-4416
> Project: Felix
> Issue Type: Bug
> Components: File Install
> Affects Versions: fileinstall-3.2.6
> Environment: Karaf 2.3.3
> Reporter: Alexandre Cartapanis
>
> FileInstall always use ISO-8859-1 for reading cfg file, even if the CFG file
> is not encoded in ISO-8859-1.
> So when the CFG file contains non-ascii characters, those characters are
> "transformed" during parsing. Typically my file contains the line
> "error.message.210=Identifiant d'entité cible invalide" (without the "") but
> after FileInstall parsing, my string is transformed into "Identifiant
> d'entité cible invalide" (still without the "").
> The org.apache.felix.utils.properties.Properties class has a default encoding
> defined to ISO-8859-1,which is always used whatever the actual file encoding
> is.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
