developer.jelix.org is not used any more and exists only for history. Post new tickets on the Github account.
developer.jelix.org n'est plus utilisée, et existe uniquement pour son historique. Postez les nouveaux tickets sur le compte github.

Opened 12 years ago

Closed 12 years ago

#473 closed bug (fixed)

Add default properties file in iso-8859-15

Reported by: laurentj Owned by: Julien
Priority: high Milestone: Jelix 1.0.3
Component: jelix Version: 1.0.2
Severity: normal Keywords:
Cc: Blocked By:
Blocking: Documentation needed: no
Hosting Provider: Php version:

Description

Some developers would like to use iso-8859-15. However, because of ticket #442 and ticket #95, there is an infinite loop when jelix doesn't find an error message in the right locale.

We should also provided a comment in jelix config, to warn the developer, to translate jelix messages if he want to change the locale or the charset. Until the ticket #95 is fixed.

Change History (3)

comment:1 Changed 12 years ago by Julien

  • Owner set to Julien

I think I can fix this while fixing #442, which quite depends on #95.

So as I'm already working on these both, I'm getting this one too.

I don't think we should duplicate jelix locales in iso-8859-15, but we should rather think about a configurable "last-chance" fallback charset, which will be iso-8859-1 or utf-8, just as I worked on the "last-chance" locale for old #95 patches.

comment:2 Changed 12 years ago by Julien

  • Status changed from new to assigned

comment:3 Changed 12 years ago by laurentj

  • Resolution set to fixed
  • Status changed from assigned to closed

I duplicated locales in iso-8859-1 because :

  • not sure that ticket #95 and #442 will be landed before the 1.0.3 release
  • if a properties file which doesn't correspond to the asked charset, is used, then the content of a web page will content characters which comes from different charset. So it is better to provide properties file for the most used charset (at least).

Landed in the 1.0.x branch and in the trunk.

Note: See TracTickets for help on using tickets.