View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002421||Scribus||Story Editor / Text Frames||public||2005-08-11 15:53||2017-03-01 22:09|
|Platform||MacOSX||OS||MacOSX||OS Version||10.4 Tiger|
|Target Version||1.5.5||Fixed in Version|
|Summary||0002421: Default charset for text import on Mac OS X|
|Description||after copy'n'paste under mac ain't working perfect i often import text regularly and wish utf-8 to be default or at least the form to remember which codeset was used last time.|
||Yes, should be utf8 by default|
I'd argue it should use the system locale by default, actually.
If your system is set to ISO-8859-15, you'd expect that a file you just created in the default charset would be imported unmangled. If we force a UTF-8 default, that won't happen.
It'd be *nice* if everyone used utf-8, but the system locale's charset is probably the more correct choice of default. A pref to override it might not be a bad plan though.
||Yes, ok, makes sense to assign to system default.. This one is for you ringerc? :=)|
Nothing to do - looks like that's the default behaviour already. Riku rocks.
Tom32k, if you run:
what is the output? My guess is that you're not in a UTF-8 locale. I'd expect Mac OS X to use a UTF-8 locale by default, but perhaps its POSIX subsystem does not for some reason.
I'll need to look at some Apple specs, but if Mac GUI apps work in UTF-8 by convention then Scribus should do the same on Mac OS X as a special case.
nothing we could work with i think.
there's no /etc/locale* anyways. it would be enough for me if scribus would remember the last charset used.
Yes - Mac OS X's locale settings appear to be completely braindead. Woohoo. Those settings imply 7-bit ASCII (not even ISO-8859-1). We're going to have to ignore them I suspect.
My personal opinion is that "last charset used" is the wrong behaviour for most people. You'll generally be working with files in a given encoding, with others being an unusual exception. Personally, I'd be surprised if the setting was remembered, as the next time I went to import a text file I'd get mangled text.
A pref might be the way to go. Sound reasonable?
I couldn't find any recommendation on default character encoding in the Apple developer docs when I did a quick search, but will have to look in more detail later. If they have a recommended encoding we should default to that. Otherwise, whatever most other apps on the platform default to - hopefully UTF-8.
Unassigning. I won't get to this for a while, so if anyone else wants to pick it up, free free.
Patches also accepted, so long as they fit the coding style, are platform independent, and are sensibly designed. If anybody's thinkig of working on it, it might be best to drop by IRC or post here with your implementation ideas.
||@cbradney due to CTL merge can you double check on this issue to see if it's still relevant ?|
|2005-08-11 15:53||TomK32||New Issue|
|2005-08-12 12:25||cbradney||Summary||default charset für text-import => Default charset for text import|
|2005-08-12 12:25||cbradney||Note Added: 0006091|
||Note Added: 0006097|
||Status||new => acknowledged|
|2005-08-13 22:03||cbradney||Note Added: 0006111|
||Status||acknowledged => assigned|
||Assigned To||=> ringerc|
||Note Added: 0006112|
|2005-08-14 09:12||TomK32||Note Added: 0006113|
||Note Added: 0006114|
||Note Added: 0006483|
||Assigned To||ringerc =>|
||Status||assigned => acknowledged|
||Summary||Default charset for text import => Default charset for text import on Mac OS X|
|2015-09-17 20:08||Kunda||Category||Story Editor / Text Frames => Story Ed/Txt Frames|
|2015-09-17 20:12||Kunda||Category||Story Ed/Txt Frames => Story Editor / Text Frames|
|2016-12-09 02:06||Kunda||Note Added: 0042806|
|2016-12-09 02:06||Kunda||Tag Attached: #pending|
|2016-12-13 01:02||Kunda||Target Version||=> 1.5.3|
|2016-12-13 01:02||Kunda||Patch||=> No|
|2017-03-01 22:09||cbradney||Target Version||1.5.3 => 1.5.5|