[Moin-user] Automatically create links

[Thomas Waldmann]

Hi Robert,

>>> I working on wikifying the Linux Document Projects doc's.
>> Cool. :) linuxwiki.de also runs moin.
> 
> Nice. Unfortunately I understand very little German, I saw that the
> logo was linuxwiki.org and hoped that there was an english site too,
> but linuxwiki.org just redirects to linuxwiki.de.

Well, the initial idea was to run it multi-language, but we lacked 
English contributors - all the founders were from Germany. I tried to 
make some international contacts, but interest in collaboration was 
lower than expected.

>> The biggest one seems to be spam.
>>
>> I suggest you try moin 1.6.3 or 1.7.0 because it will likely keep the
>> spam away if you use textchas.
> 
> Finding were textchas are enabled is still on my to do list, as well
> as PDF and plain text output and DocBook > moin > DocBook, the
> priority is to get content into wiki first though.

May I strongly advise against that priority list? If you put in content 
first, you will have a continuing spam annoyance as the spammers really 
seem to like your domain... - it will also clutter your data_dir with 
lots of fake user accounts and spam pages / spam revisions. You don't 
want that. Enabling textchas is 15 minutes, living with spam creates 
much more annoyance and work. BTW, there is a textchas_disabled_group, 
you want to put all trusted editors using the wiki regularly in that 
group, so they don't get annoyed with questions.


> I'm busy writing a script for that, unfortunately moin markup does not work
 > well with our content.

1.7 has admonitions, I guess you'ld really like that for pretty docs.

> <tt></tt> is the main one that there is problems with, a short term
> solution is just to remove any such markup (the authors abuse it
> anyway and there is no standard).
> 
> I also had a hard time doing the Vim HOWTO, as moin thinks Vim
> commands are markup.

Usually you want to put such stuff into `backticks` or some
{{{
pre section
}}}

>>> but the one I'm trying to sort out
>>> here is how to get existing docs automatically linked, even if there
>>> is no explicit link in the doc.
>> Well, for a collection of documents, maybe just use TitleIndex?
>>
>> You could also put category tags onto the pages and search for the
>> categories to autogenerate some categorized list.
> 
> Thank you for that, but some of the content that will be added can not
> be changed due to licence problems and will have an attached comment
> page. If there is a mention of the "Linux Cluster HOWTO" in the
> document, it would be nice if that just linked automatically.

Well, I implemented automagic linking some time ago, but due to some 
problems back then, it was never added to a moin production version 
(search for gaga to find discussion about it on moin wiki).

Maybe I'll retry after we have our new storage backend, it should fix 
some of those problems (but please don't hold your breath :).

Until then, the only sane way is to use [[free links]] (where allowed).

If a document's license is so restrictive you may not even add markup to 
create a good rendering of it, I am not sure it is worth caring for it.


> CameCase is not really a solution as sometimes it doesn't make sense

Sure, this is why we offer both CamelCase and [[free links]].

>>> BTW, while I'm thinking of linking, if someone can please point me in
>>> the right direction in regards to getting underscore links back in the
>>> most recent MoinMoin - I'd appreciate it.
>> I am not sure what you mean with underscore links.
>>
>> In case you mean moin magically changing spaces to underscores when
>> generating URLs, that won't ever come back (we only had troubles with it
>> and we would have even more trouble soon, when unifying attachments and
>> pages to mimetype items).
>>
>> For moin >=1.6, it is simple:
>>  * If you want underscores in a page URL, use a page name with underscores.
>>  * If you want blanks (%20), use a page name with blanks.
> 
> On the desktop version of MoinMoin that I'm experimenting with, there
> is no %20 in links, just white space.

Be careful, SOME browsers unquote the URL before showing to you in the 
URL entry line at top of the content window. Some even do for the status 
line below the content window when your mouse pointer is over the link.

You see it easily when going to a page with non-ascii name or with a 
space in the name.

If your browser shows non-ascii or a space in the URL, it is unquoting.

Moin never creates non-ascii URLs, but always url-quoted utf-8. moin 
also never creates URLs with space char in them, there is always a %20.

Cheers,

Thomas