Thank you for the response. My perception is that beginners don't know what type they are. They start out by experimenting (trial-and-error) as a way of learning TeX. Often, they do not realize what they don't know. We'll just supply the best examples we can and explain them the best we can.<br>
<br>I can respond further off-list when my Mac comes back from repair. Same for sending you a scope document.<br><br>Neale<br><br><div class="gmail_quote">On Thu, Dec 4, 2008 at 10:21 AM, <span dir="ltr"><<a href="mailto:xetex-request@tug.org">xetex-request@tug.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Send XeTeX mailing list submissions to<br>
<a href="mailto:xetex@tug.org">xetex@tug.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://tug.org/mailman/listinfo/xetex" target="_blank">http://tug.org/mailman/listinfo/xetex</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:xetex-request@tug.org">xetex-request@tug.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:xetex-owner@tug.org">xetex-owner@tug.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of XeTeX digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Request for Participation (RFP) (Peter Dyballa)<br>
2. Re: Could not load both Bold and BoldItalic. (Peter Dyballa)<br>
3. Re: Arabic Transliteration (Gareth Hughes)<br>
4. Help on pdf documents size restriction (Francisco Chaves)<br>
5. Re: Could not load both Bold and BoldItalic. (Akira Kakuto)<br>
6. Re: how to test whether a font exists? (Grzegorz Murzynowski)<br>
7. Re: Request for Participation (RFP) (Grzegorz Murzynowski)<br>
8. Re: Could not load both Bold and BoldItalic. (Stephen Moye)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 4 Dec 2008 15:57:45 +0100<br>
From: Peter Dyballa <Peter_Dyballa@Web.DE><br>
Subject: Re: [XeTeX] Request for Participation (RFP)<br>
To: Unicode-based TeX for Mac OS X and other platforms <<a href="mailto:xetex@tug.org">xetex@tug.org</a>><br>
Message-ID: <7BE66394-BAF2-488D-BC3D-9E7D5B6D528E@Web.DE><br>
Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes;<br>
format=flowed<br>
<br>
<br>
Am 04.12.2008 um 00:23 schrieb Neaale Hirsh:<br>
<br>
> \usepackage[cm-default]{fontspec} % XeLaTeX only<br>
> \defaultfontfeatures{Mapping=tex-text} % XeLaTeX only<br>
> \setmainfont{Times New Roman} % XeLaTeX only<br>
> \documentclass[12pt]{article} % XeLaTeX only<br>
> This is some text % XeLaTeX only<br>
<br>
<br>
Neale,<br>
<br>
can it be that you assume fontspec is XeTeX's LaTeX?<br>
<br>
As you wrote, XeTeX is able to use fonts in *some* way. As TeX can.<br>
LaTeX introduced, quite late, a useful scheme to handle fonts (New<br>
Font Selection Scheme, NFSS). Because XeTeX is enabling this fontspec<br>
is meant to access non-TeX features of non-TeX fonts. In XeLaTeX,<br>
XeTeX's LaTeX variant.<br>
<br>
So I diagnose that you need to learn LaTeX to understand fontspec's<br>
add-ons. This would allow you to correct what I have cited (assuming<br>
it's intended as the start of a XeLaTeX document).<br>
<br>
<br>
What I can offer is answers to questions that might have asked years<br>
ago and have now forgotten. If you could repeat my questions ? I<br>
still have (improved) answers! With these questions and (more)<br>
answers you could compile the work. It will help both: you and other<br>
XWPs.<br>
<br>
I would also comment on the compilation.<br>
<br>
<br>
Answers<br>
<br>
Xunicode is meant for those XeLaTeX users that keep writing \"a<br>
instead of ?. And so on.<br>
<br>
Xltxtra helps in using macros like \XeTeX or \XeLaTeX. It adds<br>
commands like \textsuperscript and \textsubscript, which are useful<br>
when you write about a green-house problem caused by CO2 or CH4 or<br>
H2O and also when you try to abbreviate the costs that banks cost<br>
nowadays. The \vfrac command (which works better than xfrac) could be<br>
used to describe that in some not so far future carbon-dioxide could<br>
fulfil one hundredth of the Earth's atmosphere. (There is also a now<br>
working \showhyphens command, but this is of a rather esoteric use.)<br>
<br>
--<br>
Greetings<br>
<br>
Pete<br>
<br>
Real Time, adj.:<br>
Here and now, as opposed to fake time, which only occurs there and<br>
then.<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 4 Dec 2008 16:15:21 +0100<br>
From: Peter Dyballa <Peter_Dyballa@Web.DE><br>
Subject: Re: [XeTeX] Could not load both Bold and BoldItalic.<br>
To: <a href="mailto:news2@nililand.de">news2@nililand.de</a>, Unicode-based TeX for Mac OS X and other<br>
platforms <<a href="mailto:xetex@tug.org">xetex@tug.org</a>><br>
Message-ID: <2659AED7-15DA-4E7C-864C-330847D6CE6F@Web.DE><br>
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed<br>
<br>
<br>
Am 04.12.2008 um 15:40 schrieb Ulrike Fischer:<br>
<br>
> I prefer to check the terminal output:<br>
><br>
> This is the message if xdvipdfmx fails for some reason:<br>
><br>
> Output file removed.<br>
><br>
> Error 1 (driver return code) generating output;<br>
> file test-xetex.pdf may not be valid.<br>
<br>
In Mac OS X this means that when you're lucky xdvipdfmx's output was<br>
not written to disk.<br>
<br>
Anyway, computers are like women (and men): they can tell you<br>
everything that you don't need to believe. Double-checking is better.<br>
<br>
<br>
Maybe Kakuto-san has a better explanation!<br>
<br>
--<br>
Mit friedvollen Gr??en<br>
<br>
Pete<br>
<br>
We have to expect it, otherwise we would be surprised.<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Thu, 04 Dec 2008 15:19:30 +0000<br>
From: Gareth Hughes <<a href="mailto:garzohugo@gmail.com">garzohugo@gmail.com</a>><br>
Subject: Re: [XeTeX] Arabic Transliteration<br>
To: Unicode-based TeX for Mac OS X and other platforms <<a href="mailto:xetex@tug.org">xetex@tug.org</a>><br>
Message-ID: <<a href="mailto:4937F502.8060902@gmail.com">4937F502.8060902@gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Hi Mohammad!<br>
<br>
Mohammad Gharaibeh wrote:<br>
> thank you for your help, but there are some questions left<br>
> open. I don?t know how to use the Unicode characters in<br>
> XeTeX. I already put my editor font encoding on UTF-8.<br>
<br>
Firstly, you need to be using a font that has these characters. As<br>
Tilman has already mentioned, Gentium (from <a href="http://www.sil.org/" target="_blank">http://www.sil.org/</a>) and<br>
Linux Libertine have them.<br>
<br>
Secondly, the editor you are using to prepare your document might not<br>
display these characters in its default font. I use gedit which has very<br>
good Unicode support. Which editor are you using?<br>
<br>
Thirdly, there are three ways you can get these characters in your<br>
editor. The simplest is to use a character palette/map, which most OSes<br>
have fitted as standard: find the character, copy and paste. Another way<br>
is to use an input method like SCIM or a virtual keyboard set up with<br>
the characters you want (you could play around with Yudit ?<br>
<a href="http://www.yudit.org/" target="_blank">http://www.yudit.org/</a> ? it is a text editor with built-in input methods,<br>
or BP's suggestion of BabelMap/Pad might help). The third way is to use<br>
Tilman's method of \char"0351 for ? ?ayn and \char"0357 for ? hamza, but<br>
I find this a bit clunky compared to using a good Unicode text editor.<br>
<br>
If you are still having difficulty, it would be very useful to know<br>
which operating system and text editor you are using, because these are<br>
not really XeTeX issues.<br>
<br>
Best wishes,<br>
<br>
Gareth.<br>
<br>
--<br>
Department of Eastern Christianity<br>
Oriental Institute<br>
Pusey Lane<br>
Oxford<br>
OX1 2LE<br>
<br>
+44 (0)1865 610227<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Thu, 4 Dec 2008 10:31:38 -0500<br>
From: "Francisco Chaves" <<a href="mailto:pachopepe@gmail.com">pachopepe@gmail.com</a>><br>
Subject: [XeTeX] Help on pdf documents size restriction<br>
To: <a href="mailto:xetex@tug.org">xetex@tug.org</a><br>
Message-ID:<br>
<<a href="mailto:cad5740812040731m6b31fd07h7d70d547289fc18c@mail.gmail.com">cad5740812040731m6b31fd07h7d70d547289fc18c@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Hi all<br>
<br>
I am working on project and I am generating pdf documents using XeLaTeX, but<br>
I have a constraint size of 35KB including a digital signature (more or less<br>
8KB). I 've used differents fonts such as "URW Gothic L" having as a final<br>
result a pdf documet size of 24KB. Nevertheless, I have to use the Arial<br>
Narrow font and I only have the ttf files from windows, but with this font<br>
the pdf size increases to more than 45KB.<br>
<br>
What would you suggest I have to do in order to reduce the pdf document<br>
size?<br>
I have asked my self about what are the best type of fonts to reduce the pdf<br>
size (otf, ttf, pfa, pfb, ...)? but I have not come up with an answer.<br>
does exist a converter between ttf and any other font format in order to<br>
obtain a better document size?<br>
<br>
Thanks in advance<br>
--<br>
Francisco Jose CHAVES<br>
PhD. en Informatique<br>
ENS Lyon, France<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://tug.org/pipermail/xetex/attachments/20081204/2830f683/attachment-0001.html" target="_blank">http://tug.org/pipermail/xetex/attachments/20081204/2830f683/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Fri, 05 Dec 2008 00:40:41 +0900<br>
From: Akira Kakuto <<a href="mailto:kakuto@fuk.kindai.ac.jp">kakuto@fuk.kindai.ac.jp</a>><br>
Subject: Re: [XeTeX] Could not load both Bold and BoldItalic.<br>
To: <a href="mailto:xetex@tug.org">xetex@tug.org</a>, <a href="mailto:Peter_Dyballa@web.de">Peter_Dyballa@web.de</a><br>
Cc: <a href="mailto:news2@nililand.de">news2@nililand.de</a><br>
Message-ID: <200812041540.mB4Feg3a028490@jupiter><br>
Content-Type: Text/Plain; charset=us-ascii<br>
<br>
> Then these fonts aren't PostScript Type 1.<br>
<br>
PostScript Type 1 fonts can be used by XeTeX-xdvipdfmx without<br>
tfm fonts. Of course you have to make cache for the type1 by fc-cache.<br>
Please test<br>
\font\f="Utopia/R"<br>
\f This is a test.<br>
\bye<br>
<br>
Best,<br>
Akira<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Thu, 04 Dec 2008 16:46:43 +0100<br>
From: Grzegorz Murzynowski <natror@o2.pl><br>
Subject: Re: [XeTeX] how to test whether a font exists?<br>
To: Unicode-based TeX for Mac OS X and other platforms <<a href="mailto:xetex@tug.org">xetex@tug.org</a>><br>
Message-ID: <4937FB63.4020002@o2.pl><br>
Content-Type: text/plain; charset=UTF-8; format=flowed<br>
<br>
Thanks.<br>
It really _is_ very slow in my system.<br>
<br>
Will Robertson pisze:<br>
> On 04/12/2008, at 3:25 AM, Grzegorz Murzynowski wrote:<br>
><br>
>> I know it's basic but I don't find in The XeTeX Companion a primitive<br>
>> for testing existence of a font.<br>
>><br>
>> It would be nice to write something like<br>
>><br>
>> \iffontexists "Garamond Premier Pro" \setmainfont{Garamond Premier<br>
>> Pro}<br>
>> \else \typeout{@@@@ no Garamond Premier Pro, leaving the default<br>
>> font}\fi<br>
>><br>
>> Any suggestions?<br>
><br>
> The reason this primitive doesn't exist is for performance reasons; it<br>
> can be very slow to check for the non-existence of a font.<br>
><br>
> Jonathan has a sample file floating around called<br>
> "testfontavailability" which I've reproduced below; it should be a<br>
> good starting point :)<br>
><br>
> Hope this helps,<br>
> Will<br>
><br>
> % Macros to try and find available fonts for XeTeX sample docs<br>
> %<br>
> % Usage:<br>
> %<br>
> % \testFontIsAvailable{font-name}<br>
> % sets \ifFontIsAvailable according to whether or not it could be found<br>
> %<br>
> % \FindAnInstalledFont{font-name/alternative/another/yet-another}{\cs}<br>
> % searches for an available font from among the names given,<br>
> % and \def's the control sequence \cs to the first one found<br>
> % or to <No suitable font found> if none (which will subsequently<br>
> % cause an error when used in a \font command).<br>
> \newif\ifFontIsAvailable<br>
> \def\testFontAvailability#1{<br>
> \count255=\interactionmode<br>
> \batchmode<br>
> \let\preload=\nullfont<br>
> \font\preload="#1" at 10pt<br>
> \ifx\preload\nullfont \FontIsAvailablefalse<br>
> \else \FontIsAvailabletrue \fi<br>
> \interactionmode=\count255<br>
> }<br>
> \def\FindAnInstalledFont#1#2{<br>
> \expandafter\getFirstFontName#1/\end<br>
> \let\next\gobbleTwo<br>
> \ifx\trialFontName\empty<br>
> \def#2{<No suitable font found>}%<br>
> \else<br>
> \testFontAvailability{\trialFontName}<br>
> \ifFontIsAvailable<br>
> \edef#2{\trialFontName}%<br>
> \else<br>
> \let\next\FindAnInstalledFont<br>
> \fi<br>
> \fi<br>
> \expandafter\next\expandafter{\remainingNames}{#2}<br>
> }<br>
> \def\getFirstFontName#1/#2\end{\def\trialFontName{#1}\def<br>
> \remainingNames{#2}}<br>
> \def\gobbleTwo#1#2{}<br>
><br>
> _______________________________________________<br>
> XeTeX mailing list<br>
> <a href="mailto:postmaster@tug.org">postmaster@tug.org</a><br>
> <a href="http://tug.org/mailman/listinfo/xetex" target="_blank">http://tug.org/mailman/listinfo/xetex</a><br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Thu, 04 Dec 2008 16:47:23 +0100<br>
From: Grzegorz Murzynowski <natror@o2.pl><br>
Subject: Re: [XeTeX] Request for Participation (RFP)<br>
To: Unicode-based TeX for Mac OS X and other platforms <<a href="mailto:xetex@tug.org">xetex@tug.org</a>><br>
Message-ID: <4937FB8B.1060104@o2.pl><br>
Content-Type: text/plain; charset=UTF-8; format=flowed<br>
<br>
Neaale Hirsh pisze:<br>
> once per document; we adjust the fonts or font style for<br>
> captions, math, headings, etc. In XeTeX and XeLaTeX, we<br>
> stumble around until things work, more or less:<br>
><br>
> \font\"Monaco" at 12 pt % XeTeX only<br>
Probably it should be<br>
\font\A="Monaco" at 12 pt<br>
And it's _not_ Plain XeTeX only. But why to write a hundred lines like<br>
this when LaTeX/fontspec & documentclass has already done that for you?<br>
<br>
What kind of beginner do you mind: is that a beginner who wants to have<br>
their text typeset anyhow or is that a ?beginner? who wants to prepare a<br>
book for printing and set all the layouts?<br>
<br>
><br>
> The above approaches are not compared in the existing<br>
> fontspec user manual, of course, because the readers<br>
> don't need it. But I feel certain that the next ex-word-<br>
> processor (XWP) person like me will cross the same<br>
> territory and he or she will not find much help in the<br>
> existing user manual. It wasn't written for XWPs.<br>
Again, what kind of XWP do you have in mind? If they are used to<br>
WYSIWYG, why should they learn low-lewel (Plain) XeTeX commands not just<br>
high(er) level LaTeX/fontspec's?<br>
<br>
><br>
> Collaboration Model<br>
><br>
> This ML is quite handy for announcing progress and<br>
> making drafts available for comment. The actual business<br>
> of getting organized and having dialogues about the<br>
> topics will be done via ordinary email. That's the<br>
> collaboration model I'm used to.<br>
<br>
If you're not discouraged by my remarks as far, you can put my email<br>
address to the mailing list of the project.<br>
I probably have not much time to give to your project but probably I can<br>
be helpful sometimes since I have some experience in teaching LaTeX the<br>
total beginners used to M$ Word.<br>
<br>
> Our Friends, xltxtra and xunicode<br>
><br>
> These packages are natural to you, but they're not natural to<br>
> a beginner who chooses one set of problems at a time.<br>
><br>
> Feel free to invoke these packages in (say) 20% of your<br>
> examples. We'll cover the packages eventually, but we need<br>
> a success first.<br>
><br>
I think a beginner who migrates from a WYSIWYG to LaTeX should learn to<br>
begin their documents with<br>
\documentclass{documentclass}<br>
\usepackage{xltxtra}<br>
that loads all three XeLaTeX basics. Since a XWPs has no bad habbits or<br>
Plain habbits, they should learn a good XeLaTeX habbit from the very<br>
beginning. SO my opinion is xunicode and xltxtra should be used all the<br>
time. (In fact, I use them all the time and don't know what exactly they<br>
do.)<br>
<br>
<br>
> If you're interested, send me your name and I'll send you<br>
> version 1 of the scope of the manual. Your<br>
> contributions will make up version 2. Then a couple of<br>
> drafts will follow with requests for comment.<br>
><br>
> Fontspec is a small package from the user's point of view.<br>
<br>
We have at least two kinds of (La)TeX users and I'm not quite clear<br>
which one you have in mind:<br>
<br>
In my opinion<br>
fontspec should be considered a basic and fundamentally important<br>
package from the point of view of a typesetter/typographer user.<br>
<br>
On the other hand, if we are talking of a user who just wants to write<br>
their article to a journal, they should not be interested in fontspec at<br>
all (the journal's document class should provide all the font settings),<br>
they don't even has to know about XeTeX.<br>
<br>
> A manual could be produced in a couple of months if people<br>
> want it.<br>
<br>
My name is Grzegorz Murzynowski, my email address: natror (ape sign) o2<br>
(decimal point) pl (as the sender of this post)<br>
and you can call me Natror for short.<br>
<br>
Best,<br>
<br>
Grzegorz Murzynowski (Natror).<br>
<br>
<br>
------------------------------<br>
<br>
Message: 8<br>
Date: Thu, 04 Dec 2008 11:21:49 -0500<br>
From: Stephen Moye <<a href="mailto:stephenmoye@mac.com">stephenmoye@mac.com</a>><br>
Subject: Re: [XeTeX] Could not load both Bold and BoldItalic.<br>
To: Unicode-based TeX for Mac OS X and other platforms <<a href="mailto:xetex@tug.org">xetex@tug.org</a>><br>
Message-ID: <<a href="mailto:11246252009702582003283379729369482776-Webmail@me.com">11246252009702582003283379729369482776-Webmail@me.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
On Thursday, December 04, 2008, at 10:40AM, "Akira Kakuto" <<a href="mailto:kakuto@fuk.kindai.ac.jp">kakuto@fuk.kindai.ac.jp</a>> wrote:<br>
>> Then these fonts aren't PostScript Type 1.<br>
><br>
>PostScript Type 1 fonts can be used by XeTeX-xdvipdfmx without<br>
>tfm fonts. Of course you have to make cache for the type1 by fc-cache.<br>
>Please test<br>
>\font\f="Utopia/R"<br>
>\f This is a test.<br>
>\bye<br>
><br>
>Best,<br>
>Akira<br>
<br>
Hmmm... I'm not sure that I understand. Could you please spell out how it is that xdvipdfmx can be made to use PostScript Type 1 fonts. I am using a Mac and, in my experience at least, the use of fc-cache has not been necessary.<br>
<br>
Stephen Moye<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
XeTeX mailing list<br>
<a href="mailto:XeTeX@tug.org">XeTeX@tug.org</a><br>
<a href="http://tug.org/mailman/listinfo/xetex" target="_blank">http://tug.org/mailman/listinfo/xetex</a><br>
<br>
<br>
End of XeTeX Digest, Vol 57, Issue 10<br>
*************************************<br>
</blockquote></div><br>