Modify ↓
Ticket #548 (closed defect: wontfix)
Write configuration files in UTF-8
| Reported by: | dbaeyens@… | Owned by: | jsalamero@… |
|---|---|---|---|
| Milestone: | nice to have someday | Component: | base |
| Severity: | major | Keywords: | |
| Cc: |
Description (last modified by jsalamero@…) (diff)
(Jabber server dies if c2s.xml is not an UTF-8 file) Jabber server dies unexpectedly if configuration file c2s.xml is incorrectly encoded and has special chars. File encoded in UTF-8 works OK.
Attachments
Change History
comment:2 Changed 3 years ago by jacalvo@…
- Owner changed from juruen@… to jsalamero@…
- priority changed from normal to low
Jorge, can you confirm if this is still happening? Close the ticket if not.
comment:3 Changed 3 years ago by jsalamero@…
- Status changed from new to assigned
- Component changed from jabber to base
- Description modified (diff)
- Summary changed from Jabber server dies if c2s.xml is not an UTF-8 file to Write configuration files in UTF-8
adding binmode( $fh, ":utf8" ); to writeConfFileNoCheck in EBox/Module/Base.pm fixes this problem, we will commit this after 1.4.
not a problem of jabber itself, changed to base component.
Note: See
TracTickets for help on using
tickets.
I've confirmed this. When the configuration parameter <> is in Spanish, the c2s module says:
config_load: parse error at line 55: not well-formed (invalid token)
This line belongs to the element:
which is translated to the language which has been selected on language change.