<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I have observed that the line \usepackage[portuguese]{babel} typesets well, but \usepackage[latin1]{inputenc} or \usepackage[applemac]{inputenc}<div><div>even recognize the edited latin characters when typeset.</div><div>Please, can someone help me?</div><div>regards,</div><div>Sebastian Nascimento</div><div><br></div><div><br></div><div><br></div><div><div>On Sep 12, 2011, at 4:00 PM, <<a href="mailto:macosx-tex-request@email.esm.psu.edu">macosx-tex-request@email.esm.psu.edu</a>> <<a href="mailto:macosx-tex-request@email.esm.psu.edu">macosx-tex-request@email.esm.psu.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Send MacOSX-TeX mailing list submissions to<br><span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:macosx-tex@email.esm.psu.edu">macosx-tex@email.esm.psu.edu</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br><span class="Apple-tab-span" style="white-space:pre"> </span>http://email.esm.psu.edu/mailman/listinfo/macosx-tex<br>or, via email, send a message with subject or body 'help' to<br><span class="Apple-tab-span" style="white-space:pre"> </span>macosx-tex-request@email.esm.psu.edu<br><br>You can reach the person managing the list at<br><span class="Apple-tab-span" style="white-space:pre"> </span>macosx-tex-owner@email.esm.psu.edu<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of MacOSX-TeX digest..."<br><br><br>Today's Topics:<br><br> 1. Re: TeXShop 3 and text encoding on Lion - serious problems<br> (Ross Moore)<br> 2. Re: TS 3.06 crash on Lion (Themis Matsoukas)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Mon, 12 Sep 2011 06:34:20 +1000<br>From: Ross Moore <ross.moore@mq.edu.au><br>Subject: Re: [OS X TeX] TeXShop 3 and text encoding on Lion - serious<br><span class="Apple-tab-span" style="white-space:pre"> </span>problems<br>To: TeX on Mac OS X Mailing List <macosx-tex@email.esm.psu.edu><br>Message-ID: <933F9130-9D79-4280-A2E9-B5D30C311BB3@mq.edu.au><br>Content-Type: text/plain;<span class="Apple-tab-span" style="white-space:pre"> </span>charset=utf-8<br><br>Hello Luis,<br><br>On 11/09/2011, at 8:39 PM, Luis Sequeira <lfsequeira@gmail.com> wrote:<br><br><blockquote type="cite">I am experiencing serious issues with TeXShop and text encodings in Lion. <br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">My wife sent me a tex file written using the mac roman encoding. I opened it, selecting the encoding, as usual, from the dropdown menu in the open dialog. <br></blockquote><blockquote type="cite">The accented characters don't appear. The file typesets correctly - using \usepackage[applemac]{inputenc} - which confirms that the file itself is not corrupted and is using the right encoding.<br></blockquote><br>The file is just a byte stream, and the \usepackage[applemac]{inputenc} tells LaTeX how to deal with the characters outside the ASCII range.<br><br><blockquote type="cite">Making changes to the file causes havoc, as would be expected - now new accented characters that are input show up correctly in the source but not in the pdf - suggesting that TeXShop is using a different encoding than it is was supposed to.<br></blockquote><br>No. Adding new accented characters to this file is a really bad idea.<br>I do not believe that the file encoding tells your Mac software to translate bytes to a different encoding upon input; maybe it does for UTF8 or UTF16, but certainly not for other legacy encodings. <br><br><blockquote type="cite"><br></blockquote><blockquote type="cite">I then converted the file to utf8 (using Smultron) and replaced applemac by utf8 (\usepackage[utf8]{inputenc}) - and again opened the file from the open dialog, selecting utf8 encoding.<br></blockquote><br>Is this the original file, or with the extra typed characters?<br>Personally, I would look at the converted file with a command-line editor, such as vi , to see whether the bytes have really been converted correctly. The physical file size should have increased slightly, as UTF8 requires a byte sequence for each non-ASCII character.<br><br><blockquote type="cite">In this encoding the accented characters still did not display correctly, but still the file typeset ok.<br></blockquote><br>Display correctly in which software? TeXshop's editor?<br>What does it look like in other Mac editing software, such as TextEdit?<br>Maybe there is a memory of the old encoding.<br>Did you change the file's name for the new encoding?<br><br><blockquote type="cite"><br></blockquote><blockquote type="cite">Both versions of the file (using macroman or unicode) display and typeset correctly in TeXShop 2 on Leopard.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I think this is a serious bug in TeXShop in Lion (I am using 3.04, but the same problem occurs in 2.29 in Lion). <br></blockquote><blockquote type="cite">Smultron in Lion (although an old version from 2009) has no problem handling the files. TeXShop 2 in Leopard also has no problem. The same flle displays and typesets perfectly in my wife's iBook.<br></blockquote><br>That is disturbing, that newer software is not doing the same as in older versions.<br>I'd guess that the change is in more recent Apple libraries, perhaps dropping some aspects of the support for really old methods.<br><br>What happens if you take your wife's file and convert to UTF8 using iconv on the command-line, before ever opening it in any window-based program?<br>I'd expect that now everything will look right in all programs. (touchwood)<br><br><blockquote type="cite"><br></blockquote><blockquote type="cite">For now this makes working with accented characters (which are abundant in my language, Portuguese) a nuisance. I am reverting to writing stuff like \'a for รก for the first time in years.<br></blockquote><br>Knuth's original methods show their value!<br><br><blockquote type="cite"><br></blockquote><blockquote type="cite">Luis Sequeira<br></blockquote><br>Hope this helps,<br><br> Ross<br><br>------------------------------<br><br>Message: 2<br>Date: Sun, 11 Sep 2011 17:00:37 -0400<br>From: Themis Matsoukas <tmatsoukas@me.com><br>Subject: Re: [OS X TeX] TS 3.06 crash on Lion<br>To: TeX on Mac OS X Mailing List <macosx-tex@email.esm.psu.edu><br>Message-ID: <42CD3FCD-5298-47DA-BE10-2C477CDA5994@me.com><br>Content-Type: text/plain; CHARSET=US-ASCII<br><br>On Sep 11, 2011, at 11:23 AM, Yusuke TERADA wrote:<br><br><blockquote type="cite">I was able to reproduce this issue.<br></blockquote><blockquote type="cite">I investigated the cause, and it turned out that this issue is caused from lack of the definition of fileNameExtensionForType:saveOperation: in TSDocument.m.<br></blockquote><blockquote type="cite">By inserting the definition, this issue seemed to be solved.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Here is the modified TeXShop binary: http://dl.dropbox.com/u/5807100/TeXShop3.06Terada.dmg<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">And the modified source: http://dl.dropbox.com/u/5807100/TSDocument.m<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Please test this. <br></blockquote><br>Thanks - the modified version has fixed this problem.<br><br>I appreciate the quick response -there should be a donate button on TS's homepage.<br><br>Themis<br><br><br><br>------------------------------<br><br><br>-------------------------- Helpful Info --------------------------<br>TeX FAQ: http://www.tex.ac.uk/faq<br>List Reminders and Etiquette: http://email.esm.psu.edu/mac-tex/<br>List Info: http://email.esm.psu.edu/mailman/listinfo/macosx-tex<br>List Archive: http://tug.org/pipermail/macostex-archives/<br>TeX on Mac OS X Website: http://mactex-wiki.tug.org/<br><br><br><br>End of MacOSX-TeX Digest, Vol 47, Issue 9<br>*****************************************<br></div></blockquote></div><br><div>
<span><img height="118" width="393" id="9f9a58db-7d12-4107-9ce0-f7236fc6bb59" apple-width="yes" apple-height="yes" src="cid:920C8366-1F26-4126-9413-A0E0D5DCBE3F@lan"></span>
</div>
<br></div></body></html>