Hi
I still have this on my todo list ... I post it here to hear your opinions,
and because we have only the SDB namespace atm.
Did i miss something? To be honest i thought it would be much more, but i
don't know what else to write :-)
---
Howto/SDB/FAQ?
There is some confusion about the definition of howtos, SDB articles and FAQs.
This page tries to explain the main differences between the different styles
to write documentation.
Why a different namespace for them
Working with namespaces makes searching much easier and you can see on the
first look what it is.
The different types
howto
From the wikipedia definition "A how-to is an informal, often short,
description of how to accomplish some specific task. They are generally meant
to help non-experts, and may leave out details that are only important to
experts, and may be greatly simplified from an overall discussion of the
topic."
This describes perfectly an SDB article :-)
Anyhow, most howtos are much more for experts and often more verbose. An
example for an howto is SDB:Wireless_LANs_with_SuSE_Linux.
So howtos in the openSUSE wiki are more verbose than SDB articles. If you just
want to write a short article consider to put it into the SDB.
Howtos have a separate namespace, so all Howtos should start with howto:
SDB article
SDB (Support Database) was a SUSE invention. The goal is to provide a short
and easy to read article for the customer/user how to fix a problem. The
focus was to make it easy and to use graphical tools where possible. A SDB
article should be always problem related.
Because there was only the SDB before the openSUSE wiki, you will find also
some articles which are from the definition a howto.
Check the SDB:Howto for more information about SDB articles.
SDB have a separate namespace, so all SDB articles should start with SDB:.
FAQ
A FAQ (Frequently Asked Questions) follow a different style. Example:
Q: Is it possible to install SUSE Linux on a computer with a i486 CPU?
A: No, SUSE Linux support CPUs from Pentium 1 (and compatible ones) on.
FAQs are a good way to summarise topics. It could make sense even if a howto
or SDB article already exist. Some howtos include a FAQ, usually at the end
of the howto.
FAQs have a separate namespace, so all FAQs should start with FAQ:.
--
with kind regards,
----------------------------------------------------------------------
Martin Lasarsch, Subsystems
+49 911 74053 181 +49 179 206 74 74
SUSE LINUX GmbH, Maxfeldstr. 5 90409 Nuremberg
martin.lasarsch(a)suse.de
----------------------------------------------------------------------
simply change to www.suse.de
Good morning. I found Japanese translation pages has been wrong-coded
again. Sad....but this fact is already in Bugzilla, so that's OK.
By the way, I hava question to other localization teams waiting for the
own Wiki. Do you have a mailing list or some method to communicate each
other?
We are Japanese team and would like to use Japanese and discuss on a
very localized matter, so it would not be suitable to use this ML.
At first the members were few so we could use CCs in each mail, but
these days the members are increasing.
It's my (and other starting members') first experience to organize a
team on line and I would like to know what other teams are managing.
noniko
noniko(a)netbeans.jp
JA translation team
I and my colleagues have finished the translation of the main pages.
What other have I to do to have Italian wiki (it.opensuse.org) published?
I'm waiting for your response, as written in the openSUSE Translation
Guide...
Marco
On http://en.opensuse.org/Download all the languages are done twice, or so
it seems. Look in the left lower part of the menu.
houghi
--
Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es
ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk
und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau
In my editing of the language status page
http://en.opensuse.org/Translation_Status, it has become obvious that
the current language codes used by Chinese are not correct ISO 639
codes. They are more like TLD (top-level-domain) country codes.
The correct code for Chinese is ZH with possibly ZH-CN for simplified
and ZH-TW for traditional, and not just CN and TW.
As it so happens CN is not the language code for any other language,
so there is no clash.
TW is actually the language Twi, which apparently is an african
language with millions of speakers.
Wikipedia with its vast larger number of articles combine Traditional
and Simplified under the one zh.wikipedia.org.
I see five solutions:
1. CN for Simplified, ZH for Traditional
2. ZH for simplified, ZH-TW for traditional
3. ZH-CN for simplified, ZH for traditional
4. ZH-CN for simplified and ZH-TW for traditional.
5. ZH for both simplified and traditional.
I think it is unacceptable to use TW which belongs to another language.
I would now like to say that I don't read or write either. Nor have
any real understanding of the history behind why there are two, and I
appologise beforehand if I have offended anybody through being
ignorant of their culture and language, I just want things to be
orderly.
Peter 'Pflodo' Flodin
Hi all,
I want to start making Finnish translation of opensuse wiki. It would be
nice to hear if there are other Finnish speaking people that could
contribute too.
I'm fairly new to linux and SUSE myself. I've been using SUSE for only a
couple of years now. By profession I'm a software developer but whole
OSS development is quite new to me. This will be my first contribute to
the OSS community in this size.
Thank you for reading and have a nice day!
BR, Pasi
The Swedish (SV) openSUSE.orghttp://sv.opensuse.org was "launched" on Friday, so a new language site added to the list
of present openSUSE sites; English, French, Spanish and German.
Should we announce this in any way or what is the process.
All the best,
Mikael Sundmark
(Msundmark)
http://sv.opensuse.org/User:Msundmark
With the growing number of language wikis (Swedish was just silently
launched http://sv.opensuse.org) the issue of keeping interwiki links
up to date will become an issue.
Jdd's IW template helps a bit, but it has the problem that it adds a
link to all languages if the translated page exists or not. There
should never be an interwiki link to a nonexistent page.
As discussed briefly here before, the way the wikipedia copes with
this is to use a python script. It is a well established opensource
project http://sourceforge.net/projects/pywikipediabot/
The opensuse.org wiki is using non-standard authentication, with
diverts and https.
I was hacking at the script about a month ago, and made some progress
but didn't solve it.
I thought I would have another go, but thought I would raise the
subject in case somebody else has been thinking the same thing. (I am
definetly not a Python expert).
My idea is that we would submit our changes to the sourcforge project
so that we don't have to maintain our own fork of the script going
forward.
I will update the existing page http://en.opensuse.org/openSUSE:Bots
with details and progress.
Peter 'Pflodo' Flodin.
do you think such thing could be usefull for us? I don't
know the given sites, but we may adapt this to our needs
(for example linking to the relevant opensuse mailing list,
forum...)
found on the mediawiki mailing list
jdd
-------- Original Message --------
Subject: [Mediawiki-l] del.icio.us and mediawiki
Date: Sat, 11 Mar 2006 23:25:07 +0530
From: Raj Shekhar <spamme(a)rajshekhar.net>
Reply-To: spamme(a)rajshekhar.net, MediaWiki announcements and
site admin list <mediawiki-l(a)Wikimedia.org>
Organization: Yahoo!
To: MediaWiki-l <mediawiki-l(a)wikimedia.org>
I did not see this tip on the Mediawiki FAQ or the help
page, but I
think this might prove helpful to some.
If you see most of the blogs, they have a bar at the bottom
of each post
which allows readers to bookmark it to del.icio.us, digg and
other
sites. This thing can be done in Mediawiki too (have a look at
http://dtil.info/index.php/Main_Page to see how the final
page looks)
First, create a template by going to
http://example.info/index.php/Template:Dtil and clicking on
"edit" . In
this case Dtil is the name of the template, you can call it
anything you
want. Most likely, you will need sysop powers to edit the
template
page. Add the following lines to this template
<p style="border: 1px solid rgb(159, 165, 234); margin: 0px;
padding:
5px 15px; color: rgb(103, 109, 184); text-align: center;">
[http://del.icio.us/post?url={{SERVER}}/index.php/{{PAGENAMEE}}&title={{PAGE…
Del.icio.us this!] |
[http://digg.com/submit?phase=2&url={{SERVER}}/index.php/{{PAGENAMEE}}
Digg this!]
</p>
The <p style="border: 1px solid rgb(159, 165, 234); margin:
0px;
padding: 5px 15px; color: rgb(103, 109, 184); text-align:
center;"> part
gives a nice border to the whole template. You can fiddle
with the
colors to make it suit your own theme or completely remove
it if you do
not want html in your wiki markup
Save the template.
Go to any of your pages and edit it. In the end of the edit,
add the line
{{Dtil}} (or whatever you have named your template) and save
it.
Hopefully, you will have a footer in your page with links
which will
allow your readers to bookmark your pages on digg or del.icio.us
Hope you find this useful.
Should I add this to the Mediawiki FAQ or Mediawiki hacks
page or is
there something like this already there on it ?
Cheers
--
_.-, raj shekhar
.--' '-._ http://rajshekhar.net
_/`- _ '. http://rajshekhar.net/blog
'----'._`.----. \
` \; WE APOLOGIZE FOR THE INCONVENIENCE
;_\ -- God's Last Message to his Creation
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)Wikimedia.org
http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
--
http://www.dodin.nethttp://dodin.org/galerie_photo_web/expo/index.htmlhttp://lucien.dodin.nethttp://fr.susewiki.org/index.php?title=Gérer_ses_photos
