On Dec 22, 2011, at 3:01 AM, Andrew Brown wrote:
> My target was really off in another direction, William -- we have digitized
> the characters that compose our words, but not the words themselves, so we
> remain unable to understand their meaning without examining the context, and
> perhaps no
> On the quotes front, one answer, generally inapplicable, is to move away
> from Anglo-Saxonia and to use « and », and double quotes within quotations.
> Most programs handle that automatically now.
In a XeTeX context, « and » could be made active, and expand to the
relevant language-aware quotes
My target was really off in another direction, William -- we have digitized the
characters that compose our words, but not the words themselves, so we remain
unable to understand their meaning without examining the context, and perhaps
not even then. A trivial example : every morning, a French s
On Dec 15, 2011, at 2:40 PM, Andrew Brown wrote:
> Indeed, but we continue to think that we have digitized our texts when all we
> have done is to digitize a few character forms. We are footling around in the
> dark ages.
_That_ is why TEI has a specific markup for quotes --- there are some
en
Am 17.12.2011 um 18:29 schrieb Tobias Schoel:
> Do you mean csquotes? I haven't found an enquote package, but csquotes
> defines that command. (Thanks for the recommendation.)
That’s the one I meant, yes, sorry.
> There seems to be a problem: Working with \setmainlanguage{german} and
> \seto
On 17.12.2011 15:10, msk...@ansuz.sooke.bc.ca wrote:
On Sat, 17 Dec 2011, Tobias Schoel wrote:
So we're back to the days, where one had to use escape sequences for quotation
marks (\glq,\grq,"',"`,…) as though unicode had not included u2019.
Even worse, because with OpenType some font designe
Do you mean csquotes? I haven't found an enquote package, but csquotes
defines that command. (Thanks for the recommendation.)
There seems to be a problem: Working with \setmainlanguage{german} and
\setotherlanguage{french} the commands \textfrench{\enquote{bla}} or
\foreignquote{french}{bla} s
On Sat, 17 Dec 2011, Tobias Schoel wrote:
> So we're back to the days, where one had to use escape sequences for quotation
> marks (\glq,\grq,"',"`,…) as though unicode had not included u2019.
>
> Even worse, because with OpenType some font designers might include
> substitution rules which include
Am 17.12.2011 um 11:34 schrieb Tobias Schoel:
> So we're back to the days, where one had to use escape sequences for
> quotation marks (\glq,\grq,"',"`,…) as though unicode had not included u2019.
… or use the (babel/polyglossia aware) enquote package.
On 15.12.2011 22:27, Jonathan Kew wrote:
On 15 Dec 2011, at 19:54, Peter Baker wrote:
On 12/15/11 2:34 PM, Jonathan Kew wrote:
Not particularly relevant. The "full stop" or "period" that ends a sentence is
semantically different from the "decimal point" that punctuates numbers. That doesn
On Thu, Dec 15, 2011 at 08:54:24PM +, Philip TAYLOR wrote:
>
>
> 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ě deuter
On 15 déc. 2011, at 20:34, Jonathan Kew wrote:
> Not particularly relevant. The "full stop" or "period" that ends a sentence
> is semantically different from the "decimal point" that punctuates numbers.
> That doesn't mean we have separate character codes for them. From a
> character-encoding p
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 sec
On Thu, 15 Dec 2011, Peter Baker wrote:
> apostophe and the closing quotation mark are the same glyph. We'd have to kern
> each instance manually.
>
> That said, it's pretty clear that we're stuck with what the Unicode Consortium
> has decreed for us.
Old style and lining numerals are generally th
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ý přek
2011/12/15 Philip TAYLOR :
>
>
> Jonathan Kew wrote:
>
>> This reminds me of the French convention whereby a space is often inserted
>> before punctuation such as :, ? or !. I've often felt that this should
>> really be implemented as a language-specific variant of the punctuation
>> glyph (or lang
Jonathan Kew wrote:
This reminds me of the French convention whereby a space is often inserted
before punctuation such as :, ? or !. I've often felt that this should really
be implemented as a language-specific variant of the punctuation glyph (or
language-specific kerning) in OpenType font
On 15 Dec 2011, at 19:54, Peter Baker wrote:
> On 12/15/11 2:34 PM, Jonathan Kew wrote:
>>
>> Not particularly relevant. The "full stop" or "period" that ends a sentence
>> is semantically different from the "decimal point" that punctuates numbers.
>> That doesn't mean we have separate charact
On 12/15/11 2:34 PM, Jonathan Kew wrote:
Not particularly relevant. The "full stop" or "period" that ends a sentence is
semantically different from the "decimal point" that punctuates numbers. That doesn't mean we have
separate character codes for them. From a character-encoding point of view,
On 15 Dec 2011, at 17:18, Tobias Schoel wrote:
> Hi List,
>
> On 15.12.2011 17:02, Jonathan Kew wrote:
>> On 15 Dec 2011, at 14:30, Philip TAYLOR wrote:
>>
>>> I know that a number of excellent typographers inhabit this
>>> list, so I would like to pick their brains if I may ?
>>>
>>> In "Two w
On Dec 15, 2011, at 12:18 PM, Tobias Schoel wrote:
> But why? They are semantically different. Does this “identity” come from
> historical roots?
The same stroke was used by the scribes for both purposes / the characters are
taught the same when written and when printed as metal type the same p
Hi List,
On 15.12.2011 17:02, Jonathan Kew wrote:
On 15 Dec 2011, at 14:30, Philip TAYLOR wrote:
I know that a number of excellent typographers inhabit this
list, so I would like to pick their brains if I may ?
In "Two wide ‘weaver’s windows’, usually found on the ground floor"
(which could e
On Dec 15, 2011, at 9:30 AM, Philip TAYLOR wrote:
> I know that a number of excellent typographers inhabit this
> list, so I would like to pick their brains if I may ?
>
> In "Two wide ‘weaver’s windows’, usually found on the ground floor"
> (which could equally well be "Two wide ‘weavers’ window
On Thu, 15 Dec 2011, Philip TAYLOR wrote:
> found on the ground floor", but I am not the author), the apostrophe
> of "weaver’s/weavers’" is the same Unicode character as the closing
> quotation mark of "windows’". Should it be ?
I think that's the practice recommended by the Unicode Consortium.
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’, usual
On 15 Dec 2011, at 14:30, Philip TAYLOR wrote:
> I know that a number of excellent typographers inhabit this
> list, so I would like to pick their brains if I may ?
>
> In "Two wide ‘weaver’s windows’, usually found on the ground floor"
> (which could equally well be "Two wide ‘weavers’ windows’,
I know that a number of excellent typographers inhabit this
list, so I would like to pick their brains if I may ?
In "Two wide ‘weaver’s windows’, usually found on the ground floor"
(which could equally well be "Two wide ‘weavers’ windows’, usually
found on the ground floor", but I am not the aut
27 matches
Mail list logo
