[MAGNOLIA-1406] Some calendar translation files need to be restored to UTF8 Created: 26/Feb/07 Updated: 23/Jan/13 Resolved: 30/Nov/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | admininterface, gui |
| Affects Version/s: | 3.0.1 |
| Fix Version/s: | 3.5 |
| Type: | Task | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Vivian Steller |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
Some of the calendar language files are just garbage'd... |
| Comments |
| Comment by Guillaume Pichenot [ 26/Feb/07 ] |
|
While patching the fr file to work, I thought about that particular issue, and concluded that it could be a better solution (at least, for roman alphabets), to HTML-escape every special caracter that has a HTML entity.
Now of course, there may be downsides to this approach, for example :
That's just food for thoughts on the practical side of this issue. |
| Comment by Magnolia International [ 26/Feb/07 ] |
|
note that we're talking javascript here, so depending on how the strings are used, the html entities might be irrelevant (try them in an alert box...) if we're careful about what we commit, utf8 should be easier. Even in french, i have a hard time proof reading, with just a couple of accents. I can't even start to imagine i had to do that for chinese |
| Comment by Guillaume Pichenot [ 13/Mar/07 ] |
|
You're probably right, Grégory. So I made this patch for two reasons :
|
| Comment by Vivian Steller [ 30/Nov/07 ] |
|
updated all translation files with latest from http://jscalendar.cvs.sourceforge.net/jscalendar/jscalendar/lang/. Explicitely converted spanish (es) file to UTF-8. Rechecked french, czech, german translations. |