SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As a new Slackware user, and having to hop from sites to sites to find information, the idea of a centralized/organized/up-to-date documentation site is nice ! Like a Slack's ITIL SPOC ?
If help is needed, I'd be happy to share my time. Dunno for what, though. Maybe feedbacks from a slacknoob point of view.
We would need a Slackware target version (v13.37, v14, ...) for documents. Or a MIN/MAX version number. And also agree with a starting version number. For example, a WPA guide for Slack 3.0 is useless (ok, weird example but you get my point).
Regarding translations: English is IT's "unofficialy adopted"/historical technical language. Man/info pages are all in English. Commands, functions, scripts too. So let's stick with it, no ?
As per the Linus excerpt, and the KISS principle, translations can add monstruous problems (technical and organizational).
And as many of us are not native english speakers, I think the English level will be average enough for everybody to understand, no ?
Regarding translations: English is IT's "unofficialy adopted"/historical technical language. Man/info pages are all in English. Commands, functions, scripts too. So let's stick with it, no ?
As per the Linus excerpt, and the KISS principle, translations can add monstruous problems (technical and organizational).
And as many of us are not native english speakers, I think the English level will be average enough for everybody to understand, no ?
I respectfully disagree.
Let anybody contribute in his or her native language, if so inclined.
If you look at Arch wiki you will see that these guys & gals are able to do that, so why wouldn't we?
Maybe we could learn from them what are the pitfalls and how to deal with it.
Of course it will take time for pages in other languages than English to appear, but as we say in my country "Paris ne s'est pas fait en un jour".
And please note that Slackware itself is usable even by people writing in ideographic languages, using SCIM for instance.
A lot of things haven't changed between releases. Can't think of any really significant ones, but my brain's gone into standby, so...Support for releases before 12.1 has been dropped, but there is still the possibility of people wanting to try the old stuff via virtualisation, like I did a couple of years ago.
As a new Slackware user, and having to hop from sites to sites to find information, the idea of a centralized/organized/up-to-date documentation site is nice ! Like a Slack's ITIL SPOC ?
If help is needed, I'd be happy to share my time. Dunno for what, though. Maybe feedbacks from a slacknoob point of view.
We would need a Slackware target version (v13.37, v14, ...) for documents. Or a MIN/MAX version number. And also agree with a starting version number. For example, a WPA guide for Slack 3.0 is useless (ok, weird example but you get my point).
Regarding translations: English is IT's "unofficialy adopted"/historical technical language. Man/info pages are all in English. Commands, functions, scripts too. So let's stick with it, no ?
As per the Linus excerpt, and the KISS principle, translations can add monstruous problems (technical and organizational).
And as many of us are not native english speakers, I think the English level will be average enough for everybody to understand, no ?
My personal opinion would be that the English version would be a priority and that's what we would focus on. The slackwiki admins and most of its editors would not have to worry about anything else. Later on, any translations would, imho, inevitably have to be down to any willing people who have linguistic skills and time to contribute in a particular language.
Before we worry about translations, let us make sure we have something to translate first.
Doesn't matter, I'd say. Leave it up to the author. As long as it's consistent in the section, things will work out well.
I think we should definitely have translations into other languages. We have many on this board who are able to contribute, some who try, and there must be many others who struggle through. Documentation in one's mother tongue is a wonderful thing. I don't think there's any worry that the English sections won't be filled, so there's hardly a need to emphasize it.
Let anybody contribute in his or her native language, if so inclined
I totally agree with you. I'm french too, and if I imagine myself being a young guy willing to learn Slack BUT who needs to learn English first, I'd be hammered by this HUGE learning curve ...
But having translations requires a lot of staff, and it's very hard to check if translations are correct. For example, there may be enough french speaking people here to check if someone's translation is correct, but what about 'less spoken' languages (by contributors amount I mean) ? So, definitely not saying NO, rather LATER. But I still think this should be a separate project (or a project in the project). By the way, I'd be happy to help translating from EN to FR.
In fact, this is a better version of what I think:
Quote:
Originally Posted by sycamorex
Before we worry about translations, let us make sure we have something to translate first
As per :
Quote:
Originally Posted by brianL
A lot of things haven't changed between releases.
But not "nothing has changed" . From my newbie point of view, when i read CHANGES_AND_HINTS.TXT and see for instance "l/hal-info - obsolete; replaced by various udev components" and "l/hal - obsolete; replaced by upower, udisks, various others", I wonder if reading an article about how to install a USB stick or HDD handled by HAL has much sense if I'm running Slack v14 (please don't stick to the technical correctness here as I barely know what I'm talking about). Just saying, every documentation becomes outdated at some point. And IT's a fast world ...
EDIT (damn im slow):
Quote:
Originally Posted by sycamorex
ic þence ældu Englisc ís betst
Is that Gaelic ?!
Quote:
Originally Posted by brianL
British English or American English?
I'll stick with what I said, American English. But in my case, French English with a slight Alsacian accent
But not "nothing has changed" . From my newbie point of view, when i read CHANGES_AND_HINTS.TXT and see for instance "l/hal-info - obsolete; replaced by various udev components" and "l/hal - obsolete; replaced by upower, udisks, various others", I wonder if reading an article about how to install a USB stick or HDD handled by HAL has much sense if I'm running Slack v14 (please don't stick to the technical correctness here as I barely know what I'm talking about). Just saying, every documentation becomes outdated at some point. And IT's a fast world ...
The ArchWiki is probably one of the finest examples of community-supported documentation that I've ever run across. To create a Slackware wiki project using the ArchWiki as a model would be a most excellent thing, I believe. Slackware's documentation, tips and tricks, how-tos, etc. are pretty much spread out over the Internet on IRC, private blogs, and miscellaneous support forums. To gather all that wonderful community supplied data into one place would be orgasmic to most Slackers like myself. As I said on Alien Pastures blog just a few moments ago, I would most definitely like to be a part of this project.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.