I guess I'm gonna be a PITA then - sorry Victor more patching is required, since MediaWiki resolves _'s to spaces, it thinks my username is "the angry angel" instead of what it should be Unfortunately the nowiki tags dont work in the logon box either :'(

ok that works now. I just hope wiki won't have any problems with these usernames because they aren't according to wiki standards.

Quote from Victor :

ok that works now. I just hope wiki won't have any problems with these usernames because they aren't according to wiki standards.

I just love to be difficult. Tbh, given the fact that I'm one of the few with _'s, I'm perfectly happy to have to wrap the nowiki tags around my name in the login box :o

Quote from wiki :

from within function "User::addToDatabase". MySQL returned error "1062: Duplicate entry 'the_angry_angel' for key 2 (localhost)".

Ah I'm so complicated I get the above error on logon attempt.

now it should be ok.

Next time you're in the UK you're getting at least one beer (honest this time )

it's still a bit shabby though
For example at other places in the wiki where it shows your username, it still comes out 'The angry angel'. The problem is it uses the same normalisation function as for other texts (not just usernames), so I cannot change that normalisation function, or else I risk the whole wiki screwing up.
So the real solution would be to make a separate username sanitation function and replace all the username checks in the code with that new function

Get a proper name, geek.

Can you not just add nowiki tags around the username automatically in the code to any username entered?

Quote from Victor :

it's still a bit shabby though
For example at other places in the wiki where it shows your username, it still comes out 'The angry angel'. The problem is it uses the same normalisation function as for other texts (not just usernames), so I cannot change that normalisation function, or else I risk the whole wiki screwing up.
So the real solution would be to make a separate username sanitation function and replace all the username checks in the code with that new function

TBH I can live with that behaviour, since it's not exactly life threatening. I can totally understand where you're coming from with this problem, and is one reason why I have a dislike for most wiki software. Unfortunately they're in-grained with this now though. At the end of the day, as long as I can spam the wiki with file formats, updating the other copy of the hosting guide, etc. I'm perfectly happy

Quote from Bob Smith :

Get a proper name, geek.

Don't make me spam your user page with more bullshit than I've entered into mine, Mr Smith (and yes, self editing is bad )

I'm not bumping this, I'm recycling it lol.

The only thing that we don't have is the descriptions of AS GT and North, and lyrics and bass tabs for the songs (lol).

I'm doing GT and North.

And we need to add Geraldine to the credits somewhere.

Quote from GP4Flo :

And we need to add Geraldine to the credits somewhere.

And Leo too, IMHO ^^

Maybe u've seen, french community is about to start a French LFS Wiki.
IMHO, the best place is the official Wiki, but I think there's a major problem, wich can't arise whith English/German.
Look at Introdution URL :

• in english : http://www.lfsmanual.net/wiki/Introduction
  
• in german : http://www.lfsmanual.net/wiki/Einleitung

Unfortunately, Introduction translates to Introduction in french, and that's the same with Options, so the URLs would be the same for these pages, and IMO some others too.

In my thoughts, best way would be using a common tree with a langage suffix, a langage selection on all pages (defaults to users's mother tongue), and and an automatic language suffix in all URLs, like http://lfsworld.net/wiki/introdution/fr or http://lfsworld.net/wiki/introduction?lang=fr.
Of course, if the page doesn't exist in this langage, english version would be displayed.

I've no skills in Wiki, that'll be my first experience, so dunno if this is easy to do. Maybe this feature is allready implemented in MediaWiki, I dunno. In this case, we could use it, the only (big) problem would be from german version standardisation (updating all URLs & links to fit the standard (english) tree ie http://www.lfsmanual.net/wiki/Introduction?lang=de -obviously, this link doesn't work, it displays english version-, instead of http://www.lfsmanual.net/wiki/Einleitung.

There will be some other benefits : automatic langage selection, edit restrictions, depending on the user's mother tongue, and so on.

I'm really intersted by replies (especially Victor's one ), coz if it's not possible (or requires a lot of work) we'll start our own Wiki.

Ty for reading

The language split on the current wiki is not ideal, a en.lfsmanual.net and a de.lfsmanual.net, etc, would be the best solution.

I have no clue about what's the easiest / best way to go about this.
If others agree with Bob that the manual should be split up into separate websites for each language separately, then that's not too hard to do and I can set that up. But if others have other ideas ... ?

I agree with Bob.

I agree, that's probably the best solution. That way a fr.lfsmanual.net wouldn't be a problem either.

okay, I'm conviced (almost ).
I'll read MediaWiki documentation, and if I find a good solution, I'll propose it.

Btw, what about domain redirection, depending on user's mother tongue, for it's first access to the Wiki?
Of course from LFS official web sites only, coz the site has to identify the user.

hmm, one downside to creating separate websites though : it would truly separate the wiki's 100%. Meaning, images couldn't be shared and being logged in at one wiki doesn't mean you're logged in at another (and user settings and personal pages wouldn't be shared).

Will this be a problem? I'm thinking it might be nicer if there's some integral way to do this. Guess I'll have to dig into the docs myself too later tonight.

There are language options available for sure, but never looked at them before...

Quote from Victor :

hmm, one downside to creating separate websites though : it would truly separate the wiki's 100%. Meaning, images couldn't be shared and being logged in at one wiki doesn't mean you're logged in at another (and user settings and personal pages wouldn't be shared).

There is some plan for meta logins across all Wiki projects (WP, Wikiquote, Wiktionary and whatnot) but I don't know how that works (or, more importantly, if it would need a new version of the MediaWiki software). Image sharing wise, all the Wikipedia stuff is on WikiCommons.

If the S2 licence automatically creates an account on the forum and LFS wiki, surely it could automatically create an account on more than one wiki. Maybe it could automatically make all the user pages redirects to the english wiki, or maybe that would be impossible. What I know about this web stuff could be written on the size of a postage stamp ... written with an FO8 tyre

And if they are wanted to be kept seperate, */wiki/fr/Introduction is more sensible than */wiki/Introduction/fr IMO. Make the /wiki/en ones redirect to the without the EN ones, there shouldn't be the need for the en because english will almost definatly be the most active one.

Quote from Victor :

Guess I'll have to dig into the docs myself too later tonight.

lol, thanks, there's not so urgent for french community, so take your time, have good nights, breaks, & so on
We'll not start so quick, and even in this case, we can copy the english tree, and in this case, I'm guessing (hoping) merging the english ans french wikis will be possible.

That's exaclty what I was searching for : a language selection bar http://www.mediawiki.org/wiki/Help:Contents

U can edit the page, look at the next to last line : {{Languages|Help:Contents}}

The french links end with /fr, ie Help:Contents/fr (english link is Help:Content)

There is one major difference : if a french page doesn't exist, mediawiki doesn't display english version, but ask for creating the page (obvious ^^). But maybe that behaviour can ben customized, or may we can automatically add a link to the english version.

Remember, I have no skill in Wiki, so please, if it can't aplly, be forgiving.

Edit : looking at the wiki, I've seen the english and german TOC are different. Maybe my idea is not so good.

I think creating a seperate wiki for each language and linking them in a way like Wikipedia does would be the best solution. I initially choose to put it all into one wiki, because it's a bit difficult to make those seperate installs work together.

You can read more about the multi lanuage support (called "Wiki family") here:
http://www.mediawiki.org/wiki/Manual:Wiki_family

And here is a detailed guide how to set up several wikis (one for each language) on the same server, using the same files and database. Maybe you can take a look at it, Victor?
http://www.steverumberg.com/wiki/index.php/WikiHelp

Thanks for that link - I think it's clear now and yep, looks like I'm gonna set it up like Wikipedia. So there'll be en.lfsmanual.net and de.lfsmanual to start with. Then fr.lfsmanual.net will be setup shortly after, when the German one has been sorted (I guess it needs to be separated from the current, and what will be the english website) and still have images and media shared between the different languages.

Ok, the wiki setup has changed to the following :

www.lfsmanual.net will automatically forward you to one of the following :

en.lfsmanual.net - the English version
de.lfsmanual.net - the German version

Media files (generally speaking : images) are hosted at upload.lfsmanual.net . This place is shared between all the lfsmanual.net sites. You do not need to worry about the location of files when editing pages though - the wiki will automatically use the correct url and paths. You insert images just like before.
When you upload a media file, you're automatically taken to upload.lfsmanual.net . In other words, don't worry about this paragraph

In fact, all should be quite logical browsing wise.

@ mosquito25 : Let me know when you want to start creating the French manual. I will setup the domain for you then and make it private for you and your co-editors to quietly work on your translation. Then when you're done, the new translation can be integrated into the whole.

This goes for everyone who feels like adding a new translated manual. Just post here if you are interested. (I'll also make a thread about this in the language subforum )

As usual, if you encounter any difficulties, let me know. Otherwise, enjoy.