Re: [XeTeX] pdf_link_obj(): passed invalid object.
Heiko Oberdiek wrote: * Or run the file through pdftk to generate a fixed pdf file: pdftk matrix-broken.pdf cat output matrix-fixed.pdf This solution works here. I copied matrix.pdf to get matrix-broken.pdf and ran it as above through pdftk then xelatex doc.tex. -- United in adoration of Jesus, fr. michael gilmary, mma Most Holy Trinity Monastery 67 Dugway Road Petersham, MA 01366-9725 www.MaroniteMonks.org -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] pdf_link_obj(): passed invalid object.
On Wed, Dec 22, 2010 at 04:42:30PM +0100, Ulrike Fischer wrote: > Am Wed, 22 Dec 2010 13:29:16 + schrieb Jérôme Etévé: > > > See doc.tex , flu.pdf (it works) and matrix.pdf (including it breaks). > > > > $ xelatex doc.tex > > ... > > [38] (./doc.aux) > > ** WARNING ** Could not find any valid object. > > ** WARNING ** Could not find a value in dictionary object. > > ** WARNING ** Didn't find "endobj". > > ** ERROR ** pdf_link_obj(): passed invalid object. > > I can reproduce the problem with a current miktex. > > I could process the file by including matrix.pdf with pdflatex in a > matrix2.pdf and this including this in the main document processed > by xelatex (I had to use the option --output-driver="xdvipdfmx -V5" > as pdflatex generated a 1.5.-pdf). > > xelatex itself (with option --no-pdf) worked fine. It was xdvipdfmx > which complained. So I would at first make a bug report to the > xdvipdfmx maintainer. > > (My first suspect would be the object number: The problematic pdf > start with 0 0 obj, the other (also the new matrix2.pdf) have a > number different from zero). But I don't know much about pdf. This > could also be irrelevant.) Indeed, matrix.pdf is utterly broken. And your suspicion with object number 0 is correct, the problem is the crossref table: The first object number 0 in the xref table is reserved as start of a linked list with free objects, from the PDF spec.: | The first entry in the table (object number 0) is always free | and has a generation number of 65,535; it is the head of | the linked list of free objects. The last free entry | (the tail of the linked list) links back to object number 0. | (In addition, the table may contain other free entries | that link back to object number 0 and have a generation | number of 65,535, even though these entries are not in | the linked list itself.) The first entry in matrix.pdf is: 000323 0 n It should be 000323 65536 f Rationale: * Type "f" and the generation part "65536" is a requirement of the PDF specification. * 323 is not a valid file position of a PDF object, but 323 is free object. Also the entry for object number 2 is wrong: 16 f * 16 is not a free object, as last entry of the linked list of free objects, it must point back to entry 0: 00 f The starting "0 0 obj ..." is not a valid PDF object, the "..." looks like a trailer dictionary. But this part of the PDF file is not referenced, thus it's just garbage that is usually ignored. xdvipdfmx is correct if it does not like the broken PDF file. If the very first entry of the xref table is already totally wrong, what else might be broken. The PDF file says that the producer is: www.adlibsoftware.com:EXS3190-Windows 2003:TNG If this is the producer and you have paid for the software, than try to get a fixed version or to get your money back. The file matrix.pdf seems fixable if at least the first entry of the xref table is fixed: * Replace "0 n" by "65536 f" in the line "000323 0 n". That already makes xetex/xdvipdfmx happy. * Or run the file through pdftk to generate a fixed pdf file: pdftk matrix-broken.pdf cat output matrix-fixed.pdf Yours sincerely Heiko Oberdiek -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] fontspec: Unknown feature `' in font `TeX Gyre Heros'.
On 23/12/2010, at 8:04 AM, Herbert Schulz wrote:
>
> On Dec 22, 2010, at 2:30 PM, Ross Moore wrote:
>> I get no message, with:
>>
>>
>> This is XeTeX, Version 3.1415926-2.2-0.9997.4 (TeX Live 2010)
>>
>> fontspec.sty2010/11/07 v2.1d Advanced font selection for XeLaTeX/LuaLaTeX
>> fontspec-patches.sty2010/11/07 v2.1d Advanced font selection for
>> XeLaTeX/LuaLaTeX
>>
>> You have:
>>
System is MikTeX 2.9 (XeTeX is 0.9997.4 (MiKTeX 2.9),
fontspec is 2010/11/17 v2.1e).
>>
>> So maybe a little buglet was introduced in the latest update,
>> and MikTeX just serves it up regardless.
>> Does it happen with other fonts too?
> Howdy,
>
> No problem here with fontspec 2.1e in TeX Live 2010 with the file
Yep the difference between 2.1d and 2.1e is not relevant to XeTeX.
viz.
[GlenMorangie:~/Downloads/wspr-fontspec-21a44ef/hide] rossmoor% diff -C1
../fontspec.sty `kpsewhich fontspec.sty`
*** ../fontspec.sty 2010-12-23 07:54:23.0 +1100
--- /Users/rossmoor/Library/texmf/tex/latex/fontspec/fontspec.sty
2010-11-09 10:04:45.0 +1100
***
*** 16,18
\ProvidesPackage{fontspec}
! [2010/11/17 v2.1e Advanced font selection for XeLaTeX/LuaLaTeX]
--- 16,18
\ProvidesPackage{fontspec}
! [2010/11/07 v2.1d Advanced font selection for XeLaTeX/LuaLaTeX]
***
*** 28,31
\luatex_if_engine:TF {
! \RequirePackage{luaotfload}
! \RequireLuaModule{fontspec}
}{
--- 28,31
\luatex_if_engine:TF {
! \RequirePackage{luatextra}[2010/05/10]
! \luatexRequireModule{fontspec}
}{
> Good Luck,
>
> Herb Schulz
> (herbs at wideopenwest dot com)
Herb is on MacOS X, as am I.
So there must be a difference due to platform, or to support
files used by XeTeX but not showing in the .log file.
That is potentially disturbing, though the effect on typesetting
seems to be imperceptible.
All the best,
Ross
Ross Moore ross.mo...@mq.edu.au
Mathematics Department office: E7A-419
Macquarie University tel: +61 (0)2 9850 8955
Sydney, Australia 2109 fax: +61 (0)2 9850 8114
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] fontspec: Unknown feature `' in font `TeX Gyre Heros'.
On Dec 22, 2010, at 2:30 PM, Ross Moore wrote:
> Hi Martin,
>
> On 23/12/2010, at 7:01 AM, Martin Schröder wrote:
>
>> 2010/12/22 Ross Moore :
>>> Writing a message to warn the user of their sloppiness is quite
>>> a reasonable action, in my opinion. This is done a lot in TeX
>>
>> What's wrong with my input?
>
> Sorry.
> I just looked at:
>
>> "TeX Gyre Heros/ICU:script=latn;language=DFLT;mapping=tex-text;;
>> " at 10.0pt
>
> to see the ;; .
>
> The possible after it, before the closing " is a possible
> worry too --- though that may be just the number of characters in
> the output message.
>
> I get no message, with:
>
>
> This is XeTeX, Version 3.1415926-2.2-0.9997.4 (TeX Live 2010)
>
> fontspec.sty2010/11/07 v2.1d Advanced font selection for XeLaTeX/LuaLaTeX
> fontspec-patches.sty2010/11/07 v2.1d Advanced font selection for
> XeLaTeX/LuaLaTeX
>
> You have:
>
>>> System is MikTeX 2.9 (XeTeX is 0.9997.4 (MiKTeX 2.9),
>>> fontspec is 2010/11/17 v2.1e).
>
> So maybe a little buglet was introduced in the latest update,
> and MikTeX just serves it up regardless.
> Does it happen with other fonts too?
>
>>
>> Best
>> Martin
>
>
>
> Cheers,
>
> Ross
Howdy,
No problem here with fontspec 2.1e in TeX Live 2010 with the file
%%!TEX TS-program = xelatex
%%!TEX encoding = UTF-8 Unicode
\listfiles
\documentclass{article}
\usepackage{fontspec}
\setmainfont[Ligatures=TeX]{TeX Gyre Heros}
\setsansfont[Ligatures=TeX]{TeX Gyre Heros}
\setmonofont[Scale=MatchLowercase]{Monaco}
\begin{document}
Some text and some \textsf{Sans Text}.
\end{document}
and the list of files is:
article.cls2007/10/19 v1.4h Standard LaTeX document class
size10.clo2007/10/19 v1.4h Standard LaTeX file (size option)
fontspec.sty2010/11/17 v2.1e Advanced font selection for XeLaTeX/LuaLaTeX
expl3.sty2010/11/13 v2083 L3 Experimental code bundle wrapper
l3names.sty2010/10/03 v2064 L3 Experimental Naming Scheme for TeX Primitiv
es
etex.sty1998/03/26 v2.0 eTeX basic definition package (PEB)
l3basics.sty2010/10/03 v2063 L3 Experimental basic definitions
l3expan.sty2010/09/20 v2037 L3 Experimental Argument Expansion module
l3tl.sty2010/12/18 v2103 L3 Experimental Token Lists
l3int.sty2010/10/17 v2077 L3 Experimental Integer module
l3quark.sty2010/09/20 v2036 L3 Experimental Quark Commands
l3seq.sty2010/03/29 v1879 L3 Experimental sequences and stacks
l3toks.sty2010/09/20 v2037 L3 Experimental Token Registers
l3prg.sty2010/10/03 v2063 L3 Experimental control structures
l3clist.sty2010/10/09 v2071 L3 Experimental comma separated lists
l3token.sty2010/10/03 v2063 L3 Experimental token investigation and manipu
lation
l3prop.sty2010/11/23 v2087 L3 Experimental Property Lists
l3msg.sty2010/10/02 v2052 L3 Experimental LaTeX Messages module
l3io.sty2010/10/03 v2063 L3 Experimental i/o module
l3skip.sty2010/11/23 v2088 L3 Experimental skip registers
l3box.sty2010/09/26 v2048 L3 Experimental Box module
l3keyval.sty2010/04/11 v1890 L3 Experimental keyval processing
l3keys.sty2010/11/11 v2082 L3 Experimental key-value support
l3precom.sty2010/02/09 v1793 L3 Experimental precompilation module
l3xref.sty2010/02/09 v1786 L3 Experimental cross referencing
l3file.sty2010/03/21 v1853 L3 Experimental file loading
l3fp.sty2010/12/18 v2104 L3 Experimental floating-point operations
l3luatex.sty2010/07/18 v1985 L3 Experimental LuaTeX functions
calc.sty2007/08/22 v4.3 Infix arithmetic (KKT,FJ)
xparse.sty2010/10/13 v2073 Generic document command parser
xkeyval.sty2008/08/13 v2.6a package option processing (HA)
xkeyval.tex2008/08/13 v2.6a key=value parser (HA)
fontspec-patches.sty2010/11/17 v2.1e Advanced font selection for XeLaTeX/Lu
aLaTeX
fixltx2e.sty2006/09/13 v1.1m fixes to LaTeX
fontenc.sty
eu1enc.def2010/05/27 v0.1h Experimental Unicode font encodings
eu1lmr.fd2009/10/30 v1.6 Font defs for Latin Modern
xunicode.sty2010/11/06 v0.96 provides access to latin accents and many othe
r characters in Unicode lower plane
fontspec.cfg
Good Luck,
Herb Schulz
(herbs at wideopenwest dot com)
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] fontspec: Unknown feature `' in font `TeX Gyre Heros'.
Hi Martin, On 23/12/2010, at 7:01 AM, Martin Schröder wrote: > 2010/12/22 Ross Moore : >> Writing a message to warn the user of their sloppiness is quite >> a reasonable action, in my opinion. This is done a lot in TeX > > What's wrong with my input? Sorry. I just looked at: > "TeX Gyre Heros/ICU:script=latn;language=DFLT;mapping=tex-text;; > " at 10.0pt to see the ;; . The possible after it, before the closing " is a possible worry too --- though that may be just the number of characters in the output message. I get no message, with: This is XeTeX, Version 3.1415926-2.2-0.9997.4 (TeX Live 2010) fontspec.sty2010/11/07 v2.1d Advanced font selection for XeLaTeX/LuaLaTeX fontspec-patches.sty2010/11/07 v2.1d Advanced font selection for XeLaTeX/LuaLaTeX You have: >> System is MikTeX 2.9 (XeTeX is 0.9997.4 (MiKTeX 2.9), >> fontspec is 2010/11/17 v2.1e). So maybe a little buglet was introduced in the latest update, and MikTeX just serves it up regardless. Does it happen with other fonts too? > > Best > Martin Cheers, Ross Ross Moore ross.mo...@mq.edu.au Mathematics Department office: E7A-419 Macquarie University tel: +61 (0)2 9850 8955 Sydney, Australia 2109 fax: +61 (0)2 9850 8114 -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] fontspec: Unknown feature `' in font `TeX Gyre Heros'.
2010/12/22 Ross Moore : > Writing a message to warn the user of their sloppiness is quite > a reasonable action, in my opinion. This is done a lot in TeX What's wrong with my input? Best Martin -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] fontspec: Unknown feature `' in font `TeX Gyre Heros'.
Hi Martin, On 23/12/2010, at 6:36 AM, Martin Schröder wrote: > 2010/12/22 Ross Moore : >> ;; >> causes an empty feature request. > > So it's an error in fontspec? I don't pass such judgements. Should an empty element in an array always be ignored silently? Should an extra code block search for, or catch, such a thing before passing on to achieve the main purpose of the coding? Presumably that might depend upon how much damage is being done. Writing a message to warn the user of their sloppiness is quite a reasonable action, in my opinion. This is done a lot in TeX and LaTeX, so why not here? > > Best > Martin Cheers, Ross Ross Moore ross.mo...@mq.edu.au Mathematics Department office: E7A-419 Macquarie University tel: +61 (0)2 9850 8955 Sydney, Australia 2109 fax: +61 (0)2 9850 8114 -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] fontspec: Unknown feature `' in font `TeX Gyre Heros'.
2010/12/22 Ross Moore : > ;; > causes an empty feature request. So it's an error in fontspec? Best Martin -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] fontspec: Unknown feature `' in font `TeX Gyre Heros'.
Martin,
;;
causes an empty feature request.
Cheers,
Ross
Sent from my iPad
On 23/12/2010, at 12:08 AM, Martin Schröder wrote:
> Hi,
> when I set up TeX Gyre Heros on Windows thusly:
> -
> \setmainfont[Ligatures=TeX]{TeX Gyre Heros}
> \setsansfont[Ligatures=TeX]{TeX Gyre Heros}
> -
>
> I get the warning
> -
> Requested font "TeX Gyre
> Heros/ICU:script=latn;language=DFLT;mapping=tex-text;;
> " at 10.0pt
> -> C:/Program Files (x86)/MiKTeX 2.9/fonts/opentype/public/tex-gyre/texgyreher
> os-regular.otf
> Unknown feature `' in font `TeX Gyre Heros'.
> -
>
> Why? The ligs seem to work. :-)
>
> System is MikTeX 2.9 (XeTeX is 0.9997.4 (MiKTeX 2.9), fontspec is
> 2010/11/17 v2.1e).
>
> Best
> Martin
>
>
> --
> Subscriptions, Archive, and List information, etc.:
> http://tug.org/mailman/listinfo/xetex
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] pdf_link_obj(): passed invalid object.
Jérôme Etévé wrote: > I've built a minimal breaking example. > > See doc.tex , flu.pdf (it works) and matrix.pdf (including it breaks). > > $ xelatex doc.tex > ... > [38] (./doc.aux) > ** WARNING ** Could not find any valid object. > ** WARNING ** Could not find a value in dictionary object. > ** WARNING ** Didn't find "endobj". > ** ERROR ** pdf_link_obj(): passed invalid object. File a bug report to xdvipdfmx. Here is a minimal plain TeX file exhibiting the problem: \XeTeXpdffile "matrix.pdf" page 1\relax \bye Ciao Andreas -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] pdf_link_obj(): passed invalid object.
Am Wed, 22 Dec 2010 13:29:16 + schrieb Jérôme Etévé: > Hi All, > > I've built a minimal breaking example. > > See doc.tex , flu.pdf (it works) and matrix.pdf (including it breaks). > > $ xelatex doc.tex > ... > [38] (./doc.aux) > ** WARNING ** Could not find any valid object. > ** WARNING ** Could not find a value in dictionary object. > ** WARNING ** Didn't find "endobj". > ** ERROR ** pdf_link_obj(): passed invalid object. I can reproduce the problem with a current miktex. I could process the file by including matrix.pdf with pdflatex in a matrix2.pdf and this including this in the main document processed by xelatex (I had to use the option --output-driver="xdvipdfmx -V5" as pdflatex generated a 1.5.-pdf). xelatex itself (with option --no-pdf) worked fine. It was xdvipdfmx which complained. So I would at first make a bug report to the xdvipdfmx maintainer. (My first suspect would be the object number: The problematic pdf start with 0 0 obj, the other (also the new matrix2.pdf) have a number different from zero). But I don't know much about pdf. This could also be irrelevant.) -- Ulrike Fischer -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Auto Font and Language Package in XeTeX
On 12/22/2010 6:28 AM, Yves Codet wrote: Hello Michiel. Thanks a lot for this package. There's a small typo in the documentation; if I understand well the paragraph 4.3 should read \setTransitionsFor[3], not \setTransitions[3]. Quite so, I shall fix that and submit the update to CTAN =D Without polyglossia (essai1.tex below) I got the expected result, but with polyglossia (essai2.tex) XeTeX seems to enter an infinite loop; the error message is: ./essai2.tex:15: TeX capacity exceeded, sorry [save size=5]. ...ex \...@gobble \let \glossary \...@gobble l.15 भ वान्कः। \\ No pages of output. Transcript written on essai2.log. Hmm, I'm seeing the same error, and I suspect it's because I didn't write the command with enough sense to protect \begin and \end instructions... come to think of it, I'm not sure how to protect those. Any package writers willing to quickly solve that one? =) - Mike -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] pdf_link_obj(): passed invalid object.
Thanks, Unfortunately, I cannot use pdflatex as I require system native ttf fonts and unicode/utf-8 support. Maybe someone can point me to the right place to start in the source code? Cheers. J. On 22 December 2010 14:16, Fr. Michael Gilmary wrote: > Jérôme Etévé wrote: > > >> Hi All, >> >> I've built a minimal breaking example. >> >> See doc.tex , flu.pdf (it works) and matrix.pdf (including it breaks). >> >> $ xelatex doc.tex >> ... >> [38] (./doc.aux) >> ** WARNING ** Could not find any valid object. >> ** WARNING ** Could not find a value in dictionary object. >> ** WARNING ** Didn't find "endobj". >> ** ERROR ** pdf_link_obj(): passed invalid object. >> > > > If I use XeLaTeX to compile this (as with /some/ other like files) I get a > broken pipe. I don't know why. So, the log output is the same as what you > have above with the additional: > > > Output file removed. > ] > > [31] > [32] > > [33] > [34] > > [35] > [36] > > [37] > [38] > (./doc.aux)Broken pipe > > > >> Can you guy replicate it with the attached files? >> > > Yes --- compile the file (as I did successfully here) with pdfLaTeX instead > of XeLaTeX. Someone else, however, will have to say /why/ pdfpages and > xdvipdfmx don't get along together. > > HTH. > > > > > -- > United in adoration of Jesus, > > > fr. michael gilmary, mma > > Most Holy Trinity Monastery > 67 Dugway Road > Petersham, MA 01366-9725 > > www.MaroniteMonks.org > > > > -- Jerome Eteve. http://libsquare.net -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Auto Font and Language Package in XeTeX
Hello Michiel. Thanks a lot for this package. There's a small typo in the documentation; if I understand well the paragraph 4.3 should read \setTransitionsFor[3], not \setTransitions[3]. Without polyglossia (essai1.tex below) I got the expected result, but with polyglossia (essai2.tex) XeTeX seems to enter an infinite loop; the error message is: ./essai2.tex:15: TeX capacity exceeded, sorry [save size=5]. ...ex \...@gobble \let \glossary \...@gobble l.15 भ वान्कः। \\ No pages of output. Transcript written on essai2.log. Regards, Yves essai1.tex Description: Binary data essai2.tex Description: Binary data Le 21 déc. 2010 à 17:53, Michiel Kamermans a écrit : > > Hi Yves (and everyone else) > > the ucharclasses package is now on CTAN > (http://tug.ctan.org/tex-archive/macros/xetex/latex/ucharclasses/), so if you > want to see if it breaks in combination with how you use polyglossia, let me > know what the result is. > > - Mike "Pomax" Kamermans > nihongoresources.com > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex > -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] pdf_link_obj(): passed invalid object.
Jérôme Etévé wrote: Hi All, I've built a minimal breaking example. See doc.tex , flu.pdf (it works) and matrix.pdf (including it breaks). $ xelatex doc.tex ... [38] (./doc.aux) ** WARNING ** Could not find any valid object. ** WARNING ** Could not find a value in dictionary object. ** WARNING ** Didn't find "endobj". ** ERROR ** pdf_link_obj(): passed invalid object. If I use XeLaTeX to compile this (as with /some/ other like files) I get a broken pipe. I don't know why. So, the log output is the same as what you have above with the additional: Output file removed. ] [31] [32] [33] [34] [35] [36] [37] [38] (./doc.aux)Broken pipe Can you guy replicate it with the attached files? Yes --- compile the file (as I did successfully here) with pdfLaTeX instead of XeLaTeX. Someone else, however, will have to say /why/ pdfpages and xdvipdfmx don't get along together. HTH. -- United in adoration of Jesus, fr. michael gilmary, mma Most Holy Trinity Monastery 67 Dugway Road Petersham, MA 01366-9725 www.MaroniteMonks.org -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Auto Font and Language Package in XeTeX (Khaled Hosny)
On Wed, Dec 22, 2010 at 07:34:00AM +0530, Venkatesan. S.K. (TNQ) wrote: > > > On Tue, Dec 21, 2010 at 05:15:13PM +0530, Venkatesan. S.K. (TNQ) wrote: > > I suppose these are early days for unicode, especially for Indic, Hebrew > and > > Arabic. > > I'm not sure if I understand what you mean by "early" here, but Arabic > have been part of Unicode since 1.1 (cr. 1993), bidi algorithm even > predates Unicode. > > Regards, > Khaled > > -- > Khaled Hosny > Arabic localiser and member of Arabeyes.org team > Free font developer > > > When Arabic and English and Tamil are mixed in UTF-8 I can demonstrate > interesting behaviors in gedit and other text editors. Many other text editors > just render them in byte order, like byte editors, which is fine... I fail to see how having unreadable Arabic text would be fine, unless one don't intend to read that text of course. > It may not be early days for the Unicode specs, but the implementing > applications have been having finding it difficulty, not to mention that there GNU Fribidi (the bidi implementing library used by GTK+ and thus Gedit) have been first released in 1999, I'd not call that new either. > have been new characters and changes being constantly made in every Unicode > version, 5.1, 6.0, etc...The OS releases lag behind and where are the bloody > fonts that has implemented Unicode 6.0? It is a nightmare for implementors and > users. New characters added to Unicode has almost no effect in how bidi is handled by applications. > Do unicode committee have a proof of concept application (like Amaya browser > for W3 HTML) or a font? > It is possible create a font using all their PDFs but license will be problem, > I suppose... > Each and every OS and editors show different levels of compliance... Sorry, I don't see what fonts have to do with the issue we are discussing here (whatever this issue actually is, you don't say what difficulties you see/have). There are already free fonts covering all RTL characters in Unicode, and more are being developed (I'm working on one right now myself). > Apart from all this, there are the users who are used to WYSIWYG paradigm and > get very confused when there are different outputs in XML editors and the PDF > output. > We have had interesting problems where book authors used Arabic/Hebrew in an > insensitive version of MS Word that doesn't switch right to left and they want > the output that way and when we open it an recent version of MS Word or the > other way around, we get very interesting emails and discussions. I generally > tell them please send me a PDF and tell me what is exactly you want in the > output, we will take care of the XML. Of course, if you use a non-Middle-East > version of InDesign then right to left will not work; I suppose InDesign folks > think that Arabic should not be used non-Middle-East folks... Still, I'm not understanding what are the problem here, and how it is related to TeX. Regards, Khaled -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
[XeTeX] fontspec: Unknown feature `' in font `TeX Gyre Heros'.
Hi,
when I set up TeX Gyre Heros on Windows thusly:
-
\setmainfont[Ligatures=TeX]{TeX Gyre Heros}
\setsansfont[Ligatures=TeX]{TeX Gyre Heros}
-
I get the warning
-
Requested font "TeX Gyre Heros/ICU:script=latn;language=DFLT;mapping=tex-text;;
" at 10.0pt
-> C:/Program Files (x86)/MiKTeX 2.9/fonts/opentype/public/tex-gyre/texgyreher
os-regular.otf
Unknown feature `' in font `TeX Gyre Heros'.
-
Why? The ligs seem to work. :-)
System is MikTeX 2.9 (XeTeX is 0.9997.4 (MiKTeX 2.9), fontspec is
2010/11/17 v2.1e).
Best
Martin
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Auto Font and Language Package in XeTeX (Khaled Hosny)
On 12/21/2010 6:04 PM, Venkatesan. S.K. (TNQ) wrote: Do unicode committee have a proof of concept application (like Amaya browser for W3 HTML) or a font? They don't need a PoC application, as the algorithms are fully described. The problems usually occur when specific font features need to be applied in a specific order, and the font engine either lacks the capability to apply them in the right order, or the capability to apply them at all. Being Unicode and OpenType compliant (rather than just compatible) is a fiendishly complex job. As for the font, the Unicode Consortium uses many different fonts, all contributed by numerous foundries and individuals (see http://unicode.org/charts/fonts.html) It is possible create a font using all their PDFs but license will be problem, I suppose... Rather! You are, in fact, expressly forbidden from extracting any font used in the Unicode specification PDF files. Each and every OS and editors show different levels of compliance... This is mostly because they all use different engines. Your OS will use Uniscribe, Core Text or (most likely) Pango depending on whether it's windows, mac or *nix, and individual applications may completely ignore these render engines and use their own layout management and glyph fetchers instead. Depending on how much the developers feel they need to reinvent the wheel because the default engines available don't offer what they need, applications will be more or less Unicode and OpenType compatible (I'm not aware of any text engine that is fully compliant, but if there is one, I'd love to know about it!) - Mike "Pomax" Kamermans nihongoresources.com -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] pdf_link_obj(): passed invalid object.
I'm using pdfpages and XeLaTeX without any problem, just using TeXlive 2010 defaults, under Ubuntu GNU/Linux 10.10. Dominik On 21 December 2010 20:35, Andreas Matthias wrote: > Peter Dyballa wrote: > > > At least *my* copy of the pdfpages documentation tells: > > > > Furthermore it requires a recent version of: > > pdftex.def http://www.tug.org/applications/pdftex/ > > This is a relict from old times when then recent TeX-distributions > like teTeX were bundled with not up-to-date versions of pdftex.def. > I added it to keep all those mail from me asking why this and > that didn't work, e.g. multi-page pdf inclusion. > > Since a few years pdfpages has support for XeTeX, too, so you need a > recent xetex.def of course. Anyway, all recent TeX-distribution > nowadays have up-to-date pdftex.def and xetex.def files. Thus > this remark is unnecessary today. I haven't heard of any problems > with old pdftex.def or xetex.def files recently. > > I just had a look: Pdfpages requires a pdftex.def from 2000/09/14 > at least. That shouldn't be a problem nowadays. And I do not > even check the date of xetex.def. > > > Ciao > Andreas > > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex > -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
