documentation at oooauthors

Documentation General
#13

Hi Sigrid, :slight_smile:

I wanted to check a few of the chapters, that Ron ported from OOo to
LibO. When I logged in at oooauthors, I couldn't find the folder given
in this link:

If you're planning to do proofreading on documentation, may I just
voice my 2 cents?

Since you're a German speaker who speaks good English but not as a
mother tongue, I'd say that your best contribution to documentation
would be to copy-write - in either English or German - but to leave
proofreading and editing any English stuff to someone of English
mother tongue. That way we'll arrive at the best quality. Anything in
English you proofread will just have to be proofread again
afterwards...

Maybe it would be a more profitable use of your time and skills if you
decided to *write* one of the missing chapters?

What do you think?

David Nelson

#14

IMO the first thing needed for the LibO docs is REVIEWING (to see that
the content is accurate), after which comes editing (which is probably
what everyone erroneously calls "proofreading").

Sigrid would be excellent at REVIEWING; that is, spotting what needs
to be changed from the OOo docs to turn them into LibO docs, since she
is very familiar with OOo. I suspect that is what she has in mind to
do.

Actually, from working with Sigrid over the past 6? longer? years, I
can say that she will do an excellent job regardless of how she
chooses to contribute. :slight_smile: Including, perhaps, writing up some of the
LibO features that are not part of OOo... though that might not
require separate chapters, but rather additional sections in existing
chapters.

--Jean

#15

Hi, :slight_smile:

IMO the first thing needed for the LibO docs is REVIEWING (to see that
the content is accurate), after which comes editing (which is probably
what everyone erroneously calls "proofreading").

Sigrid would be excellent at REVIEWING; that is, spotting what needs
to be changed from the OOo docs to turn them into LibO docs, since she
is very familiar with OOo. I suspect that is what she has in mind to
do.

Actually, from working with Sigrid over the past 6? longer? years, I
can say that she will do an excellent job regardless of how she
chooses to contribute. :slight_smile: Including, perhaps, writing up some of the
LibO features that are not part of OOo... though that might not
require separate chapters, but rather additional sections in existing
chapters.

OK, guys, do what you think. :wink: It's your time, so use it the way you want. :wink:

(David mutters, "Damned cats!")

David Nelson

#16

David Nelson wrote:

OK, guys, do what you think. :wink: It's your time, so use it the way you want. :wink:

(David mutters, "Damned cats!")

Meow! <Flicks tail>

#17

Hi, :slight_smile:

David Nelson wrote:

OK, guys, do what you think. :wink: It's your time, so use it the way you want. :wink:

(David mutters, "Damned cats!")

Meow! <Flicks tail>

I'm smiling with you, Jean. But I do think this: you're not committed
to TDF and the LibreOffice, you're standing in the middle between the
two. Me, I want to see TDF succeed, and I'm willing to devote time and
work to that (and I am doing it right at this time). I'm a little sad
that you're not contributing to that. Just *my* 2 cents. :wink:

David Nelson

#18

Hi David,
I was talking about the screenshots. I did finish loading all that I've done so far to OOoAuthors. Wasn't sure if the wiki was the best place for those, but will put them anywhere you like.

Rrruff. Can the dogs play here too?
Ron

#19

I think the most useful thing I can do is just what I am doing: updating
OOo user guides, which the LibO team can (if they choose) then port to
LibO in whatever form the team decides.

--Jean

#20

Hi Ron, :slight_smile:

I was talking about the screenshots. I did finish loading all that I've done
so far to OOoAuthors. Wasn't sure if the wiki was the best place for those,
but will put them anywhere you like.

Might I suggest that you post the material on your user page on the
wiki, and that I could come along after that and figure out what the
best solution would be?

In any case, on behalf of all the users out there, thanks for all your work. :wink:

David Nelson

#21

Hi,

Sigrid,

Link works for me.

Thanks Andy.

What I find very strange is, that I have manager rights on oooauthors,
I see the review list, but I can't see this folder.

I checked the rights that I had, changed them, logged off and on again
- and still nothing changed. I can't see any content in this folder.

Btw, I also don't see an "English" folder in the left bar when I go to
oooauthors, I only see it, when I add /english to the url manually.

That's so strange.

Sigrid

I have similar rights as Sigrid and facing similar problems. How can I solve these?

Many thanks
Best regards

#22

Leo, I have no idea what is wrong and how to fix it. :frowning:

The latest version of the draft LibO Getting Started guide chapters are
here: http://wiki.documentfoundation.org/Documentation

Ron Failes took all the published chapters and applied the new LibO
template to them. However, as far as I can tell, no other changes have
yet been made, for example changing OpenOffice.org to LibreOffice
(except on the title pages), and the list of contributors to the OOo
chapters does not appear in the LibO files that I checked. Other changes
that were made to the draft chapters have not been made to the latest
ones, either, so whoever works on these will need to do all of that
again. Comparing them with the draft chapters would help with those
updates, but not if you cannot get to the drafts.

The files are very much NOT ready for translation. In fact, IMO they are
not ready to be put on the LibO site, where other people can find and
copy them.

--Jean

#23

The earlier draft files can be found here (scroll to the bottom of the page):
http://wiki.documentfoundation.org/User:Rmfaile

#24

Hi Jean,

The files are very much NOT ready for translation. In fact, IMO they are
not ready to be put on the LibO site, where other people can find and
copy them.

I'm interested in the reason why you think they are not ready for
translation, other than the points you mention in your post - could you
enlighten me a little ?

Alex

#25

Isn't that enough? But perhaps I don't know how clean you guys want your
files before starting translation; perhaps I mis-spoke.

The OOo versions are ready for translation as OOo docs. If translators
want to also do all the work of adapting the files to LibO (cutting out
bits that are not relevant to LibO; adding bits that are relevant but
not in the OOo version; changing the links from OOo links to LibO links;
etc...) then I guess they are ready.

--Jean

#26

Hi Leo,

Hi,

Sigrid,

Link works for me.

Thanks Andy.

What I find very strange is, that I have manager rights on oooauthors,
I see the review list, but I can't see this folder.

I checked the rights that I had, changed them, logged off and on again
- and still nothing changed. I can't see any content in this folder.

Btw, I also don't see an "English" folder in the left bar when I go to
oooauthors, I only see it, when I add /english to the url manually.

That's so strange.

Sigrid

I have similar rights as Sigrid and facing similar problems. How can I solve
these?

sorry, I don't have an idea. I've tried with deleting everything in my
browser cache and also tried different browsers (besides Chromium,
original Chrome, Firefox and Opera) and with no browser can I access
the English folder with the LibO-Documents. The only way I can see the
contents is to use a different computer.

But I agree, that this is not a satisfactory solution.

Sigrid

#27

Isn't that enough? But perhaps I don't know how clean you guys want your
files before starting translation; perhaps I mis-spoke.

No, I just got the impression that there was something more to do than
what you'd mentioned.

The OOo versions are ready for translation as OOo docs. If translators
want to also do all the work of adapting the files to LibO (cutting out
bits that are not relevant to LibO; adding bits that are relevant but
not in the OOo version; changing the links from OOo links to LibO links;
etc...) then I guess they are ready.

Well, I think that's good news :slight_smile: As for the differences, I am going to
be focussing on Base to start with, and there are not, AFAICT any major
differences between OOo and LibO as yet.

Alex

#28

Hi Alex,

Isn't that enough? But perhaps I don't know how clean you guys want your
files before starting translation; perhaps I mis-spoke.

No, I just got the impression that there was something more to do than
what you'd mentioned.

The OOo versions are ready for translation as OOo docs. If translators
want to also do all the work of adapting the files to LibO (cutting out
bits that are not relevant to LibO; adding bits that are relevant but
not in the OOo version; changing the links from OOo links to LibO links;
etc...) then I guess they are ready.

Well, I think that's good news :slight_smile: As for the differences, I am going to
be focussing on Base to start with, and there are not, AFAICT any major
differences between OOo and LibO as yet.

What language are you going to translate to? If you need help or a first reader in case of French, just ping me :slight_smile:

Kind regards
Sophie

#29

I concur. I've downloaded the first file: 0101GS3-IntroducingLibO.odt and have found many instances of OpenOffice.org, as well as OpenOffice.org specific instructions (how to operate from the command line, for example). Moreover, the links throughout the document are all to a site with which we are not affiliated. I'll upload what I've been able to change on my own when through, later today, however even then it will need to be gone over by the drupal team, at least.

#30

Hi Leo, Sigrid, *,

because I has not enough time to read all the emails on the list, I has not
enregistered this thread.

Hi Leo,

> Hi,
>
>>> Sigrid,
>>>
>>> Link works for me.
>>
>> Thanks Andy.
>>
>> What I find very strange is, that I have manager rights on oooauthors,
>> I see the review list, but I can't see this folder.
>>
>> I checked the rights that I had, changed them, logged off and on again
>> - and still nothing changed. I can't see any content in this folder.
>>
>> Btw, I also don't see an "English" folder in the left bar when I go to
>> oooauthors, I only see it, when I add /english to the url manually.
>>
>> That's so strange.
>>
>> Sigrid
>
> I have similar rights as Sigrid and facing similar problems. How can I
> solve these?

sorry, I don't have an idea. I've tried with deleting everything in my
browser cache and also tried different browsers (besides Chromium,
original Chrome, Firefox and Opera) and with no browser can I access
the English folder with the LibO-Documents. The only way I can see the
contents is to use a different computer.

But I agree, that this is not a satisfactory solution.

The issue is here a misconfiguration of the language setting for the whole folder.
The default language inside the Plone CMS of OOoAuthors.org is language neutral. This
is the only setting, which guarantees, that all members can see the directory and
it's content. You can translate the folder with LinguaPlone to another language. This
means that every user with the language setting according to the translation will see
the translated version in that language. The other members (with no available
translation) will see the default folder (with language neutral setting).
You can realise the misconfiguration, if you change your language setting by clicking
on the English flag.

Regards,
Andreas

#31

Hi Jeremy, :slight_smile:

I'll upload what I've been able to change on my own when through, later
today, however even then it will need to be gone over by the drupal team, at
least.

I received your off-list mail with the attached file. Thank you very
much for that. I will take a look at it and post it on the wiki.

I just wanted to point one thing out to everyone as regards the
subject of Drupal. There have been many postings on many of the TDF
mailing lists about Drupal, but - in reality - there has been no
official decision to adopt a Drupal site at the moment, not for
documentation and not for anything else. No official decision could be
taken before The Document Foundation [TDF] has a board of directors,
at which time the board of directors will take any such decision.

As for the handling of documentation by a Drupal site, that would
first depend on a decision being taken to adopt Drupal as a tool for
the docs team. That, in itself, is far from being a foregone
conclusion. Other solutions exist (use the wiki, etc.). For the
moment, there has not been any proper technical evaluation of a Drupal
based workflow, so any discussion about Drupal is currently pure
conjecture.

David Nelson

#32

I just wanted to point one thing out to everyone as regards the
subject of Drupal. There have been many postings on many of the TDF
mailing lists about Drupal, but - in reality - there has been no
official decision to adopt a Drupal site at the moment, not for
documentation and not for anything else. No official decision could be
taken before The Document Foundation [TDF] has a board of directors,
at which time the board of directors will take any such decision.

The steering committee has given the website team a mandate for the
rapid-up temporary site with a Drupal replacement being implemented
within 6 months. (Note that this will not replace the wiki)
It is now up to the website team to develop the tools in Drupal in
order to meet the needs of every part of the community. If this cannot
be done for a given team then we can consider using other tools.

As for the handling of documentation by a Drupal site, that would
first depend on a decision being taken to adopt Drupal as a tool for
the docs team.

I totally agree with allowing the individual teams drive the
development of the tools they want to use, and almost anything is
possible using the Drupal framework.
Can I encourage people to throw up ideas of the tools they want the
website team to build rather than perpetuating the myth that Drupal
document management is fixed. It is flexible and fluid, and as long as
the ideas are well formulated and logical, we can build them in
Drupal.

Michael Wheatland

Impressum (Legal Info) | Datenschutzerklärung (Privacy Policy)   Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.