Tocharian BEdit

Note that if you are copying entries from some other site (some of the entries seem to be only present in Palaeolexicon), it might constitute a copyright violation. The site does not seem to have any information on the copyright and licensing, so I would be wary. SURJECTION ·talk·contr·log· 17:38, 12 September 2018 (UTC)


I'm getting them from http://www.win.tue.nl/~aeb/natlang/ie/tochB.html. This is my first time entering things on Wiktionary, so I'm not very familiar with the copyrighting. How would I go about citing the source in-line with wiktionary protocols? GabeMoore (talk) 18:02, 12 September 2018 (UTC)
It would seem that the page gets its content from one book. In that case, it should be fine if referenced. For this, you can use Template:R:txb:Adams 1999. See īke (particularly the References section) for an example. SURJECTION ·talk·contr·log· 18:11, 12 September 2018 (UTC)
It looks to me that the "Further reading" heading is the right one for this instead. "References" is for inline references that give reference to a particular bit of information on the page, like on for example *aiskōną. "Further reading" is for providing more information on the word in general, without referencing a particular fact. —Rua (mew) 18:50, 8 March 2019 (UTC)
Oof. So I would have to go through all my entries, most of which have 'references', and change them to 'further reading'? Is there a bot I can use for this?
By the way, I hopped over to your page and absolutely love your Proto-Germanic work. I bookmarked both the Beowulf and neo-germanic pages in my browser. GabeMoore (talk) 18:58, 8 March 2019 (UTC)
It's not a big deal. The meaning/use of the headings was changed somewhat recently by a vote, but the process to fix up existing entries is still ongoing. You don't have to fix them all immediately, just try to fix a few here and there as you notice them and it's fine. —Rua (mew) 13:08, 9 March 2019 (UTC)

etyl template langsEdit

Make sure to replace the target language when using der/bor/inh, as I did for you in this edit. The first language code represents the destination language (txb in case of Tocharian B). Also, as the summary pointed out, der from the same language should only be used when a word is reborrowed (borrowed into another language and then back), otherwise you can just use {{m}} for the word something was derived from. — surjection?〉 17:02, 4 February 2019 (UTC)

Thank you! GabeMoore (talk) 17:18, 4 February 2019 (UTC)

Entry formattingEdit

Small note: don't forget to add headword-line templates to any new entries you create. I fixed it for you now:

Cheers, — Mnemosientje (t · c) 15:11, 10 February 2019 (UTC)

Again, e.g. Special:Diff/51719253/51731071. If you don't know the appropriate template, compare other entries. — Mnemosientje (t · c) 12:05, 12 March 2019 (UTC)
(Woops, the entry was deleted already, so the diff is not visible anymore. It was at Proto-Indo-European *bʰerH-os-, which lacked a headword template.) — Mnemosientje (t · c) 15:01, 12 March 2019 (UTC)

अन्तःपुरEdit

Is this supposed to be Sanskrit? Tocharian B doesn't use this script right..? User: The Ice Mage talk to meh 16:16, 4 March 2019 (UTC)

Wow, yes, you're right. I'm working on a project right now with a bunch of Tocharian B words that are loaned from Sanskrit, so I mix up the two codes sometimes when making new entries. Thank you for telling me this; that was embarassing. GabeMoore (talk) 16:25, 4 March 2019 (UTC)

On Slavic *brunětiEdit

Hi, regarding Sl. *bruněti, I'm not sure whether we should reconstruct it at all. It is mentioned by V. Orel as a possible indirect cognate of Proto-Germanic *brūnaz, however, except for this mentioning, it's not listed anywhere else. Personally, I have encountered this verb only as the onomatopoeic Bulg. бруня (to spout, to burst). In principle, it could be a ne-extension of *brujiti, however, in my opinion it's better just to switch *bruněti with *brujiti as a descendant of *bʰrewh₁-. Bezimenen (talk) 19:21, 11 March 2019 (UTC)

That seems to work fine. I only suggested moving the term to *bʰrewh₁- from bʰruHnós, where you originally wrote it, because it appears to be derived directly as a form of *bʰrewh₁- + *-(e)yeti. GabeMoore (talk) 19:28, 11 March 2019 (UTC)
Yes, I meant in *bʰrewh₁-. Actually, I think I found the origin of the alleged *bruněti (to shine). Some Russian and Slovenian dialects have the verb брунеть (brunetʹ, to darken) which ESSJa /Vol 3, p.41/ derives from *broněti. I think that is what Orel's source refer to as *bruněti. Bezimenen (talk) 19:53, 11 March 2019 (UTC)
  • The PIE roots for brown and boil are totally separate. I'm reverting all your edits to that effect. --{{victar|talk}} 21:28, 11 March 2019 (UTC)
    Every single PIE root for 'brown' linked in a page for one of its reflexes redirects to the page for the word for 'to boil', Victar. This is why I thought they were the same word with different meanings, as the reconstructions are identical. An example for the definition of the root of 'brown' being the same as the root for 'to boil' can be found at the page for beaver, which is untouched by my "garbage edits". GabeMoore (talk) 23:43, 11 March 2019 (UTC)
    We have many roots that have the same reconstruction, but what you did in error was assume some etymological connection where there is none. See *ǵʰer-, for example. --{{victar|talk}} 00:02, 12 March 2019 (UTC)
    So how would I go about making separate entries for identical reconstructions? Would I just make another entry on the *bʰrew- page with the definition of 'brown', and put all of its derived terms under it, like with *ǵʰer-? GabeMoore (talk) 00:15, 12 March 2019 (UTC)
    @GabeMoore, Bezimenen, I've added the possible "brown" forms here: *bʰerH-. It's a few to many "perhaps" for my liking, but there it is. --{{victar|talk}} 10:36, 12 March 2019 (UTC)

SourcesEdit

Gabe, if you're going to work in proto languages, you need to cite sources. --{{victar|talk}} 20:14, 11 March 2019 (UTC)

The pages I'm getting everything from, (beaver and bear) don't have sources as to those etymologies. If I was getting them from somewhere else I would of course cite sources (as I have done in my Tocharian B work), but all I'm trying to do here is fill in "gaps" where one page says something and another doesn't, where they don't conflict of course. If the entry for 'beaver' says that it's from the PIE term for 'brown', and that that term is from the term for 'to boil, brew', while the entry for the root for 'to boil, brew' doesn't list the PIE term for 'brown' under its derived terms, I would make the assumption that it's simply not listed rather than that the etymology for the entry for English 'beaver' is wrong. GabeMoore (talk) 00:12, 12 March 2019 (UTC)
Gabe, that's a really bad way to go about things, and is why we're having so much trouble right now. It's one thing for an entry to offhandedly mention some spurious or otherwise incorrect etymology, but it's another level entirely to create an whole entry based on it. Going forward, please don't created entries unless you have actual sources for them. Thanks. --{{victar|talk}} 15:46, 12 March 2019 (UTC)

Descendants listsEdit

Borrowings in descendants lists been to be marked with an arrow (→), either manually or preferably by use of {{desc|bor=1}}. --{{victar|talk}} 21:18, 11 March 2019 (UTC)

I'll make sure to do that, thanks for the clarification. GabeMoore (talk) 23:45, 11 March 2019 (UTC)
  • Hey Gabe, please don't null out reconstructible languages in descendants lists, ex. {{desc|ine-toc-pro|-}}. --{{victar|talk}} 05:52, 10 April 2019 (UTC)
  • Gabe, why are you entering entries like this? Please take the time to properly format your work. --{{victar|talk}} 01:30, 3 May 2019 (UTC)
  • Wow, thanks for checking me. I don’t know how that slipped past.
Additionally, you said to use {{desc}} when listing descendants. However, I see lots of pages using <language name> {{l}}. (For example, {{desc|la|puella}} vs Latin: {{l|la|puella}}). Is there any preference as to which of these to use? They seem to display the same thing. GabeMoore (talk) 02:22, 3 May 2019 (UTC)
No worries. {{desc}} is a newer template, which is why many older entries still use {{l}}. That said, usage of {{desc}} is not mandatory, just prefered. --{{victar|talk}} 02:28, 3 May 2019 (UTC)

TocharianEdit

Gabe, please only entries for attested forms in Tocharian A and B. So if the form is in plural, the entry should be in plural. --{{victar|talk}} 06:02, 10 April 2019 (UTC)

The attestation is in the singular, at least with the reference I gave. @Rua also reverted your edit back to mine, so by the looks of it I was just fine. GabeMoore (talk) 14:25, 10 April 2019 (UTC)

Strange coincidenceEdit

I couldn't help but notice that I too am an American high school senior who probably shouldn't have used my real name as a username... Thanks for your Tocharian entries, they are much appreciated. —AryamanA (मुझसे बात करेंयोगदान) 23:57, 14 August 2019 (UTC)

KhotaneseEdit

Gabe, please don't add Khotanese entries until the Khotanese unicode is ready. Also, add Khotanese to descendent trees as such, {{desc|kho|tr=ustama}}. --{{victar|talk}} 06:49, 20 August 2019 (UTC)

Thanks. What would the harm be in that, though? It seems like it would be easier to have Khotanese entries already written in Latin script and go through and provide native Khotanese transcriptions once they’re ready than to have to recreate each page. GabeMoore (talk) 15:39, 20 August 2019 (UTC)
The unicode is being actively worked on and I'm creating a font for it. --{{victar|talk}} 16:36, 20 August 2019 (UTC)

Community Insights SurveyEdit

RMaung (WMF) 14:34, 9 September 2019 (UTC)

Reminder: Community Insights SurveyEdit

RMaung (WMF) 19:14, 20 September 2019 (UTC)

Reminder: Community Insights SurveyEdit

RMaung (WMF) 17:04, 4 October 2019 (UTC)