Le 6 nov. 2010 à 14:10, André Bellaïche a écrit :
>
> Le 30 oct. 2010 à 11:55, Peter Dyballa a écrit :
>
>>
>> Am 29.10.2010 um 23:51 schrieb André Bellaïche:
>>
>>> I have looked into changebar.sty, and it does not seems to be easy to
>>> replace the Postscript commands by a simple command
Le 30 oct. 2010 à 11:55, Peter Dyballa a écrit :
>
> Am 29.10.2010 um 23:51 schrieb André Bellaïche:
>
>> I have looked into changebar.sty, and it does not seems to be easy to
>> replace the Postscript commands by a simple command drawing an hrule or a
>> vrule.
>
>
> André,
>
> if you nee
Am 30.10.2010 um 17:42 schrieb Peter Dyballa:
Get the archive and unzip it for example somewhere in /tmp.
Actually I think it's much easier to save the archive somewhere, say,
in the download folder or in /tmp, and then to cd to /usr/local/
texlive/texmf-local. There, on the command line,
Am 30.10.2010 um 12:38 schrieb André Bellaïche:
I have also find a `frutiger' package for LaTeX:
http://www.ctan.org/tex-archive/fonts/truetypemetrics/frutiger/
Get the archive and unzip it for example somewhere in /tmp. Change
directory (cd, pushd) on the command line into that directory.
Le 30 oct. 2010 à 11:55, Peter Dyballa a écrit :
>
> Am 29.10.2010 um 23:51 schrieb André Bellaïche:
>
>> I have looked into changebar.sty, and it does not seems to be easy to
>> replace the Postscript commands by a simple command drawing an hrule or a
>> vrule.
>
>
> André,
>
> if you nee
Am 29.10.2010 um 23:51 schrieb André Bellaïche:
I have looked into changebar.sty, and it does not seems to be easy
to replace the Postscript commands by a simple command drawing an
hrule or a vrule.
André,
if you need to compare two XeLaTeX files, then you don't need the
fancy XeLaTeX
Le 29 oct. 2010 à 19:26, Peter Dyballa a écrit :
>
> Am 29.10.2010 um 18:30 schrieb André Bellaïche:
>
>> Is this normal?
>
>
> Yes. With
>
> %%!TEX encoding = UTF-8 Unicode
>
> you tell TeXShop how the file's encoding is. The preference you set is just a
> default for *new* files or
Am 29.10.2010 um 18:30 schrieb André Bellaïche:
Is this normal?
Yes. With
%%!TEX encoding = UTF-8 Unicode
you tell TeXShop how the file's encoding is. The preference you set is
just a default for *new* files or for old files *without* that
encoding declaration. This declaration
On Fri, Oct 29, 2010 at 06:30:04PM +0200, André Bellaïche wrote:
> And I have observed the following: If a tex file contains the two lines
>
> %!TEX TS-program = xelatex
> %!TEX encoding = UTF-8 Unicode
>
> and has been saved on the user-utf8 side, as a utf8 file, and you open it
> from the user
It works now, and I can type set with Frutiger. Thank you all for your help.
Two more questions:
1. Does it exists a version of changebar.sty compatible with xelatex?
2. I have created two users on my mac, say user-mac and user-utf8, where the
encoding preferences of TeXShop are different : app
Am 23.10.2010 um 17:30 schrieb Ulrike Fischer:
Am Sat, 23 Oct 2010 11:27:46 +0200 schrieb Peter Dyballa:
1. Is it possible to replace unicode by applemac encoding? What are
the commands in this case?
If you want to continue typing in applemac input encoding you better
stay with the much m
Am 23.10.2010 um 18:14 schrieb Ulrike Fischer:
So why not tell them that there is a choice?
Because you need to record each file's particular encoding in order to
share its contents with other users – or editors/TeX front-ends/TeX
engines.
--
Mit friedvollen Grüßen
Pete
There's no
Am Sat, 23 Oct 2010 17:48:46 +0200 schrieb Arthur Reutenauer:
>> Why shouldn't someone be forced to use utf8 encoding if its texts
>> use only chars from a 8bit codepage? Xetex is quite able to handle
>> them if you declare the encoding.
>
> Quite, but not entirely. If you use \XeTeXinputencod
> Why shouldn't someone be forced to use utf8 encoding if its texts
> use only chars from a 8bit codepage? Xetex is quite able to handle
> them if you declare the encoding.
Quite, but not entirely. If you use \XeTeXinputencoding to use some
other character set, XeTeX will still write to files u
Am Sat, 23 Oct 2010 10:53:42 +0200 schrieb André Bellaïche:
> Let me ask some questions:
> 1. Is it possible to replace unicode by applemac encoding? What
> are the commands in this case?
Yes. You will have to put \XeTeXinputencoding "mac" at the start
(somewhere before the first non-ascii ch
Am Sat, 23 Oct 2010 11:27:46 +0200 schrieb Peter Dyballa:
>> 1. Is it possible to replace unicode by applemac encoding? What are
>> the commands in this case?
> If you want to continue typing in applemac input encoding you better
> stay with the much more developed pdfTeX. All packages wor
On 23 oct. 2010, at 18:52, André Bellaïche wrote:
>
> Le 23 oct. 2010 à 11:33, Cyril Niklaus a écrit :
>
>> On 23 oct. 2010, at 17:53, André Bellaïche wrote:
>>
>>>
>>> 2. If the main roman font is Frutiger® 55 Roman (Linotype Original names),
>>> I doubt that the system will find out that if
Am 23.10.2010 um 11:46 schrieb André Bellaïche:
Yes, but it does not seem that the Postscript name is the one you
type in the command \setromanfont.
The family name should be OK since it does not restrict the font to
one variant (roman, italic, bold, a mixture). Look into Font Book
(Livr
Le 23 oct. 2010 à 11:33, Cyril Niklaus a écrit :
> On 23 oct. 2010, at 17:53, André Bellaïche wrote:
>
>> I am new to XeTeX, and I could not find a text for beginners.
>
>> ===
>>
>> Let me ask some questions:
>>
>> 1. Is it possible to re
Le 23 oct. 2010 à 11:27, Peter Dyballa a écrit :
>
> Am 23.10.2010 um 10:53 schrieb André Bellaïche:
>
>> 1. Is it possible to replace unicode by applemac encoding? What are the
>> commands in this case?
>
> If you want to continue typing in applemac input encoding you better stay
> with the
On 23 oct. 2010, at 17:53, André Bellaïche wrote:
> I am new to XeTeX, and I could not find a text for beginners.
> ===
>
> Let me ask some questions:
>
> 1. Is it possible to replace unicode by applemac encoding? What are the
> commands in
Am 23.10.2010 um 10:53 schrieb André Bellaïche:
1. Is it possible to replace unicode by applemac encoding? What are
the commands in this case?
If you want to continue typing in applemac input encoding you better
stay with the much more developed pdfTeX. All packages work with
pdfTeX, an
22 matches
Mail list logo
