You might indicate how many entries you expect to have.
If you don't need all your glossary at the same time, there are
inclusion macros that will allow you to just bring in the parts (read
only) you need at any given moment (like all the "A"s). Check out the
IncludePlugin (from http://tiddlywiki.abego-software.de).
I haven't tried it, but it looks like the code for the
TiddlerListMacro could be made case insensitive, assuming that
Javascript knows how to determine the lower case of non-english
characters. Each statement in the macro plugin like this:
tiddlers.sort(function (a,b) {if(a[pOrder] == b[pOrder]) ...
would get changed to:
tiddlers.sort(function (a,b) {if(a[pOrder].toLowerCase() == b
[pOrder].toLowerCase() ) ...
Looks like there are only four places to make the change. But this was
quick survey.
If you try this, be sure to make sure you have a copy of your file
before you start. Also, the changes won't take effect until you've
saved and refreshed.
-- Mark
On May 8, 12:08 pm, aless <[email protected]> wrote:
> I work as a freelance translator and I need an easy way to create my
> personal glossaries. There are powerful and overly complicated
> terminology management softwares on the market, but for my needs I
> think a wiki would be enough.
>
> I organize the glossary as follows:
>
> - one tiddler per entry created from a template, so that I only have
> to fill in the relevant information
>
> - tags to categorize the different entries (whether the source word is
> in Italian, Spanish or English, the specific field it belongs too,
> etc.)
>
> - TiddlerListMacro to get an alphabetical list of the entries that I
> can filter by tags
>
> The glossary I created works perfectly so far, ecxept for the annoying
> problem of the sort order both in the Timeline and with the
> TiddlerListMacro: words beginning with a capital letter comes before
> the ones that begins with a lower case letter, and the ones beginning
> with an accented letter after these ones, i.e.:
>
> Páis
> américa
> ficha
> águila
>
> instead of:
>
> águila
> américa
> ficha
> País
>
> Having read some post about bad performance as the TW grows bigger, I
> wonder if a database solution like ccTiddly would solve my problem. My
> test glossary is small, but if I finally decide to implement it using
> TW it's going to grow fairly big, as I'd be adding entries constantly.
>
> I tried other wikis that would scale better, like PMWiki, MoinMoin and
> DokuWiki, but all of them have some limitation, mainly:
>
> - they normally use page names instead of page titles, so no spaces in
> titles and conversion of all non-ascii characters.
>
> - page revisions (I don't need them, but wouldn't be a problem)
>
> - cumbersome process to delete a page, I'm the only user of the wiki,
> if I want to delete a page, I mean it :)
>
> - difficult to rename a page
>
> - categories instead of tags, almost impossible to batch-rename them
> in multiple pages, less flexibles than tags
>
> each of them has some of the above features but lacks others, dokuwiki
> has tags, for example, and pmwiki could be tweaked to suit my needs
> with *a lot* of costumization. The wikiengine that gets closer to what
> I need is Moinmoin, but it lacks tags.
>
> TW would be perfect, but on a long term I'm worried about performance
> issues. Is there some implementation of TW taht could solve this
> problem? Or is there any other wikiengine I haven't tried that would
> suit my needs?
>
> aless
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/TiddlyWiki?hl=en
-~----------~----~----~----~------~----~------~--~---
