Project

General

Profile

Bug #4758

glossaire csv export with international chars do not work

Added by Laurent Opprecht over 7 years ago. Updated over 7 years ago.

Status:
Bug resolved
Priority:
Normal
Category:
-
Target version:
Start date:
16/05/2012
Due date:
% Done:

100%

Estimated time:
Complexity:
Normal
SCRUM pts - complexity:
?

Description

The output is not correctly displayed.

In Excel international chars are not correctly interpreted
In other applications html entities are not displayed as plain text


Related issues

Related to Chamilo LMS - Feature #3857: Import glossary itemsBug resolved31/08/2011

Actions

History

#1

Updated by Laurent Opprecht over 7 years ago

Two issues:

utf8 encoding
html entities

#2

Updated by Laurent Opprecht over 7 years ago

Looks like Excel requires the byte order mark: "\xEF\xBB\xBF"

#3

Updated by Marko Kastelic over 7 years ago

this is corrent. If the BOM is not specified at the begining of the file, MS (depends on OS version) can use it's ANSI (CP somenumber: default interface language encoding) or try to guess encoding from the content of the file (Windows 7 at least). UTF-8 intepretation is usualy fixed with inserting BOM at the begging of the file. This is not related to the excel only but to other tools too (eq: notepad, ...). Just check with Cacl too.
edit: for the reference only phpExcel http://phpexcel.codeplex.com/ (LGPL)

#4

Updated by Laurent Opprecht over 7 years ago

  • Assignee set to Laurent Opprecht
#5

Updated by Laurent Opprecht over 7 years ago

Note: translating html entities to utf8 is fine but it is not possible to translate html tags without changing formatting.

#6

Updated by Laurent Opprecht over 7 years ago

  • Status changed from New to Needs testing
  • % Done changed from 0 to 90

Note that I have added a folder under inc/lib. I believe this is fine since it contains utility functions only - i.e. not related to Chamilo as opposed to the zombie classes for example. Plus putting right under inc/lib would have generated too much noise.

#7

Updated by Julio Montoya over 7 years ago

Laurent Opprecht wrote:

Note that I have added a folder under inc/lib. I believe this is fine since it contains utility functions only - i.e. not related to Chamilo as opposed to the zombie classes for example. Plus putting right under inc/lib would have generated too much noise.

what's the name of the folder? try to add the "#4758" in your commits

#8

Updated by Laurent Opprecht over 7 years ago

That's system/io and system/text. I believe the number is in the commit.

#9

Updated by Yannick Warnier over 7 years ago

  • Target version set to 1.9 Beta
#10

Updated by Yannick Warnier over 7 years ago

Marko Kastelic wrote:

edit: for the reference only phpExcel http://phpexcel.codeplex.com/ (LGPL)

PhpExcel is a very heavy library. I'm not too keen on including it, but if we really need it, we'll have to make some space for it :-)

#11

Updated by Yannick Warnier over 7 years ago

I think there is a little misunderstanding here (even for Julio). In order for Redmine to make the link with Mercurial (Google Code), you have to use the task number with a prefix:
  • "see #4758" or
  • "refs #4758" or
  • "closes #4758" (this one closes the task as well!) or
  • "fixes #4758" (this one closes the task as well!) or
  • "fixes #4758" (this one closes the task as well!)

So it's not just the task ID. Please make sure you do that correctly, otherwise the link is not created (and I promise you that I use these a lot when something happens one year later that is similar to a previous bug).

#12

Updated by Yannick Warnier over 7 years ago

This is the corresponding commit:
http://code.google.com/p/chamilo/source/detail?r=87a9ec8aec6785d025fb4e668af7578264487a1f&repo=classic&path=/main/inc/lib/system/text/utf8_decoder.class.php
Exceptionally, Laurent, as you reported the bug, you can close it as well if you think that fixes it. It is difficult for me to test and make sure it is closed because in your report you didn't indicate examples of the characters that wouldn't be managed correctly, so I'm not sure what I should try out.

#13

Updated by Laurent Opprecht over 7 years ago

  • Status changed from Needs testing to Bug resolved
  • % Done changed from 90 to 100

This was about html entities not been translated to utf8 - i.e. &eacute instead of é, etc. For me this is good.

Also available in: Atom PDF