Hi Jos,

(removed my private address)

On Sunday 17 July 2011 Jos Poortvliet wrote:
> 
> I'm shamelessly replying to you sending this to the person whom I think
> of when someone mentions openSUSE translations - Thomas Schraitle. I've
> also CC'ed the opensuse-doc mailinglist (no idea if I'm subscribed or
> what'll happen when I turn out not to be).

Thanks for the fame, but I'm not involved in translations at all. ;)
I think, Karl is the right person to ask (he reads opensuse-doc too) and he 
does all the good things in and with translations. 

 
> So your question is: where is the source of the starters guide to
> openSUSE 11.4 to be found? The original is still to be found on the
> Novell site (soon to be the SUSE.com site).

The source code is not available from the Novell site; it contains only the 
end product (read: HTML and PDF).

The sources can be found in our documentation SVN at BerliOS:
  https://svn.berlios.de/svnroot/repos/opensuse-doc/trunk/documents

The project is hosted at BerliOS:
  http://developer.berlios.de/projects/opensuse-doc/

To create HTML or PDF, you need daps (Document Authoring and Publishing 
Suite), the successor of susedoc. You can install it from OBS, repo 
Documentation:Tools.

 
> [...]
> and I think you are looking for this:
> http://en.opensuse.org/openSUSE:Documentation_Contribute#SVN_Structure
> However, I might be wrong (it's been noted to happen) and in that case,
> I'm sure Thomas or some other openSUSE documentation Wichtl (?) will set
> me straight.

The structure is still correct.

Hope I could clarify some questions. If you still have some questions, just 
ask. :)


-- 
Gruß/Regards,
    Thomas Schraitle

----------------------------------------------------------------------
SUSE LINUX Products GmbH   (o<   Tel:   +49-(0)911-740 53 131
Maxfeldstrasse 5           /\\   Documentation Specialist
90409 Nuernberg, Germany  _\_v   http://www.suse.com
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 
--
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to