Module talk:sa-headword
Add topicIf you want to discuss about various written scripts of Sanskrit, please go to Module talk:sa-convert instead. |
(Notifying AryamanA, Bhagadatta, SodhakSH, JohnC5): I have expanded this module to encompass nouns, verbs and adjectives, converting the templates into Lua code. In the process I added error checking to Sanskrit verb classes, types and modes and cleaned up a lot of garbage entries. There are still a lot of non-lemma verb forms that claim to be lemmas and need to be cleaned up. Benwing2 (talk) 23:44, 4 April 2021 (UTC)
- @Benwing2: Thanks, great work! I'll be cleaning up those entries soon. -- 𝓑𝓱𝓪𝓰𝓪𝓭𝓪𝓽𝓽𝓪(𝓽𝓪𝓵𝓴) 01:43, 8 April 2021 (UTC)
Eastern Nagari
[edit]Words that are in both the Assamese and Bengali script are currently being categorised as only in the Assamese script, not as being in the Bengali script, not as being in both! Surely this is wrong! Should we have a single header for them, or should they be entered twice, once for the Assamese, and once for Bengali? If they are to be entered just once, what do we do if the inflections differ? Do we just produce two inflection tables? Is someone aiming to produce a merged inflection table with footnotes?
Pali has a similar issue for multiple writing systems. I've recently taken to using plain text heading for two different tables for massively different systems, such as alphabetic and abugidic for Thai and Lao. I don't know that alphabetic Thai-script Sanskrit exists. I've been contemplating a footnote system for Pali inflections. RichardW57 (talk) 16:18, 9 April 2021 (UTC)
When I invoke {{sa-sc}}
for such words, should I explicitly list them for both scripts, or is there a plan for the identification to be handled automatically? RichardW57 (talk) 16:18, 9 April 2021 (UTC)
Manual Rectification of Failure to Transliterate
[edit]Module:sa-convert does not yet transliterate all scripts. If it does not deliver a transliteration for a script, but one is provided in the invocation of {{sa-alt}}
, should an inconsistency in transliteration be reported? I think not, and intend to correct this anomaly. The problem came up with the case form पिता (pitā) and the Lanna script, whose equivalent to प needs to be encoded differently in different parts of the cultural region - Northern and Northeast Thailand differ. RichardW57m (talk) 15:43, 13 April 2021 (UTC)
- It seems we were generating unmatched opening 'li' tag and it was messing up the display. I therefore cleaned up the logic so we get the bullet and script name if and only if we display a non-empty list for the script. The only 'alternative form' excluded now is the page name. This logic cured the Assamese/Bengali silly where if one of these was the current script, we usually show an empty list for Bengali and didn't mention Assamese. RichardW57m (talk) 14:30, 15 April 2021 (UTC)
- I've corrected the anomaly; the module no longer adds the word to a maintenance category if automatic transliteration fails but a manual transliteration is provided. RichardW57 (talk) 19:01, 21 April 2021 (UTC)
Confusing form glosses
[edit](Notifying AryamanA, Bhagadatta, Svartava, JohnC5, Kutchkutch, Inqilābī, Getsnoopy, Rishabhbhat, Dragonoid76): , @Benwing2: Nouns, proper nouns, adjectives and participles are currently having thir headwords tagged with the 'gloss' 'root form'. This especially confusing because there is a category of mostly consonant stems known as root nouns, and in fact one of the commonest type of noun is formed as root plus thematic vowel. It is particularly confusing when a participle is tagged as 'root form', as the headword is very much more than the root. I propose changing 'root form' to 'stem'; I'll consider a request to use 'masculine stem' for adjectives and participles. --RichardW57m (talk) 13:31, 12 December 2023 (UTC)
- @RichardW57 Done. Benwing2 (talk) 06:00, 13 December 2023 (UTC)
- @Benwing2: Thank you, but I raised the topic to get consensus, not to request an edit. --RichardW57 (talk) 08:53, 13 December 2023 (UTC)
- @RichardW57 OK, sorry, let's see what others say and we can change it as necessary. Benwing2 (talk) 09:22, 13 December 2023 (UTC)
- @Benwing2: Thank you, but I raised the topic to get consensus, not to request an edit. --RichardW57 (talk) 08:53, 13 December 2023 (UTC)
Deva parameter or PAGENAME
[edit](Notifying AryamanA, Bhagadatta, Svartava, JohnC5, Kutchkutch, Inqilābī, Getsnoopy, Rishabhbhat, Dragonoid76): For {{sa-alt}}
, I have tweaked the code so that where present, |Deva=
is used rather than the page name. Before this change, on non-Devanagari pages one could list alternative forms in all scripts by sequences such as {{sa-alt|स्त}}
{{sa-alt|ष्ठ}}
, but on Devanagari pages it would only list a single non-Devanagari form. --RichardW57 (talk) 11:22, 7 January 2024 (UTC)
category 'periphrastic future'
[edit]@Dragonoid76 @RichardW57m Currently the headwords termed 'periphrastic future' do not get a category (same with 'imperfect' and 'conditional' but those don't tend to have separate stems). So should 'periphrastic future verbs' be a category next to 'future verbs', or should they both be classified as 'future verbs' and then make 2 new categories 's-future' and 'periphrastic future', similar to the categories of aorist-types? Exarchus (talk) 16:07, 27 March 2024 (UTC)
- @Exarchus I think that's a good idea. Dragonoid76 (talk) 02:34, 28 March 2024 (UTC)