Just get freeBSD which is a free operating system which OS X is completely based off of. The only differences are that it doesn't have the security vulnerabilities that OS X has because of those braindead developers meddling with a perfect system.
Braindead Mac Os 11
cbradney 2005-08-12 12:25 administrator ~0006091 | Yes, should be utf8 by default |
ringerc 2005-08-13 05:06 reporter ~0006097 | 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. |
cbradney 2005-08-13 22:03 administrator ~0006111 | Yes, ok, makes sense to assign to system default.. This one is for you ringerc? :=) |
ringerc 2005-08-14 08:32 reporter ~0006112 | Nothing to do - looks like that's the default behaviour already. Riku rocks. Tom32k, if you run: $ locale 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. |
TomK32 2005-08-14 09:12 reporter ~0006113 | 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. |
ringerc 2005-08-14 09:31 reporter ~0006114 | 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. |
ringerc 2005-09-09 02:10 reporter ~0006483 | 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. |
Kunda 2016-12-09 02:06 updater ~0042806 | @cbradney due to CTL merge can you double check on this issue to see if it's still relevant ? |
Braindead Mac Os X
cbradney 2005-08-12 12:25 administrator ~0006091 | Yes, should be utf8 by default |
ringerc 2005-08-13 05:06 reporter ~0006097 | 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. |
cbradney 2005-08-13 22:03 administrator ~0006111 | Yes, ok, makes sense to assign to system default.. This one is for you ringerc? :=) |
ringerc 2005-08-14 08:32 reporter ~0006112 | Nothing to do - looks like that's the default behaviour already. Riku rocks. Tom32k, if you run: $ locale 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. |
TomK32 2005-08-14 09:12 reporter ~0006113 | 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. |
ringerc 2005-08-14 09:31 reporter ~0006114 | 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. |
ringerc 2005-09-09 02:10 reporter ~0006483 | 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. |
Kunda 2016-12-09 02:06 updater ~0042806 | @cbradney due to CTL merge can you double check on this issue to see if it's still relevant ? |
Braindead Mac Os X
- Create systems that run on the Mac OS X platform, he suggests.Doctors, believed to be among the early adopters of computer technology, gravitated toward Macintosh computers for home use long before the average user, he theorizes, and they may be able to make the transition to computer use in the office more easily using a Mac rather than a PC.
- © Valve Corporation. All rights reserved. All trademarks are property of their respective owners in the US and other countries. Privacy Policy Legal Steam.
- Monitored Anesthesia Care (MAC) services (can be billed by a qualified nonphysician anesthetist or physician) G8. Deep complex complicated, or markedly invasive surgical procedures. Appended with an anesthesia code to indicate that the patient has a history of a severe cardiopulmonary condition. A normal healthy patient.
