Hi Elpidio,

On Saturday 19 June 2004 00:41, Elpidio Latorilla wrote:

> - more capacity to format the text
> - tables support

(although it has a bit ugly table syntax ;-)

> > 3) who can explain me the namespace concept (and what should we use
> > it for?)
>
> Basing on what I have read quickly, it can be used to configure the CSS
> design.

(after reading the help page Wilfried pointed me to: )
Wikipedia also uses the namespace notation for i18n. When you want to 
point to the same article but in a different language, you write 
  [[language code:Title]]
at the bottom of the article. (language code = en, fr, it ...) This makes 
the link appear in the "Other Languages"-Box below the navigation menu.

To link directly to the foreign language article you have to prefix an 
extra colon - e.g. 
[[:de:Hond]]    or    [[:de:Hond|German translation of Hond]]

(see http://en.wikipedia.org/wiki/Wikipedia:Interlanguage_links )

BTW: setting up the locale code as (virtual) server name for the localized 
docs-wiki might be a good idea, too. (" de.docs.care2x.org ")

> > I like the wiki as a tool for cooperative work on documents, but a
> > valuable documentation should IMHO be searchable for each language
> > separately.
>
> One solution to that is to install a Mediawiki for each language using
> its own database. This is practical due to very easy installation.
> Also, the server donated by the MFH company can support it. I will
> install another Mediawiki for the german language very soon.

ok, this seems to be a good solution because then the whole wiki is also 
set up in the given language :-)

> >Maybe it should also provide some kind of
> > non-(publicly)-editable view for customers (allowing only annotations
> > / user comments like the mysql online docs).
>
> This is possible by creating a non editable page and linking it to a
> public page as a template. Or creating a non-editable page and using
> the "discussion" function for the annotations or public feedback.

we should test this.
as a first step, it would make sense to restrict editing to logged-in 
users - then one could see, who was editing what. Just IP numbers are not 
so well self-explaining ;-)

Regards, 
Nino


-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
Care2002-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/care2002-developers

Reply via email to