From MacOSX-TeX@email.esm.psu.edu Mon Oct 14 20:09:21 2002
Received: from email.esm.psu.edu ([130.203.247.204]) by engrmail1.engr.psu.edu with Microsoft SMTPSVC(5.0.2195.5329);
Mon, 14 Oct 2002 20:00:27 -0400
Date: Mon, 14 Oct 2002 20:00:01 -0400
Subject: MacOSX-TeX Digest #454 - 10/14/02
From: "TeX on Mac OS X Mailing List"
To: "TeX on Mac OS X Mailing List"
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Sender:
Precedence: Bulk
List-Software: LetterRip Pro 3.0.7 by Fog City Software, Inc.
List-Subscribe:
List-Digest:
List-Unsubscribe:
Return-Path: MacOSX-TeX@email.esm.psu.edu
Message-ID:
X-OriginalArrivalTime: 15 Oct 2002 00:00:27.0924 (UTC) FILETIME=[DE979D40:01C273DD]
MacOSX-TeX Digest #454 - Monday, October 14, 2002
Re: [OS X TeX] Math font wierdness
by "Jean-Claude DE SOZA"
Re: [OS X TeX] Unicode and TexShop, iTexMac
by "J=E9r=F4me Laurens"
Re: [OS X TeX] TexShop & Textures
by "J=E9r=F4me Laurens"
Re: [OS X TeX] Unicode and TexShop, iTexMac
by "Cyril Niklaus"
Where is my help file?
by "Claus Atzenbeck"
Re: [OS X TeX] Where is my help file?
by "Nigel King"
Re: [OS X TeX] Where is my help file?
by "Claus Atzenbeck"
Math fonts wierdness: UPDATE
by "Andrew Farmer"
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Math font wierdness
From: "Jean-Claude DE SOZA"
Date: Mon, 14 Oct 2002 06:22:27 +0200
It's true that the bottom of some symbols appears to be truncated in=20
the previewer and if you try to print the pdf file in TeXShop you'll=20
see the same truncated symbols but if you do it in Acrobat Reader, all=20=
is fine.
So it is not a driver problem but an Apple problem.
Two weeks ago, I submitted the problem to my brother who transmitted it=20=
to Apple and here is the answer :
> Thanks for the PDF file. It turns out this is a known issue, it has =
to
> do with certain fonts that have incorrect bounding boxes for some
> chars. The fix lies in clipping to the computed glyph size instead of
> relying on the bounding box numbers. I've cc'd myself to the Radar =
bug
> and I'd be happy to let you know when the fix gets released.
Jean-Claude DE SOZA
Le dimanche, 13 oct 2002, =E0 22:58 Europe/Paris, Andrew Farmer a =E9crit =
:
> At 13 October, 2002 Themis Matsoukas wrote:
>> This is a problem with the previewer, not with the pdf file. The
>> bottom of some symbols (integrals, large parentheses) appears=20
>> truncated
>> in the TeXShop previewer, if these symbols extend beyond the visible
>> part of the page (a problem at high magnifications). If you scroll to
>> bring the full equation in view, the previewer does not fully refresh
>> the page and these symbols look like they are missing their bottom. =
To
>> force the previewer to refresh, scroll to the position you want, go=20=
>> one
>> page back (or forward), then return to the page you want. The symbols
>> should look fine. Or, decrease the magnification so that you see the
>> full page. This solution works in OS X 10.1.5. Still, the file prints
>> correctly regardless of how it looks on the screen.
>
> Not true. The printed version looks incorrect as well.
>
> For anybody who wants to test this problem, here's a test file:
>
> --- BEGIN TEST FILE ---
> \documentclass[12pt]{article}
> \usepackage{amsmath}\usepackage{amssymb}
> \begin{document}
> $$\sqrt{\dfrac{1}{2}}$$ \\ $$\left(\dfrac{1}{2}\right)$$
> \end{document}
> --- END TEST FILE ---
>
> The printed version has truncated radical and parentheses when printed
> from TeXShop or Preview. However, Acrobat views and prints this just
> fine.
>
> Ugh. Hope this isn't a NSPDFRepresentation bug.
>
> --=20
> Andrew Farmer
> andfarm@thibs.menloschool.org
>
> -----------------------------------------------------
> Mac TeX info, resources, and news can be found at:
>
> -----------------------------------------------------
> List archives can be found at:
>
> Threaded list archives can be found at:
>
> -----------------------------------------------------
> See message headers for list info.
> -----------------------------------------------------
>
>
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Unicode and TexShop, iTexMac
From: "J=E9r=F4me Laurens"
Date: Mon, 14 Oct 2002 10:07:28 +0200
--Apple-Mail-2-441074104
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=3DUTF-8;
format=3Dflowed
Le samedi, 12 oct 2002, =3DC3=3DA0 06:47 Europe/Zurich, Cyril Niklaus a =
=3D
=3DC3=3DA9crit :
> Hi all,
> Having recently decided to "waste" time banging my head on unicode =
and=3D20=3D
> tex (and some perl to go back and forth between the two; =
unsuccessfull=3D20=3D
> until now --perl newbie--, so if someone has an idea, please share), =
I=3D20=3D
> did reformat one Sanskrit text from the normal TeX format to using=3D20
> directly letters with diacriticals (ie \=3D3D{a} to =3DC4=3D81 etc).
> I had to do this in TextEdit as neither TeXShop or iTeXMac do =
display=3D20=3D
> properly UTF-8, nor give the option to use UTF-8. They do compile=3D20
> properly the text though.
> Why is that so, and are there plans to bring UTF-8 support to these=3D20
> editors? Is it still too much of a mess at the moment?
> Cheers,
Please notice that iTeXMac provides support for UTF-8, and all other=3D20
encodings in Mac OS X: there is help available, I hope
Mac Roman
ISO 8859-1
Windows Latin 1
UTF-8
Mac Central European Roman
should be saved at
~/Library/Application\ Support/iTeXMac/General/Encodings.plist
If you want i can send this file as an attached document (I think the=3D20
list don't accept attached documents)
--Apple-Mail-2-441074104
Content-Transfer-Encoding: quoted-printable
Content-Type: text/enriched;
charset=3DUTF-8
Le samedi, 12 oct 2002, =3DC3=3DA0 06:47 Europe/Zurich, Cyril Niklaus a =
=3D
=3DC3=3DA9crit :
Hi all,
Having recently decided to "waste" time banging my head on unicode and
tex (and some perl to go back and forth between the two; unsuccessfull
until now --perl newbie--, so if someone has an idea, please share), I
did reformat one Sanskrit text from the normal TeX format to using
directly letters with diacriticals (ie \=3D3D{a} to =3DC4=3D81 etc).
I had to do this in TextEdit as neither TeXShop or iTeXMac do display
properly UTF-8, nor give the option to use UTF-8. They do compile
properly the text though.
Why is that so, and are there plans to bring UTF-8 support to these
editors? Is it still too much of a mess at the moment?
Cheers,
Please notice that iTeXMac provides support for UTF-8, and all other
encodings in Mac OS X: there is help available, I hope
<
<
<
<
<Mac Roman<
<ISO 8859-1<
<Windows Latin 1<
<UTF-8<
<<
<Mac Central European Roman<
<
<
should be saved at
~/Library/Application\ =3D
Support/iTeXMac/General/Encodings.plist
If you want i can send this file as an attached document (I think the
list don't accept attached documents)
--Apple-Mail-2-441074104--
----------------------------------------------------------------------
Subject: Re: [OS X TeX] TexShop & Textures
From: "J=E9r=F4me Laurens"
Date: Mon, 14 Oct 2002 11:41:49 +0200
Le samedi, 12 oct 2002, =E0 09:19 Europe/Zurich, William McCallum a =
=E9crit=20
:
>
> On Saturday, October 12, 2002, at 12:07 AM, Michael Murray wrote:
>
>> Based on the feature set it had
>> when I used it a few years back I think the sychronocity feature
>> of Textures where you click on the dvi preview and get transported=20
>> back to
>> the right point of the input file would be an attractive feature.
>
> You can get this feature for free now also, using xdvi and emacs, both=20=
> installed from fink.
> Also MacXdvi from Tom Kiffe has the same feature with emacs, BBedit,=20=
> and a couple of other
> editors I think.
>
No, this is just a free pale copy...=
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Unicode and TexShop, iTexMac
From: "Cyril Niklaus"
Date: Mon, 14 Oct 2002 22:06:22 +0900
On Monday, October 14, 2002, at 05:07 PM, J=C3=A9r=C3=B4me Laurens =
wrote:
> Please notice that iTeXMac provides support for UTF-8, and all other=20=
> encodings in Mac OS X: there is help available, I hope
Glad to discover that, and thanks for the plist. Now on to the=20
nitpicking:
with document:
\documentclass[11pt]{article}
\usepackage{ucs}
\usepackage[utf8]{inputenc}
\begin{document}
Avad\=3D{a}na \\
Avad=C4=81na
\end{document}
I've added the plist, and opened my test file, changed the string=20
encoding to utf-8, typed a few letters with the extended unicode=20
keyboard, saved, compiled: all perfect: displays fine both in the=20
editor and in the preview.
Close the document, reopen it: first problem: the letters are not what=20=
they should be:
ie the "a macron" is now a "=C6=92=C3=85", and the string encoding =
claims it's=20
western-mac. If I compile, things are balmy though. If I change the=20
encoding back to utf-8, compilation coughs on : "
! Package ucs Error: Unknown Unicode character 402 =3D U+0192,
(ucs) possibly declared in uni-1.def.
(ucs) Type H to see if it is available with options.
See the ucs package documentation for explanation.
Type H for immediate help.
...
l.6 Avad^^c6^^92
^^c3^^85na
? h
Unicode character 402 =3D U+0192:
LATIN SMALL LETTER F WITH HOOK
LATIN SMALL LETTER SCRIPT F
Character is not defined in uni-*.def files.
Enter I! to define the glyph.
"
If I erase the =C6=92=C3=85 and replace it with the "a macron", things =
again are=20
fine.
Am I right in guessing that the editor does not pay attention to the=20
string encoding when opening files, and thus messes them up (at least=20
visually, since they still compile correctly?), and when restating the=20=
unicode nature of the text, the messed-up diacritics get in the way.
It's bugging me, as the point of using unicode was (to me) to get a=20
more visually readable text in the first palce, so if my diacritics=20
TeX-style are to be replaced by other, less readeable characters...
De toute mani=C3=A8re, merci pour un programme bien pratique,
Cyril=
----------------------------------------------------------------------
Subject: Where is my help file?
From: "Claus Atzenbeck"
Date: Mon, 14 Oct 2002 17:11:01 +0200
Hello,
I was installing iTeXMac 1.2, but it there is no iTeXMac help available
in MacOS's help viewer. I didn't find a help file on iTeXMac's homepage
either.
Is there no help file?
Is there any other documentation where I can read about certain menu
entries or other iTeXMac features?
Claus
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Where is my help file?
From: "Nigel King"
Date: Mon, 14 Oct 2002 17:53:20 +0100
Claus,
> I was installing iTeXMac 1.2, but it there is no iTeXMac help available
> in MacOS's help viewer. I didn't find a help file on iTeXMac's homepage
> either.
>
> Is there no help file?
> Is there any other documentation where I can read about certain menu
> entries or other iTeXMac features?
>
> Claus
In the Readme it says to put the help file from the Documentation folder
into a Library/Documentation/Help. It should then work!
--
Nigel
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Where is my help file?
From: "Claus Atzenbeck"
Date: Mon, 14 Oct 2002 19:10:29 +0200
Am Montag, 14.10.02 um 18:53 Uhr schrieb Nigel King:
>> Is there no help file?
>> Is there any other documentation where I can read about certain menu
>> entries or other iTeXMac features?
>>
>> Claus
> In the Readme it says to put the help file from the Documentation
> folder
> into a Library/Documentation/Help. It should then work!
Ops, I just have overseen this. Sorry...
Thanks for your help!
Claus
----------------------------------------------------------------------
Subject: Math fonts wierdness: UPDATE
From: "Andrew Farmer"
Date: Mon, 14 Oct 2002 14:06:15 -0700
Well, I've tried a variety of programs, and the problem does indeed seem
to be with Apple's NSPDFRepresentation class. Bummer.
On the other hand, iTeXMac offers an option to view the resulting PDF
using Acrobat Reader, which bypasses Apple's buggy class. The only issue
remaining is:
Why is iTeXMac's syntax parser so slow?
After starting to use iTeXMac, I noticed that input seemed inordinately
slow, running CPU utilization up to around 75% with average-speed
typing. After searching for the problem, I finally realized that the
syntax coloring slowed the editor down immensely.
I've turned off syntax coloring for now, but this has the unfortunate
side-effect of locking the font into the system monospace, which is not
the font I'd prefer to be using.
Does anybody have any other solutions to this problem, save using a
different editor?
--
Andrew Farmer
andfarm@thibs.menloschool.org
----------------------------------------------------------------------
End of MacOSX-TeX Digest
-----------------------------------------------------
Mac TeX info, resources, and news can be found at:
-----------------------------------------------------
List archives can be found at:
Threaded list archives can be found at:
-----------------------------------------------------
See message headers for list info.
-----------------------------------------------------