W3C home > Mailing lists > Public > public-qt-comments@w3.org > August 2009

[Bug 7202] [XSLT 2.0] Traditional Hebrew Numbering

From: <bugzilla@wiggum.w3.org>
Date: Thu, 27 Aug 2009 15:16:24 +0000
To: public-qt-comments@w3.org
Message-Id: <E1Mggi8-0003b5-RG@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7202





--- Comment #1 from Efraim Feinstein <efraim.feinstein@gmail.com>  2009-08-27 15:16:24 ---
This feature request really comes down to a request for an additional standard
way for a user to provide the XSLT processor with nonstandard language-specific
options.

The specific issues for "traditional Hebrew" are:

Sometimes numbers are printed with additional marks to indicate that they are
numbers, sometimes they aren't.  The specification uses both conventions, once
in the example for dates, once in the example for numbering.  The types of
additional marks also change.  In modern texts, numbers are sometimes marked
with a geresh (1=א׳) following the number, and sometimes with a gershayim
(21=כ״א); In archaic texts, overdots are sometimes used to indicate that the
value is numeric and not a word (21=כׄאׄ).

When the number is represented as words, it could be masculine or feminine, in
both ordinal and cardinal forms.  There's currently no way to specify masculine
or feminine for cardinal forms.

Also, there are two conventions for how to specify a number in words.  The
modern convention (the equivalent of representing 1234 as "one thousand two
hundred thirty four") and an archaic convention ("four and thirty and two
hundred and one thousand").

It's probably beyond the scope of XSLT to define all possible options for all
possible languages, but, in the interests of interoperability between
processors, ideally, the set of options for each language could be expanded in
some way involving community-consensus, perhaps by a list of non-normative best
practices for each language.

A model for how to do it might be in the @ordinal attribute of xsl:number (XSLT
2.0, sec 12.3):
"For inflected languages that vary the ending of the word, the preferred
approach is to indicate the required ending, preceded by a hyphen: for example
in German, appropriate values are -e, -er, -es, -en."

Similarly, a new @options attribute to indicate language-specific options could
be added to the spec.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 27 August 2009 15:16:34 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:40 UTC