[libreoffice-documentation] Styles naming and usage in LibO manuals
Hi, (copy to the FR discuss list where it all started) I'm at a loss about the styles names and use in LibO docs (I'm referring here to http://wiki.documentfoundation.org/images/f/f5/0101GS3-IntroducingLibO.odt, but the same goes to others) I'm wondering why the styles used are OOoSomeNewStyle while predefined styles already exist for the same purpose in the software (eg: OOoTextBody vs pre-defined TextBody) I think the current naming scheme is faulty and that this important drawback should be addressed. The problem I see here is interoperability. This pilar of Free Software is very welcome into our office automation tools. This way, our documents can be transferred everywhere and used by anyone, the style name being translated and meaningful to the reader (eg: the paragraph style Heading 1 in English is Titre 1 in French). - Any non-standard expression is a source of misunderstanding. - Any non-standard naming can't be easily translated. The second drawback is much worse. If I want to display documents using my own style sheets, I can configure any pre-defined style to fit my needs or desires and create my own templates (this is basic styles and templates use). This way, when I get a document from anywhere, I can be sure it will look the way *I* want. - Any non-standard naming defeats in-house rules. I'm sure there's some reason why the obscure OOoSomeNewStyle scheme has been adopted but I can't see any explanation that would overrule the two problems above. Also, we must be aware that the documents we produce here are to be used as good practice examples by our audience. Anytime I teach Writer, I emphasize on styles and good practices about them. Having official documents (well, there's the TDF logo somewhere, right?) that don't actually apply such good practices is bad teaching. Can anyone with a long experience explain this naming thingy? Because of the problems listed above, I think we should review the documents styles and adopt the predefined styles wherever they are concerned, additional styles being introduced very sparingly. Best regards, -- Jean-Francois Nifenecker, Bordeaux -- Unsubscribe instructions: E-mail to documentation+h...@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] Styles naming and usage in LibO manuals
Personally, I prefer using the factory style names as much as possible and only create custom style names as the need arises. The OOo prefix in the custom style names was in use before I first used them while editing the Writer user guide, templates, and style guides and such during the OOo version 2.x docs in the spring of 2006--obviously a carryforward from the OOo version 1.x years. I and others continued to employ them to the present and onto the LO docs. Gary On 1/8/2012 4:50 AM, Jean-Francois Nifenecker wrote: Hi, (copy to the FR discuss list where it all started) I'm at a loss about the styles names and use in LibO docs (I'm referring here to http://wiki.documentfoundation.org/images/f/f5/0101GS3-IntroducingLibO.odt, but the same goes to others) I'm wondering why the styles used are OOoSomeNewStyle while predefined styles already exist for the same purpose in the software (eg: OOoTextBody vs pre-defined TextBody) I think the current naming scheme is faulty and that this important drawback should be addressed. The problem I see here is interoperability. This pilar of Free Software is very welcome into our office automation tools. This way, our documents can be transferred everywhere and used by anyone, the style name being translated and meaningful to the reader (eg: the paragraph style Heading 1 in English is Titre 1 in French). - Any non-standard expression is a source of misunderstanding. - Any non-standard naming can't be easily translated. The second drawback is much worse. If I want to display documents using my own style sheets, I can configure any pre-defined style to fit my needs or desires and create my own templates (this is basic styles and templates use). This way, when I get a document from anywhere, I can be sure it will look the way *I* want. - Any non-standard naming defeats in-house rules. I'm sure there's some reason why the obscure OOoSomeNewStyle scheme has been adopted but I can't see any explanation that would overrule the two problems above. Also, we must be aware that the documents we produce here are to be used as good practice examples by our audience. Anytime I teach Writer, I emphasize on styles and good practices about them. Having official documents (well, there's the TDF logo somewhere, right?) that don't actually apply such good practices is bad teaching. Can anyone with a long experience explain this naming thingy? Because of the problems listed above, I think we should review the documents styles and adopt the predefined styles wherever they are concerned, additional styles being introduced very sparingly. Best regards, -- Gary Schnabl Southwest Detroit, two miles NORTH! of Canada--Windsor, that is... Technical Editor forum http://TechnicalEditor.LivernoisYard.com/phpBB3/ -- Unsubscribe instructions: E-mail to documentation+h...@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] Help for Alfresco implementation
Hi David, thank you for welcoming me and I think that this week I could spend some hours working on this Alfresco instance. Cheers, Piergiorgio 2012/1/5 David Nelson li...@traduction.biz: Hi Piergiorgio, I apologise for waiting so long to get back to you. Your involvement in admin'ing and developing the LibreOffice Alfresco platform is most welcome, and thank you very much for the offer. I've been really busy recently. Anyway, welcome on board. In a separate mail, I am going to forward you a mail thread about an outage we're currently suffering with Alfresco. That thread contains all the login info you'd require for admin'ing and working on the server, by the way. I'll keep you updated about the outage. ;-) -- David Nelson On Sat, Nov 26, 2011 at 6:27 PM, Piergiorgio Lucidi piergior...@apache.org wrote: Hi guys, taking a look at the Alfresco wiki [1] I noticed that you need some help customizing Alfresco. I would like to contribute on this task if you want and if you need. I'm an Open Source ECM Specialist and I'm working at Sourcesense. I'm an Open Source contributor, I'm contributing on The Apache Software Foundation (Apache ManifoldCF) and on the JBoss Community (portals). I have 8 years experience on ECM systems (Open Source and not), I have a four years experience in Alfresco. I wrote a book about Alfresco (Alfresco 3 Web Services published by Packt Publishing) and I'm the Certified Alfresco Trainer for Italy, UK and NL. I'm continuing to work for Packt because I also am their Technical Reviewer for ECM and Alfresco books to review books before publishing. I think that I can find a few hours a month to help. Please let me know if you are interested in my involvement in the project. Thank you for your time. Regards, Piergiorgio [1] http://wiki.alfresco.com/wiki/Help_Wanted#LibreOffice_Alfresco_Implementation -- Piergiorgio Lucidi http://www.open4dev.com -- Piergiorgio Lucidi http://www.open4dev.com -- Unsubscribe instructions: E-mail to documentation+h...@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] Alfresco: server down, troubleshooting in progress
I think that before upgrading from 3.4 to 4 we have to try to upgrade a vanilla installation of Alfresco to test the migration patches, and if this procedure will be correctly executed and tested, we can try to upgrade the current repository. I have to test the migration procedure because all the Alfresco partners must only work on the Enterprise version and now the latest version is Alfresco 3.4.x. I can work on this task this week. Could you please create an Alfresco account for me? Could you please give me some hints about ssh access? Thank you. Cheers, Piergiorgio 2012/1/5 David Nelson li...@traduction.biz: Sorry, guys, it looks like the best solution is to roll back to our 3.4 platform of Dec 22, 2011. I'll keep you posted, though... -- David Nelson -- Unsubscribe instructions: E-mail to documentation+h...@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 -- Piergiorgio Lucidi http://www.open4dev.com -- Unsubscribe instructions: E-mail to documentation+h...@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: Report Builder
2012.01.06. 19:04 keltezéssel, drew írta: On Fri, 2012-01-06 at 12:42 -0500, drew wrote: On Fri, 2012-01-06 at 16:50 +0100, Reizinger Zoltán wrote: Hi Dan, I was the community volunteer QA who helped the report builder developer, to remove bugs from the application. You can create static report with report designer only when you use the report wizard. In design view no option to run report as static report. The static report was no question, during times when I participated in report builder development. No issue/bug was opened on it. Regards, Hi Zoltan I think this is a case where the term doesn't carry over from the one tool to the other. In the case of the Report Wizard you can save the results into the ODB wrapper and then when it's opened next you need to have designated whether it will be treated as a template or document. If template the report definition saved in the hidden fields is re-run, in the case of the document (static report) it is simply opened. In the case of the Report Designer an actual report definition, as a unique type, is introduced. So after running a report definition you create the equivalent of the Wizard's static report simply by saving the ODT or ODS file generated. When you execute a save function in the Designer interface you are always saving only the definition back into the ODB wrapper. I hope that helps, //drew Sorry for the double post - but I assume Dan is asking because of his work on the manual, so I wanted to just add another piece of information here. One of the side effects of this change is the following: In the case of the Report Wizard generated document (static report if you will) the report definition (query, grouping, etc) is embedded in the final file, by default. Distribute that file without removing the hidden fields and you distribute that information also. Now this doesn't include anything about the actual data connection used, so you aren't ever going to give up a password or anything like it this way. There is one thing that is not available, in the Wizard' however which is any user supplied variables at run time. What I mean is this. Say our report is based on the following query: Select * from FOOBAR where FOOBAR.DATE1= :startdate and FOOBAR.DATE = :enddate. Now when the report is run the user is prompted to supply date values for the two values. In the report wizard there is no way, from the POV of the report developer, to incorporate the users responses into the actual body of the report. Now in the Report Designer things are different. The designer works with a separate report definition file and uses this to generate the final report document. The document generated will by default have none of the information regarding the query, sorting, etc settings from the report definition, just the data. However what is now available, to the report developer, is the ability to reference the user response from any variable values supplied at run time - the values could then be placed in a report (not page) header for instance. You can put parameters into all places, page/report header/footer. Zoltan At least I think that made it in, I know it was requested and I thought implemented - though I didn't double check that just now. IMO that is a fairly significant difference. //drew 2012.01.06. 15:55 keltezéssel, Dan Lewis írta: The report wizard in both OOo and LO gives a choice of a static or dynamic report. Where is this choice in the Report Builder? I can't find it. Or, has it been decided that a static report no longer serves a purpose? I know that limitations can be placed upon the query or view upon which the report is based. This might take the place of a static report. But would this always be the case? I don't know. Example: a report shows an abnormality. After this is corrected, data is modified in the database. Run the report again, and the abnormality might disappear. Where is the proof that the abnormality every existed? Just a thought. This is going to both lists in case someone from one of them knows the answer. --Dan - To unsubscribe, e-mail: ooo-users-unsubscr...@incubator.apache.org For additional commands, e-mail: ooo-users-h...@incubator.apache.org - To unsubscribe, e-mail: ooo-users-unsubscr...@incubator.apache.org For additional commands, e-mail: ooo-users-h...@incubator.apache.org - To unsubscribe, e-mail: ooo-users-unsubscr...@incubator.apache.org For additional commands, e-mail: ooo-users-h...@incubator.apache.org - To unsubscribe, e-mail: ooo-users-unsubscr...@incubator.apache.org For additional commands, e-mail: ooo-users-h...@incubator.apache.org -- Unsubscribe instructions: E-mail
[libreoffice-documentation] OOo-Kindle Extension LibreOffice
Hi :) This LibreOffice-Kindle Extension might be of interest to people wanting to self-publish books to avoid needing to use a publishing house. It is proprietary and costs quite a lot until you compare it to the costs of alternatives. http://www.kindletemplate.com/ It has not been extensively tested against LibreOffice but has been used with OpenOffice for quite some time. There might be an opportunity for a couple of people to get involved with testing and perhaps upgrading this for LibreOffice. Regards from Tom :) --- On Sun, 8/1/12, Brian Kindle-Expert wrote: From: Brian Kindle-Expert Subject: RE: OOo-Kindle Extension LibreOffice To: Tom Davies tomdavie...@yahoo.co.uk Date: Sunday, 8 January, 2012, 12:31 Hi Tom, Thanks for the heads up. The template works in LibreOffice just the same as OO, in fact, I recommend LO - I will update the info on the site. I'll be starting a series of QA calls on using the template with Libre Office in a few weeks. I'll send you an invite and if you can join us, that would be great! My best,Brian Original Message Subject: OOo-Kindle Extension LibreOffice From: Tom Davies tomdavie...@yahoo.co.uk Date: Sun, January 08, 2012 2:56 am To: Brian Kindle-Expert Hi :) Your website about an OpenOffice-Kindle extension http://www.kindletemplate.com/ doesn't mention LibreOffice. I guess you already know that almost all extensions that work on OpenOffice also work on LibreOffice. Also market-share for LibreOffice is increasing much more rapidly than appears to have been the case for OpenOffice. LibreOffice has a central point for most Extensions although there is nothing to suggest that is the only place where extensions can be hosted! http://extensions.libreoffice.org/ Regards from Tom :) -- Unsubscribe instructions: E-mail to documentation+h...@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
