Re: [libreoffice-documentation] Getting Started Guide for LO v5.0
Hello Jean I just uploaded the LO5.1 GS Preface in the 5.1 LO Draft folder. On reading it, I noticed that under the FAQ section, the 1st question still refers to LibreOffice 4.4. Regards Olivier Em 04/03/2016 00:02, Jean Weber escreveu: > I have now compiled and uploaded the ODT and PDF of the full book > Getting Started Guide for LO v5.0, to both ODFAuthors and the > Publications wiki. I'll soon add it to the get-help/docs page on the > website. > > I'm working on the print version and should have that published within > a day or so and will add links to it from wiki and get-help/docs. > > As soon as I've finished all that, I expect someone to find a major > error or several. That's the way it usually works! > > Cheers, Jean > -- Olivier Hallot Comunidade LibreOffice http://ask.libreoffice.org/pt-br -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/documentation/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-documentation] Re: [libreoffice-l10n] Request to save in odfauthors website files used for examples in guides
Il 2 marzo 2016 21:23:03 CET, "elcico2001 एल्चिको" ha scritto: >Hello all, >May I ask all people working in the documentation group to save, for >later use, example files created while writing libo guides? >In this way localizators won't have to completely recreate them when >localizing images. >I think the best place to save files is the odfauthors website (where >there is already 1 file saved - for the calc guide). >Thank you very much! >Namastè all :) Hi I agree and support this idea :) Ciao! Valter -- Open Source is better! Inviato dal mio dispositivo Android con K-9 Mail. -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/documentation/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-documentation] Tracking documentation content gap
Hi Sophie Em 16/03/2016 10:41, Sophie escreveu: > Hi Olivier, > Le 15/03/2016 21:08, Olivier Hallot a écrit : >> Hi >> >> I visited several documentation pages in the wiki and I have a question. >> >> Assuming I am a skilled LO writer user, if I have to start producing >> content, where do I look to start? > > This is not clear to me if you are speaking about contributing > documentation, or producing own content using advanced functions It is the missing contents. The job in documenting is twofold: 1) update existing books with the changes in the applications, and 2) write about the new features. It is slightly diferent. Do you all agree? > > What are the missing contents in the >> guides vis-a-vis of the developments of the latest LO versions? > > As Martin said, mostly updates on the per module guides >> >> Please let me know if there is a wiki page for that purpose because the >> one I saw is refers to easy-hacks and is outdated, poorly highlighted. > > The wiki needs to be structured since a long time :). I think the "Help > produce documentation" part should be divided in User guides/Wiki > content/Help content/Videos/etc. and guide contributions from dedicated > pages Agree. It is quite time consuming to get the full picture. >> >> If help is welcome here, does it make sense to the documentation >> comunity to have a metabug in bugzilla to track the missing >> documentation contents? [1]. An update of the easy hack wikipage shall >> suffice? Or a specific wiki page for that purpose is prefered? > > I'm not sure people here would be at ease with BugZilla which is far > from being user friendly, I find Redmine easier than BZ and the wiki > easier than both. I am ok with a wiki page. As I answered Martin, I'll produce a wiki page that can let us track features x versions for the 5.x family and beyond. > What does others think? > > Cheers > Sophie > -- Olivier Hallot Comunidade LibreOffice http://ask.libreoffice.org/pt-br -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/documentation/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-documentation] Tracking documentation content gap
On Thu, Mar 17, 2016 at 1:41 PM, Olivier Hallot wrote: > Hello Martin > Thanks for aswering. > > Em 16/03/2016 07:58, Martin Srebotnjak escreveu: >> Hi, >> >> if you are asking about the guides, the guides were updated to the latest >> release versions as seen on the publications wiki, i.e. Getting Started >> Guide was recently released for 5.0. It needs updating to 5.1. All the >> work-in-progress can be tracked on the odfauthors.org site. Dedicated >> module guides were mostly released for the 4.x series so they might not be >> so much up-to-date. > > I'm glad to get your summary. > >> >> IMHO GS is the most important guide as it is the entry level guide and it >> is mostly required by any public administration or large deployment where >> LO wants to be present - it is the proof that documentation exists and is >> up-to-date. And of all the guides this one is the one that l10n teams do >> and probably should devote most resources to localize (if they do not have >> resources to localize all). > > Indeed. There seems to be a concensus that the english GS is the base > for translations. > >> >> The GS guides do not cover all aspects of LO, and they are not intended to. > > Agree. > > >> For that there are special guides for modules. So the GS guide is updated >> and checked for errors with every update and I believe that Jean and her >> team did a good work (as much as I could see from localizing the updated >> strings), so I guess there are no known errors nor are there really missing >> topics in GS50. It just needs to be updated to the latest release(s). > > And thus my question: what are the topics introduced in the software > that needs documentation writing? If there is a list somewhere, then > fine, and I'd like to see it. If there is'nt, then ok I'll try to write > one. > >> >> With 5.1 (and upcoming 5.2) there was/is a lot of menu restructuring going >> on in LO so the updaters will have a lot of work with updating the menu >> paths and with updating the screenshots (where menus are present), so the >> 5.1 update of GS guide will not be so much in adding content but in getting >> it true to all the changes. And with all those menu changes LO really does >> not have a truly up-to-date general or module-specific guide (LibreOffice >> Base Handbook might be the only exemption, because there were no radical >> changes in Base). > > Indeed > >> >> So I guess it would help to set priorities and the teams that will work on >> those priorities. And we, the l10n teams will have something to localize >> again ... > > There is a wikipage that shows the tasklist for the Guides[1]. > > I see that the GS guides are quite updated and have been carried well > given the resource limitations. > > The modules guides concerns me because they are lagging behind > LibreOffice development. > > For these modules guides I plan to write a wiki page with the topics x > version that are missing. That way we will have a roadmap on producing > contents, that will come along the update of the existing guides. > > If there are objections to this initiative, please let me know (It may > be a very large job to carry). > > [1] > https://wiki.documentfoundation.org/Documentation/Development/UserGuideTasks >> I have found that the most time consuming thing is to check what has changed in LO and therefore needs updating in the books, even more than what is missing because it is new in LO. I have to look at the program and compare it to the book, testing the procedures as I go, in order to find many topics that need updating. Sometimes the images need to be changed, even if the text is still correct. With new topics, one must decide where they should go: in which chapter and where in that chapter. Sometimes this is easy to decide, but many times it is not. Writing about new features often requires changing text in other places as well (for example, the change to the sidebar has meant a lot of rewriting on where to find tools in topics about using those tools). So a list of topics is a good and important thing to do, but will probably not be enough unless it is very detailed. But I'm sure you know all this. --Jean -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/documentation/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-documentation] Tracking documentation content gap
Hello Martin Thanks for aswering. Em 16/03/2016 07:58, Martin Srebotnjak escreveu: > Hi, > > if you are asking about the guides, the guides were updated to the latest > release versions as seen on the publications wiki, i.e. Getting Started > Guide was recently released for 5.0. It needs updating to 5.1. All the > work-in-progress can be tracked on the odfauthors.org site. Dedicated > module guides were mostly released for the 4.x series so they might not be > so much up-to-date. I'm glad to get your summary. > > IMHO GS is the most important guide as it is the entry level guide and it > is mostly required by any public administration or large deployment where > LO wants to be present - it is the proof that documentation exists and is > up-to-date. And of all the guides this one is the one that l10n teams do > and probably should devote most resources to localize (if they do not have > resources to localize all). Indeed. There seems to be a concensus that the english GS is the base for translations. > > The GS guides do not cover all aspects of LO, and they are not intended to. Agree. > For that there are special guides for modules. So the GS guide is updated > and checked for errors with every update and I believe that Jean and her > team did a good work (as much as I could see from localizing the updated > strings), so I guess there are no known errors nor are there really missing > topics in GS50. It just needs to be updated to the latest release(s). And thus my question: what are the topics introduced in the software that needs documentation writing? If there is a list somewhere, then fine, and I'd like to see it. If there is'nt, then ok I'll try to write one. > > With 5.1 (and upcoming 5.2) there was/is a lot of menu restructuring going > on in LO so the updaters will have a lot of work with updating the menu > paths and with updating the screenshots (where menus are present), so the > 5.1 update of GS guide will not be so much in adding content but in getting > it true to all the changes. And with all those menu changes LO really does > not have a truly up-to-date general or module-specific guide (LibreOffice > Base Handbook might be the only exemption, because there were no radical > changes in Base). Indeed > > So I guess it would help to set priorities and the teams that will work on > those priorities. And we, the l10n teams will have something to localize > again ... There is a wikipage that shows the tasklist for the Guides[1]. I see that the GS guides are quite updated and have been carried well given the resource limitations. The modules guides concerns me because they are lagging behind LibreOffice development. For these modules guides I plan to write a wiki page with the topics x version that are missing. That way we will have a roadmap on producing contents, that will come along the update of the existing guides. If there are objections to this initiative, please let me know (It may be a very large job to carry). [1] https://wiki.documentfoundation.org/Documentation/Development/UserGuideTasks > > Lp, m. > > 2016-03-15 21:08 GMT+01:00 Olivier Hallot : > >> Hi >> >> I visited several documentation pages in the wiki and I have a question. >> >> Assuming I am a skilled LO writer user, if I have to start producing >> content, where do I look to start? What are the missing contents in the >> guides vis-a-vis of the developments of the latest LO versions? >> >> Please let me know if there is a wiki page for that purpose because the >> one I saw is refers to easy-hacks and is outdated, poorly highlighted. >> >> If help is welcome here, does it make sense to the documentation >> comunity to have a metabug in bugzilla to track the missing >> documentation contents? [1]. An update of the easy hack wikipage shall >> suffice? Or a specific wiki page for that purpose is prefered? >> >> Please advise. >> >> [1] metabug for helpcontent missing/outdated pages: >> https://goo.gl/ixqz7N >> >> -- >> Olivier Hallot >> Comunidade LibreOffice >> http://ask.libreoffice.org/pt-br >> >> -- >> To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org >> Problems? >> http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ >> Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette >> List archive: http://listarchives.libreoffice.org/global/documentation/ >> All messages sent to this list will be publicly archived and cannot be >> deleted >> >> > -- Olivier Hallot Comunidade LibreOffice http://ask.libreoffice.org/pt-br -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/documentation/ All messages sent to this list will be publicly archived and cannot be deleted
