Re: [Mwiki] New accounts by invitation only?
Hi Jan, On 21.11.2012 20:24, jan iversen wrote: having looked at the mediawiki pages, especially the amount of updates, and make a trial installation my my private server, I know I can cope with the maintenance problems (but NOT with spam attacks, that requires more than just one person). If the community agrees to it, using the lazy consensus, I volunteer to make maintenance of the mwiki (wiki.openoffice.org). Thank you very much! +1 from me If nobody object I will very fast do the proposed mysql changes: - remove accounts with no contributions during the last year. - removing all new users within the last 2 weeks. and prepare an update to the newest version, (and as Alexandro suggest have a test server) which first run it on my own ubuntu, before going live. I agree, except that I suggest to remove only accounts that never contributed anything. There are many pages from the pre-AOO times with very interesting content that were created or updated by people lost AOO out of their focus in the meantime. Their contributions are valuable though and should not be forgotten. Maybe the page histories would suffer by removing such accounts completely. [...] I have one question though, why do we have cwiki and wikiI might be the only one, but I get confused where to find which information, so maybe we should decide to have all information in just one wiki ?? If I remember correctly there was an issue with the license of our mediawiki, such that the existing content could not simply be relicensed to ALv2 Herbert
Re: [Mwiki] New accounts by invitation only?
See below please. On 22 November 2012 09:27, Herbert Duerr h...@apache.org wrote: Hi Jan, On 21.11.2012 20:24, jan iversen wrote: having looked at the mediawiki pages, especially the amount of updates, and make a trial installation my my private server, I know I can cope with the maintenance problems (but NOT with spam attacks, that requires more than just one person). If the community agrees to it, using the lazy consensus, I volunteer to make maintenance of the mwiki (wiki.openoffice.org). Thank you very much! +1 from me If nobody object I will very fast do the proposed mysql changes: - remove accounts with no contributions during the last year. - removing all new users within the last 2 weeks. and prepare an update to the newest version, (and as Alexandro suggest have a test server) which first run it on my own ubuntu, before going live. I agree, except that I suggest to remove only accounts that never contributed anything. There are many pages from the pre-AOO times with very interesting content that were created or updated by people lost AOO out of their focus in the meantime. Their contributions are valuable though and should not be forgotten. I agree, the intention is to remove the account, not their contribution. I am not totally sure, but my idea is to move them a account called archive or something. Maybe the page histories would suffer by removing such accounts completely. [...] I have one question though, why do we have cwiki and wikiI might be the only one, but I get confused where to find which information, so maybe we should decide to have all information in just one wiki ?? If I remember correctly there was an issue with the license of our mediawiki, such that the existing content could not simply be relicensed to ALv2 Herbert
Re: [Mwiki] New accounts by invitation only?
On 11/22/2012 03:27, Herbert Duerr wrote: Hi Jan, On 21.11.2012 20:24, jan iversen wrote: having looked at the mediawiki pages, especially the amount of updates, and make a trial installation my my private server, I know I can cope with the maintenance problems (but NOT with spam attacks, that requires more than just one person). If the community agrees to it, using the lazy consensus, I volunteer to make maintenance of the mwiki (wiki.openoffice.org). Thank you very much! +1 from me If nobody object I will very fast do the proposed mysql changes: - remove accounts with no contributions during the last year. - removing all new users within the last 2 weeks. and prepare an update to the newest version, (and as Alexandro suggest have a test server) which first run it on my own ubuntu, before going live. I agree, except that I suggest to remove only accounts that never contributed anything. There are many pages from the pre-AOO times with very interesting content that were created or updated by people lost AOO out of their focus in the meantime. Their contributions are valuable though and should not be forgotten. Maybe the page histories would suffer by removing such accounts completely. [...] I have one question though, why do we have cwiki and wikiI might be the only one, but I get confused where to find which information, so maybe we should decide to have all information in just one wiki ?? If I remember correctly there was an issue with the license of our mediawiki, such that the existing content could not simply be relicensed to ALv2 Herbert Hi, all, There may be a little confusion on the current state of the wiki. It is very good: thanks to the really super work by a really super crew of volunteers, the spam is all deleted; the average life-span of new spam is about half an hour. But we can't keep that up forever. What needs SQL-level deleting is: * empty new accounts (never any activity) * blocked accounts with only deleted contributions (the deleted contribs, spam, should go, too) The removal of this trash shouldn't cause problems (fingers crossed). With the wiki set to invitation only new accounts, we should have time for some longer-range planning. /tj/
Re: [RELEASE] AOO.next = AOO 4.0
On 11/21/12 10:14 PM, Marcus (OOo) wrote: Am 11/21/2012 09:41 PM, schrieb jan iversen: On 21 November 2012 21:30, Andrea Pescettipesce...@apache.org wrote: Jürgen Schmidt wrote: I got the impression that the majority would support a 4.0 version as our next release. So do I. Besides the next major release we should also continue the discussion on further language packs based on 3.4.1 to make the latest translations available as soon as possible. One way to make these language packs available would be to integrate the new translations on the AOO34 branch, build the language packs and a new source release based on this revision. The effort should be minimal Since we have no critical bugs in 3.4.1, I would keep using the 3.4.x series until 4.0 is available. If a security issue emerges that suggests we should make a new release, we will fix it and release 3.4.2; otherwise, I would just keep adding new languages to 3.4.1 and make a couple of 4.0-beta releases, to get better exposure and QA, rather than a 3.5 release. But the 3.4.x series must have some predictable schedule or this won't work. For example, I would propose the following: - We announce on ooo-l10n that 2 December is the first deadline for integration of new languages in 3.4.1 December 2 is very close, when I think of the work in progress on a number of languages, I would suggest end of the year. indeed very close and I will be offline for some further days next week. I count at least 3 languages Danish, Polish, Scots Gaelic. And when we increase the deadline until the end of the year we potentially get even more. - We integrate and build available new languages in the week after it (and we already have two, Danish and Polish) - Native-language teams do some QA - We approve/publish the new builds and the new source release (a 3.4.1 respin, rather than a 3.4.2, since this would confuse users) Would it not be more confusing to change the 3.4.1 distribution files ? I would warmly suggest only to release language packs, since they are separate and do NOT change the existing distribution. If I have understood it correct, only new full install and langpacks files will be distributed - or maybe only langpack files. both would be possible, I ma flexible here. For using the same download mechanism and no further special handling it would be helpful to have the same files as for all other langs. I don't think that it's needed to replace files except for the source files. Exactly, we would release the new languages only on base of 3.4.1 and a new src release. When we do a further 3.4.2 release we can build the new languages in the same way as the others. Juergen
Re: [RELEASE] AOO.next = AOO 4.0
On 11/21/12 5:33 PM, Keith N. McKenna wrote: Rob Weir wrote: On Wed, Nov 21, 2012 at 11:04 AM, Keith N. McKenna keith.mcke...@comcast.net wrote: Regina Henschel wrote: Hi Jürgen, Jürgen Schmidt schrieb: Hi, first of all I would like to volunteer again as release manager for our next release if it's ok for our community. +1 +1 on that from me also Second I would like to define with you what our next release will be. After various discussion and activities on the mailing list and also at the ApacheCon, I got the impression that the majority would support a 4.0 version as our next release. I'm not in favor of an version 4.0 as next release. The changes have listed below would justify a version 4.0. But I doubt, that they are possible in a time frame, I see for the next release. I am with Regina on this one. I do not see a Jan or Feb time frame as feasible for the design and implementation of a new and still a comfortable bit of padding to deal with the inevitable gremlins that will sneak out of the woodwork to assure the kind of quality release that is expected of OpenOffice and that we expect of ourselves. Uh, Juergen never suggested January or Feburary as a time frame for 4.0. So I don't see how one can dismiss a 4.0 proposal as being unfeasible based on dates that he never suggested. Maybe we should ask Juergen what timeframe he had in mind for 4.0? Of course, it might be possible to do both, provided we have volunteers willing to own testing and release management for 3.5. -Rob As I re-read the post you are correct Rob and I apologize to Juergen for reading to much between the lines. What timeframe were you considering for a 4.0 release Juergan? Well I had indeed not February in mind but when we targeting on end of March or April we will have more time. Maybe we can take first a look on what others have in mind to put in the next release. Juergen
Re: did the Decision making and Infrastructure modules
The modules are written very clearly, although they're quite the read in volume. I don't mind whatsoever, but I think it's a good test to get a feel of how committed a volunteer is. If one applied for volunteership in the spur of the moment, being asked to read all these orientation modules can be a quality threshold of its own. (I can see why you would intentionally want to make it so) If at any point the threshold appears to be too high for newcomers, I think creating videos of their content could be a nice in-between-solution. For now I think they're great. On Thu, Nov 22, 2012 at 1:34 AM, Kay Schenk kay.sch...@gmail.com wrote: On Wed, Nov 21, 2012 at 2:53 PM, Georges Bolssens marvel...@gmail.com wrote: modules asked me to notify you of this fact, so here it is... George -- Thanks for letting us know! These orientation modules are relatively new and it's great you're using them. Please give additional feedback and/or join mailing lists if you feel so inclined. -- MzK “How wrong is it for a woman to expect the man to build the world she wants, rather than to create it herself?” -- Anais Nin
Fwd: [Mwiki] New accounts by invitation only?
-- Forwarded message -- From: jan iversen j...@apache.org Date: 22 November 2012 13:53 Subject: Re: [Mwiki] New accounts by invitation only? To: Daniel Shahaf d...@daniel.shahaf.name I will look at the fail2ban, thanks for the advice. Sorry I misunderstood the SQL removal, I will do exactly as stated (but make a backup first, and try it on my own copy second). You all did a major job, so thank you for getting Wiki back in relatively normal state, I expect to do my part tonight (I still miss to have a certificate activated, and the mysql root password). I will keep this informed of each step I do, before I do it !!
Re: Could anybody who has MS word 97 help to verify bug 35763?
Hi, On 22.11.2012 03:25, lou ql wrote: https://issues.apache.org/ooo/show_bug.cgi?id=35763 It's about the import/export of underling color, I have verified with MS word 2003, but I don't have MS word 97, could anybody help with this? I looked for Microsoft Word 97 at my MSDN subscription. It contains - Microsoft Office 95 - Microsoft Office XP - Microsoft Office 2003 - Microsoft Office 2007 - Microsoft Office 2010 - Microsoft Office 2013 no Microsoft Word 97 or Microsoft Word 2000. I am sorry, I can not help here. May be we should close this issue as FIXED. If somebody with Microsoft Word 97 is available, we can reopen it in case it is not fixed for this version. Best regards, Oliver.
Re: Look at the pretty branches
Am Donnerstag, 15. November 2012 um 22:20 schrieb jan iversen: On 15 November 2012 22:16, Rob Weir robw...@apache.org wrote: On Thu, Nov 15, 2012 at 4:00 PM, jan iversen jancasacon...@gmail.com wrote: +1 to move. But please help me out with a simple question, if I delete a file/directory in SVN, I assume it is only deleted from that version, so if I do a checkout of an old version it is included ?? If you check out a tree you get the contents of that tree at that specific revision. By default you get the most-recent revision, the head. But you can specify a specific earlier revision as needed. This will also resurrect deleted files that existed in that revision. There are some administrative things an admin could do with svnadmin dump and svndumpfilter to truly expunge a file, for legal or other extreme reasons. But this is very rare. If I am correct, why do we keep these things in trunk ? Not so much that anyone decided to keep it, but that no one decided to clean it up. 2nd Law of Thermodynamics, etc. Not I know why I never passed that exam as engineerI think you once wrote to me JFDI, it is quite confusing when you try to get into the code, and there seems to be more examples like binfilter. binfilter is on the way to become removed ;-) Juergen Regards, -Rob rgds jan I. On 15 November 2012 21:57, Rob Weir robw...@apache.org wrote: On Thu, Nov 15, 2012 at 3:09 PM, jan iversen jancasacon...@gmail.com wrote: Apart from the branches it seems we have a directory called trunk-orig, that only seems to contain 3 files, are they important ?? +1 to remove branches when they are integrated, it gives a lot better overview. These were some scripts we used during the original import of the OpenOffice.org codebase. Not needed anymore, but if we want them for future reference they might be better under /devtools, maybe directly into /devtools/hg2svn (Was mainly concerned with migration from Mercurial to SVN). If there are no objections I'll do such a move. -Rob Jan. On 15 November 2012 13:19, Rob Weir robw...@apache.org wrote: On Wed, Nov 14, 2012 at 7:03 PM, Andrew Rist andrew.r...@oracle.com wrote: On 11/14/2012 3:10 PM, Rob Weir wrote: I see that our project is growing new branches. Would it make sense to start documenting these on a wiki page, so it is clear what each one is, and who is maintaining it? Current branches are: AOO34/ --- Our 3.4.x branch, would be used if we ever need a 3.4.2 alg/ -- This is Armin's long-term graphics rendering improvement work, maybe integrated for AOO 4.1 gbuild/ -- This looks new, from Andrew. Sounds build-related. But what is it? And what is the plan for getting it integrated? Is this planned AOO 4.0? This is a continuation of this: http://mail-archives.apache.org/mod_mbox/incubator-ooo-dev/201209.mbox/%3c505a1dc4.5030...@oracle.com%3E integration of a set of CWSes: ause131 ause130 writerfilter10 gnumake4 sd2gbuild And integration? Is this targeted for AOO 4.0? If so it would be good to get it reflected in this table: https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.0+Release+Planning That helps with the QA planning. The more we know about what is going into 4.0, the more we can start thinking about how we will test it, maybe even start writing the test cases for new features, if the design is clear enough now. Thanks! -Rob The initial branch for doing this work was deleted and this new branch created. With the original branch, I had applied all of the patches en masse, followed by one massive check-in. We'll just say that this was sub-optimal. After discussions at ApacheConEU - it was decided the best course was to start from scratch, that way we don't have to merge up to the latest trunk. I'm in the process now of applying and committing all the patches, followed by changing all the headers in newly created files. fun A. writer001/ -- Ditto. What is it and what is the plan for getting it integrated? Thanks!
Re: [Question] generated source files with languages (l10n process) overwriting original files.
Ok, I just saw 2 files on my ubuntu, that was overwritten, so I thought it was general, but that may have other reasonsI will do some more research. Jan. Ps. No problem with the mail, better late than never :-) On 22 November 2012 15:38, Juergen Schmidt jogischm...@gmail.com wrote: Am Mittwoch, 14. November 2012 um 21:47 schrieb jan iversen: While programming the l10n translation, I have stumbled across something which I do not know is a real or theoretical problem. I need an opinion from people with more experience. Description of the current situation: When you run configure with e.g. --with-lang=da, all languages Are inserted in the source files alongside with the original en-US text. This works without problems BUT, if the developer forget to do a checkout (thereby removing the extra languages) but does a commit, then SVN will have all languages in the file. After the commit a snapshot (or development) build will contain all languauges for that file. Note: If a translation changes, it will be replaced in the file with the next build, so it will work. However: - developer/snapshot contains an unwanted language part - it is not clean that all language are in this file, as well as in the sdf file (original), and can lead to confusion, where what is maintained. What I easily could do, was NOT to overwrite the file, but place a new file (same content but with all languages added) in the platform/misc directory, therefore the original would be left untouched. This requires of course some makefile changes (the new l10n process requires anyhow changes), which I will do (in a sub-branch) when the system is ready. Question: Is it a problem that the original is overwritten, and it would be better to write a new file (in misc) ? or Am I thinking about a theoretical problem, that is no real world problem ? First of all sorry for the late response, I am still haven't read all mails after my vacation. I am not sure if I understand you correct but normally no originals are overwritten during the build. Files get merged in the local output directory and later used from there. Juergen Just to be sure, the effort of doing one or the other are the same, so that is not an argument (at least for me), we should do what is correct. Jan I.
Re: Could anybody who has MS word 97 help to verify bug 35763?
Hi, On 22.11.2012 14:55, Rob Weir wrote: On Thu, Nov 22, 2012 at 8:23 AM, Oliver-Rainer Wittmann orwittm...@googlemail.com wrote: Hi, On 22.11.2012 03:25, lou ql wrote: https://issues.apache.org/ooo/show_bug.cgi?id=35763 It's about the import/export of underling color, I have verified with MS word 2003, but I don't have MS word 97, could anybody help with this? I looked for Microsoft Word 97 at my MSDN subscription. It contains - Microsoft Office 95 - Microsoft Office XP - Microsoft Office 2003 - Microsoft Office 2007 - Microsoft Office 2010 - Microsoft Office 2013 no Microsoft Word 97 or Microsoft Word 2000. I am sorry, I can not help here. May be we should close this issue as FIXED. If somebody with Microsoft Word 97 is available, we can reopen it in case it is not fixed for this version. I have Word 97. You can assign it to me. Now, it is yours. Best regards, Oliver.
Re: [RELEASE] AOO.next = AOO 4.0
On Nov 22, 2012, at 3:50 AM, Jürgen Schmidt wrote: On 11/21/12 10:14 PM, Marcus (OOo) wrote: Am 11/21/2012 09:41 PM, schrieb jan iversen: On 21 November 2012 21:30, Andrea Pescettipesce...@apache.org wrote: Jürgen Schmidt wrote: I got the impression that the majority would support a 4.0 version as our next release. So do I. Besides the next major release we should also continue the discussion on further language packs based on 3.4.1 to make the latest translations available as soon as possible. One way to make these language packs available would be to integrate the new translations on the AOO34 branch, build the language packs and a new source release based on this revision. The effort should be minimal Since we have no critical bugs in 3.4.1, I would keep using the 3.4.x series until 4.0 is available. If a security issue emerges that suggests we should make a new release, we will fix it and release 3.4.2; otherwise, I would just keep adding new languages to 3.4.1 and make a couple of 4.0-beta releases, to get better exposure and QA, rather than a 3.5 release. But the 3.4.x series must have some predictable schedule or this won't work. For example, I would propose the following: - We announce on ooo-l10n that 2 December is the first deadline for integration of new languages in 3.4.1 December 2 is very close, when I think of the work in progress on a number of languages, I would suggest end of the year. indeed very close and I will be offline for some further days next week. I count at least 3 languages Danish, Polish, Scots Gaelic. And when we increase the deadline until the end of the year we potentially get even more. - We integrate and build available new languages in the week after it (and we already have two, Danish and Polish) - Native-language teams do some QA - We approve/publish the new builds and the new source release (a 3.4.1 respin, rather than a 3.4.2, since this would confuse users) Would it not be more confusing to change the 3.4.1 distribution files ? I would warmly suggest only to release language packs, since they are separate and do NOT change the existing distribution. If I have understood it correct, only new full install and langpacks files will be distributed - or maybe only langpack files. both would be possible, I ma flexible here. For using the same download mechanism and no further special handling it would be helpful to have the same files as for all other langs. I don't think that it's needed to replace files except for the source files. Exactly, we would release the new languages only on base of 3.4.1 and a new src release. When we do a further 3.4.2 release we can build the new languages in the same way as the others. I think that we will need a new source release - we could call the source release 3.4.1b. It would give us good practice at voting on a release based on simple IP scans with RAT and svn diff to prove that the only changes are language files. We trust, but we must verify. I don't have any strong opinions regarding whether we hurry for a 3.5 or develop a feature rich and well tested 4.0. Once we reach consensus on this issue we should have Marketing publish the plan so the user base will know what to expect with an estimated timeline - emphasis on estimated. Regards, Dave Juergen
Re: desktop publishing
Juergen, Maybe 1 machine has a MS office package for the unsalvable problems the 99 others have Windows with LO ,OO, Thunderbird, Inkscape, Gimp, Image Magick and a free Adobe PDF reader We can read and write MS text and spreadsheets, in the editing world PDF is the exchange format by exelence. (For that reason PDF must been a graphic format in LO and LO :-) Maybe you comes to Fosdem in Brussels, we would be happy to invite you to show on the work floor how is works here Greetz Fernand Hi Fernand, I would love to read a more detailed public success story about your experience and work with writer. It sounds very interesting especially when you stay in one world, means no heavy exchange of MS formats. Thanks for sharing Juergen Am Donnerstag, 15. November 2012 um 09:34 schrieb Fernand Vanrie: Alexandro , On Tue, Nov 13, 2012 at 11:24 PM, Phillip Zadro ricaza1...@hotmail.com.auwrote: hi Is there any likelihood that OpenOffice will one day include a desktop publisher? There is only one thing that is stopping me from migrating completely from Microsoft Office to either OpenOffice or LibreOffice and it is their lack of a Desktop Publisher comparable with MS Publisher. I have used Publisher for over 15 years and love its practicality, particularly with paginating of booklets. Even a separate program like Serif PagePlus cannot save in MS format either, so I am obliged to stay with MS Office. Pity.. Thanks Phil Draw is a perfect Desktop publisher, is so perfect is compatible with other We uses exclusifly Writer (+ lot of basic macro's) to make over 8.000 full color magazine pages par year. This pages are all i2 languages versions, with cutouts (we uses Edit Contour) transparancies etc...) Our Editors places lowres images embedded in there documents, a final macro checks the resolution quality and changes the lowres with the highres (stored on a server) just before exporting to PDF Sinds there is SVG, we no longer use EPS and Adobe to make our PDF's. PostScript is dead anyhow (lack of transparency) the LO/OO- PDF export is with use off a Lanczos filter nearly perfect. We only needs a payed Color Server to transfer our RGB PDF's to CMYK Our magazines are printed by different print houses (15.000-3.000 exp.) on high quality paper, there are no complaints from our printers and the readers can not sea the difference between our Magazines an thus maded by payed DTP applications Just a pitty thats SVG is still exported as bitmap (sould been repaired in 3.7) and PDF is still not a accepted as a graphic format like we can use (Tiff, jpg, etc...) Greetz Fernand desktop publishers like Scribus and is based on a frame based paradigm. There are some features that would be desirable but is pretty easy to complete basic and medium tasks like Flyers, Booklets and all it has layers which keeps design separated from content. And have multiple layouts and use of vectorial forms. With improved use of SVG Draw is also gaining strenght in the area of design compatibility and would be improving as more features are considered.
Re: desktop publishing
Hi Phil, It is not completely impossible that an extension could be added to AOO to read and write Publisher files. It just takes one or two Java programmers with the time and interest. See [1] for where the effort could start. On Nov 22, 2012, at 8:36 AM, Fernand Vanrie wrote: Juergen, Maybe 1 machine has a MS office package for the unsalvable problems the 99 others have Windows with LO ,OO, Thunderbird, Inkscape, Gimp, Image Magick and a free Adobe PDF reader We can read and write MS text and spreadsheets, in the editing world PDF is the exchange format by exelence. (For that reason PDF must been a graphic format in LO and LO :-) It would great if PDF could be imported into any of Presenter, Writer and Draw. Perhaps this can be a goal of the new Drawing work. BTW - Postscript lives inside the PDF file format all of the drawing primitives are very close to postscript and operate the same way. SVG is also a descendent of Postscript. (as Postscript is a descendent of Xerox Interpress plus III) But I'm biased and have built a publishing chain based on applications producing postscript pages with special comments, shell scripts to collate into postscript documents, conversion to PDF w/ghostscript or editable PPTX using Java and Apache POI. We've also done PDF into editable shapes and text in PPTX using Apache PDFBox and Apache POI. Should we make the effort to go to ODF we will likely be using ODFToolkit. To close the loop if you want to process Publisher files and help with understanding the files format Apache POI is a good place. [1] Regards, Dave [1] http://poi.apache.org/hpbf/index.html Maybe you comes to Fosdem in Brussels, we would be happy to invite you to show on the work floor how is works here Greetz Fernand Hi Fernand, I would love to read a more detailed public success story about your experience and work with writer. It sounds very interesting especially when you stay in one world, means no heavy exchange of MS formats. Thanks for sharing Juergen Am Donnerstag, 15. November 2012 um 09:34 schrieb Fernand Vanrie: Alexandro , On Tue, Nov 13, 2012 at 11:24 PM, Phillip Zadro ricaza1...@hotmail.com.auwrote: hi Is there any likelihood that OpenOffice will one day include a desktop publisher? There is only one thing that is stopping me from migrating completely from Microsoft Office to either OpenOffice or LibreOffice and it is their lack of a Desktop Publisher comparable with MS Publisher. I have used Publisher for over 15 years and love its practicality, particularly with paginating of booklets. Even a separate program like Serif PagePlus cannot save in MS format either, so I am obliged to stay with MS Office. Pity.. Thanks Phil Draw is a perfect Desktop publisher, is so perfect is compatible with other We uses exclusifly Writer (+ lot of basic macro's) to make over 8.000 full color magazine pages par year. This pages are all i2 languages versions, with cutouts (we uses Edit Contour) transparancies etc...) Our Editors places lowres images embedded in there documents, a final macro checks the resolution quality and changes the lowres with the highres (stored on a server) just before exporting to PDF Sinds there is SVG, we no longer use EPS and Adobe to make our PDF's. PostScript is dead anyhow (lack of transparency) the LO/OO- PDF export is with use off a Lanczos filter nearly perfect. We only needs a payed Color Server to transfer our RGB PDF's to CMYK Our magazines are printed by different print houses (15.000-3.000 exp.) on high quality paper, there are no complaints from our printers and the readers can not sea the difference between our Magazines an thus maded by payed DTP applications Just a pitty thats SVG is still exported as bitmap (sould been repaired in 3.7) and PDF is still not a accepted as a graphic format like we can use (Tiff, jpg, etc...) Greetz Fernand desktop publishers like Scribus and is based on a frame based paradigm. There are some features that would be desirable but is pretty easy to complete basic and medium tasks like Flyers, Booklets and all it has layers which keeps design separated from content. And have multiple layouts and use of vectorial forms. With improved use of SVG Draw is also gaining strenght in the area of design compatibility and would be improving as more features are considered.
Re: [RELEASE] AOO.next = AOO 4.0
On Thu, Nov 22, 2012 at 11:36 AM, Dave Fisher dave2w...@comcast.net wrote: On Nov 22, 2012, at 3:50 AM, Jürgen Schmidt wrote: On 11/21/12 10:14 PM, Marcus (OOo) wrote: Am 11/21/2012 09:41 PM, schrieb jan iversen: On 21 November 2012 21:30, Andrea Pescettipesce...@apache.org wrote: Jürgen Schmidt wrote: I got the impression that the majority would support a 4.0 version as our next release. So do I. Besides the next major release we should also continue the discussion on further language packs based on 3.4.1 to make the latest translations available as soon as possible. One way to make these language packs available would be to integrate the new translations on the AOO34 branch, build the language packs and a new source release based on this revision. The effort should be minimal Since we have no critical bugs in 3.4.1, I would keep using the 3.4.x series until 4.0 is available. If a security issue emerges that suggests we should make a new release, we will fix it and release 3.4.2; otherwise, I would just keep adding new languages to 3.4.1 and make a couple of 4.0-beta releases, to get better exposure and QA, rather than a 3.5 release. But the 3.4.x series must have some predictable schedule or this won't work. For example, I would propose the following: - We announce on ooo-l10n that 2 December is the first deadline for integration of new languages in 3.4.1 December 2 is very close, when I think of the work in progress on a number of languages, I would suggest end of the year. indeed very close and I will be offline for some further days next week. I count at least 3 languages Danish, Polish, Scots Gaelic. And when we increase the deadline until the end of the year we potentially get even more. - We integrate and build available new languages in the week after it (and we already have two, Danish and Polish) - Native-language teams do some QA - We approve/publish the new builds and the new source release (a 3.4.1 respin, rather than a 3.4.2, since this would confuse users) Would it not be more confusing to change the 3.4.1 distribution files ? I would warmly suggest only to release language packs, since they are separate and do NOT change the existing distribution. If I have understood it correct, only new full install and langpacks files will be distributed - or maybe only langpack files. both would be possible, I ma flexible here. For using the same download mechanism and no further special handling it would be helpful to have the same files as for all other langs. I don't think that it's needed to replace files except for the source files. Exactly, we would release the new languages only on base of 3.4.1 and a new src release. When we do a further 3.4.2 release we can build the new languages in the same way as the others. I think that we will need a new source release - we could call the source release 3.4.1b. It depends on what is in the source release. If the tarball contains only the newly added PO translation files, then it could be called 3.4.1 without any confusion. Let's avoid any code changes, since that merely complicates future upgrades. It would give us good practice at voting on a release based on simple IP scans with RAT and svn diff to prove that the only changes are language files. We trust, but we must verify. If the only thing included in the source tarball are PO files then the proof is rather simple, yes? Just include the PO files, the LICENSE and NOTICE and a README that says to unzip these files over the already released full 3.4.1 source tarball. RAT scan of the PO files should be easy enough (assuming it understands PO files). Otherwise we can manually inspect the files for license headers. I don't have any strong opinions regarding whether we hurry for a 3.5 or develop a feature rich and well tested 4.0. Once we reach consensus on this issue we should have Marketing publish the plan so the user base will know what to expect with an estimated timeline - emphasis on estimated. Regards, Dave Juergen
Re: desktop publishing
Dave , Hi Phil, It is not completely impossible that an extension could be added to AOO to read and write Publisher files. It just takes one or two Java programmers with the time and interest. See [1] for where the effort could start. On Nov 22, 2012, at 8:36 AM, Fernand Vanrie wrote: Juergen, Maybe 1 machine has a MS office package for the unsalvable problems the 99 others have Windows with LO ,OO, Thunderbird, Inkscape, Gimp, Image Magick and a free Adobe PDF reader We can read and write MS text and spreadsheets, in the editing world PDF is the exchange format by exelence. (For that reason PDF must been a graphic format in LO and LO :-) It would great if PDF could be imported into any of Presenter, Writer and Draw. Perhaps this can be a goal of the new Drawing work. BTW - Postscript lives inside the PDF file format all of the drawing primitives are very close to postscript and operate the same way SVG is also a descendent of Postscript. (as Postscript is a descendent of Xerox Interpress plus III) in the long terme SVG can/sould be a full alternative for PDF ? now we open PDF files in Inkscape and save them as SVG, simpel PDF's survive this action and can been placed as SVG in all OO docs But I'm biased and have built a publishing chain based on applications producing postscript pages with special comments, shell scripts to collate into postscript documents, conversion to PDF w/ghostscript or editable PPTX using Java and Apache POI. We've also done PDF into editable shapes and text in PPTX using Apache PDFBox and Apache POI. Should we make the effort to go to ODF we will likely be using ODFToolkit. To close the loop if you want to process Publisher files and help with understanding the files format Apache POI is a good place. [1] Regards, Dave [1] http://poi.apache.org/hpbf/index.html Maybe you comes to Fosdem in Brussels, we would be happy to invite you to show on the work floor how is works here Greetz Fernand Hi Fernand, I would love to read a more detailed public success story about your experience and work with writer. It sounds very interesting especially when you stay in one world, means no heavy exchange of MS formats. Thanks for sharing Juergen Am Donnerstag, 15. November 2012 um 09:34 schrieb Fernand Vanrie: Alexandro , On Tue, Nov 13, 2012 at 11:24 PM, Phillip Zadro ricaza1...@hotmail.com.auwrote: hi Is there any likelihood that OpenOffice will one day include a desktop publisher? There is only one thing that is stopping me from migrating completely from Microsoft Office to either OpenOffice or LibreOffice and it is their lack of a Desktop Publisher comparable with MS Publisher. I have used Publisher for over 15 years and love its practicality, particularly with paginating of booklets. Even a separate program like Serif PagePlus cannot save in MS format either, so I am obliged to stay with MS Office. Pity.. Thanks Phil Draw is a perfect Desktop publisher, is so perfect is compatible with other We uses exclusifly Writer (+ lot of basic macro's) to make over 8.000 full color magazine pages par year. This pages are all i2 languages versions, with cutouts (we uses Edit Contour) transparancies etc...) Our Editors places lowres images embedded in there documents, a final macro checks the resolution quality and changes the lowres with the highres (stored on a server) just before exporting to PDF Sinds there is SVG, we no longer use EPS and Adobe to make our PDF's. PostScript is dead anyhow (lack of transparency) the LO/OO- PDF export is with use off a Lanczos filter nearly perfect. We only needs a payed Color Server to transfer our RGB PDF's to CMYK Our magazines are printed by different print houses (15.000-3.000 exp.) on high quality paper, there are no complaints from our printers and the readers can not sea the difference between our Magazines an thus maded by payed DTP applications Just a pitty thats SVG is still exported as bitmap (sould been repaired in 3.7) and PDF is still not a accepted as a graphic format like we can use (Tiff, jpg, etc...) Greetz Fernand desktop publishers like Scribus and is based on a frame based paradigm. There are some features that would be desirable but is pretty easy to complete basic and medium tasks like Flyers, Booklets and all it has layers which keeps design separated from content. And have multiple layouts and use of vectorial forms. With improved use of SVG Draw is also gaining strenght in the area of design compatibility and would be improving as more features are considered.
Re: desktop publishing
Armin , Hi Fernand, On 15.11.2012 09:34, Fernand Vanrie wrote: Alexandro , ---snip--- Draw is a perfect Desktop publisher, is so perfect is compatible with other We uses exclusifly Writer (+ lot of basic macro's) to make over 8.000 full color magazine pages par year. This pages are all i2 languages versions, with cutouts (we uses Edit Contour) transparancies etc...) Our Editors places lowres images embedded in there documents, a final macro checks the resolution quality and changes the lowres with the highres (stored on a server) just before exporting to PDF Sinds there is SVG, we no longer use EPS and Adobe to make our PDF's. PostScript is dead anyhow (lack of transparency) the LO/OO- PDF export is with use off a Lanczos filter nearly perfect. We only needs a payed Color Server to transfer our RGB PDF's to CMYK Our magazines are printed by different print houses (15.000-3.000 exp.) on high quality paper, there are no complaints from our printers and the readers can not sea the difference between our Magazines an thus maded by payed DTP applications Just a pitty thats SVG is still exported as bitmap Which export are you talking about? To ODF (save) or PDF (or something else)...? This would be very interesting to me :-) when making a PDF, save as or something else there is no difference... sinds 3.3 SVG are plased in the PDF as bitmaps there is a well documented LO issue https://bugs.freedesktop.org/show_bug.cgi?id=42092 42092. there is also work around - open the SVG in Draw and then copy to Writer (gives a internall LO graphic) - When xeporting to a specific PDF format (Tagged or PDF A/1a then we have a high resolution bitmap who can replace the vector data greetz Fernand (sould been repaired in 3.7) and PDF is still not a accepted as a graphic format like we can use (Tiff, jpg, etc...) Greetz Fernand ---snip--- Sincerely, Armin -- ALG
Allow detection of words being in italic or not
Hello! I few months ago I asked to the persons of LanguageTool if there was a way of suggesting to change words to italic just like MS Office 2010 does (for example, for Latin terms or abroad words). I was told it was not possible. Is there a way of improving AOO 4.0 in order to make this possible? Thanks! Kind regards, Marco A.G.Pinto --- --
Re: Wiki spamming is going to get worse if something isn't done soon...
On Thu, Nov 22, 2012 at 8:29 PM, Rory O'Farrell wrote: Thank, Clayton. I was wondering if there might be a malicious anti-AOO intent behind the spam, but from what you say it does not seem likely. It's definitely not anti-OOo vandalism. Just the usual blog/SEO spam. Clayton
Re: Apache OpenOffice: Call for Marketing Volunteers
On Thu, Nov 22, 2012 at 3:40 PM, jan iversen j...@apache.org wrote: Thanks rob. I changed ssi.mdtext (in SVN) as you suggested, and just had to make a change on a page so I could get the site generated again, and IT WORKED !! so that is the way to do these kind of changes. In CMS there are two buttons publish site, which is quite understandable, and production, which I dont quite get...is it just calling up the url for me ? Yup. production is analogous to staging, showing the current version on the production versus staging server. Generally you follow those links from left to right, edit, then follow the staging build, then verify on staging, then publish then verify on production server. -Rob Jan. On 21 November 2012 23:24, Rob Weir robw...@apache.org wrote: On Wed, Nov 21, 2012 at 5:19 PM, jan iversen j...@apache.org wrote: Help me out please... 1) I thought imacat had helped me update l10n to the standard template, is that the same as branding ? 2) SVN stores the full html, if I modify that will I then loose the mdtext (I have never understood where mdtext is stored, it seems to be somewhere locally in cms) ? 3) Would it not be better if l10n was changed to use the standard template ? The file brand.mdtext controls the banner message for L10n: https://svn.apache.org/repos/asf/incubator/ooo/ooo-site/trunk/content/l10n/brand.mdtext You probably inherited this by copying an NL site template. These were designed so the banner messages could be translated. But this probably doesn't make sense for the L10n site, since it is English. If you want to use the site-wide English brand.mdtext I wonder if that can be done by editing the L10n template here: https://svn.apache.org/repos/asf/incubator/ooo/ooo-site/trunk/templates/l10n/ssi.mdtext (MDtext files are stored in SVN, as part of our project. The HTML conversion of them are stored also in SVN, by the CMS) -Rob Sorry for being a newbie, but I prefer to ask a question instead of ruining a site ! Jan. On 21 November 2012 23:07, Andrea Pescetti pesce...@apache.org wrote: jan iversen wrote: the l10n.openoffice.org, still has the old banner ? Should I do something, I thought that when someone updated the master template, it was all changed ?? If you use custom branding (and /l10n does, like /it does) you need to update the banner manually: see http://svn.apache.org/viewvc?**view=revisionrevision=1412312 http://svn.apache.org/viewvc?view=revisionrevision=1412312 (the same change, just made for /it) for more. I personally do the change in an SVN checkout, then commit, then open the CMS, update and publish. But you can probably do everything within the CMS if you prefer to work online. Regards, Andrea.
Re: [RELEASE] AOO.next = AOO 4.0
Am 11/22/2012 12:57 PM, schrieb Jürgen Schmidt: On 11/21/12 5:33 PM, Keith N. McKenna wrote: Rob Weir wrote: On Wed, Nov 21, 2012 at 11:04 AM, Keith N. McKenna keith.mcke...@comcast.net wrote: Regina Henschel wrote: Hi Jürgen, Jürgen Schmidt schrieb: Hi, first of all I would like to volunteer again as release manager for our next release if it's ok for our community. +1 +1 on that from me also Second I would like to define with you what our next release will be. After various discussion and activities on the mailing list and also at the ApacheCon, I got the impression that the majority would support a 4.0 version as our next release. I'm not in favor of an version 4.0 as next release. The changes have listed below would justify a version 4.0. But I doubt, that they are possible in a time frame, I see for the next release. I am with Regina on this one. I do not see a Jan or Feb time frame as feasible for the design and implementation of a new and still a comfortable bit of padding to deal with the inevitable gremlins that will sneak out of the woodwork to assure the kind of quality release that is expected of OpenOffice and that we expect of ourselves. Uh, Juergen never suggested January or Feburary as a time frame for 4.0. So I don't see how one can dismiss a 4.0 proposal as being unfeasible based on dates that he never suggested. Maybe we should ask Juergen what timeframe he had in mind for 4.0? Of course, it might be possible to do both, provided we have volunteers willing to own testing and release management for 3.5. -Rob As I re-read the post you are correct Rob and I apologize to Juergen for reading to much between the lines. What timeframe were you considering for a 4.0 release Juergan? Well I had indeed not February in mind but when we targeting on end of March or April we will have more time. That sounds good. Should be enough time to implement and test new things. So, back to the question Next release 4.0 or not? ;-) Suggestion from me: - define within the next few weeks what features are for good for a 4.0 release - when we find only big things then implement them for 4.0 in March/April - when we see *additionally* enough smaller things, then a 3.5 could be done, too. Maybe until end of January? I assume the following is no problem and already agreed: - release new languages with 3.4.1 codebase - do a 3.4.x when we have serious issues that can/should not wait for the next bigger release Maybe we can take first a look on what others have in mind to put in the next release. OK Marcus
Re: [RELEASE] AOO.next = AOO 4.0
On 22/11/2012 Jürgen Schmidt wrote: On 11/21/12 10:14 PM, Marcus (OOo) wrote: Am 11/21/2012 09:41 PM, schrieb jan iversen: On 21 November 2012 21:30, Andrea Pescetti wrote: I would propose the following: - We announce on ooo-l10n that 2 December is the first deadline for integration of new languages in 3.4.1 December 2 is very close ... indeed very close and I will be offline for some further days next week. I count at least 3 languages Danish, Polish, Scots Gaelic. I we have 3 languages ready I wouldn't wait much longer. I mean, if we reach the point where we can automate it enough (we have to, at least for the 3.4.x series), then we can respin 3.4.1 even on a monthly basis. If it is too much work then we have an infrastructural problem to solve. Of course, since most of this work is on you, Ariel and mirrors I would perfectly accept to shift the date forward if you believe it's better; but communicating a clear deadline and releasing a few new languages soon would prove that we are ready to do these releases without too much overhead, and that volunteers can test their work without waiting for months. Marcus (OOo) wrote: When we release new languages I think it's worth enough to name it 3.4.2. No, if we name it 3.4.2 we imply it has something new in the English, German, Italian, ... version and communicating it would be unnecessary complex. If it is 3.4.1, it must be distributed as 3.4.1. Regards, Andrea.
Re: Wiki spamming is going to get worse if something isn't done soon...
On 22/11/2012 C wrote: TJ pointed me at the Wiki Spam problem. I can try to lend a hand. Thanks Clayton, you probably know the inner details of our Mediawiki configuration better than most people here, so it is great that you are going to coordinate with Jan to neutralize this attack. Regards, Andrea.
Re: Bad press
On 21/11/2012 Rob Weir wrote: Google shows 337 stories for the Freiburg story. But did you see a mention of the Leipzig story? I saw a few, but even though it was the larger migration, I saw only brief mentions. If we can manage to invite the Leipzig administrators to be interviewed, or write a guest blog post, on the official OpenOffice blog, this might be a good answer. I have no idea on how to contact them, but we have quite a few volunteers in Germany who could approach them if desirable. Regards, Andrea.
Re: Apache OpenOffice at FOSDEM 2013
On 11/21/2012 3:46 PM, Jürgen Schmidt wrote: On 11/13/12 7:21 PM, Andrew Rist wrote: On 11/13/2012 2:05 AM, RA Stehmann wrote: Am 12.11.2012 21:53, schrieb Andrea Pescetti: FOSDEM 2013 will be held in Brussels, Belgium, 2-3 Feb 2013 and it is a huge, free, developer-oriented, technical conference. OpenOffice has three opportunities to be featured there. 2) The Apache OpenOffice booth/stand. See https://fosdem.org/2013/call_for_stands.html Again, I can take care of submitting the request, but we will need to be sure that we have enough people available to attend to it. Mechtilde and Michael will very likely be there, right? Yes, we'll be there. We have some years experience presenting OpenOffice at the FOSDEM. Organizers want to be sure that we will have at least two people on Sat 2 Feb and Sun 3 Feb, full days. I'm hopefully, some of our friends running the dev-room will join and help us on the other day. We prefer more people will join us, because running a booth with many people is more joyfully. But we're able to ensure the organizers wants even we've to do it alone. Please state your availability: if we have enough people, it would be nice to request a large stand instead of a normal one. Timeline: proposals due by 28 Nov. We think a normal stand is better than a large one. It's better there are lot of Apache people around a smaller stand than only a few around a large one. And we have no merchandize articles to present (like other projects). What would you want to give out if you could? Is there something that we could use to help the image of the project in the wider open source community? What would you want? (and how many?) In the past I have created T-Shirts for example and we gave them more or less for a small donation to people. They were initially paid by the Community Council (Team OpenOffice). The collected money (minus production costs) went back to Team OpenOffice . We could do something similar and the money would go back to the ASF. We had also other small stuff that we gave away for donations. Always nice are cups, T-Shirts, stickers, flyers,... something like that. Ideally not branded for FOSDEM but more neutral for AOO that it can be used for other events as well. We can also think about AOO branded note pads (~1500-2000) that we can give the organizers to put it in the conference welcome packs. Information on the note pad could be info where to find our DevRoom and the booth for example. We could also benefit some of some banners (roll up banners for example) If we want to do something like this, we need ideas for an logo/image we want to put on shirts, cups, etc. and of course the technical realization that can be used for the production. Other questions: - collecting quotes for the production and volunteers who take care of it - who can carry the material to the event (I booked my flight already and can't carry too much) The time is running and many questions would have to be clarified. Some more info and basic quotes: - rollup banner - 100-150€ - note pad, 1000 pieces, á 50 sheets, 100% recycling paper, 2 color print, glue laminated on one site, first quote I found ~1050 € - stickers, 100mm, 1000 pieces, ~150€ See for some concrete stuff (shirt, banner) http://wiki.openoffice.org/wiki/Conferences/FOSDEM/2009 http://wiki.openoffice.org/wiki/Conferences/FOSDEM/2010 I'm supporting your request. Maybe you should resend it as a separate [Proposal]. As well, I'm not sure about the policies. Maybe it's up to the PMC to decide. From my point of view the PMC. Best regards, Peter Juergen A. So a normal stand would fit. A booth is a place where people can find and meet Apache supporters to talk, get information etc.. People walk around and see: Oh, there is also an Apache OpenOffice booth! And we can encourage them to ask us, get information etc.. We can contact people who don't prospect us specificly. In that way a booth is important even than a dev-room exists. We like to invite other Apache projects to join and support us and to present their project at the booth. Regards Michael
Re: [RELEASE] AOO.next = AOO 4.0
On Nov 22, 2012, at 3:24 PM, Andrea Pescetti wrote: On 22/11/2012 Jürgen Schmidt wrote: On 11/21/12 10:14 PM, Marcus (OOo) wrote: Am 11/21/2012 09:41 PM, schrieb jan iversen: On 21 November 2012 21:30, Andrea Pescetti wrote: I would propose the following: - We announce on ooo-l10n that 2 December is the first deadline for integration of new languages in 3.4.1 December 2 is very close ... indeed very close and I will be offline for some further days next week. I count at least 3 languages Danish, Polish, Scots Gaelic. I we have 3 languages ready I wouldn't wait much longer. I mean, if we reach the point where we can automate it enough (we have to, at least for the 3.4.x series), then we can respin 3.4.1 even on a monthly basis. If it is too much work then we have an infrastructural problem to solve. We will still need to VOTE as it will be a source release. That is not automatic. Of course, since most of this work is on you, Ariel and mirrors I would perfectly accept to shift the date forward if you believe it's better; but communicating a clear deadline and releasing a few new languages soon would prove that we are ready to do these releases without too much overhead, and that volunteers can test their work without waiting for months. Marcus (OOo) wrote: When we release new languages I think it's worth enough to name it 3.4.2. No, if we name it 3.4.2 we imply it has something new in the English, German, Italian, ... version and communicating it would be unnecessary complex. If it is 3.4.1, it must be distributed as 3.4.1. Yes, but also distinct from the other 3.4.1 source release. Regards, Dave Regards, Andrea.
Re: Allow detection of words being in italic or not
hi Pinto: Very interesting suggestion! But let me clarify something. You mean, in some kind of language (in your case, the Portuguese for example), when you referring some characters or words from foreign languages, such characters and words should be marked as italic style, right? And you said you are creating something about Language Tools Rules for Portuguese writing. Sorry for my stupid question that, what is the Language Tool and its rules? How should it works? And more specifications, what do you exactly need? A series specified UNO APIs for marking/identifying/setting characters or words from foreign languages? Or the totally implementations inside the SW core functions which need not external UNO extension developing? In general, such behaviors is possible to be implemented inside AOO writer, identical words, customized context menu items, set italic font style... all of them. But here, my concern is, seems not all the languages have the same custom on showing words from foreign languages. For example in Chinese, there is no such kind of custom. And in English, the italic font style is commonly indicates a book or article title which is referred inside. Which means, we need to know the exact range of languages that should apply this custom, before supplying the function you want. 在 2012/11/23 4:42 AM，Marco A.G.Pinto marcoagpi...@mail.telepac.pt写道： Hello Regina, I meant italic as a font style. For example, when I am writing a Portuguese document in Office 2010 and write, for example, the word e-mail, since it is not Portuguese, Office 2010 underlines it in green and when we right click it, it says make sure Latin and foreign words are in italic or something like that. I wanted this to be possible also in AOO using LanguageTool. I am creating the Portuguese rules in LanguageTool and I want things to be as good or better than Office 2010. Thanks for your time! Kind regards, Marco A.G.Pinto --- On 22-11-2012 20:15, Regina Henschel wrote: Do you mean italic as font type or as language? In what situation do you need it? In normal running AOO you can search for language and for font type as well with the FindSearch dialog. In the file itself it is more laborious. First you have to scan the styles to get the names of those with the desired attribute and then you have to scan the paragraphs and headings for span elements with that style name. --
Re: Allow detection of words being in italic or not
On Thu, Nov 22, 2012 at 10:41 PM, Fan Zheng zheng.easy...@gmail.com wrote: hi Pinto: Very interesting suggestion! But let me clarify something. You mean, in some kind of language (in your case, the Portuguese for example), when you referring some characters or words from foreign languages, such characters and words should be marked as italic style, right? And you said you are creating something about Language Tools Rules for Portuguese writing. Sorry for my stupid question that, what is the Language Tool and its rules? How should it works? And more specifications, what do you exactly need? A series specified UNO APIs for marking/identifying/setting characters or words from foreign languages? Or the totally implementations inside the SW core functions which need not external UNO extension developing? In general, such behaviors is possible to be implemented inside AOO writer, identical words, customized context menu items, set italic font style... all of them. But here, my concern is, seems not all the languages have the same custom on showing words from foreign languages. For example in Chinese, there is no such kind of custom. And in English, the italic font style is commonly indicates a book or article title which is referred inside. Which means, we need to know the exact range of languages that should apply this custom, before supplying the function you want. We have this convention in English as well, in more formal writing styles. This sounds like something that could be done via Smart Tags: http://wiki.openoffice.org/wiki/Smart_Tags But it would rely on a dictionary of foreign phrases. There is a lot of interesting app dev work that could be done for internal workflows. For example, recognizing customer names or account numbers, pr order numbers, or product codes, and automatically adding hyperlinks to internal services related to those codes. -Rob 在 2012/11/23 4:42 AM，Marco A.G.Pinto marcoagpi...@mail.telepac.pt写道： Hello Regina, I meant italic as a font style. For example, when I am writing a Portuguese document in Office 2010 and write, for example, the word e-mail, since it is not Portuguese, Office 2010 underlines it in green and when we right click it, it says make sure Latin and foreign words are in italic or something like that. I wanted this to be possible also in AOO using LanguageTool. I am creating the Portuguese rules in LanguageTool and I want things to be as good or better than Office 2010. Thanks for your time! Kind regards, Marco A.G.Pinto --- On 22-11-2012 20:15, Regina Henschel wrote: Do you mean italic as font type or as language? In what situation do you need it? In normal running AOO you can search for language and for font type as well with the FindSearch dialog. In the file itself it is more laborious. First you have to scan the styles to get the names of those with the desired attribute and then you have to scan the paragraphs and headings for span elements with that style name. --
Re: Apache OpenOffice at FOSDEM 2013
On 21/11/2012 Jürgen Schmidt wrote: Always nice are cups, T-Shirts, stickers, flyers,... something like that. Ideally not branded for FOSDEM but more neutral for AOO that it can be used for other events as well. Excellent idea. At least we should have some t-shirts for volunteers and a simple gadget to distribute (a notepad can be ok, a USB stick with OpenOffice and related content might be nice too, but it's probably more expensive). We can also think about AOO branded note pads (~1500-2000) that we can give the organizers to put it in the conference welcome packs. I'm not sure FOSDEM has conference welcome packs. I don't recall being given one in recent years. If we want to do something like this, we need ideas for an logo/image Yes, and consider that, with the rebranding currently ongoing, it could happen that we have a new logo soon. So we shouldn't exaggerate with quantities. Regards, Andrea.
Re: Open Office QA volunteer.
Welcome to join us. I'm Wang Li Feng, Living in Beijing. I have 3 years experiences in testing. mainly focus on FVT and automation test with Java。 I am also a new comer in AOO community for about 1 year. when I joined OO community, I started from verify defects, then start to mannal FVT and wrote automation scripts. I'm familiar with Impress and know some usages about Base. Now I focus on automation test(BVT,FVT,SVT). If you are interesting about OO QA, you can get start from: http://incubator.apache.org/openofficeorg/orientation/intro-qa.html http://wiki.openoffice.org/wiki/QA http://wiki.openoffice.org/wiki/QA/QA_Tasks 2012/11/21 Alexandro Colorado j...@oooes.org Welcome to our community please confirm your membership to the Mailing list at: https://incubator.apache.org/openofficeorg/mailing-lists.html#qa-mailing-list Also try to read about the TCM and how to use it. http://wiki.openoffice.org/wiki/QA/Testlink On 11/20/12, PRADEEP KOULAGI pradeep_e...@yahoo.com wrote: Hello, My name is Pradeep Koulagi I am from Bangalore, India. I am a Batchelor of Engineering graduate and interested to make my career in testing. I like contributing to the open source projects. Thank You. -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org -- Best Wishes, LiFeng Wang
