HHOLY MOLY!! I think that's it!! Thank you!!
I will let you know what I find when I try to implement / test. In the meantime, your other questions: Yes -- those are two different words that happen to share a similar > sound.. You could use the caption or description field so that they could > share the title "Go" for sorting and searching. They'll get superscripts, which is how most dictionaries treat homophones like this. Actually Go 1 would need to be split into each meaning. (Go (bodily > function), Go (movement), Go (turn)...) One for each entry in a good > dictionary -- assuming that you will want to use the data in some manner. Generally, dictionaries list meanings, but don't separate them. All the meanings of go (NOT the game), for example, are generally listed in one entry: https://www.merriam-webster.com/dictionary/go A sample of my current template, modeled on teanglann.ie (I speak Irish): # ''tree'' (N:AS) #* ~ ''mera'': tree chosen for a treehouse #* ~ ''daunhe'': tree inhabited by giant spiders # ''family'' (N:CO) #* ~ ''wai'': extended family; specifically refers to all blood relatives descended from a single great-grandmother # ''rope ladder'' (N:LF) What outputs do you want? How do you expect to use this data? The thing is I think tags would be easier, but I don't wanna see all of them. Just in my short example above, there would be the following tags, if I did it the atomic way tag-wise: N AS CO LF 20000 20500 60000 60600 60601 30000 32100 32160 50000 51800 51824 ... and that's not even all of them. That's a super simplified example, and all are nouns. There are words with TONS of meanings (like English "do"), that fall into a zillion semantic domains. Having those tagged is good, but seeing a huge list of number is not awesome. If you could hide tags, what tags would you hide? all the semantic domain tags (hundreds depending on how detailed I get - and I don't plan to get super detailed, but already have ~200), all the part of speech tags (50-100), various markers (past tense, plural, etc. ~200) > Hmm. Will your polysynthetic language have a single word that indicates > all those things? Ah, here's the fun part about polysynthetic langs! :) So yeah, because a polysynthetic word is built up from lots of pieces, some of which are mandatory, the "parts" that I'm creating aren't words most of the time. No more than -ed is a word. I mean, you can't just say "I ed the other day"- there's got to be a verb in there. I walked or I barfed or whatever. In this language, verbs of handling, like pick up or set or throw, all require a class marker which comes before the verb part. The verb for "picking up a container of something" is a different word in a totally different place in the dictionary than the verb that means "pick up a squirmy puppy", and a sleeping puppy is a different word too! That example with the "killing it for him" is a couple pieces , built on what would be under the verb "stab", which would be a not-transparent conglomeration of "make die with a knife". An example: die : bash >> make die : tosh >> make die with a knife : girosh >> I stabbed it : ngirotse All that happened by perfectly regular, but not obvious, sound changes. Dang I love polysynthesis :) Bash (die V:In2), Tosh (kill V:Tr11), Girosh (stab V:Tr11) are all related, but different words. Are these words you will be constructing? Or are you trying to classify > existing words? Yes. I am constructing them ( a la Esperanto / Klingon / Na'vi / Dothraki / Elvish / Etc.). Yes, I need to classify existing words. And the semantic domain stuff helps - easier to think of / create all the words related to frogs all/mostly at once. On Thursday, July 18, 2019 at 2:33:35 PM UTC-6, Mark S. wrote: > > You could insert the "subfilter" operator. Then use transclusion > subfilter{MyTiddlerWithAVeryLongFilter} and change the contents of > MyTiddlerWithAVeryLongFilter as you needed on the fly. > > If there's a limit to filter run size, I haven't hit it yet ;-) > > On Thursday, July 18, 2019 at 1:28:08 PM UTC-7, Aidan Grey wrote: >> >> >> After some thought and digging, a better idea. >> >> I can go into $:/core/ui/ViewTemplate/tags and change the filter list to >> prevent certain tags / kinds of tags from showing in the tag wrapper. >> They'll still be on the tiddler, just not shown. >> >> Unfortunately, that would be a giant list - are there limits on how large >> a filter can be? Is there a way to transclude the tag list or something? >> >> If I need to see them again - I can either restore the original filter or >> go to the tiddler manager and edit from there. >> >> >> >> >> >> >> >> >> On Thursday, July 18, 2019 at 10:43:38 AM UTC-6, Aidan Grey wrote: >>> >>> Can someone ELI5* how to use / work with fields as lists of tags? What >>> are the limitations and methods for using them? >>> >>> I understand that you can use buttons to edit the list, thanks to the >>> listops widget (I think it's a widget), but I don't understand how it all >>> goes together. Is it really just create a field and put items in it, like >>> this? >>> >>> partofspeech: N:IN V:Tr22 V:Di12 Part:Case >>> >>> where V:Tr22 is a whole "tag" that I can subject to filters like >>> [prefix[V:Tr], [suffix[22], and so forth? >>> >>> I'm particularly interested because I have fields in a dictionary TW >>> that really should have multiple items, like part of speech above. A word >>> can be a noun, several kinds of verbs, and an adverb, for example, and >>> ideally, I'd like to be able to tag them all in there, filter on the tags >>> in the field, etc. In other words, treat them just like a list. They >>> wouldn't change a lot and I don't really need the tags visible since >>> they're in the dictionary entry. I just need them for filtering. >>> >>> I also think using fields this way might be a way to solve another issue >>> - some tags I don't want visible on certain kinds of tiddlers, but the >>> solutions I've seen so far have been ... aesthetically unappealing to me >>> ($:/ will work for some, but not all of them). Multicol dropdowns are >>> great, but when I have literally 100 tags, it's impossible. >>> >>> Thanks, >>> Aidan >>> >>> * just in case, ELI5 = Explain Like I'm 5 >>> >> -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/7e8acdf9-31e5-4dba-a6b6-b0861e3e1163%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
