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. A
2011/11/4 Peter Dyballa :
>
> Am 04.11.2011 um 01:13 schrieb Zdenek Wagner:
>
>> 2011/11/4 Peter Dyballa :
>>>
>>> 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
>>>
>> Strang
2011/11/4 A u :
> Here is the strace.log file
>
There is something wrong with your ls-R files. As you can see on lines
2137, 2138, 2149, xetex tries to locate devtrel.tec in the current
directory only and then gives up. Compare for instance lines 2119 and
below. File tex-text.tec is not found in th
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
Am 04.11.2011 um 01:13 schrieb Zdenek Wagner:
> 2011/11/4 Peter Dyballa :
>>
>> 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 sav
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
2011/11/4 Peter Dyballa :
>
> 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 conta
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 inf
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/fo
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 wrote:
>
> Am 03.11.2011 um 16:57 schrieb Zde
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:
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
Hi Heiko,
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.
With
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
On Thu, Nov 03, 2011 at 06:46:12PM +0100, Zdenek Wagner wrote:
> 2011/11/3 Arthur Reutenauer :
> > 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
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
--
Subscript
2011/11/3 Arthur Reutenauer :
> 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
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.:
h
It is important for a book on which I am currently working
that hyphenation be according to the rules of and not
. I have just invoked TLMGR, and cannot see where the
default language should be set. I have the file :
hyph-en-gb.tex
and in pre-TeX Live / XeTeX days, would simply have l
2011/11/3 Peter Dyballa :
>
> 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 distribu
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 restr
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
2011/11/3 A u :
> 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.
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 height200b
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`\
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/gro
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
At least you can do your macro programming in whatever language you want,
in XeLaTeX, just like I do my macro programming only in Persian (which had
been my dream for a long time). see attached for an example.
2011/11/3 Danyll Wills
> Phil, I use XeLaTeX for Chinese, Japanese and Mongolian. I ha
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. Yo
I am repatedly asked to compile here is the process of what I did
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
2011/11/3 A u :
> 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 instal
you need to use teckit_compile which is included in TeXLive.
On Thu, Nov 3, 2011 at 10:26 PM, bhutex wrote:
>
>
> On Thu, Nov 3, 2011 at 3:54 AM, A u 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
On Thu, Nov 3, 2011 at 3:54 AM, A u 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 usin
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.
On Wed, Nov 2, 2011 at 7:33 PM, Zdenek Wagner wrote:
> 2011/11/2 A u :
> > I am attaching the files, can you tell me w
Dear Arthur, Paul, Heiko, Ross, others --
Please stop. I am serious. Just stop.
I was serious too (even when speaking of nominating Heiko
for the non-existent position of vice-Grand-Wizard of TeX :
that was a genuine expression of respect for his quite remarkable
solution to the problem o
35 matches
Mail list logo
