Ranmaru

Member

1. Cuneiform Input Method For Mac Operating System
2. Cuneiform Input Method For Mac Download
3. Cuneiform Input Method For Machinery
4. Cuneiform Input Method For Mac Os

Joined

Apr 26, 2009

Messages

5

Reaction score

0

Points

1

Your Mac's Specs

MacBook Pro 2.33 GHz, 2 GiB RAM, OS X 10.5.6; iPod touch 16 GiB

Hello,
I have a problem with Leopard's traditional Chinese input method. When I switch to pinyin input, my keyboard layout becomes messed up. I type on a standard US keyboard (QWERTY layout) which works fine when I use the Hanin input, but when I switch to pinyin, the layout becomes QWERTZ. That sucks because I constantly mix up the Y and Z keys and I can't get used to type Z where Y is supposed to be. On top of that, the punctuation marks like colon, semicolon, ditto marks etc. are someplace I can't find them.
Okay, I could just use the Hanin method to type Chinese since the layout is correct there but Hanin forces me to input the tone mark after every single character I type and that slows me down thoroughly, especially since I don't know the tone mark for every single character I want and I have to try and find it then which is extremely annoying.
So does anyone know where I can change the keyboard layout of the pinyin input back to standard QWERTY? I searched the preference pane but unlike Kotoeri (Apple's Japanese IME) it hasn't such an option. The help menu also doesn't seem to have an item on that matter.
Thank you in advance.

NISUS WRITER PRO (MAC only) In Nisus Writer Pro, automatic text is linked with a glossary. A glossary, when loaded, is available for all documents, whatever template is used. The Cuneiform glossary is a file with cuneiform signs and associated entries. For more informations, see the NWP guide. Format: Cuneiform.ngloss.

IPA input method for Mac OS X. Contribute to zhenlin/ipa-input-method development by creating an account on GitHub. IMKQIM is a Chinese Pinyin input method running on Mac OS X. It provides unprecedented speed and flexibility along with a rich set of features for an improved user experience in Mac OS X. Three main features of QIM: Display the candidates in real time. Intelligent Sentence input.

Unicodefonts for Cuneiform

Input plugin for Mac OS X (designed under Lion) which allows conversion of legitimate transliteration sequences to Unicode cuneiform. Cuneiform font not provided at this time, but is in development. The term input method generally refers to a particular way to use the keyboard to input a particular language, for example the Cangjie method, the pinyin method, or the use of dead keys. On the other hand, the term input method editor on Microsoft products refers to the actual program that allows an input method to be used (for example MS New.

OldBabylonian (crusive and monumental script), Neo-assyrian, Hittite

I.UnicodeStandard5.0 andCuneiform: generalprinciples and critical notes

II.Cuneiformfonts:Oldbabylonian, Neo-Assyrian, Hittite

Installation

SignList and notes

Automatictext

I.UnicodeStandard5.0 andcuneiform

TheUnicodeStandardversion 5.0(July2006, seehttp://unicode.org)now includesblocks for Cuneiform(12000-1236E)andCuneiformNumbersand Punctuation (12400-12462and12470-12473).

Unicodeis ancomputer standard which assign to each character a unique number(code point), wathever the operating system, the software and thelanguage may be. This standard was developped during the times formany writing systems, but was lacking for Cuneiform script.Initiativefor Cuneiform Encoding(ICE http://www.jhu.edu/ice/), foundedinBaltimore in2000, aimedto fill this gap.In2006, a finalproposalfor thecuneiform writing system was elaborated by SteveTinney, Michael Everson andKarljürgen Feuerherm(http://std.dkuug.dk/jtc1/sc2/wg2/docs/n2786.pdf).

The assignment of newblocks for Cuneiform has the purpose to give a solution thatnon-Unicode fonts could not provide. Limitedto 256 characters,they do notpermit the encoding of signs in a single font. Two, three, and evenfour fonts were necessary to have the whole set of signs for Oldbabylonian, Hittite or Neo-Assyrian. The encoding itself wasdifferent from one font to antoher. In this point of view, theUnicode proposal for Cuneiform would make easier the encoding and theuse of the fonts. On the whole, the results are more than positiveand weimmediately see the advantages: electronical corpora, lexicographicdatabases, research oncorpus (sorting, occurrences, index... see http://www.jhu.edu/ice/)..

As every innovation, theUnicode Standard 5.0, even if it meets the major needs, gives rise tosome difficulties and problems, which probably would need someimprovements. The main critical review has been done by R. Borger inthe introduction to Listof Neo-Assyrian Cuneiform Signs. A practical and critical guide tothe Unicode blocks «Cuneiform» and «CuneiformNumbers» of Unicode StandardVersion 5.0(http://www.sumerisches-glossar.de/download/SignListNeoAssyrian.pdf),compiledbyM. Studt (D.Bachmann's revised list).See also thearticleUnicodecuneiform (2007, August 24): Wikipedia,The Free Encyclopedia(http://en.wikipedia.org/wiki/Unicode_cuneiform).

The final proposal sets outthe general principles for encoding.

1)Thecharacter inventory is based on the Ur III sign list, compiled by theCuneiformDigital Library Initiative.As said, thisis a first stage in the definition of code points; other stagesshould concern other periods (OldAkkadien, 2334-2154 et Early Dynastic, 2900-2335, Archaic Cuneiform).

As Borger wrote, theproposed list is limited, in the sense that it does not account fordifferent periods and regions using cuneiform writing. Theconsequence is that some signs used by Hittite or even Neo-Assyriando not have code point for Hittite or even for Neo-Assyrian (see thelists). Several code points should be added to get a complete list,concerning all chronological and geographical aspects of cuneiformwriting system.

2)Cuneiformsign and cuneiform characters do not necessarily correspond; complexsigns and compound signs are distinguished (see final proposal, p.7).

°complexsigns are made up of primary sign with one or more secondary signwritten within it or otherwise conjoined to it. The whole is a unit.For example, the single sign KA��is used to form complex sign KAxGU��(whereGU is writteninKA), KAxLI ��...The complexsign being a unit, it has a specific code point, in this example,KA = U12157, KAxGU = U1216B, KAxLI = U12172.

Some signs of Borger's Listin MeZLdo not have code point. These are rare signs, KAxTU,KAxḪAR, LAGABxGI etc.,aboutthirty, fourty signs. Others are attested for Hittite: KAxÀŠ,KAxÚR, KAxGAG, KAxGIŠ, KAxPA, KAxLUM, SIxSÁ, EZENxŠE,AMARxKU₆,ÁBxA, KISIM₅xÚ-MAŠ.

°compoundsigns are made of two or more signs organized in linear sequences.Each sign exists in other respects as singlecharacter. The whole is generally viewed as a unit, but eachcomponent will be separately encoded.For example:IDIGNA, composedofMAŠ+GÚ+GÀR, codepointsU12226+U12118+U120FC������.

The UnicodeStandard 5.0list ofCuneiform signs is arranged according to the latin alphabet and givesan 'etymological' description of the signs (simple, complexand compound, see Cuneiform Unicode, Wikipedia).

This list, Borger says,'introduces new set on conventional readings, without offeringany explanation', instead of known and generally usedconventional readings in Assyriology. The aim is to describe the sign(Cuneiform sign A, Cuneiform sign KA times LI, etc.),but the use often is not practical (we have to know that GIR =ḪAgûnu,AMAŠ =DAG KISIM5 times LU + plus MASH2).The mostcritically point of view about this new way deals with the signanalysis on the one hand, and the sometimes laborious useof code points. The 'splittability' of some signs actuallyseems arbitrary and could be discussed ; see for exampleBorger, MeZL,n° 754 MEŠ, whichhas to be decomposedME+U+U+U(ME = U12228;U+U+U = U1230D) orn° 459 DUL splittedU+TÚG (U1230B+U12306) accordingto theUnicodeStandard;but accordingto Borger, these signs are not really 'splittable'. Inother cases, it will be necessary to combine one, two,or three code points:U12226+U12118+U120FCforIDIGNA, U12263+U121EC forTÙR (NUN-LAGAR), etc. Ligaturesare in theory impossible, unless another font is made, which containsthe needed variants (that could be absolutely artificial, see, forHittite, notes with the sign lists). For Old babylonian andNeo-Assyrian sign NIGIN(MeZL,n°804) = LAGAB-LAGAB (U121B8+ U121B8), weget����,without thepossibility of a real ligature.

Inother cases, the split of signs is difficult, like for Hittite, whichuses signs based on an Old Babylonian cursive from North Syria(E. Neu - C. Rüster, HethitischesZeichenlexikon,Wiesbaden, 1989). Thesign IDIGNA,as used inHittite syllabary, is not splittable in practice:U12226+U12118+U120FCgives������,not very likethe 'real' sign������.For this kindof compound sign, we have made the resolution to isolate artificiallyeach component, that means to designvariant for MAŠ, for GÚ, for GÀR, which permit to getthe final sign. This kind of variant is pointed out in the footnotesin the sign list. The use of automatical text will also permit to getround this problem (see below).

II. Cuneiform fonts:Old babylonian, neo-assyrian, hittite

The Unicode Cuneiform fonts(TTF) have been designed by Sylvie Vanséveren.

- Santakku: OldBabylonian, cursive script

- SantakkuM: OldBabylonian, momumental script (Hammurabi)

- Assurbanipal:Neo-Assyrian

- Ullikummi (A, B, C):Hittite.

They are freely availablefor the scientific community. They can not be altered or solded.

Fonts installation

°MacOSX: put the fontsinto User/Library/Fonts.

°Windows (XP):

click on Start, thenConfigure settings

click on Fonts: the fontfolder opens

two ways for adding fontsin Windows:

- direct copy of fonts inthe font folder

- click on File menu in thefont window and choose Install new font. Select the font in the Listof fonts. Click on OK.

Sign List and notes

Each sign list contains thefollowing:

- MeZL numbering

- Unicode code point

- sign (conventionalreading and Unicode description)

- sign in the font (andvariant for Hittite)

- autotext

Explanationnotes and remarks in each list concernsome specific problem about a sign, about the split of signs, andabout the necessaryvariants for composing complex and compound signs (almost forHittite).

Automatic Text

Once theencoding is made, it remains to use the fonts in concrete terms, thatis to write in cuneiform. It always is possible to access to thesigns via the Character Palette in Mac OSX orvia the Special Character menu in text editor, but this method islaborious and tedious, since there is necessary to know the signs, orrecognize them, or to know the code point of each specific sign. Inorder to make things easier, one can use automatic text.

Cuneiform Input Method For Mac Operating System

Automatictext insertion is possible in text editors like Word and Nisus WriterPro. File templates are given here for Word and Nisus.Eachtemplate can be modified by the user, who can add, modify or deleteentries.

NB.Neo-et OpenOffice(Mac et PC) do not seem to correctly embed the fonts (nor via specialcharacter insertion, neither via Character Palette in OSX). Othertext editor (like Mellel for Mac) do not offer autotext.

Theprinciple consists in associating an automatic text entry with asign, or group of signs. It is so possible to write in Cuneiformwithout having to know the code point of the signs. In order to dothat, some latin characters are encoded in the fonts (characters fromthe Cuneitruetype font with kind permission of Prof. DominiqueCharpin).

So typing for example theentry 'ma', and then select automatic insertion (viaInsertion menu or keyboard shortcut, see below), we obtain the sign(U12220)

��(Assurbanipal)

��(Santakku)

��(SantakkuM)

��(UllikummiA)

In thesame way, the entry 'lugal' will give (U12217)

��(Assurbanipal)

��(Santakku)

��(SantakkuM)

��(UllikummiA)

Forcompound signs, made of two or more signs in linear sequence, foreach of which one code point is assigned,the principle permits to associate the signs:

'mac'(MAŠ)U12226 ����

'gu2'(GÚ)U12118 ����

'gar3'(GÀR)U120FC ����

'idigna' ������(Assurbanipal)