• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Writing Text files
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Writing Text files


  • Subject: Re: Writing Text files
  • From: Andreas Kiel <email@hidden>
  • Date: Tue, 20 Nov 2012 10:47:06 +0100

Thanks again to all.

Finally Rainer is right.
I won't change anything with my app (as by default it saves UTF-8) and people have to take care whether their app can read it correctly.

Thanks
Andreas

On Nov 18, 2012, at 1:50 AM, Rainer Standke wrote:

> I think the bottom line is to save everything in UTF-8, especially when it comes to XMLs...
>
> Rainer
>
>
> On Nov 17, 2012, at 10:18, John Delacour <email@hidden> wrote:
>
>> On 17/11/12 15:16, Andreas Kiel wrote:
>>> The problem is that the application is used by many people on many machines.
>>> So on each individual machine it works fine in most cases - unfortunately only in most but not all.
>>>
>>> ... For one of them it will be misinterpreted in Apple's DVD SP - even though both use the same version of the app. And there is no way to set up decoding for the latter app.
>>> Another user with a different version of the OS (other stuff the same) creates the same file with my app - but the other people (first two) will have problems with this text file.
>>>
>>> So in any case you have to do a kind of "force encoding" when opening the text file and re-save it.
>>>
>>> This behavior does not apply only to the text files created by my app. You can create a text file in TextEdit with some special characters, save it - and the behavior is the same.
>>
>> The simple fact is that no matter what legacy encoding (perish the thought!) you give to the file, no application will know what the encoding is, and the same goes for UTF-8.  If DVD Studio Pro can't read UTF-8 then they should use an application that belongs to the 21st century instead.  All text editors in the modern era should be set to default to UTF-8 and if your users have chosen for some odd reason to set their default encoding to some obsolete so-miscalled "MacRoman" or "iso-8859-1" or anything else then that's their lookout.
>>
>> JD
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> applescriptobjc-dev mailing list      (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> applescriptobjc-dev mailing list      (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
applescriptobjc-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Writing Text files (From: Andreas Kiel <email@hidden>)
 >Re: Writing Text files (From: John Delacour <email@hidden>)
 >Re: Writing Text files (From: Andreas Kiel <email@hidden>)
 >Re: Writing Text files (From: John Delacour <email@hidden>)
 >Re: Writing Text files (From: Rainer Standke <email@hidden>)

  • Prev by Date: Re: Writing Text files
  • Next by Date: [ANN] Update to AppleScriptObjC Explorer
  • Previous by thread: Re: Writing Text files
  • Next by thread: [ANN] Update to AppleScriptObjC Explorer
  • Index(es):
    • Date
    • Thread