View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0011648||Scribus||Import / Export||public||2013-07-08 12:09||2016-12-13 18:53|
|Target Version||Fixed in Version|
|Summary||0011648: UTF-8 detection via Byte Order Mark|
|Description||This is not a huge issue, but it could maybe be implemented better.|
Concerning bug 0006341, I would like to add:
It would be better if UTF-8 were automatically detected in text files, even if "system default" is selected. This can be done with the Byte Order Mark.
Some (or many) UTF-8 text files contain this at the beginning. When opening a UTF-8 file with system default in Scribus in version 1.4.2, the imported text starts with ï»¿ . It is highly unlikely that this is "real" language, therefore it can be safely assumed that the text would be a UTF-8 encoded file.
In a case where this is real text, the user can still manually select the correct encoding (e.g. ISO-8859-1).
This would be good because it is a nuisance to select the correct encoding before importing. Some people may also not be very apt in computing and actually may not know what an encoding is and that their file is encoded in UTF-8. It is therefore better if the importing process is automated as far as possible.
<Kunda> avox, question: what's the status of a bug like https://bugs.scribus.net/view.php?id=11648 in relation to the CTL work that's been done so far ? <avox> no relation. that bug concerns gettext functionality, not the rendering. <avox> should be an #+easyhack, too
||@avox is this something you have a moment to take a stab at ?|
|2013-07-08 12:09||Hellstorm||New Issue|
|2016-05-23 10:59||Kunda||Patch||=> No|
|2016-05-23 10:59||Kunda||Description Updated||View Revisions|
|2016-05-23 10:59||Kunda||Relationship added||related to 0006341|
|2016-05-23 11:00||Kunda||Tag Attached: #pending|
|2016-05-23 11:00||Kunda||Note Added: 0041334|
|2016-05-23 12:18||Kunda||Tag Attached: #easyhack|
|2016-05-23 12:18||Kunda||Note Added: 0041341|
|2016-12-13 18:53||Kunda||Note Added: 0042962|