User:Malku H₂n̥rés/Projects

Here I list all my projects on Wikipedia and Wiktionary. These are projects I make to improve linguistic content on these two platforms. I make these projects alone, but you can help me if you want (if you have nothing to do or if you have no project idea for these platforms).

• Click here to access the redlink I am currently creating because I saw it.
• Click here to access the entry I am creating through a project of sequence of redlinks to create.
• Click here to create a new subpage.
• Click here or here to have infos about a language with its code.

• To transfer.
  • Trees to fill, a list of trees which you just have to copy then fill reflexes, for each languages family.
• Projected: Having three big subpages, the first for models for entire entries, the second for free knowledge and the third for regular sound changes.
  • Free knowledge, a list, by language and script, of free, accessible and reliable knowledge, templates providing a link, linkless templates and simple links.
  • Entries to fill, a list, by languages existing on Wiktionary, of already-made entries, just to fill. Including a "coming soon" section for languages that might come into Wiktionary in the next years, particularly reconstructed languages which could become widely accepted and securely reconstructed.
    • To extract:
      • trees by language from Trees to fill.
      • references by language from and Free knowledge.
  • Regular sound changes, a list, by language families then by language, of regular sound changes (RSC) from the direct ancestor of a language to it. Thus one will be able to access easily the RSC of a language to see if a word is or not the regular reflex of its etymon. It will also be helpful for the reconstruction namespace because one could easily check from where each phoneme or cluster could have descended and if all the descendants point regularly to the same reconstruction, it can only be the right one. As one person can't know the RSC of each language, if you have any comparative linguistics knowledge about a language family of a unique language, your help is welcome. Each shown RSC have to be accompanied of either a reference stating the RSC or a list of words matching the aforementioned RSC.

Useful templates, modules and bot functions I could create when I'll have learnt the programming language (except if it's in JS) and how to program templates, modules and a bot:

• Templates to automate transcription to IPA, tr, ts etc. in languages without such template and for which transcriptions is regular from entry to IPA.
  • IPA transcription: (Proto-languages shouldn't have IPA transcription so it's unclear for me whether it's reserved for some or even PIE and PAA should have an IPA template) PGmc, PAnat, PAN
  • "tr" transcription: See among Turkic and Semitic languages
  • "ts" transcription: some cuneiform-written languages (Sumerian, Akkadian, Hittite, other anatolian and oldest recorded IE languages, Old Persian)
• A module to store the Regex functions and other common code used in all transcription templates.

A module or bot function you put on a redirect page and it changes the links thereto to where it redirects, making the redirect page good for bin. How it would work:

1. A user put the template on a redirect page.
2. It keeps the link it redirects to in a variable.
3. It goes to the "What links here" of the redirect page.
4. For each page found, it goes to the concerned page.
5. It replaces, in the page, the links to the redirect page by the variable-kept link but not the text if originally different from the link.
6. It puts {{delete|useless now nothing links here}} on the redirect page for its deletion (if it must be deleted, otherwise it would be kept as a simple redirect if people have motivation to search it, like if it's on some reliable dictionary).

• PIE: make a/improve the template(s) so that it does as much of the work as possible (i.e. you enter the least parameters and it shows the most inflection). Only if PIE-related templates aren't already optimized.

About numerals entries in some languages that need creation, modernization ({{cardinalbox| }} instead of {{enum}}).

Refs:

• From Wikipedia PT pronouns and numbers:
• From Wiktionary entries:

1. *yẹt(t)i (“seven”)
2. *sekiz (“eight”): add cardinal box
3. *tokuŕ (“nine”)
4. *ōn (“ten”)
5. *yėgirmi (“twenty”)
6. *otuŕ (“thirty”):add cardinal box
7. *kïrk (“forty”)
8. *ellig (“fifty”)
9. *altmïĺ (“sixty”)
10. *yétmiĺ (“seventy”)
11. *sekiŕ ōn (“eighty”)
12. *dokuŕ ōn (“ninety”)
13. *yǖŕ (“hundred”)
14. *bïŋ (“thousand”)

See User:Malku H₂n̥rés/Afroasiatic consistency.

Categories listing redlinks in poorly filled reconstructed languages. Of course I'll create only the ones with references, well attested descendants and clear characteristics.

1. Category:Proto-Afroasiatic redlinks

Wikipedia articles with knowledge absent from Wiktionary entries.

1. Phoenician

1. Pronouns

1. Numerals

1. Basic Vocabulary

1. Pronouns and numbers
2. Basic Vocabulary

• Appendix:List of Proto-¿? reconstructions

• Appendix:Vocabulary lists of African languages

• Reconstructed languages: PIE, Proto-Turkic, Proto-Kartvelian, Proto-Semitic, Proto-Afroasiatic (carefully), Proto-Austronesian
• Attested languages
  • Old Languages: Sumerian, Akkadian, Hittite, Ancient Greek, (Classical) Latin, Old Spanish, Old French, Middle French, Middle English
  • Modern languages: French, English, Spanish
• Specific types of entries: Numerals, Swadesh-list words, other frequent or basic words, scientific vocabulary (when borrowed or coined from Greco-Latin lexicon), literary words in French (and somewhat in Spanish and English),

1. Create entries if there's only one descendant family.
   1. Create PIA entries if there's only Sanskrit.
   2. Create Proto-Hellenic entries if there's only Ancient Greek.
   3. Create PIt entries if there's only Latin.
2. (Trivial but never know) Create entries without existing references.
   1. Tip: look if linked pages exist (e.g. if Proto-Nuristani descendants pages don't exist, no ref exists for them).
   2. Create PAA entries with only PSem and PCdc cognates.
   3. Create unattested terms on normal entries (e.g. some cuneiform word whereas it's unattested in the current language).
   4. Create Proto-Nuristani entries at all (until serious researches are done).

The purpose of this project is to gather chronological data about as much reconstructed languages as possible in order to make a timeline, which could be put on some Wikipedia articles related to languages families or comparative linguistics (about origin of language, glottochronology or reconstructed languages).

This timeline could be a picture or a graph, but I don't know neither how to draw the former or the latter from data nor if one of them can be interactive (e.g. if you click or pass the cursor on a part, it shows something).

I'd like too to add a gif picture or something like that showing the homelands in function of chronological data gathered. Thus it would show the historical and geographical evolution of proto-languages, but one more time I ignore the same things as above (how to do it and if it can be interactive).

• Afroasiatic:16,000-10,000 BCE
• Sino-Tibetan:7,000 BCE
• Austronesian:6,000-4,000 BCE
• Algic:5,000 BCE
• Uralic:7,000-2,000 BCE
• Nilo-Saharan:?-4,000 BCE
• Indo-European:4,500-2,500 BCE
• Niger-Congo:3,500 BCE
• Dravidian:4,000-2,000 BCE
• Uto-Aztecan:3,000 BCE
• Eskimo-Aleut:?-2,000 BCE
• Hmong-Mien:500 BCE
• Turkic:500 BCE
• Tungusic:500 BCE-500 CE
• Mongolic:?-1,200 CE

1. On Proto-Indo-European numbers, from *óynos to *tuHsont-, changed from {{enum}} to {{cardinalbox}} template, and filled it.
2. On Proto-Germanic numbers, from *ainaz to *þritehun, changed from {{enum}} to {{cardinalbox}} template, and filled it.
3. Improving of Phoenician entries.
4. Improving of poorly-attested old languages of IE and Semitic families.
5. Improving the "About:" page and entries of Proto-Semitic, and the Proto-West Semitic entries.

1. Proto-Tocharian language. For the moment: evolution, phonology and morphology.