You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2017/09/08 08:14:00 UTC

[jira] [Updated] (FELIX-4416) Ability to specify an encoding for config files

     [ https://issues.apache.org/jira/browse/FELIX-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet updated FELIX-4416:
-----------------------------------
    Summary: Ability to specify an encoding for config files  (was: CFG file encoding)

> Ability to specify an encoding for config files
> -----------------------------------------------
>
>                 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
>             Fix For: fileinstall-3.6.2
>
>
> 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.4.14#64029)