Yes.
Since we're here...
FWIW, the old ECMA Open XML docs defined the following selection of
numeric format switches in addition to the \*alphabetic, \*arabic etc.
that the English-language help tends to cover. I don't have the ISO
equivalent to hand but I think it's fairly similar. I've left examples
in where they seem to be readable and helpful. I would guess these
formats are just the ones that were perceived to be in demand in the
relevant countries/languages, although one or two other representations
are certainly not here.
AIUEO Formats a numeric result using hiragana characters in the
traditional a-i-u-e-o order. [Example: 1 \* AIUEO results in ã‚¢. end
example]
ARABICABJAD Formats a numeric result using ascending Abjad numerals.
[Example: 12 \* ARABICABJAD results in Ù„. end example]
ARABICALPHA Formats a numeric result using characters in the Arabic
alphabet. [Example: 12 \* ARABICABJAD results in س. end example]
ArabicDash Formats a numeric result using Arabic cardinal numerals, with
a prefix of "- " and a suffix of " -"
BAHTTEXT Formats a numeric result using the given Thai style (cf.
DOLLARTEXT)
CHINESENUM1 Formats a numeric result using ascending numbers from the
Chinese counting system. [Example: 10 \* CHINESENUM1 results in å. end
example]
CHINESENUM2 Formats a numeric result using sequential numbers from the
Chinese simplified legal format. [Example: 123 \* CHINESENUM2 results in
壹佰贰拾å. end example]
CHINESENUM3 Formats a numeric result using sequential numbers from the
Chinese counting thousand system. [Example: 10 \* CHINESENUM3 results in
一百二å三. end example]
CHOSUNG Formats a numeric result using sequential numbers from the
Korean Chosung format. [Example: 1 \* CHOSUNG results in ㄱ. end example]
CIRCLENUM Formats a numeric result using decimal numbering enclosed in a
circle, using the enclosed alphanumeric glyph character for numbers in
the range 1–20. For non- negative numbers outside this range, formats
them as with ARABIC. [Example: 12 \* CIRCLENUM results in â‘«. end example]
DBCHAR Formats a numeric result using double-byte Arabic numbering.
[Example: 123 \* DBCHAR results in １２３. end example]
DBNUM1 Formats a numeric result using sequential digital ideographs,
using the appropriate character. [Example: 12 \* DBNUM1 results in 一二.
end example]
DBNUM2 Formats a numeric result using sequential numbers from the Korean
counting system. [Example: 12 \* DBNUM2 results in ì‹ì´. end example]
DBNUM3 Formats a numeric result using sequential numbers from the
Japanese legal counting system. [Example: 12 \* DBNUM3 results in 壱拾
å¼. end example]
DBNUM4 Formats a numeric result using sequential numbers from the
Japanese digital ten thousand counting system. [Example: 12 \* DBNUM4
results in 一二. end example]
GANADA Formats a numeric result using sequential numbers from the Korean
Ganada format. [Example: 12 \* GANADA results in 타. end example]
GB1 Formats a numeric result using decimal numbering followed by a
period, using the enclosed alphanumeric glyph character. [Example: 12 \*
GB1 results in â’“. end example]
GB2 Formats a numeric result using decimal numbering enclosed in
parenthesis, using the enclosed alphanumeric glyph character. [Example:
12 \* GB2 results in â‘¿. end example]
GB3 Formats a numeric result using decimal numbering enclosed in a
circle, using the enclosed alphanumeric glyph character. Once the
specified sequence reaches 11, the numbers may be replaced with
non-enclosed equivalents.
GB4 Formats a numeric result using decimal numbering enclosed in a
circle, using the enclosed alphanumeric glyph character. Once the
specified sequence reaches 11, the numbers may be replaced with
non-enclosed equivalents.
HEBREW1 Formats a numeric result using Hebrew numerals. [Example: 123 \*
HEBREW1 results in גכק. end example]
HEBREW2 Formats a numeric result using the Hebrew alphabet. [Example:
123 \* HEBREW2 results in מתתתתת. end example]
Hex Formats the numeric result using uppercase hexadecimal digits.
[Example: For page 355, PAGE \* Hex results in "FF". end example]
[[Shurely shome mishtake? 255? - Peter J]]
HINDIARABIC Formats a numeric result using Hindi numbers.
HINDICARDTEXT Formats a numeric result using sequential numbers from the
Hindi counting system.
HINDILETTER1 Formats a numeric result using Hindi vowels.
HINDILETTER2 Formats a numeric result using Hindi consonants.
IROHA Formats a numeric result using the Japanese iroha. [Example: 12 \*
IROHA results in オ. end example]
KANJINUM1 Formats a numeric result using a Japanese style using
sequential digital ideographs, using the appropriate character.
[Example: 12 \* KANJINUM1 results in 一二. end example]
KANJINUM2 Formats a numeric result using the Japanese counting system.
[Example: 12 \* KANJINUM2 results in å二. end example]
KANJINUM3 Formats a numeric result using the Japanese legal counting
system. [Example: 12 \* KANJINUM3 results in 壱拾å¼. end example]
SBCHAR Formats a numeric result using single-byte Arabic numbering.
[Example: 123 \* SBCHAR results in 123. end example]
THAIARABIC Formats a numeric result using Thai numbers.
THAICARDTEXT Formats a numeric result using sequential numbers from the
Thai counting system.
THAILETTER Formats a numeric result using Thai letters.
VIETCARDTEXT Formats a numeric result using Vietnamese numerals.
[Example: 12 \* VIETCARDTEXT results in mÆ°Æ¡Ì€i hai. end example]
ZODIAC1 Formats a numeric result using sequential numerical traditional
ideographs. [Example: 1 \* ZODIAC1 results in 甲. end example]
ZODIAC2 Formats a numeric result using sequential zodiac ideographs.
[Example: 1 \* ZODIAC2 results in å. end example]
ZODIAC3 Formats a numeric result using sequential traditional zodiac
ideographs. [Example: 1 \* ZODIAC3 results in 甲å. end example]
As for translations of "one", "two" etc. - Doug has covered that - it's
determined by the language of the text in which the field is found.
However, if you want to insert something like
"Page 1 of 2"
a. the texts "page" and "of" are fixed "trim". If you want your page
to be viewable in different languages, you would have to deal with all
the issues - different words per language, different sequence of tokens
etc.
b. The language used to insert this stuff is the "primary editing
language"
As a partial response to grammatim's question:
<<
and I don't know whether Windows is able to grab
them from there to use them in place of ordinary Arabic numerals.
In Windows XP/Vista, in the Regional options for many languages, you get
to select a set of "standard digits" and there is a "use native digits"
option with possible values "Context", "Never" and "National". However,
there only seem to be 6 such sets in Windows XP, and around 12 or so in
Vista. Whether that has anything to do with the base version of Windows
or what language packs you have installed, I don't know.
As far as I can tell from some brief experiments, the format used by
Word, e.g. to format { PAGE },
a. /never/ uses those "standard digits"
b. bases its formatting on the primary editing language rather more
than I would expect. If you insert something like {=123} and switch to
an RTL script as the primary editing language, the direction of the
field code is reversed (digit digit digit = }, and so on.
All that said, there seem to be so many factors that /could/ influence
the display that there may be more to it than that (e.g. language pack
installation might or might not have a significant impact).
Peter Jamieson
http://tips.pjmsn.me.uk
