Ulrike Fischer wrote:
I can solve the problem with the euro sign by resetting the font to
latin modern typewriter with
\makeatletter \font\s...@tt=LMMono10-Regular\makeatletter
Or maybe even :
\makeatletter \font\s...@tt=LMMono10-Regular\makeatother %%% ?!
Philip Taylor
Pablo Rodríguez wrote:
You are right, but I'm afraid this doesn't solve the problem with
Reconstruction failed error messages. Thanks anyway
No, sorry, I didn't think it would fix that problem, but
it could have caused other errors if left as Ulrike had
originally formulated it.
** Phil.
catcode.
Philip Taylor
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
0.666
leads to
** WARNING ** Transformation matrix not invertible.
** WARNING ** --- M = [0 0 0 0 -43.6535 -396.088]
How is one intended to accomplish fractional scaling, please ?
Philip Taylor
--
Subscriptions, Archive, and List information, etc
to display different Unicode spaces differently,
such that the user can visually differentiate between them ?
Philip Taylor
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
One option would be to colour-code them, but I was
more interested in the philosophy than the implementation.
** Phil.
Not in every case. How would you visually differentiate between all the
white space characters (space vs. non-break space, thin space (u2009)
vs. narrow no-break
Tobias Schoel wrote:
Now, that the practicability is cleared, let's come back to the
philosophical part:
Actually, I think this is the practical/pragmatic part,
but let's carry on none the less ...
Should nbsp=u00a0 be active and treated as ~ by default? Just like
u202f and u2009 should be
, for the youngsters XML, TeX, HTML are per definition plain text files.
No, they are text files, not /plain/ text files. Look
at some mime types :
text/plain (for plain text)
text/html (for HTML)
Philip Taylor
--
Subscriptions, Archive, and List
troublesome than
any of the sixteen or so currently reserved characters
when it comes to transput : that is why \unexpanded exists.
Philip Taylor
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Keith J. Schultz wrote:
Hi Phillip,
Am 14.11.2011 um 09:36 schrieb Philip TAYLOR:
Keith J. Schultz wrote:
So, Unicode needs an editor to be displayed correctly.
Why ? Not meant to sound aggressive, but seems a very
odd assertion, IMHO. Editors are for changing things;
why would you
Chris Travers wrote:
Ok, so why don't we have a similar macro here? Something like:
\obeynbsps
See above : there are /some/ things that TeX does that
transcend category codes (which are the basis for \obeylines);
in particular [1] :
$$ TeX deletes any space characters (number 32) that
Chris Travers wrote:
But what's the point of putting non-breaking spaces between a word and
the end of a line? or for that matter what if I alternate spaces and
special unicode spaces? Do I get a word space for each of them?
In (e.g.,) HTML, it is by no means unusual to interweave
spaces
When you are willing to come back to a serious discussion we talk.
I am participating in a serious discussion, Keith,
but I am more than happy to ignore your own inane
babble if it will make you any happier.
Philip Taylor
Keith J Schultz wrote :
Hi Humpty Dumpty,
Go read
that it is, /a priori/,
invalid for XeTeX ?
Remainder snipped, so that we can debate one point at a time.
Philip Taylor
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
msk...@ansuz.sooke.bc.ca wrote:
XeTeX is a TeX engine. Obviously, it is free to define its own input
format, and that format already differs from other TeX engines by (for
instance) allowing some Unicode code points outside the 7-bit range.
I think (with respect) that some Unicode code
msk...@ansuz.sooke.bc.ca wrote:
On Mon, 14 Nov 2011, Philip TAYLOR wrote:
I think (with respect) that some Unicode code points outside the 7-bit range
is a gross understatement. As far as I am aware, XeTeX permits a very
considerable
subset of Unicode (perhaps even all of it; I do not know
that it is, /a priori/,
invalid for XeTeX ?
Remainder snipped, so that we can debate one point at a time.
Philip Taylor
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Zdenek Wagner wrote:
The only reasonable solution seems to be the one suggested by Phil Taylor, to
extend \catcode up to 255 and assign special categories to other types
of characters. Thus we could say that normal space id 10, nonbreakable
space is 16, thin space is 17 etc. XeTeX will then
Chris Travers wrote:
But we are talking two different things here. The first is user
interface, and the second is mechanism.
What I am saying is special handling of this sort should be required
to be enabled somehow by the user. I don't really care how. It could
be by a commandline switch
Zdenek Wagner wrote:
If you know what such characters are (and it will certainly be
documented), you just set their categories back to 12 in order to get
the old behaviour.
No ! A catcode is for life, not just for Christmas ! Once a
character has been read, and bound into a
Arthur Reutenauer wrote:
On Tue, Nov 15, 2011 at 02:20:17PM +, Philip TAYLOR wrote:
No ! A catcode is for life, not just for Christmas ! Once a
character has been read, and bound into a character/catcode pair,
that catcode remains immutable.
Do you mean that as a general good
Zdenek Wagner wrote:
Of course, I know it. What I meant was that you could set \catcode of
all these extended characters to 12 at the beginning of your
document. Thus you get the same behaviour as now.
Ah yes : with that, I have no problem.
** Phil.
Arthur Reutenauer wrote:
The latter is what the TeXbok says (P.~39) : Once a category code
has been attached to a character token, the attachment is permanent.
Yes, because you meant individual tokens (which I understood in
retrospect). But in the context of the discussion, you really
Herbert Schulz wrote:
The latter is what the TeXbok says (P.~39) : Once a category code
has been attached to a character token, the attachment is permanent.
** Phil.
What happens in a verbatim environment?
The verbatim environment sets up an environment within
which characters that have
I think it made more sense with can't, Herb,
but that could be a trans-Atlantic difference
of usage -- you would, I think, say I could care
less where I would say I couldn't care less.
** Phil.
Herbert Schulz wrote:
What I meant to say was...
So what you are saying is not that you
Ross Moore wrote:
Hi Phil,
On 16/11/2011, at 10:08 AM, Zdenek Wagner wrote:
Not I, Sir : Zdeněk !
** Phil.
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Keith J. Schultz wrote:
Am 17.11.2011 um 11:26 schrieb Keith J. Schultz:
O.K.
You mention in a later post that you do consider a space as a printable
character.
This line should read as:
You mention in a later post that you consider a space as a
non-printable
Ross, I do not dispute your arguments : I was answering
Keith's question in an honest way. I (personally) do not
think of a space in TeX output as a character at all,
because I am steeped in TeX philosophy; but I am quite
willing to accept that /if/ the objective is not to
produce output for the
Keith J. Schultz wrote:
The crux of of the problem is in (Xe)TeX's parsing algorithm. I never liked it
and personally I have many problems it.
Is this XeTeX-specific, Keith, or do you also dislike
TeX's parsing algorithm ? And what is it that you
dislike, and how would you propose that it
Zdenek Wagner wrote:
I admit that things could be done better than in nowadays TeX but its
complete revamping seems to me as bad investment. I would rather think
of an FO processor.
And I agree with Zdeněk : this discussion will be productive only
if we focus on what can be accomplished
Is it safe to assume that these code listings
are restricted to the ASCII character set ? If
so, yes, spaces are likely to be a problem, but
if the code listing can also include ligature-
digraphs, then these are likely to prove even
more problematic.
** Phipl.
Ulrike Fischer wrote:
Keith J. Schultz wrote:
Me I am almost 50 and have been around computers since the 80s.
First was a Apple IIe, at the university we used a main frame.
My first computer was a Clary 404, with 8K of magnetic core memory,
a magnetic card reader and/or teletype as input device,
hope that this does not happen, and that before then
we have an Omnicode consortium to review the mistakes of Unicode
and to address them in a future, more orthogonal, more consistent,
specification.
Philip Taylor
--
Subscriptions, Archive, and List
) and feature requests (many) from his early adopters.
Philip Taylor
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Does anyone have (or know of) a VIQR (Vietnamese Quoted-Readable)
pre-processor, written in (Xe)TeX, that would allow me to input
documents of the form :
1. Ba’nh pho^`ng to^m | Prawn Crackers (£1.00)
2. Rong bie^?n | Crispy seaweed (£2.50)
and to have these VIQR forms internally
Vafa Khalighi wrote:
You need to create mapping for that.
Well, maybe. If that is the case, then let me re-formulate
my question (since I haven't the slightest idea how to create
a mapping) : has anyone created a VIQR mapping for XeTeX ?
** Phil.
Thank you, Vafa : that looks achievable, so if after a decent
wait it would appear that one does not exist, I shall have a
go at creating one.
** Phil.
Vafa Khalighi wrote:
I do not know if there is one but in case there is none, creating one is easy.
I have attached a guide on teckit
Could you offer an example of ambiguous VIQR input, Andrew ?
I am not sufficiently familiar with the encoding to envisage
in what way ambiguity might occur.
Philip Taylor
Andrew Cunningham wrote:
You will need to make sure that ambiguous VIQR input is escaped as
appropriate
Andrew Cunningham wrote:
Word final vowels with punctuation following, e.g. full stop, question mark.
Understood, thank you Andrew. Yes, some of these
crept into the original version : fortunately
I spotted them before they went to print.
Philip Taylor
Ross Moore wrote:
At least here we have \.space (since '.' has catcode 12, not 11).
So it should be possible to modify the definition of \.{ } within
the NFSS processing of \. to assign a special meaning.
This is coding that could be easily included within Xunicode.sty ,
but applied only
would also not have
software installation privileges. Thus direct input of VIQR,
and saving /as/ VIQR, is, for her, the simplest solution,
and it then becomes my responsibility to accept her VIQR and
convert it to Unicode within XeTeX.
Philip Taylor
Cảm ơn, Minh : I have Unikey running -- it is just a question
of getting my wife to translate the buttons for me !
** Phil.
Quang Minh Nguyen ()阮光明 wrote:
On a Windows machine, I think Unikey is the way to go. You don't need
to install it, it's a stand alone exe, so no need to have
name demonstrates
exactly the problem : something that TeX cannot
accomplish without special fonts, since it has
no primitive for positioning two diacritics over
a single character.
Philip Taylor
--
Subscriptions, Archive, and List information, etc
MY thanks to all who have offered helpful suggestions
in VIQR. Unikey looks promising as an IME (I am waiting
for my wife to tell me what the buttons say !), and
a list member has kindly offered off-list to have a go
at creating a TECkit map as and when he has time. So
let us not expend further
Aleksandr Andreev wrote:
Mezenets Unicode is a font I'm developing for Znamenny neumatic notation
Oohhh, this is exciting : [p]nuematic notation as in [p]neumes
and as in [p]neumatic music ? Will this be a first for TeX, if
you succeed ?
Philip Taylor
...rces/Images/TAR-2.pdf width \hsize \relax
H E L P !!!
Philip Taylor
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Paul Isambert wrote:
Use \XeTeXpdffile ...
Sounds very sane, Paul, but then why does \XeTeXpicfile say
! Unable to load picture or PDF file
Surely if it cannot handle PDF files, it would just say
! Unable to load picture
... and keep cool :)
Easy to say if you
Zdenek Wagner wrote:
2011/12/1 Philip TAYLORp.tay...@rhul.ac.uk:
P.S. But what about the fact that the \vfill \eject
is ignored if no text precedes the \XeTeXpicfile ?
What is \XeTeXpicfile from the TeX point of view? \vfil is a
discardable element thus it seems that \XeTeXpicfile is also
Paul Isambert wrote:
Le 01/12/2011 13:13, Philip TAYLOR a écrit :
P.S. But what about the fact that the \vfill \eject
is ignored if no text precedes the \XeTeXpicfile ?
It seems to be a particular case of the situation where a \special is alone on
its page. I don't know what TeX
The behaviour is even stranger than I thought.
Used unadorned, \XeTeXpicfile introduces a significant
right shift for all text that follows it on the current
page; concealed within a \centerline, all is well yet
concealed within braces the artifact remains (so it
is not a scoping issue).
Sorry, please read that as \XeTeXpdffile -- not
tested with \XeTeXpicfile, which I will now do.
Philip TAYLOR wrote:
The behaviour is even stranger than I thought.
Used unadorned, \XeTeXpicfile introduces a significant
right shift for all text that follows it on the current
page; concealed
of \XeTeXpdffile.
Anyhow, this one must wait until I have removed all the dross.
Philip Taylor
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
On Thu, 1 Dec 2011, Khaled Hosny wrote:
Suppose someone types
f\textcolor{red}{f}
In this case FireFox colourises half of resulting ff ligatures (1/3 in
ffi etc),
And if you look at the rendered output, is there a single
ff ligature-digraph glyph, or two f glyphs kerned ?
Philip
with the path to a non-existence JPG, and
! Unable to load picture or PDF file
when it is called with the path to a most-definitely-existent PDF
must certainly be one of the most confusing things that he will have
encountered in his life.
Philip Taylor
Heiko Oberdiek wrote:
It's your choice to use low level internals. Higher level interfaces
are already written and some can also be used with plain TeX:
\input miniltx
\def\Gin@driver{xetex.def}
\input graphicx.sty
\resetatcatcode
\noindent
\includegraphics[width=\hsize]{s1.png}
\vfil
and
* that they should be used inside a \hbox to avoid trouble
with discarded items at the top of a page.
That would indeed be a great help.
Philip Taylor
[1] http://tex.loria.fr/moteurs/etex_ref.html
--
Subscriptions, Archive, and List
.
Philip Taylor
% !TeX Program=XeTeX
\def \onehalf {0.5}
\def \twothirds {0.66}
\newdimen \innermargin
\newdimen \outermargin
\newdimen \uppermargin
\newdimen \lowermargin
\newdimen \cropwidth
\newdimen \cropheight
\newdimen \Knuthoffset
\pdfpagewidth = 210 mm
\pdfpageheight = 297mm
Heiko Oberdiek wrote:
On Thu, Dec 01, 2011 at 06:06:13PM +, Philip TAYLOR wrote:
Heiko Oberdiek wrote:
Because they are solving those problems for you and others now
and in the future. That is one of the main reasons for a package,
providing an easier interface for tricky low level
Sorry, list : this was meant to go to Dominik, not everyone ...
** Phil.
Philip TAYLOR wrote:
Ah, Dominik, you mad mad early adopter : I shall be adopting
TeX Live 2011 only when they announce that it is frozen in order
to start work on TeX Live 2012
), the apostrophe
of weaver’s/weavers’ is the same Unicode character as the closing
quotation mark of windows’. Should it be ?
Philip Taylor
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Thank you, Jonathan (but I really do wish the answer
had been no : it is far to easy to mis-parse the
author's text).
Philip Taylor
Jonathan Kew wrote:
In Two wide ‘weaver’s windows’, usually found on the ground floor
(which could equally well be Two wide ‘weavers’ windows’, usually
Zdenek Wagner wrote:
This convention is not used in the Czech language
With the greatest respect, Zdeněk, I do not necessarily agree.
Please take a look at Bible: Písmo svaté Starého a Nového zákona
včetně deuterokanonických knih, Česká biblická společnost:
Praha 1985. [tzv. Ekumenický
Philip TAYLOR wrote:
With the greatest respect, Zdeněk, I do not necessarily agree.
Please take a look at Bible: Písmo svaté Starého a Nového zákona
včetně deuterokanonických knih, Česká biblická společnost:
Praha 1985. [tzv. Ekumenický překlad]
Well worth comparing this with the Czech
Zdenek Wagner wrote:
You should start with \tolerance=.
In such a case you should not have overfull boxes (if you still have
them, some changes in the text may be needed). After this run you find
the highest badness of the underfull box. Set \tolerance to this value
and \hbadness to one
The following code fragment, from plain XeTeX source,
results in an undefined control sequence : \XeTeX
message. Where is \XeTeX canonically defined, please ?
Philip Taylor
\noindent {\smallit Typeset using Jonathan Kew’s \XeTeX\ in Janusz M Nowacki’s
{\smallrmat Antykwa Toruńska
answers given,
assume the Universe of Discourse to be Plain TeX (or Plain PdfTeX, or Plain XeTeX, or
Plain anyTeX).
Philip Taylor
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Ulrike Fischer wrote:
My name is Ulrike.
Mea culpa, mea culpa, mea maxima culpa.
Sincere apologies, Ulrike.
I saw that you wanted to use plain. But you didn't ask how to get
the logo with plain but Where is \XeTeX canonically defined. I
assumed as a plain user you would be able to look in
Heiko Oberdiek wrote:
Unless you are using iniTeX it's probably a bug. In the latest
version I can't reproduce it, however the latest version isn't
yet on CTAN. I send it off-list to you, thus you can even
use it with iniTeX (xetex --ini):
\catcode`\{=1
\catcode`\}=2
% ... and other settings
by any reader of Pinyin, but
is not really the right character for the job.
Philip Taylor
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Daniel Greenhoe wrote:
Wouldn't a simple \v{u} render sufficient quality?
Reinhard Kotucha wrote :
I suppose that the idea was to use \v{u} in order to compose the
glyph and am sure that you don't need LaTeX in order to achieve this.
You are both quite correct, it almost certainly
Herbert Schulz wrote:
Another inquiry... I've got TL2011, via the MacTeX installer, with all updates
and there is no exceltex program or package. Is that a Windows only item?
Jim Hefferon, him say : TeX Live -this package is not in TeX Live-
Philip Taylor
I can send you the code I use to produce one, but
it's TeX, not LaTeX. Of any use/interest ?
http://tex-consultants.org.uk/projects/Joan/Genealogy-2011.pdf
Philip Taylor
Jacobo Myerston wrote:
I was wondering if somebody knows a latex package to represent genealogical
(Win/XP's number
for UTF-8) so that I can see the accented e in Natércia's name
correctly, I get instead the above end of file message.
Can anyone hazard a guess as to why ?
Philip Taylor
--
Subscriptions, Archive, and List information, etc
. None of these fonts may be redistributed to others, nor may they be
sold, without prior written consent from BRILL.
It will certain be informative to follow this link and to find out
whether Brill would propose to charge a licence fee for the usage
you have in mind.
Philip Taylor
Peter Dyballa wrote:
Am 3.2.2012 um 12:58 schrieb Philip TAYLOR:
Can anyone hazard a guess as to why ?
Did you look into the LOG file?
Yes, just shows end of file.
Did you load polyglossia and fontspec?
No : this is pure XeTeX, not XeLaTeX or any other extension
other than those provided
Pander wrote:
The email address does not exist.
There would appear to be a not-inconsiderable
element of verisimilitude in that assertion.
Philip Taylor
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman
, Version 3.1415926-2.2-0.9997.4 (Web2C 2010)
restricted \write18 enabled.
**\relax
entering extended mode
*é
! Emergency stop.
* \relax
No pages of output.
Transcript written on texput.log.
As you can see, the é, when entered in code page
65001, is interpreted as a Ctrl-z.
Philip Taylor
-
years ahead of the PC, the much-vaunted Finder is no
better than Windows Search ? Do these manufacturers
vie with each other to see who can produce the cr@ppiest code ?!
Philip Taylor
--
Subscriptions, Archive, and List information, etc.:
http
Zdenek Wagner wrote:
I am not the one who decides what can be included in TL and what
cannot. Authors can decide how their packages can be used and
maintainers of distributions have their own right to decide what to
include. I wanted to write a useful answer explaining why the package
is not
Zdenek Wagner wrote:
The author has right to decide how his package can be used. If people
are discouraged to distribute it, TL maintainers feel discouraged and
do not distribute it.
But Mike does not seek to discourage people from distributing
it, Zdeněk : he seeks only to discourage them
I think that Jonathan has different kind of mapping in mind. First
macros are expanded (active characters will be expanded at the very
same time).
And expandable primitives (such as \if) will also
be expanded at this time.
Philip Taylor
\defaultfontfeatures
{Mapping=tex-text}
?
Could an expert advise, please ?
Philip Taylor
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
msk...@ansuz.sooke.bc.ca wrote:
[...] Here we go again...
C'est-à-dire ?!
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Herbert Schulz wrote:
That command is defined in the fontspec package used in xelatex processing. I'm
not sure how, or even if, you can call it in Plain xetex.
Oh. I /need/ it ! Any Plain XeTeXers able to advise, please ?
** Phil.
--
Jonathan Kew wrote:
If you want to use the mapping (to convert -- to en-dash, `` to
double-open-quote, etc) in plain xetex, you can specify it directly when loading fonts, as in
\font\myromanfont = Times New Roman:mapping=tex-text at 11pt
(or wrap this up in whatever custom TeX macros
Peter Dyballa wrote:
Am 16.3.2012 um 13:32 schrieb Philip TAYLOR:
If I were to want to insert an image with (say) 90% transparency
(i.e., 10% opacity), how might I best go about this ?
In ConTeXt.
Universe of Discourse : Plain XeTeX (as stated previously
Peter Dyballa wrote:
Am 16.3.2012 um 14:28 schrieb Philip TAYLOR:
Universe of Discourse : Plain XeTeX (as stated previously).
I don't know what this is meant to express,
That I use XeTeX; I do not use XeLaTeX, ConTeXt or any other
higher-level interface. I use the raw engine
Jonathan Kew wrote:
This would depend on the output driver's capabilities - xetex doesn't have any
built-in magic to do this, but I wouldn't be surprised if xdvipdfmx supports
\special{}s that can achieve it. Possibly a \special before the \XeTeXpdffile
command to set up transparency, and
msk...@ansuz.sooke.bc.ca wrote:
[...]and if you're comfortable working in a Plain
TeX environment, the package source code may be easier to understand than
the engine source code.
Yes, thank you for the suggestion, Mathew : much appreciated.
** Phil.
and
for Plain TeX.
Philip Taylor
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
, with full Unicode support.
Philip Taylor
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Tobias Schoel wrote:
What does normalise mean with angstrom and ohm?
Perhaps as per
http://en.wikipedia.org/wiki/Unicode_equivalence#Normalization
Philip Taylor
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman
Alan Hoenig wrote:
Any insight you can provide will put me in your debt FOREVER! Thanks...
FOREVER is a very long time, Alan :-)
** Phil.
--
MIL-05991/237/2012-B : Any loss of data or other computer malfunction
resulting directly or indirectly from the use of Linux will be regarded
as a
Adam Twardoch (List) wrote:
I believe that the TeX world needs a policy on naming engine-specific
commands. This is akin to the CSS browser-specific prefixes, such as
-webkit-text-security or -moz-font-features. XeTeX already does
this: all the XeTeX-specific commands are prefixed with XeTeX.
Martin Schröder wrote:
That's why you should use ConTeXt or LaTeX, which will isolate your
document from differences in the engine.
Yes, and I should drive an automatic so I don't have to worry
about which gear I should be in. In fact, I should employ
a chauffeur, so I don't have to worry
Martin Schröder wrote:
You are right.
Do a 'texdoc xetex' and 'texdoc luatex' and compare. :-)
E.g. polyglossia does not work with LuaTeX (yet).
OK, fears concerned. But of course polyglossia is a macro
package; do you happen to know what is different at the
TeX/XeTeX/LuaTeX primitive
Joel C. Salomon wrote:
I know for a fact that LuaTeX enables features of OpenType Math fonts
that XeTeX does not. See, e.g.,
https://github.com/wspr/unicode-math/issues/40.
And, of course, there are XeTeX-specific features (most prominently
interchartoks) which LuaTeX does not implement.
Khaled Hosny wrote:
I wish people could just ignore what Mr Dyballa writes, as most of time
he has absolutely no idea what he is talking about.
/Ad hominem/ attacks, justified or not, reflect more badly on
those levelling the accusation than they do on the individual named.
Philip Taylor
Dominik Wujastyk wrote:
How nasty of you, Phil to insult Khaled for rebuking Dyballa. Ooops!
What does that say about me? ...
Well, as my good friend Mr Churchill might have said (had he not
been too busy mongering), This is the depth of level down to
which I will not sink
** P.
Ulrike Fischer wrote:
Well some days ago I tried to use otfinst.py. The version on CTAN
mixes tabs and spaces and used an obsolete syntax for print. My
python didn't like both. To correct the second was not so difficult,
but the first was really trying. How to you get correct identation
when
1 - 100 of 760 matches
Mail list logo
