Re: [XeTeX] How to Convert Devanagari (sanskrit) text to Telugu Text
On Thu, Nov 3, 2011 at 3:54 AM, A u akupadhyay...@gmail.com wrote: I did not get any error message either in my Mac or on my linux message. I did run mktexlsr after creating the ,map file. I am attaching the output that I got in my mac machine. After creating map file you have to convert it into ,tec file using Teckit (download it from Silmaris - XeTeX's site). Only map file can't do anything. -- Happy TeXing The BHU TeX Group क्या आप यह देख पा रहें हैं। इस का मतलब आप का कम्प्यूटर यूनीकोड को समझती है। देर किस बात की हिन्दी मे चिठ्ठियां लिखिये। -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] How to Convert Devanagari (sanskrit) text to Telugu Text
you need to use teckit_compile which is included in TeXLive. On Thu, Nov 3, 2011 at 10:26 PM, bhutex bhu...@gmail.com wrote: On Thu, Nov 3, 2011 at 3:54 AM, A u akupadhyay...@gmail.com wrote: I did not get any error message either in my Mac or on my linux message. I did run mktexlsr after creating the ,map file. I am attaching the output that I got in my mac machine. After creating map file you have to convert it into ,tec file using Teckit (download it from Silmaris - XeTeX's site). Only map file can't do anything. -- Happy TeXing The BHU TeX Group क्या आप यह देख पा रहें हैं। इस का मतलब आप का कम्प्यूटर यूनीकोड को समझती है। देर किस बात की हिन्दी मे चिठ्ठियां लिखिये। -- 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] How to Convert Devanagari (sanskrit) text to Telugu Text
2011/11/3 A u akupadhyay...@gmail.com: I did not get any error message either in my Mac or on my linux message. I did run mktexlsr after creating the ,map file. I am attaching the output that I got in my mac machine. Tha .map file itself does nothing, the .tec file is important? Have you run mktexlsr AFTER installing the .tec file? If the .tec file is in a correct directory, mktexlst has been run and it still does not work, it will be necessary to try strace xelatex DevtoTel in order to see what files are used. On Wed, Nov 2, 2011 at 7:33 PM, Zdenek Wagner zdenek.wag...@gmail.com wrote: 2011/11/2 A u akupadhyay...@gmail.com: 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 your help Is there some error message? Trying with txtconv I can verify that the map converts the file to something that looks like Telugu but then I have a problem typical for RHEL based distros, XeTeX finds the Pothana2000 font but xdvipdfmx cannot find it although the font is installed and other applications can use it. On Wed, Nov 2, 2011 at 8:49 AM, Zdenek Wagner zdenek.wag...@gmail.com wrote: 2011/11/2 A u akupadhyay...@gmail.com: 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 square brackets). You can also add it to the current font by \addfontfeatures[Mapping=mapfilename]. It is described in the fontspec manual. आशा कि यह सलाह आपके लिए लाभदायक होगा। On Wed, Nov 2, 2011 at 1:04 AM, bhutex bhu...@gmail.com wrote: On Tue, Nov 1, 2011 at 5:10 PM, A u akupadhyay...@gmail.com wrote: Thanks for your help. I am attaching the .map file I created. I was wondering if you can tell me if there are any errors. because I am getting a blank pdf output. After creating the .map file you have to compile it with teckit and .tec file will be the output. .tec file is a binary file. You have to keep this in appropriate directory and then run mktexlsr. After that you will tell XeTeX or XeLaTeX to use this .tec file. Then only your devnagari document will convert in telugu script. -- Happy TeXing The BHU TeX Group क्या आप यह देख पा रहें हैं। इस का मतलब आप का कम्प्यूटर यूनीकोड को समझती है। देर किस बात की हिन्दी मे चिठ्ठियां लिखिये। I use OpenOffice3.1! Do you!! -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Zdeněk Wagner http://hroch486.icpf.cas.cz/wagner/ http://icebearsoft.euweb.cz -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Zdeněk Wagner http://hroch486.icpf.cas.cz/wagner/ http://icebearsoft.euweb.cz -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Zdeněk Wagner http://hroch486.icpf.cas.cz/wagner/ http://icebearsoft.euweb.cz -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] TECkit map for Latin alphabet to Unicode IPA
Attached to this email is an ASCII to Unicode IPA map file (TECkit mapping file). It is not complete; for example, it does not cover somewhat exotic symbols like characters for disordered speech. A more complete package can be downloaded from here: http://banyan.cm.nctu.edu.tw/~dgreenhoe/groups/ascii-uipa.zip It includes these files: ascii-uipa.map: not-compiled map file ascii-uipa.tec:compiled map file test.pdf: simple demo test.tex: XeLaTeX source for test.pdf zhipa.pdf: IPA renderings for the roughly 403 sounds (disregarding tones) of Mandarin Chinese typeset using ascii-uipa.map mappings. In case it is not immediately clear from examining these files, it should be pointed out that I am not an expert in either IPA or Chinese. So, there are no guarantees of accuracy in anything anyone may find in any of the files mentioned previously. I wish I could offer a more complete package. But at this point, it is difficult to justify the time. Many many thanks to all the people who so generously offered help along the way including (but certainly not necessarily limited to) Andy Lin, Ross Moore, Zdenek Wagner (who introduced me to TECkit mapping with regards to another project), Ulrike Fischer, and Peter Dyballa. Dan ascii-uipa.map Description: Binary data -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
[XeTeX] Anchor names
Hello,
to get more to the point, I start a new thread.
As we have learned, the PDF specification uses byte strings
for anchor names. And there is a wish to use normal characters
in anchor names. Let's make an example:
xetex --ini --output-driver='xdvipdfmx -V4' test
%%% test.tex %%%
\catcode`\{=1
\catcode`\}=2
\pdfpagewidth=100bp
\pdfpageheight=200bp
\shipout\vbox{%
\kern-1in\relax
\hbox{%
\kern-1in\relax
\vrule width0pt height200bp depth0pt\relax
% Destination at (30bp,150bp)
\raise150bp\hbox to 0pt{%
\kern30bp %
\special{pdf:dest (änchør) [@thispage /XYZ @xpos @ypos null]}%
\kern-1bp
\vrule width2bp height1bp depth1bp\relax
\hss
}%
% Link annotation center at (70bp,50bp),
% rectangle at [68bp 48bp 72bp 52bp]
\raise50bp\hbox to 0pt{%
\kern70bp %
\kern-2bp
\special{%
pdf:ann width 4bp height 2bp depth 2bp%
/Type/Annot%
/Subtype/Link%
/Border[0 0 1]%
/C[0 0 1]% blue border
/A%
/S/GoTo%
/D(änchør)%
%
%
}%
\vrule width4bp height2bp depth2bp\relax
\hss
}%
}%
}
\end
%%% test.tex %%%
The link is not working. Looking into the PDF file we can find
the link annotation:
4 0 obj
/Type/Annot
/Subtype/Link
/Border[0 0 1]
/C[0 0 1]
/A
/S/GoTo
/Dfeff00e4006e0063006800f80072
/Rect[68 48 72 52]
endobj
and the destination:
7 0 obj
[3 0 R/XYZ 30 150 null]
endobj
8 0 obj
/Names[c3a46e6368c3b8727 0 R]
endobj
The positions of both the link annotation and the destination are perfect.
The name for änchør is given both times as hexadecimal string.
That's ok, too. But the names are different:
Destination: c3a46e6368c3b872 == UTF-8
Link annot.: feff00e4006e0063006800f80072 == UTF-16BE with BOM
Conclusion:
* The encoding mess with 8-bit characters remain even with XeTeX.
Then I tried to be clever and a workaround by using
/Dc3a46e6368c3b872 for the link name in the source.
But it got converted and the PDF file still contains:
/Dfeff00e4006e0063006800f80072
Only the other way worked:
\special{pdf:dest feff00e4006e0063006800f80072 ...}
\special{pdf:ann ... /D(änchør) ...}
Result:
* Even for nice short names the size is doubled and increased
by two bytes.
* Assymetrical behaviour of \special commands.
* No documentation.
* Unfair, arbitrary byte strings can't be written.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
[XeTeX] bann...rule...eann == noann?
Hello,
I don't get an annotation using bann...eann:
% xetex --ini --output-driver='xdvipdfmx -V4' test
\catcode`\{=1
\catcode`\}=2
\pdfpagewidth=100bp
\pdfpageheight=200bp
\font\tenrm=cmr10\relax
\tenrm
\shipout\vbox{%
\kern-1in\relax
\hbox{%
\kern-1in\relax
\vrule width0pt height200bp depth0pt\relax
% Destination at (30bp,150bp)
\raise150bp\hbox to 0pt{%
\kern30bp %
\special{pdf:dest (foobar) [@thispage /XYZ @xpos @ypos null]}%
\kern-1bp
\vrule width2bp height1bp depth1bp\relax
\hss
}%
% Link annotation at (70bp,50bp)
\raise50bp\hbox to 0pt{%
\kern70bp %
\kern-2bp
\special{%
pdf:bann%
/Type/Annot%
/Subtype/Link%
/Border[0 0 1]%
/C[0 0 1]% blue border
/A%
/S/GoTo%
/D(foobar)%
%
%
}%
% ABC%
\vrule width4bp height2bp depth2bp\relax
\special{pdf:eann}%
\hss
}%
}%
}
\end
The annotation apperas, if there are characters inbetween (ABC).
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] How to Convert Devanagari (sanskrit) text to Telugu Text
2011/11/3 A u akupadhyay...@gmail.com: I am repatedly asked to compile here is the process of what I did Yes, I know. I tried your .tec file by txtconv and it seems to work. Under this directory /usr/local/texlive/2011/texmf-dist/fonts/misc/xetex/fontmappings/ 1. I created a folder called xetex-devtotel 2. I put the .map file there. 3. Run the teckit_compile 4. It generated the .tec file. 5. Ran the mktexlsr After that I run my .tex file using xetex. I got a blank output. am I missing something or is there anything wrong in the process I followed. run: strace xelatex DevtoTel 2strace.log and send me strace.log, I will try to find what's wrong On Thu, Nov 3, 2011 at 8:33 AM, Zdenek Wagner zdenek.wag...@gmail.com wrote: 2011/11/3 A u akupadhyay...@gmail.com: I did not get any error message either in my Mac or on my linux message. I did run mktexlsr after creating the ,map file. I am attaching the output that I got in my mac machine. Tha .map file itself does nothing, the .tec file is important? Have you run mktexlsr AFTER installing the .tec file? If the .tec file is in a correct directory, mktexlst has been run and it still does not work, it will be necessary to try strace xelatex DevtoTel in order to see what files are used. On Wed, Nov 2, 2011 at 7:33 PM, Zdenek Wagner zdenek.wag...@gmail.com wrote: 2011/11/2 A u akupadhyay...@gmail.com: 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 your help Is there some error message? Trying with txtconv I can verify that the map converts the file to something that looks like Telugu but then I have a problem typical for RHEL based distros, XeTeX finds the Pothana2000 font but xdvipdfmx cannot find it although the font is installed and other applications can use it. On Wed, Nov 2, 2011 at 8:49 AM, Zdenek Wagner zdenek.wag...@gmail.com wrote: 2011/11/2 A u akupadhyay...@gmail.com: 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 square brackets). You can also add it to the current font by \addfontfeatures[Mapping=mapfilename]. It is described in the fontspec manual. आशा कि यह सलाह आपके लिए लाभदायक होगा। On Wed, Nov 2, 2011 at 1:04 AM, bhutex bhu...@gmail.com wrote: On Tue, Nov 1, 2011 at 5:10 PM, A u akupadhyay...@gmail.com wrote: Thanks for your help. I am attaching the .map file I created. I was wondering if you can tell me if there are any errors. because I am getting a blank pdf output. After creating the .map file you have to compile it with teckit and .tec file will be the output. .tec file is a binary file. You have to keep this in appropriate directory and then run mktexlsr. After that you will tell XeTeX or XeLaTeX to use this .tec file. Then only your devnagari document will convert in telugu script. -- Happy TeXing The BHU TeX Group क्या आप यह देख पा रहें हैं। इस का मतलब आप का कम्प्यूटर यूनीकोड को समझती है। देर किस बात की हिन्दी मे चिठ्ठियां लिखिये। I use OpenOffice3.1! Do you!! -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Zdeněk Wagner http://hroch486.icpf.cas.cz/wagner/ http://icebearsoft.euweb.cz -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Zdeněk Wagner http://hroch486.icpf.cas.cz/wagner/ http://icebearsoft.euweb.cz -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Zdeněk Wagner http://hroch486.icpf.cas.cz/wagner/ http://icebearsoft.euweb.cz --
Re: [XeTeX] How to Convert Devanagari (sanskrit) text to Telugu Text
Am 03.11.2011 um 13:46 schrieb A u: /usr/local/texlive/2011/texmf-dist/fonts/misc/xetex/fontmappings/ The correct pathname would be: /usr/local/texlive/2011/texmf-dist/fonts/misc/xetex/fontmapping. Since your files are local additions to the TeX distribution it's better you save them in /usr/local/texlive/texmf-local/fonts/fonts/misc/xetex/fontmapping sudo mkdir -p /usr/local/texlive/texmf-local/fonts/misc/xetex/fontmapping/dev2tel # for easier reading sudo cp /path/to/your/file.map /usr/local/texlive/texmf-local/fonts/misc/xetex/fontmapping/dev2tel sudo teckit_compile /usr/local/texlive/texmf-local/fonts/misc/xetex/fontmapping/dev2tel/your file.map -o /usr/local/texlive/texmf-local/fonts/misc/xetex/fontmapping/dev2tel/your file.tec sudo mktexlsr /usr/local/texlive/texmf-local If the PDF output is still quite empty we'd need the source file and the LOG file from the XeLaTeX run. -- Greetings Pete Theory and practice are the same, in theory, but, in practice, they are different. -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Hyperref \hyperlink and \hypertarget not working with accented characters
I think you are right. Surely the reason most of us care about these issues is that we are working in other languages, not just English. I began using XeTeX specifically because of how it handles multiple languages. My view is terribly simple: the world is far too interesting a place to be restricted to ASCII! Sent from my iPhone On 3 Nov, 2011, at 21:53, Philip TAYLOR (Webmaster, Ret'd) p.tay...@rhul.ac.uk wrote: Danyll Wills wrote: Phil, I use XeLaTeX for Chinese, Japanese and Mongolian. I have watched the discussion over the past few days and am 100 per cent behind you. I started my programming life in the early '80s using 8086 Assembly language. Nothing irritates me more than the idea that ASCII is the only way to go. Your latest explanation was spot on! Well done. /Danyll Thank you, Danyll. Although there are times when I feel like a lone prophet crying in the desert, I genuinely believe that people such as Heiko, Ross, Arthur et al are actually on our side : they too understand the need for people to be able to mark-up and typeset in any of the world's languages, and have probably done more than most to make this possible (and are still doing so). Yet there /are/ lacunæ, and when they are identified (such as the lack of support for arbitrary Unicode characters in the first parameter to \hyperlink and \hypertarget), then surely it is better to accept that work still needs to be done, rather than attempt to sweep the problem under the carpet by saying Don't use non-ASCII characters in the link without adding until this limitation can be overcome, or by stating that Letters and digits are safe without clarifying that by letter the author is referring solely to a very restricted set of letters that almost certainly excludes such common letters as ł or ę, ư or ẻ. ** Phil. -- 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] How to Convert Devanagari (sanskrit) text to Telugu Text
2011/11/3 Peter Dyballa peter_dyba...@web.de: Am 03.11.2011 um 13:46 schrieb A u: /usr/local/texlive/2011/texmf-dist/fonts/misc/xetex/fontmappings/ The correct pathname would be: /usr/local/texlive/2011/texmf-dist/fonts/misc/xetex/fontmapping. Since your files are local additions to the TeX distribution it's better you save them in /usr/local/texlive/texmf-local/fonts/fonts/misc/xetex/fontmapping This little misprint should not be a problem, AFAIK xetex finds the .tec files below $TEXMF/fonts/misc, thus fontmappings instead of fontmapping should not matter but doubling fonts in texmf-local/fonts/fonts/misc/... will be a problem. The output of strace could help. sudo mkdir -p /usr/local/texlive/texmf-local/fonts/misc/xetex/fontmapping/dev2tel # for easier reading sudo cp /path/to/your/file.map /usr/local/texlive/texmf-local/fonts/misc/xetex/fontmapping/dev2tel sudo teckit_compile /usr/local/texlive/texmf-local/fonts/misc/xetex/fontmapping/dev2tel/your file.map -o /usr/local/texlive/texmf-local/fonts/misc/xetex/fontmapping/dev2tel/your file.tec sudo mktexlsr /usr/local/texlive/texmf-local If the PDF output is still quite empty we'd need the source file and the LOG file from the XeLaTeX run. -- Greetings Pete Theory and practice are the same, in theory, but, in practice, they are different. -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Zdeněk Wagner http://hroch486.icpf.cas.cz/wagner/ http://icebearsoft.euweb.cz -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] XeTeX/TeX Live : Setting the default language
Just edit your language.def file. Actually, you can create a one-line file that says british loadhyph-en-gb.tex (not hyph-en-gb.tex!) and create the format with fmtutil. Arthur -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] [tex-live] XeTeX/TeX Live : Setting the default language
2011/11/3 Arthur Reutenauer arthur.reutena...@normalesup.org: Just edit your language.def file. Actually, you can create a one-line file that says british loadhyph-en-gb.tex (not hyph-en-gb.tex!) and create the format with fmtutil. The British hyphenation patterns are loaded in the XeLaTeX format so that you can just switch them using Polyglossia. They are also loaded in plain XeTeX (unless it was deselected at TL install time). You have to look into xetex.log, find the corresponding number and then assign it to \language, it is not necessary to build a format. Arthur -- Zdeněk Wagner http://hroch486.icpf.cas.cz/wagner/ http://icebearsoft.euweb.cz -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] [tex-live] XeTeX/TeX Live : Setting the default language
Merci, Arthur ! Arthur Reutenauer wrote: Just edit your language.def file. Actually, you can create a one-line file that says british loadhyph-en-gb.tex (not hyph-en-gb.tex!) and create the format with fmtutil. Arthur -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] [tex-live] XeTeX/TeX Live : Setting the default language
On Thu, Nov 03, 2011 at 06:46:12PM +0100, Zdenek Wagner wrote:
2011/11/3 Arthur Reutenauer arthur.reutena...@normalesup.org:
Just edit your language.def file. Actually, you can create a one-line
file that says british loadhyph-en-gb.tex (not hyph-en-gb.tex!) and
create the format with fmtutil.
The British hyphenation patterns are loaded in the XeLaTeX format so
that you can just switch them using Polyglossia. They are also loaded
in plain XeTeX (unless it was deselected at TL install time). You have
to look into xetex.log, find the corresponding number and then assign
it to \language, it is not necessary to build a format.
Even simpler (assuming the pattern is loaded in the format):
\input knuth
\uselanguage{british} % or ukenglish or UKenglish, all synonyms
\input knuth
\bye
Works for all etex based engines.
Regards,
Khaled
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] [tex-live] XeTeX/TeX Live : Setting the default language
Khaled Hosny wrote:
Even simpler (assuming the pattern is loaded in the format):
\input knuth
\uselanguage{british} % or ukenglish or UKenglish, all synonyms
\input knuth
\bye
Works for all etex based engines.
Excellent, thank you Khaled. Of course, it took me
a minute or two to discover that \input Knuth was
pulling in some sample text and not the definition
of \uselanguage ! And, sadly, British is not
a synonym of british, even though I can think of
no context in which it would ever be spelled with
a lower-case b ...
** Phil.
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] How to Convert Devanagari (sanskrit) text to Telugu Text
Am 03.11.2011 um 16:57 schrieb Zdenek Wagner: doubling fonts in texmf-local/fonts/fonts/misc/... will be a problem. Bad mistake, indeed. Too many interrupts might excuse this faux-pas... The output of strace could help. Mac OS X comes without strace. But it has DTrace... -- Greetings Pete You can never know too little of what is not worth knowing at all. – Anon. -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] How to Convert Devanagari (sanskrit) text to Telugu Text
I am attaching the .map file, I did everything as Wagner I am getting this error desktop:~$ sudo teckit_compile /usr/local/texlive/texmf-local/fonts/misc/xetex/fontmapping/dev2tel/devtotel.map -o /usr/local/texlive/texmf-local/fonts/misc/xetex/fontmapping/dev2tel/devtotel.map unexpected identifier: U at line 54 compilation failed: status = -9 I checked line number 54 and it looks like this U+092F U+0C2F On Thu, Nov 3, 2011 at 4:36 PM, Peter Dyballa peter_dyba...@web.de wrote: Am 03.11.2011 um 16:57 schrieb Zdenek Wagner: doubling fonts in texmf-local/fonts/fonts/misc/... will be a problem. Bad mistake, indeed. Too many interrupts might excuse this faux-pas... The output of strace could help. Mac OS X comes without strace. But it has DTrace... -- Greetings Pete You can never know too little of what is not worth knowing at all. – Anon. -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex devtotel.map Description: Binary data -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] How to Convert Devanagari (sanskrit) text to Telugu Text
I created new map file and it did not give any errors. but I am still getting blank pdf. I am attaching the tex file that I am working with along with pdf output and log file. I would appreciate your help On Thu, Nov 3, 2011 at 4:36 PM, Peter Dyballa peter_dyba...@web.de wrote: Am 03.11.2011 um 16:57 schrieb Zdenek Wagner: doubling fonts in texmf-local/fonts/fonts/misc/... will be a problem. Bad mistake, indeed. Too many interrupts might excuse this faux-pas... The output of strace could help. Mac OS X comes without strace. But it has DTrace... -- Greetings Pete You can never know too little of what is not worth knowing at all. – Anon. -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex DevtoTel.tex Description: TeX document DevtoTel.pdf Description: Adobe PDF document DevtoTel.log Description: Binary data -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] How to Convert Devanagari (sanskrit) text to Telugu Text
On Nov 3, 2011, at 5:53 PM, A u wrote: I am attaching the .map file, I did everything as Wagner I am getting this error desktop:~$ sudo teckit_compile /usr/local/texlive/texmf-local/fonts/misc/xetex/fontmapping/dev2tel/devtotel.map -o /usr/local/texlive/texmf-local/fonts/misc/xetex/fontmapping/dev2tel/devtotel.map unexpected identifier: U at line 54 compilation failed: status = -9 I checked line number 54 and it looks like this U+092F U+0C2F On Thu, Nov 3, 2011 at 4:36 PM, Peter Dyballa peter_dyba...@web.de wrote: Am 03.11.2011 um 16:57 schrieb Zdenek Wagner: doubling fonts in texmf-local/fonts/fonts/misc/... will be a problem. Bad mistake, indeed. Too many interrupts might excuse this faux-pas... The output of strace could help. Mac OS X comes without strace. But it has DTrace... -- Greetings Pete You can never know too little of what is not worth knowing at all. Howdy, Let's see... line 54... that has U+092E U+0C2EU and isn't that an extra U at the end? Good Luck, Herb Schulz (herbs at wideopenwest dot com) -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] How to Convert Devanagari (sanskrit) text to Telugu Text
Am 03.11.2011 um 23:53 schrieb A u: I checked line number 54 and it looks like this U+092F U+0C2F To me it looks like U+092E U+0C2EU -- Greetings Pete Remember: use logout to logout. -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] How to Convert Devanagari (sanskrit) text to Telugu Text
2011/11/4 Peter Dyballa peter_dyba...@web.de: Am 03.11.2011 um 23:53 schrieb A u: I checked line number 54 and it looks like this U+092F U+0C2F To me it looks like U+092E U+0C2EU Strange... I have looked at the file I saved 24 hours ago. At this file line 54 is empty, all mappings contain and there is no superfluous U. -- Greetings Pete Remember: use logout to logout. -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Zdeněk Wagner http://hroch486.icpf.cas.cz/wagner/ http://icebearsoft.euweb.cz -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] How to Convert Devanagari (sanskrit) text to Telugu Text
Am 04.11.2011 um 00:04 schrieb A u: I am attaching the tex file that I am working with along with pdf output and log file. You would have found the cause of the failures if would have looked into the LOG file... Firstly you are obviously using TeX Live 2010. So installing the teckit files in TeX Live 2011 could not yield much. Which the LOG file reports (at line #446: Font mapping `devtel.tec' for font `Pothana2000 ' not found.) XeLaTeX, and *every* other programme, cannot find a file that does not exist. Didn't you attach devtotel named files? And the effective TEC file did not exist when you did run XeLaTeX because it was created due to the polluted and therefore faulty MAP file. Secondly the LOG file records: Missing character: There is no ध in font Pothana2000 /ICU:script=telu;language=DFLT;mapping=devtel;;! This is just a faulty error, because due to the first error XeLaTeX was indeed using the originally used Devanagari characters and not Telugu. A bit of accuracy would have saved you some days of whatever. -- Greetings Pete You can never know too little of what is not worth knowing at all. – Anon. -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] How to Convert Devanagari (sanskrit) text to Telugu Text
Am 04.11.2011 um 01:13 schrieb Zdenek Wagner: 2011/11/4 Peter Dyballa peter_dyba...@web.de: Am 03.11.2011 um 23:53 schrieb A u: I checked line number 54 and it looks like this U+092F U+0C2F To me it looks like U+092E U+0C2EU Strange... I have looked at the file I saved 24 hours ago. At this file line 54 is empty, all mappings contain and there is no superfluous U. Could be the programme you are using for counting lines starts with a line #0? -- Greetings Pete Encryption, n.: A powerful algorithmic encoding technique employed in the creation of computer manuals. -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] How to Convert Devanagari (sanskrit) text to Telugu Text
Am 04.11.2011 um 00:04 schrieb A u: I created new map file and it did not give any errors. but I am still getting blank pdf. By using the correct TEC file's name I get something Indic with a Latin page number 1. The fonts used are, according to pdfinfo: name type emb sub uni object ID - --- --- --- - DXJXWE+LMRoman12-Regular-Identity-H CID Type 0C yes yes yes 5 0 NSPUNS+Pothana2000 CID TrueType yes yes yes 7 0 -- Greetings Pete If it dies, it's biology. If it blows up, it's chemistry. If it doesn't work, it's physics. – University washroom sgraffito -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] How to Convert Devanagari (sanskrit) text to Telugu Text
2011/11/4 Peter Dyballa peter_dyba...@web.de: Am 04.11.2011 um 01:13 schrieb Zdenek Wagner: 2011/11/4 Peter Dyballa peter_dyba...@web.de: Am 03.11.2011 um 23:53 schrieb A u: I checked line number 54 and it looks like this U+092F U+0C2F To me it looks like U+092E U+0C2EU Strange... I have looked at the file I saved 24 hours ago. At this file line 54 is empty, all mappings contain and there is no superfluous U. Could be the programme you are using for counting lines starts with a line #0? No, I use vim, gedit and oXygen/ and all of them start at 1. -- Greetings Pete Encryption, n.: A powerful algorithmic encoding technique employed in the creation of computer manuals. -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Zdeněk Wagner http://hroch486.icpf.cas.cz/wagner/ http://icebearsoft.euweb.cz -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Anchor names
On Fri, Nov 04, 2011 at 07:31:02AM +1100, Ross Moore wrote:
On 04/11/2011, at 1:58 AM, Heiko Oberdiek wrote:
Hello,
to get more to the point, I start a new thread.
Yes. very good idea.
As we have learned, the PDF specification uses byte strings
for anchor names. And there is a wish to use normal characters
in anchor names.
Within the (La)TeX source, yes!
Of course it needs to be encoded to be safe within the PDF.
That's the problem, the anchor names could also be used as
official part of the PDF file, because it could be referenced, e.g.:
mybeautifuldocument.pdf#Introduction
Let's make an example:
xetex --ini --output-driver='xdvipdfmx -V4' test
\special{pdf:dest (änchør) [@thispage /XYZ @xpos @ypos null]}%
\special{%
pdf:ann width 4bp height 2bp depth 2bp%
/Type/Annot%
/Subtype/Link%
/Border[0 0 1]%
/C[0 0 1]% blue border
/A%
/S/GoTo%
/D(änchør)%
The link is not working. Looking into the PDF file we can find
the link annotation:
4 0 obj
/Type/Annot
/Subtype/Link
/Border[0 0 1]
/C[0 0 1]
/A
/S/GoTo
/Dfeff00e4006e0063006800f80072
In my reading of the PDF Spec. I came to the conclusion
that this UTF-16BE based format is not supported for Name objects.
But maybe I'm wrong here.
My understanding is that it does not matter, whether the byte
string could be interpreted in some encoding. The characters
are just bytes. Also there are keys in the /Dests name tree
and are compared at the byte level. Thus a name encoded as
UTF-8, ISO-8859-1 or UTF-16BE are different strings and thus
different names.
Destination: c3a46e6368c3b872 == UTF-8
Link annot.: feff00e4006e0063006800f80072 == UTF-16BE with BOM
The spec reads that differences in Literal strings are allowed,
provided that they convert to the same thing in Unicode.
So there must be an internal representation that Adobe uses,
but is not visible to us, as builders of PDF documents.
Where, which section?
A literal string can be written different ways at syntax level:
(test) = 74657374 = (\164\145\163\164) = (\164e\163t)
Probably you are referring the Text String Type used for
the text in the bookmarks, the document information and other
places. These strings can be encoded either in PDFDocEncoding
or UTF-16BE with BOM.
Conclusion:
* The encoding mess with 8-bit characters remain even with XeTeX.
Well, surely it is manifest only in the driver part: xdvipdfmx
No, the problem are both parts. XeTeX can only write UTF-8,
the death for binary data.
Then I tried to be clever and a workaround by using
/Dc3a46e6368c3b872 for the link name in the source.
But it got converted and the PDF file still contains:
/Dfeff00e4006e0063006800f80072
Only the other way worked:
\special{pdf:dest feff00e4006e0063006800f80072 ...}
\special{pdf:ann ... /D(änchør) ...}
OK.
Glad you did this test.
It shows two things:
1. that such text strings may well be valid for Names,
and that the PDF spec. is unclear about this;
I can't follow. Both string representations are covered
by the PDF specification, a literal string can be
specified in parentheses with an escaping mechanism (backslash)
or given as hex string in angle brackets. Unclear is the
syntax of the argument for \special{pdf:dest ...}.
2. these UTF16-BE strings are *not* equivalent to other
ways of encoding Name objects, after all.
This is something that should be reported as a bug to Adobe.
There is no problem with the PDF specification. A destination
name is a byte string. You can use UTF-16BE, invalid UTF-8,
a mixture of UTF-32BE with us-ascii, ... all are valid byte strings.
The problem is with xdvipdfmx that recodes the UTF-8 string
provided by XeTeX's specials in different ways.
Can you produce a set of 3 or more PDFs that show the different
behaviours ?
Better still: a single PDF that illustrates the (non-)working
of hyperlinks according to the encodings of the Name objects
and Destinations.
Save my example as test.tex and run
xetex --ini --output-driver='xdvipdfmx -V4' test
(I miss an easy switch for XeTeX to set the PDF version).
With PDF-1.4 object stream compression is not available
and the PDF file can be analyzed directly using a simple
text viewer. (Otherwise the destination and annotation
objects are compressed).
Do it both with XeTeX and pdfTeX (with appropriate inputenc,
to handle the UTF8 input), to test whether there are any
differences.
pdfTeX is fine, because it doesn't reencode the strings.
Also \pdfescapestring, \pdfescapename, \pdfescapehex
are available for syntactically correct literal strings.
I've not tested pdfTeX yet, because of the extra macro layer
required. Does hyperref handle the required conversions then?
It depends on which part of hyperref you are looking.
Yours sincerely
Heiko Oberdiek
