[[case insensitive title|??]] will do a literal, case-insensitive title search. It will return the first tiddler it finds.
Examples:
[[this is a test|??]] will link to eg: "This is a Test" ... If the tiddler exists!I only just noticed your Uni-link Search feature! Very handy - I have been frequently writing things like [[really good idea|Really Good Ideas]], so this will save me a lot of time.
I have a question however: Is there any way to customise exactly how the search is applied?
I'm wondering if there is a way to use Uni-link search, but tweak it so it will ignore the final "s"? So [[books|??]] would automatically link to [[Book]].
Si wrote:...I only just noticed your Uni-link Search feature! Very handy - I have been frequently writing things like [[really good idea|Really Good Ideas]], so this will save me a lot of time.
I'm wondering if there is a way to use Uni-link search, but tweak it so it will ignore the final "s"? So [[books|??]] would automatically link to [[Book]].
The main problem is, that singular / plural rules depend on the language. book - books in German is Buch - BücherSo a hardcoded rule won't help the plugin.The second problem is, that it has to work in both directions. So imo a link like [[books|??]] needs to search for "book" and "books" ... [[book|??]] has to do the same thing. ... This will make the search function 50% slower :/It would be possible to implement "plural" / "singular" filter rules. But they will be language specific. Some 3rd party libraries will be needed. So there would be an additional plugin per language.
The re-link plugin is very popular and I try to keep uni-link compatible with it. IMO the singular / plural links will definitely be out of the scope, what re-link should handle. ...
The question is interesting and valid, and it seems to be an easy change. .. But due to its language specific nature, it isn't. Implementing it will probably double the actual complexity of the plugin.
While it is possible to emulate natural language usage (i.e. code for variations of plurals; or passive v. active voice) I'm not sure it is ever satisfying.
That's right, because languages haven't been designed to be expressed by algorithms. They have been designed by the human brain. And it seems humans do like "exceptions" from the norm, which tend to cause problems for programs.
There is a little work around, that looks a bit strange. eg: I found some [[book|??]]s. So the link will only cover the book text. I know that's not pretty but it creates valid sentences.
The question is interesting and valid, and it seems to be an easy change. .. But due to its language specific nature, it isn't. Implementing it will probably double the actual complexity of the plugin.
--
You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/35_6ltCXEvs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/a68737d8-c2ab-457d-91c8-d0942d696133n%40googlegroups.com.
For example take [[books|??]]. By default this will work as it currently does, but from a global config the user could add the filter trim:suffix[s]. This would be applied to [[books]] and then the result used as the search term.
>>> The problem is, that I would need to add a generic way. It may work for your, but an other user would probably have fun to link to [[foot]] ;) ...I'm not sure I understand what you are saying here! Is "[[foot]]" an autocorrect error?
... I would not be surprised if there were data sets one could import for English at least to search for equivalents.