Thanks - in that case, I'll wait for 4.0 and see what it has.Well for what it's worth, we've mostly finished implementing support for arbitrary pronunciation systems for 4.0, so it's almost certain that will be included.
Yes, there definitely is! I just figured you were busy and didn't want to put you under pressure. After all, you are doing this in your free time, and even without the result being a lot of use for yourself! Big thanks for that!Is there still any demand for the additional items?
I've been caught up with various professional studies which has taken up some of the free time I previously had for this kind of thing.
Awesome, that should make things a lot easier I guess!Well for what it's worth, we've mostly finished implementing support for arbitrary pronunciation systems for 4.0, so it's almost certain that will be included.
Without dragging out a dead conversation, how is this dictionary installed? I downloaded the files from Github yet Pleco has issues importing it. Is there a thread anywhere to explain the process? Ah Minnan, reminds me of taking Minnan classes at NTU (not very successfully) few years back
Not at all sure that this is the right place to ask, but what's the current progress in Pleco providing Minnan/Taiwanese dictionary & flashcard production support along the same lines as has been provided for Cantonese?Well for what it's worth, we've mostly finished implementing support for arbitrary pronunciation systems for 4.0, so it's almost certain that will be included.
Yeah I figured that it would be pretty much impossible to work around at least under the current system. Very much looking forward to 4.0!So this should be throughly fixable in 4.0, but there's not much we can do in the current release - overrides fix pronunciation but then the search engine simply ignores the field entirely. And indeed it probably would not have been possible to do this well in anything but a horrifyingly complicated multi-year bottom-up rewrite like 4.0 is since we had like a decade-and-a-half worth of accumulated pinyin-related assumptions to work through
Maybe, but that would mean this dictionary wouldn’t be searchable by character, right? I guess you could just put the character lemma within the definition text and then let users find it using full-text search (is that possible for custom E-C dictionaries?)… But then that search wouldn’t be able to differentiate between the head word and a random word appearing in the definition or an example. So I think such an E-C dictionary wouldn’t be viable as a substitute for the current one, but only as an index for where you can look up the characters.Maybe consider making a Tai-lo user dictionary as an English-to-Chinese instead of a Chinese-to-English one? The "English" should at least avoid mucking up letters, and our current English collator totally ignores spaces.
That's a great idea, thanks! I installed the dictionary but for some reason the entries won't show up when I perform search by pinyin or hanzi. The middle option from your screenshot (#a tok a), however, works for me. Any ideas?Hi everyone, I came up with a workaround that should make searching a bit more ergonomic. I created a separate dictionary with Mandarin head words and the corresponding Taiwanese words and romanizations in the definition. This makes it possible to find a Taiwanese word by searching in Mandarin or by doing a full-text search of the pronunciation (remember to enable full-text searches in the dictionary settings):
View attachment 3339View attachment 3340View attachment 3341
Once you look up a word, you can click on a link to take you to the actual definition.
Here's the pqb: dict-twblg-index.pqb.zip
I also updated the original dictionary to include alternate pronunciations. For example, the entry for 頭毛 (thau5-mng5) now includes an alternate pronunciation (thau5-moo1) in the definition text. I've updated the links in my original post to point to the new version. I hope it's helpful!