Module talk:tl-headword
Latest comment: 6 months ago by Benwing2 in topic Transcription
Transcription
[edit]@BenWing2 Hi, tr=- in Baybayin entries to remove the transcriptions isn't working. Ysrael214 (talk) 05:57, 10 February 2024 (UTC)
- @Benwing2 Different tag. Ysrael214 (talk) 05:58, 10 February 2024 (UTC)
- @Ysrael214 You now have to specify it like this:
{{tl-noun|+|tr=-}}
otherwise you get an error. See Module:tl-headword/documentation. BTW can you take a look at the module errors in Category:Pages with module errors? They are all due to invalid values for the|type=
field in Tagalog verbs, which now trigger an error. Either we need to correct the verb types, or if they are correct, modify Module:tl-headword to support these verb types. Benwing2 (talk) 06:02, 10 February 2024 (UTC)- @Benwing2 I just removed the types. I (or we) can fix the types for verb by batch at a later time. Ysrael214 (talk) 06:16, 10 February 2024 (UTC)
- @Ysrael214 Hmm, OK. What was the issue here? Were the types generally incorrect? Benwing2 (talk) 06:17, 10 February 2024 (UTC)
- @Benwing2 I think there's no standard names for the triggers. Sure there are actor, object, directional triggers but I don't know who decided which ones goes 1, 3, 5. The ones that gave an error probably followed the now unused
{{tl-infl}}
which has a different assignment than the one in the module. @TagaSanPedroAko Can you answer this? I'm not an editor yet at Wiktionary when the triggers were added. Ysrael214 (talk) 06:20, 10 February 2024 (UTC)- I think the issue is there is no override function on the Tagalog Baybayin transliteration function. I have added an override for the equivalent Ilocano module to handle cases where the Baybayin/Kur-itan "la" should be transliterated "ra" or "rra", but haven't followed up for Tagalog. TagaSanPedroAko (talk) 07:27, 10 February 2024 (UTC)
- @TagaSanPedroAko This may be true but it's unrelated to the issue of the verb types mentioned above. BTW @Ysrael214 I notice that of the 21,000 Tagalog lemmas, over 16,000 of them have a Baybayin script value specified, the large majority of which now use
|b=+
to request the default. Should we instead generate the Baybayin script by default and require that lemmas that don't want it turn it off using|nob=1
? Benwing2 (talk) 07:41, 10 February 2024 (UTC)- @Benwing2 I guess that's okay since it's now majority but initials (abbreviations) that currently do not have Baybayin shouldn't have Baybayin. But could you please give me a txt files of the ones that previously have no Baybayin but will have a Baybayin spelling? (Maybe get the list before execution) I'm worried about the ones with consecutive vowels borrowed from Spanish (ex. Aguilar, correct baybayin is ᜀᜄᜒᜎᜇ᜔ (agilad), not ᜀᜄᜓᜁᜎᜇ᜔ (aguilad)) as well as proper nouns not getting the correct one. Another example (arkeolohiya, should get b=arkeyolohiya, not b=+). But anyway, I'll also just fix the Baybayin of entries of what I find in the list that may need fixing. Thanks! Ysrael214 (talk) 07:50, 10 February 2024 (UTC)
- @Benwing2 Although, the reasoning why I previously didnt make Baybayin default is to make editors double check the Baybayin entries first and prevent users from simply relying on the default because it could be wrong. It's better to have no Baybayin than a wrong Baybayin. (though, majority agrees with the Latin spelling anyway, hence you see a lot of b=+) Sorry, maybe you can add b=+ instead for now for the other entries, instead of making it default? Ysrael214 (talk) 07:58, 10 February 2024 (UTC)
- @Ysrael214 In that case we should probably check the remaining entries before just adding
|b=+
. The list of such entries is found in Category:Tagalog terms without Baybayin script (warning, there are 6200 entries). I can make you a text file containing the contents of that category if it will help. It might be easiest if you just scan for cases that need something other than the default and mark those, and for the remainder we can add|b=+
. Benwing2 (talk) 08:29, 10 February 2024 (UTC)- @Ysrael214 See User:Benwing2/tagalog-terms-without-baybayin-script. Let me know if you need it in a different format. Benwing2 (talk) 08:38, 10 February 2024 (UTC)
- @Benwing2 By the way, is there a way that the headwords doesn't look redundant but keep the categorizations? Example is ᜈᜒᜈ᜔ (nin). Ysrael214 (talk) 17:32, 10 February 2024 (UTC)
- @Benwing2 Also, they aren't marked as suffixes when in Baybayin script. Ysrael214 (talk) 17:36, 10 February 2024 (UTC)
- @Ysrael214 Both issues should be fixed now, using
|suffix=1
and|addlpos=
. See Module:tl-headword/documentation. Benwing2 (talk) 21:15, 10 February 2024 (UTC)
- @Ysrael214 Both issues should be fixed now, using
- @Benwing2 Not sure about this but ligatures and enclitics weren't suffixes originally. If they are but maybe they belong to a different kind of suffixes?
- Wiktionary doesn't define it in the category tree
- Category:Tagalog_ligature-forming_suffixes
- Category:Tagalog_enclitic_suffixes Ysrael214 (talk) 02:18, 12 February 2024 (UTC)
- @Ysrael214 What do you mean "ligatures and enclitics weren't suffixes originally"? Can you give some examples? BTW there is a part of speech "enclitic", see CAT:Enclitics by language, but it's underused in favor of suffixes, I think. Benwing2 (talk) 02:22, 12 February 2024 (UTC)
- @Benwing2 I mean they have their own categories instead of being part of "Tagalog suffixes". Ysrael214 (talk) 02:28, 12 February 2024 (UTC)
- @Ysrael214 What do you mean "ligatures and enclitics weren't suffixes originally"? Can you give some examples? BTW there is a part of speech "enclitic", see CAT:Enclitics by language, but it's underused in favor of suffixes, I think. Benwing2 (talk) 02:22, 12 February 2024 (UTC)
- @Benwing2 Also, they aren't marked as suffixes when in Baybayin script. Ysrael214 (talk) 17:36, 10 February 2024 (UTC)
- @Benwing2 All Tagalog words with special cases (I think) have their Baybayin cleaned up. Please proceed with adding b=+ everywhere. Although please skip initialisms (if caps(text) == text). Thank you! Ysrael214 (talk) 09:37, 17 February 2024 (UTC)
- @Benwing2 This is just a follow up, in case you haven't seen it yet. Thanks! Ysrael214 (talk) 20:11, 19 February 2024 (UTC)
- @Ysrael214 Yup, I will get to this shortly. Benwing2 (talk) 04:58, 21 February 2024 (UTC)
- @Ysrael214 This is running and should be done within 30 mins. You can check Category:Tagalog terms without Baybayin script; when it's done it should contain only acronyms, since you asked me to skip them. Benwing2 (talk) 10:25, 21 February 2024 (UTC)
- @Ysrael214 Yup, I will get to this shortly. Benwing2 (talk) 04:58, 21 February 2024 (UTC)
- @Benwing2 This is just a follow up, in case you haven't seen it yet. Thanks! Ysrael214 (talk) 20:11, 19 February 2024 (UTC)
- @Benwing2 By the way, is there a way that the headwords doesn't look redundant but keep the categorizations? Example is ᜈᜒᜈ᜔ (nin). Ysrael214 (talk) 17:32, 10 February 2024 (UTC)
- @Benwing2 I'll mark what needs to be mark and inform you if you can now simply do b=+ on the rest. And yes, the page of Tagalog terms w/o Baybayin script is fine. Thank you. Ysrael214 (talk) 08:43, 10 February 2024 (UTC)
- @Ysrael214 See User:Benwing2/tagalog-terms-without-baybayin-script. Let me know if you need it in a different format. Benwing2 (talk) 08:38, 10 February 2024 (UTC)
- @Ysrael214 In that case we should probably check the remaining entries before just adding
- @Benwing2 Although, the reasoning why I previously didnt make Baybayin default is to make editors double check the Baybayin entries first and prevent users from simply relying on the default because it could be wrong. It's better to have no Baybayin than a wrong Baybayin. (though, majority agrees with the Latin spelling anyway, hence you see a lot of b=+) Sorry, maybe you can add b=+ instead for now for the other entries, instead of making it default? Ysrael214 (talk) 07:58, 10 February 2024 (UTC)
- @Benwing2 I guess that's okay since it's now majority but initials (abbreviations) that currently do not have Baybayin shouldn't have Baybayin. But could you please give me a txt files of the ones that previously have no Baybayin but will have a Baybayin spelling? (Maybe get the list before execution) I'm worried about the ones with consecutive vowels borrowed from Spanish (ex. Aguilar, correct baybayin is ᜀᜄᜒᜎᜇ᜔ (agilad), not ᜀᜄᜓᜁᜎᜇ᜔ (aguilad)) as well as proper nouns not getting the correct one. Another example (arkeolohiya, should get b=arkeyolohiya, not b=+). But anyway, I'll also just fix the Baybayin of entries of what I find in the list that may need fixing. Thanks! Ysrael214 (talk) 07:50, 10 February 2024 (UTC)
- @TagaSanPedroAko This may be true but it's unrelated to the issue of the verb types mentioned above. BTW @Ysrael214 I notice that of the 21,000 Tagalog lemmas, over 16,000 of them have a Baybayin script value specified, the large majority of which now use
- I think the issue is there is no override function on the Tagalog Baybayin transliteration function. I have added an override for the equivalent Ilocano module to handle cases where the Baybayin/Kur-itan "la" should be transliterated "ra" or "rra", but haven't followed up for Tagalog. TagaSanPedroAko (talk) 07:27, 10 February 2024 (UTC)
- @Benwing2 I think there's no standard names for the triggers. Sure there are actor, object, directional triggers but I don't know who decided which ones goes 1, 3, 5. The ones that gave an error probably followed the now unused
- @Ysrael214 Hmm, OK. What was the issue here? Were the types generally incorrect? Benwing2 (talk) 06:17, 10 February 2024 (UTC)
- @Benwing2 I just removed the types. I (or we) can fix the types for verb by batch at a later time. Ysrael214 (talk) 06:16, 10 February 2024 (UTC)
- @Ysrael214 You now have to specify it like this: