On Mon, Nov 14, 2011 at 02:27:03AM -0800, Chris Travers wrote:
> On Mon, Nov 14, 2011 at 2:24 AM, Petr Tomasek 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 rest of the
Am Mon, 14 Nov 2011 15:09:41 -0800 schrieb Chris Travers:
> Would you be opposed to requiring an on-switch which would be required
> before unicode whitespace characters acquire special meaning?
The various unicode whitespaces already have special meaning. Like
"a" give something else than "b
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
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 in a font is turned on ?
For example, the "k" in
Hi all,
I agree that XeTeX should support all printable characters.
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.
To go back in history, one of my pet peeves in LaTeX was that I had to
enter the Ge
On Tue, Nov 15, 2011 at 2:27 AM, Keith J. Schultz 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 space is to me a pr
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 :
> On 11/14/2011 4:56 PM, Zdenek Wagner wrote:
>>
>> 2011/11/14 Mike Maxwell:
>>>
>>> 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 Xe(La)Tex, we be *allowed* t
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 enabl
2011/11/15 Mike Maxwell :
> 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 unic
2011/11/15 Zdenek Wagner :
> 2011/11/15 Mike Maxwell :
>> 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,
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 b
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 :
> 2011/11/15 Zdenek Wagner :
>> 2011/11/15 Mike Maxwell :
>>> 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
2011/11/15 Philip TAYLOR :
>
>
> 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 i
2011/11/15 Philip TAYLOR :
>
>
> 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 car
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 character/catc
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
2011/11/15 Philip TAYLOR :
>
>
> 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
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 pract
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 ca
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 :
>
> 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
> "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 y
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 in
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 h
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?
>
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."
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
> f
2011/11/15 Vafa Khalighi :
> 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 Wagner
http:/
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 y
(just as an aside)
I always thought that people who said 'I could care less' somehow
hadn't heard the 'nt' and didn't consciously parse the grammar of the
sentence, making it a kind of frozen form. Similar in process to how
people (in my area in Canada) at one time would reply to 'no way' with
'ye
On Nov 15, 2011, at 11:46 AM, Philip TAYLOR wrote:
> 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
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 completely.
What if you really want the Ux0
Am 15.11.2011 um 06:46 schrieb Stephan:
> Is there a way of printing, let's say, all the glyphs that would be used if a
> feature in a font is turned on ?
Otfinfo can report the features of a font. The fontspec documentation contains
some code on how to access "stylistic alternatives" or "vari
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.
>
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 disagree completely.
What if you r
2011/11/15 Ross Moore :
>
> 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 completely
Hi Zdenek,
On 16/11/2011, at 8:58 AM, Zdenek Wagner wrote:
> 2011/11/15 Ross Moore :
>>
>> 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 X
2011/11/15 Ross Moore :
> Hi Zdenek,
>
> On 16/11/2011, at 8:58 AM, Zdenek Wagner wrote:
>
>> 2011/11/15 Ross Moore :
>>>
>>> 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
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
>>
2011/11/15 Ross Moore :
> 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 sp
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 back
On 16/11/2011, at 9:45 AM, Zdenek Wagner wrote:
> 2011/11/15 Ross Moore :
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 ride.
From the typographical point of view i
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
2011/11/16 Ross Moore :
>
> On 16/11/2011, at 9:45 AM, Zdenek Wagner wrote:
>
>> 2011/11/15 Ross Moore :
>
> 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 ride.
>
> From
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 bar
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?
Th
52 matches
Mail list logo
