[OS X TeX] Re: Latexian 1.0 Released

Claus Gerhardt claus.gerhardt at uni-heidelberg.de
Thu Dec 9 19:06:50 CET 2010


BBEdit and TextEdit (the newer versions) can detect the encoding of a plain text file when opening it and they are using the corresponding encoding when saving the file. In TextEdit's preferences the default encoding should be set to automatic.

Hence, TeXShop and other editors could have the same capabilities though a slight rewriting of the code might be necessary. The Developer's Documentation offers some references.

Claus


On Dec 9, 2010, at 16:59, Herbert Schulz wrote:

> 
> On Dec 9, 2010, at 9:47 AM, Alain Matthes wrote:
> 
>> 
>> Le 9 déc. 2010 à 14:08, Herbert Schulz a écrit :
>> 
>>> Howdy,
>>> 
>>> If you are using an editor that ``understands'' the encoding line (introduced by TeXShop and carried on by TeXworks)
>>> then the encoding used when opening the file will always be the one in that line. That way no matter what the default encoding is set for that Editor in its preferences the file will be used in the ``correct'' encoding.
>> 
>> Yes I understand, simply I always work with utf8 : html, css, tex and sty and cls files. 
>> 
>> Sometimes (often) somebody send me a file with latin1 encoding and with
>> \usepackage[latin1]{inputenc},  so in this case, I prefer change \usepackage[latin1]{inputenc}
>> with \usepackage[utf8]{inputenc} and I save the file with utf8 encoding. 
>> 
>> Now I don't understand why texshop is by default with applemac
>> 
>> OS X like Ubuntu  and Windows 7 are write with unicode. By default on linux now
>> the files are in utf8. apple.com is write with utf8
>> 
>> <!DOCTYPE html>
>> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang="en-US">
>> <head>
>> 	<meta http-equiv="content-type" content="text/html; charset=utf-8" />
>> 
>> All the great sites are now build with utf8
>> 
>> XeTeX logically is build to use utf8, luatex too
>> 
>> so it's harmful to keep on editing with applemac or latin1.
>> 
>> But this is personal and it's my point of view and I understand that
>> a lot of people prefers to continue with the same encoding to  avoid problem.
>> 
>> 
>> Best Regards
>> 
>> Alain Matthes
> 
> Howdy,
> 
> It has nothing to do with what is ``best'' (in the eyes of the beholder) but a fact of life that people use all sorts of editors and many of them, either from age or by design, don't ``know'' utf-8 and most of those folks have no idea what input encoding even is. It's all well and nice if someone sends you a latin1 encoded file and you translate it to utf-8 but what happens when you send it back to them and they open it up in their editor and get what appears like garbage? Remember collaboration is a two way street.
> 
> Good Luck,
> 
> Herb Schulz
> (herbs at wideopenwest dot com)
> 
> 
> 
> ----------- Please Consult the Following Before Posting -----------
> TeX FAQ: http://www.tex.ac.uk/faq
> List Reminders and Etiquette: http://email.esm.psu.edu/mac-tex/
> List Archive: http://tug.org/pipermail/macostex-archives/
> TeX on Mac OS X Website: http://mactex-wiki.tug.org/
> List Info: http://email.esm.psu.edu/mailman/listinfo/macosx-tex
> 
> 

----------- Please Consult the Following Before Posting -----------
TeX FAQ: http://www.tex.ac.uk/faq
List Reminders and Etiquette: http://email.esm.psu.edu/mac-tex/
List Archive: http://tug.org/pipermail/macostex-archives/
TeX on Mac OS X Website: http://mactex-wiki.tug.org/
List Info: http://email.esm.psu.edu/mailman/listinfo/macosx-tex




More information about the macostex-archives mailing list