Ross Moore wrote:
On 02/11/2011, at 10:40 AM, Andy Black wrote:
\hyperlink{rAsociación}{APLT (1988)}
Don't use non-ASCII characters in the link.
Oh dear, does PDF still live in the TeX 2 era ? Surely /someone/ in
Adobe is aware that there are character sets other than US English,
an
Hi Tobias,
Polyglossia works fine for german! I believed you missed a error message.
You have to change one line, you need:
\defaultfontfeatures{Ligatures=TeX}
regards
Keith.
Am 28.10.2011 um 16:53 schrieb Tobias Schoel:
> As a simple user (very simple: none of my work gets published,
Dear All:
I have a document with 2 successive pagenotes, I want to add a separator as
in footmisc package and multfootsep.
I would appreciate if there is a solution to this.
This is a test file:
\documentclass{amsbook}
\usepackage[pdfusetitle,xetex,breaklinks,hyperfootnotes=false]{hyperref}
\u
2011/11/2 Philip TAYLOR (Webmaster, Ret'd) :
>
>
> Ross Moore wrote:
>
>> On 02/11/2011, at 10:40 AM, Andy Black wrote:
>>
\hyperlink{rAsociación}{APLT (1988)}
>>
>> Don't use non-ASCII characters in the link.
>
> Oh dear, does PDF still live in the TeX 2 era ? Surely /someone/ in
> Adobe
Zdenek Wagner wrote:
2011/11/2 Philip TAYLOR (Webmaster, Ret'd):
Adobe _does_ live in such era because tha last really portable reader
for all operating systems is version 3. Bugs reported by me in January
2002 and April 2002 have not been fixed so far.
PDF is based on PS and the string typ
2011/11/2 Philip TAYLOR (Webmaster, Ret'd) :
>
>
> Zdenek Wagner wrote:
>>
>> 2011/11/2 Philip TAYLOR (Webmaster, Ret'd):
>
>> Adobe _does_ live in such era because tha last really portable reader
>> for all operating systems is version 3. Bugs reported by me in January
>> 2002 and April 2002 have
Zdenek Wagner wrote:
No, it won't be that easy. Syntax (string) in links is in
AdobeStandardEncoding and some of these characters are not valid in
UTF-8.
OK. But could a PDF reader not use the same detection algorithm
as (say) the Microsoft C# Compiler -- "No BOM : ASCII; BOM : UTF-8" ?
**
> OK. But could a PDF reader not use the same detection algorithm
> as (say) the Microsoft C# Compiler -- "No BOM : ASCII; BOM : UTF-8" ?
Of course not; UTF-8 strings do not necessarily contain a BOM. Where
did you get that strange idea from?
Arthur
-
Arthur Reutenauer wrote:
OK. But could a PDF reader not use the same detection algorithm
as (say) the Microsoft C# Compiler -- "No BOM : ASCII; BOM : UTF-8" ?
Of course not; UTF-8 strings do not necessarily contain a BOM. Where
did you get that strange idea from?
I didn't :-) But that
2011/11/2 Arthur Reutenauer :
>> OK. But could a PDF reader not use the same detection algorithm
>> as (say) the Microsoft C# Compiler -- "No BOM : ASCII; BOM : UTF-8" ?
>
> Of course not; UTF-8 strings do not necessarily contain a BOM. Where
> did you get that strange idea from?
>
BOM is alread
> BOM is already used in outlines but the application that creates PDF
> has to write BOM. As Arthur wrote, there are a lot of files in UTF-8
> that do not have BOM. Even in XML BOM is only optional.
Actually, it even used to be frowned upon in UTF-8 text :-) It was
originally meant for tagging
On Wed, Nov 02, 2011 at 10:24:11AM +, Philip TAYLOR (Webmaster, Ret'd)
wrote:
> Zdenek Wagner wrote:
>
> >No, it won't be that easy. Syntax (string) in links is in
> >AdobeStandardEncoding and some of these characters are not valid in
> >UTF-8.
>
> OK. But could a PDF reader not use the sa
On Wed, Nov 02, 2011 at 10:44:27AM +, Philip TAYLOR (Webmaster, Ret'd)
wrote:
> Arthur Reutenauer wrote:
> >>OK. But could a PDF reader not use the same detection algorithm
> >>as (say) the Microsoft C# Compiler -- "No BOM : ASCII; BOM : UTF-8" ?
> >
> > Of course not; UTF-8 strings do not
Heiko Oberdiek wrote:
Example: Destination names in PDF are just byte strings.
Thus you could put arbitrary rubbisch in there. The string
is used as id label to identify a destination/anchor.
Regarding hyperref: an anchor name has similar restrictions
as a \label name. Letters and digits are
On Wed, Nov 02, 2011 at 11:14:54AM +, Philip TAYLOR (Webmaster, Ret'd)
wrote:
> Heiko Oberdiek wrote:
>
> >If the OP needs funny stuff as labels
>
> Heiko, you are, I believe, a native German speaker
> (please correct me if I am mistaken). In your
> personal opinion, are the following "let
Heiko Oberdiek wrote:
On Wed, Nov 02, 2011 at 11:14:54AM +, Philip TAYLOR (Webmaster, Ret'd)
wrote:
Heiko Oberdiek wrote:
If the OP needs funny stuff as labels
Heiko, you are, I believe, a native German speaker
(please correct me if I am mistaken). In your
personal opinion, are the
Hi Phil,
On 02/11/2011, at 7:54 PM, Philip TAYLOR (Webmaster, Ret'd) wrote:
> Ross Moore wrote:
>
>> On 02/11/2011, at 10:40 AM, Andy Black wrote:
>>
\hyperlink{rAsociación}{APLT (1988)}
>>
>> Don't use non-ASCII characters in the link.
>
> Oh dear, does PDF still live in the TeX 2 era
Hi Phil,
On 02/11/2011, at 7:54 PM, Philip TAYLOR (Webmaster, Ret'd) wrote:
> Ross Moore wrote:
>
>> On 02/11/2011, at 10:40 AM, Andy Black wrote:
>>
\hyperlink{rAsociación}{APLT (1988)}
>>
>> Don't use non-ASCII characters in the link.
>
> Oh dear, does PDF still live in the TeX 2 era
Ross Moore wrote:
My advice is simply that if you restrict yourself to ASCII
letters, then you will not face any difficulties.
This is pure pragmatism; nothing less.
As was Knuth's decision to base TeX on US-ASCII.
Fortunately, FMi and others were able to convince
him that he was wrong, whe
I created the .tec file. How would I tell XeTeX to use the .tec file? I
created a directory under this path and saved the .map and .tec file there.
/usr/local/texlive/2011/texmf-**dist/fonts/misc/xelatex/**fontmappings/
On Wed, Nov 2, 2011 at 1:04 AM, bhutex wrote:
>
>
> On Tue, Nov 1, 2011 at
2011/11/2 A u :
> I created the .tec file. How would I tell XeTeX to use the .tec file? I
> created a directory under this path and saved the .map and .tec file there.
> /usr/local/texlive/2011/texmf-dist/fonts/misc/xelatex/fontmappings/
>
When selecting the font, use option Mapping=mapfilename (in
On Wed, Nov 02, 2011 at 11:42:38AM +, Philip TAYLOR (Webmaster, Ret'd)
wrote:
> Heiko Oberdiek wrote:
> >On Wed, Nov 02, 2011 at 11:14:54AM +, Philip TAYLOR (Webmaster, Ret'd)
> >wrote:
> >
> >>Heiko Oberdiek wrote:
> >>
> >>>If the OP needs funny stuff as labels
> >>
> >>Heiko, you are,
On Wed, 2 Nov 2011, Philip TAYLOR (Webmaster, Ret'd) wrote:
> Fortunately, FMi and others were able to convince
> him that he was wrong, whence TeX 3. Now we clearly
> need to start on Adobe (and Heiko !).
If Ross Moore's and other recent technical postings are to be believed,
this is a non-issue
On Wed, Nov 02, 2011 at 12:21:49PM +, Philip TAYLOR (Webmaster, Ret'd)
wrote:
> Ross Moore wrote:
>
> >My advice is simply that if you restrict yourself to ASCII
> >letters, then you will not face any difficulties.
> >This is pure pragmatism; nothing less.
>
> As was Knuth's decision to bas
Heiko Oberdiek wrote:
ä, ö, ü, ß
\bye
is anything other than a normal, everyday, document ?
The mail header of your posting, send by the list server
contains:
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Then I must have received a quite abnormal mail out of
On Wed, Nov 02, 2011 at 01:11:04PM +, Philip TAYLOR (Webmaster, Ret'd)
wrote:
> >Byte string means that the string consists of bytes 0-255 (or 1..255).
> >Can you write them with XeTeX in a file or use as destination names
> >without using a different encoding?
>
> I do not understand the qu
Heiko Oberdiek wrote:
XeTeX can't write byte strings.
Is this a XeTeX or an (x)dvipdfmx limitation, Heiko?
** P.
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
2011/11/2 Heiko Oberdiek :
> On Wed, Nov 02, 2011 at 01:11:04PM +, Philip TAYLOR (Webmaster, Ret'd)
> wrote:
>
>> >Byte string means that the string consists of bytes 0-255 (or 1..255).
>> >Can you write them with XeTeX in a file or use as destination names
>> >without using a different encodi
On Wed, Nov 02, 2011 at 01:30:53PM +, Philip TAYLOR (Webmaster, Ret'd)
wrote:
> Heiko Oberdiek wrote:
>
> >XeTeX can't write byte strings.
>
> Is this a XeTeX or an (x)dvipdfmx limitation, Heiko?
AFAIK both.
Yours sincerely
Heiko Oberdiek
--
Heiko Oberdiek wrote:
XeTeX can't write byte strings.
[PT] Is this a XeTeX or an (x)dvipdfmx limitation, Heiko?
AFAIK both.
OK, I'm glad we have managed to identify a real problem. Thank you.
** Phil.
--
Subscriptions, Archive, and List
I have personally had to look at depth at times at some of Heiko's packages
and have the greatest respect for what he dies in trying to make the whole
lot work together well across all the international standards and other
difficult bits which are on no standard at present and feel that he and the
I am attaching the files, can you tell me what I am doing wrong. I created
"xetex-devtotel" directory under this path /usr/local/texlive/2011/texmf-**
dist/fonts/misc/xetex/**fontmappings/
place .map and .tec file under the director. I am attaching the tex file
along with output also.
thanks for y
Dear Paul -- Thank you for your spirited defence of Heiko,
which is accepted in the spirit in which it was made. I,
too, have the greatest respect for Heiko's work (indeed, it
is only a a short time since I said I had considered nominating
him for the non-existent position of vice-Grand-Wizard of
2011/11/2 A u :
> I am attaching the files, can you tell me what I am doing wrong. I created
> "xetex-devtotel" directory under this
> path /usr/local/texlive/2011/texmf-dist/fonts/misc/xetex/fontmappings/
> place .map and .tec file under the director. I am attaching the tex file
> along with outpu
Phil,
Please stop. I am serious. Just stop.
Arthur
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Hi Phil,
On 03/11/2011, at 10:26 AM, Philip TAYLOR (Webmaster, Ret'd) wrote:
> And when
> I added a throw-away line to the effect that Heiko,
> as well as Adobe, need to put US ASCII behind them
> and move into the 21st Century
Unless you have actually read the PDF specs, you really
are not qua
36 matches
Mail list logo
