level 0 Booklet Errata Appendices

From Lojban
Jump to navigation Jump to search

Appendix Errata

Appendix A

  • (Note: these nits are from .filip. and apply to the PDF version bearing file date 2002-12-10 15:50 +0100)
  • Arabic -- I think the fathatan should be not above the final alif but before it (like a separate, spacing, character, and maybe roughly top-aligned with the alif rather than higher), since it really modifies the preceding consonant rather than the alif, which is (AIUI) an orthographical convention but is not pronounced. Check this, if you can.
    • I don't have much control over this; this is really up to how PC Word treats Arabic. In any case, I don't seem to have any fathatan, just dammatan.
  • Arabic -- not sure about the position of the sukun in "wufu:d". The original (modifying the waw) may have been correct. Can you check with someone else (.iusris.?)?
    • There's a sukun modifying both the waw and the dal. Yusri hasn't been answering emails.


    • Spanish g bato (plosive, not fricative) It should be gato.
    • (Note: these nits apply to the PDF version bearing file date 2002-12-03 15:56 +0100)
      • Talen bless you, filip. (for surely it is you).
        • Indeed it is (sorry for not signing my name to it) -- mi'e .filip.
    • The Lojban letters in Chinese (the first column) inconsistently uses the "Lojban" (monospace) font -- most letters are in a Times-like font.
      • Word got grievously confused by the alternation of Chinese and monospace in the generated RTF, and after three sleepless nights of trying to get it to work (Apple 16/600, Substitute Device Fonts, Optimize for Speed, Outline Fonts, Postscript Level 1), I didn't feel like tidying the document any more. I'll more likely remember to next time. :-)
    • The first letter for "Hindi & Urdu" ("a") is also in a Times-like font, rather than in the "Lojban" font.
      • Same problem.
    • The example words for Arabic, Chinese, and Hindi/Urdu do not use boldface to indicate which sound of the example word exemplifies the pronunciation of the Lojban letter
      • They were intended to, but the font I've used for the transliterations (Gentium) doesn't come in bold; not many good freeware Unicode fonts do. The deal breaker is Latin Extended Additional, that I've been using for Arabic. I have two choices: underline Gentium (which will look revolting), or have a less pedantic Arabic transliteration. I will probably go with the latter.
    • Some of the Chinese example words don't carry accents (for example, Datong, fei long wu feng, pinyin, Aol�ng (first syllable), Tang, hen hao, Feizhou, Meiguo, Beijing, Yazhou, Yingguo, wu ye, Puyi, Luoma.
      • aulun gave them without accents here, so that's how I put them. If anyone knows the accents, let me know them, because it's hard enough for me to navigate Hindi dictionaries...
        • I don't think it's necessary with well-known proper names or phrases (nor, in general, providing pinyin tone marks along with the characters!), but okay: Da4tong2, fei1 long2 wu3 feng4 (the dragon's flying and the phoenix's dancing), Ao4long2, Tang2, hen3 hao3, Fei1zhou1, Mei3guo2, Bei3jing1, Ya4zhou1, Ying1guo2, wu3ye4 (if I remember it right: midnight?), Pu3yi2 (the last emperor!), Luo2ma3 (Rome) -- coi mi'e .aulun.
        • I'll see what pne can do. No promises, though.
    • Does alif-waw-heh really spell "vah" in Urdu? I would have guessed that the initial alif should go.
      • Oops. Should have been waw alef heh.
        • That makes more sense to ne.
    • Is "el-kor'a:nu" supposed to be "the Koran"? I'm pretty sure that's "al-Qur'a:n", spelled alif-lam-qaf-ra-(alif with madda)-nun. That is, with qaf not kaf and with alif-with-madda (looks like a tilde above) rather than two alifs in a row.
      • The textbook must have spelt it like that to emphasise the hiatus. Spelling normalised per yours; no idea where the k came from...
    • You use "d-with-underline" to transliterate both dhal (in "ha:da:") and tha (in "kadira"). Is the tha in the latter word a typo, or the transliteration d-with-underline?
      • The latter
    • Should the Arabic for "giddan/jiddan" use fathatan (two high slanted lines representing "an") before the final alif?
    • Should "has.s.atan" use fathatan at the end?
      • Bugger. You mean, fathatan and the other -atan's are not optional like the other vowel points? That makes sense, actually, because I don't know how you'd disambiguate them. Inserted.
        • Um, I don't know -- and I don't really know Arabic. I think they're just as optional as the other vowel points. However, I would write them if "an" is represented by alif. I don't know what Arabic practice is; I can imagine that the alif by itself is sufficient clue to the reading (and in spoken language, the endings generally get lost anyway, don't they?). IOW, don't take my word as authority here. Oh, and the has.s.atan I just thought should have it for consistency with the others. See next comment about the "fully pointed" bit.
    • Should the Arabic for "mas-'alatun" use dammatan (representing "un") at the end over the ta marbuta, for consistency with "s.aifun", "haufun", and "buneiyun" in the following examples, both of which use dammatan? (And also "merkebun" and "motun" earlier.) And "sih.run" should probably also have dammatan.
      • I'm blindly following, but you did notice the vowel example words are fully pointed, and the rest aren't, right?
        • No, I didn't notice. Hence some of my suggestions for consistency's sake are for a false consistency. I noticed some words were pointed and some not but didn't bother to look at the pattern. So I just figured "most words transliterated -un have dammatan, why not all?". I suppose the answer may be "only this which demonstrate vowel pronunciations have explicit dammatan", which is fair enough. Similar with has.s.atan, which is also not fully pointed and, by that token, should probably not have any -atan.
      • All the exx you mention are fully pointed. If the dammatan is not normally used in written Arabic, it doesn't belong in mas-'alatun, because as a consonant example that word is not pointed.
      • The tanween are not included in normal unpointed Arabic, just like the vowel letters. So out they go again...
    • Should there be a space between the Arabic for "mata:r" and the following comma, for readability?
      • I don't like typographical tricks. The sensible thing to do instead is to make the comma part of the Arabic text, which it isn't currently.
        • Well, some Arabic words appear (on my screen) to have a space between word and comma and some don't. In some case, the no-space variant has the comma smudged right against the rightmost Arabic letter, which looked a bit ugly.
    • The sukun in the final example "wufu:d" looks as if it's between the waw and the dal; can it be moved further to the left in order to be firmly over the dal or possibly even a bit to the left of it?
      • I've currently got the sukun modifying the waw; I take it it should be modifying the dal instead (so not wufuw0d, but wufuwd0). Done.
        • Oh, was that supposed to be there? *thinks* I suppose it has a point. I'm not sure whether waw or ya take sukun when they serve as long vowel marker; I suppose they might. I'd've written them without any point if they just mark long vowel, but don't take my word on that. I just went by the transliteration (which has no final vowel) to suggested the sukun on the dal.
        • My textbook has sukun on consonantal y,w, and considers the diphthongs to be aw, ay. So sukun on the w and the d.

I obviously had no idea what I was doing; do keep checking on me! -- n.

    • (Note: these nits are from .filip. and apply to the PDF version bearing file date 2002-12-10 15:50 +0100)
    • Chinese -- "Nanking", should be "Nanning", underlined as "Nanning"
    • Chinese -- "nongren", should also underline the ng and the final n.
    • Chinese -- "gongfu", should also underline the o since it's pronounced /u/ (compare Wade-Giles spelling "kung fu")