Ticket #2198 (closed defect: fixed)

Opened 9 years ago

Last modified 9 years ago

Bad handling of default translation values

Reported by: gracinet Owned by: gracinet
Priority: P2 Milestone: CPS 3.5.1
Component: TranslationService Version: 3.5.1rc2
Severity: normal Keywords: calendar translate i18n unicode
Cc:

Description

Each time the translation service is been called, there's an optional defautlt value. In some cases, this value is plain string whereas the service's contract is to return unicode. The decoding charset is hardcoded iso-8859-15.

This happens for example often with such ZPT fragments:

  <span i18n:translate="">Already translated content</span>

And usually, a good enough fix downstream is to remove the i18n:translate (and that makes also for one miss less in poor catalog).

In some cases, it's not that easy to predict whereas the content is already translated. For example actions on CPSSharedCalendar's Calendar objects mix the two. This is currenly the only reported case where this bug has a visible effect.

Change History

comment:1 Changed 9 years ago by gracinet

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

Fixed two month ago

Note: See TracTickets for help on using tickets.