Module talk:etymon
Latest comment: 2 months ago by Ioaxxere in topic Ideas for tracking categories
Manual transliteration
[edit]@Ioaxxere Is there a parameter for manual transliteration when the automated transliteration is incorrect and needs to be corrected? If examples of this are needed, some of them may found be in:
For example, if an etymology tree were to be displayed at Gujarati ઈદ (īda), the automated transliteration īda would have to be corrected to īd. Such a parameter may also be useful for terms without automatic transliteration such as at برابر. Kutchkutch (talk) 17:43, 31 May 2024 (UTC)
- @Kutchkutch There is no parameter for that currently. It would be better to not duplicate information between different pages or templates. Ideally, lang:transliterate would be smart enough to handle these sorts of difficult cases (Chinese transliteration in particular seems to work very well). Alternatively, the module could scrape the page and look for a
|tr=
parameter. @Theknightwho what do you think? Ioaxxere (talk) 18:31, 31 May 2024 (UTC)- @Ioaxxere We can't automate transliteration en masse like that, or it would've already been done. I'd say the solution is to include a
tr=
parameter, but each{{etymon}}
template would only need to include the transliteration for the next level up, if that makes sense. Pinging @Benwing2, who may have thoughts. Theknightwho (talk) 19:36, 31 May 2024 (UTC)
- @Ioaxxere We can't automate transliteration en masse like that, or it would've already been done. I'd say the solution is to include a
Ideas for tracking categories
[edit]For some of these, it might be better to throw an error rather than silently accept invalid input.
|1=
is an etymology-only language code (should never happen, I think).- Bad IDs in the etymon parameter, e.g.
en>word>fakeid
is set as an etymon but word#English:_fakeid doesn't exist. - Improper use of keywords, e.g.
inh
is set on a etymon whose language isn't an ancestor of the current language. - Special characters in
|id=
. In particular,>
(the etymon separator) should probably not be allowed. Also, excessively long or short IDs shouldn't be allowed. - Trees with a height of less than 3 (there's no reason to create a tree of height 1 or 2).
- Redundant
|title=
parameter. - Redundant keywords, e.g. in
|inh|bor|etymonparam
theinh
is completely ignored.