On Mon, Nov 14, 2011 at 02:27:03AM -0800, Chris Travers wrote:
On Mon, Nov 14, 2011 at 2:24 AM, Petr Tomasek toma...@etf.cuni.cz wrote:
Using different color.
Do we really want to tie XeTeX users to a small number of editors?
Chris Travers
Do we really make XeTeX incompatible with the
Hi Tobias,
Am 14.11.2011 um 18:42 schrieb Tobias Schoel:
Am 14.11.2011 18:30, schrieb msk...@ansuz.sooke.bc.ca:
[snip, snip]
Now we come to the trouble of Unicode specifying a line-breaking algorithm (
http://www.unicode.org/reports/tr14/tr14-26.html ), which probably isn't
On Tue, Nov 15, 2011 at 2:27 AM, Keith J. Schultz keithjschu...@web.de wrote:
Hi all,
I agree that XeTeX should support all printable characters.
Given your definition I would say all visible printed characters.
Invisible characters are a problem in a programming language.
A non.breaking
Keith J. Schultz wrote:
A non.breaking space is to me a printable character, in so far that
it is important and must be used to distinguish between word space, et all.
If, for you, [a] non.breaking space is a printable character, then
presumably that character must be taken from some font.
2011/11/14 Mike Maxwell maxw...@umiacs.umd.edu:
On 11/14/2011 4:56 PM, Zdenek Wagner wrote:
2011/11/14 Mike Maxwellmaxw...@umiacs.umd.edu:
We are not (at least I am not) suggesting that everyone must use
the Unicode non-breaking space character, or etc. What we *are*
suggesting is that in
On 11/15/2011 5:39 AM, Chris Travers wrote:
My recommendation is:
1) Default to handling all white space as it exists now.
2) Provide some sort of switch, whether to the execution of XeTeX or
to the document itself, to turn on handling of special unicode
characters.
3) If that switch is
2011/11/15 Mike Maxwell maxw...@umiacs.umd.edu:
On 11/15/2011 5:39 AM, Chris Travers wrote:
My recommendation is:
1) Default to handling all white space as it exists now.
2) Provide some sort of switch, whether to the execution of XeTeX or
to the document itself, to turn on handling of
2011/11/15 Zdenek Wagner zdenek.wag...@gmail.com:
2011/11/15 Mike Maxwell maxw...@umiacs.umd.edu:
On 11/15/2011 5:39 AM, Chris Travers wrote:
My recommendation is:
1) Default to handling all white space as it exists now.
2) Provide some sort of switch, whether to the execution of XeTeX or
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
2011/11/15 Chris Travers chris.trav...@gmail.com:
2011/11/15 Zdenek Wagner zdenek.wag...@gmail.com:
2011/11/15 Mike Maxwell maxw...@umiacs.umd.edu:
On 11/15/2011 5:39 AM, Chris Travers wrote:
My recommendation is:
1) Default to handling all white space as it exists now.
2) Provide some
2011/11/15 Philip TAYLOR p.tay...@rhul.ac.uk:
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
2011/11/15 Philip TAYLOR p.tay...@rhul.ac.uk:
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
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
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 practice in TeX programming, or as
2011/11/15 Philip TAYLOR p.tay...@rhul.ac.uk:
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
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
On Nov 15, 2011, at 8:52 AM, Philip TAYLOR wrote:
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
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.
2011/11/15 Herbert Schulz he...@wideopenwest.com:
On Nov 15, 2011, at 8:52 AM, Philip TAYLOR wrote:
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
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 seemed to
be saying that you
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
Stephan,
you can print font glyphs in XeTeX using \XeTeXglyph followed by the
glyph's decimal index.
You'd need to use a different tool to do the parsing of the OpenType
Layout tables, though. The Python package FontTools/TTX or FontForge
compiled as a Python module can be used to extract this
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
On Nov 15, 2011, at 11:19 AM, Philip TAYLOR wrote:
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
http://fa.wikipedia.org/wiki/%D8%B2%DB%8C%E2%80%8C%D9%BE%D8%B1%D8%B4%DB%8C%D9%86
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
On Nov 15, 2011, at 11:11 AM, Herbert Schulz wrote:
On Nov 15, 2011, at 11:19 AM, Philip TAYLOR wrote:
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
On Tue, Nov 15, 2011 at 06:46, Stephan wrote:
Good day,
I have been trying to print out the glyphs of a font (in my case Minion) that
are used in a stylistic variant. But I have not been able to do that...
Is there a way of printing, let's say, all the glyphs that would be used if a
feature
2011/11/15 Vafa Khalighi vafa...@gmail.com:
http://fa.wikipedia.org/wiki/%D8%B2%DB%8C%E2%80%8C%D9%BE%D8%B1%D8%B4%DB%8C%D9%86
خوب
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--
Zdeněk
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
On Nov 15, 2011, at 2:43 PM, Ross Moore wrote:
On 16/11/2011, at 5:56 AM, Herbert Schulz wrote:
Given that TeX (and XeTeX too) deal wit a non-breakble space already (where
we usually use the ~ to represent that space) it seems to me that XeTeX
should treat that the same way.
No, I
2011/11/15 Ross Moore ross.mo...@mq.edu.au:
On 16/11/2011, at 5:56 AM, Herbert Schulz wrote:
Given that TeX (and XeTeX too) deal wit a non-breakble space already (where
we usually use the ~ to represent that space) it seems to me that XeTeX
should treat that the same way.
No, I disagree
Hi Zdenek,
On 16/11/2011, at 8:58 AM, Zdenek Wagner wrote:
2011/11/15 Ross Moore ross.mo...@mq.edu.au:
On 16/11/2011, at 5:56 AM, Herbert Schulz wrote:
Given that TeX (and XeTeX too) deal wit a non-breakble space already (where
we usually use the ~ to represent that space) it seems to
2011/11/15 Ross Moore ross.mo...@mq.edu.au:
Hi Zdenek,
On 16/11/2011, at 8:58 AM, Zdenek Wagner wrote:
2011/11/15 Ross Moore ross.mo...@mq.edu.au:
On 16/11/2011, at 5:56 AM, Herbert Schulz wrote:
Given that TeX (and XeTeX too) deal wit a non-breakble space already
(where we usually use
Hi Phil,
On 16/11/2011, at 8:45 AM, Philip TAYLOR wrote:
Ross Moore wrote:
On 16/11/2011, at 5:56 AM, Herbert Schulz wrote:
Given that TeX (and XeTeX too) deal wit a non-breakble space already (where
we usually use the ~ to represent that space) it seems to me that XeTeX
should treat
2011/11/15 Ross Moore ross.mo...@mq.edu.au:
Hi Phil,
On 16/11/2011, at 8:45 AM, Philip TAYLOR wrote:
Ross Moore wrote:
On 16/11/2011, at 5:56 AM, Herbert Schulz wrote:
Given that TeX (and XeTeX too) deal wit a non-breakble space already
(where we usually use the ~ to represent that
I was going to make the following point earlier--maybe in light of
Phil's conclusion I should do it now.
There seems to be a tendency not to distinguish between a(n orginal)
character in the sense of character of a writing system, and a computer
character.
The former are visible symbols on a
Hi Phil,
On 16/11/2011, at 10:08 AM, Zdenek Wagner wrote:
How do you explain to somebody the need to do something really,
really special to get a character that they can type, or copy/paste?
There is no special role for this character in other vital aspects
of how TeX works, such as there
2011/11/16 Ross Moore ross.mo...@mq.edu.au:
On 16/11/2011, at 9:45 AM, Zdenek Wagner wrote:
2011/11/15 Ross Moore ross.mo...@mq.edu.au:
What if you really want the Ux00A0 character to be in the PDF?
That is, when you copy/paste from the PDF, you want that character
to come along for the
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
Is there a way to align characters at their centers instead of at
their baselines?
Take for example
{\scshape Ee}.
This will produce one big uppercase E and one little uppercase E;
and their lower horizontal bars will be aligned. But is there any way
I can make them aligned at their centers
On Wed, Nov 16, 2011 at 11:28:33AM +0800, Daniel Greenhoe wrote:
Is there a way to align characters at their centers instead of at
their baselines?
Take for example
{\scshape Ee}.
This will produce one big uppercase E and one little uppercase E;
and their lower horizontal bars will be
Hi Zdenek,
On 16/11/2011, at 11:19 AM, Zdenek Wagner wrote:
Just like any other Unicode character, if you want it then
you should be able to put it in there.
You ARE able to do it. Choose a font with that glyph, set \catcode to
11 or 12 and that's it. What else do you wish to do?
The
43 matches
Mail list logo
