Re: tdf#51165 -> code pointer needed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 08.11.2015 um 01:43 schrieb Thorsten Behrens: > Christina Roßmanith wrote: >> I'm revisiting tdf#51165. It looks like rendering is the >> problem, not importing the SVG file. To continue I'd need some >> code pointers where rendering is implemented. >> > Hi Christina, > > oh, this is an interesting corner case - the polypolygon in the > bugdoc has both closed and open polygons, therefore > B2DPolyPolygon::isClosed() will yield false. Thusly > xmloff/source/draw/ximpshap.cxx:1514 and following will pick the > open shape service. > > The case at hand can be fixed, the problem in general is that LibO > cannot handle mixed open & closed polygons within a *single* > shape. Then for the mixed case the problem could be solved by iterating over the polypolygon and calling writePathShape() with each individual subpolygon. Or are there reasons not to proceed this way? Christina > > HTH, > > -- Thorsten > -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJWP7s1AAoJEN/hiApPuw9SaK8H/1dlm7H8Llhd88dMTyNgxjjt MHH0uydfLj8ENsh/wEBC4bGmpPsT0tBvd2uPo/SObavypFNMW8zRkXCanPnx91IH yv8u1aX82DJoUIMRaLz6wG1vWYLiU95YKI7d8OEQYWo2KB43oPTZYRkR/niT5/jL xRpmRIBeoEumuJMT8ArKcYCHYsQAYATXOa0Dhqmo0Q6NdiPSCl0f9CmGCCOPYTzH goGgzrf2DoEdEiipy2VspPGwOpX6ODG0n94j7OSXS9hBIYsSMQgB+RE8Q/Z5c4in wcuwRwWrSgJtivERk3GBCvdCki4Q+g8/TI/v3LtYV/z18pQziNF0wgC31BchPB8= =9z0l -END PGP SIGNATURE- ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
tdf#51165 -> code pointer needed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm revisiting tdf#51165. It looks like rendering is the problem, not importing the SVG file. To continue I'd need some code pointers where rendering is implemented. Christina -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEbBAEBAgAGBQJWO8phAAoJEN/hiApPuw9SaGAH92VdZh8zvgNBm8mVUmbSMxbI Gz/JxmYT1wLCBPQoqsW+MLiHPE+haQcyPTOpDsd3w26DIprCa10IC4eNskW2MH2g 5X+RLumFEuFOCjZFogGar8zKOWaUUVCviaack4ioGVn9NFYsIlDPJv0j3PmZC3yK CxOF7M8tTGeq1sGSB2cm/mS3VMMfdPnYwT8wzS9NV4J/aJgTiMauH7ndjLqAd0Ad s4RSPaUktXYr9l6LtOCm+BykuuFz52skSbiO4oOquX/jcPAixdGXFdUk61Af2v5H 02AMGGUBFx8fHRJfq/s1cLNzU8J9el2tTtdpoDlSMlkB6hqPN5KhC6RbncHdqA== =yQ6o -END PGP SIGNATURE- ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
SVG Break
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Thorsten, could it be that after breaking an inserted or opened SVG in Draw, a path isn't known any longer as SVG path but as some general manually closed polygon which is closed and to which different stroking rules apply than to manually closed SVG paths? Just for the records a small example: ?xml version=1.0 encoding=UTF-8 standalone=no? svg xmlns:dc=http://purl.org/dc/elements/1.1/; xmlns:cc=http://creativecommons.org/ns#; xmlns:rdf=http://www.w3.org/1999/02/22-rdf-syntax-ns#; xmlns:svg=http://www.w3.org/2000/svg; xmlns=http://www.w3.org/2000/svg; version=1.1 width=210mm height=297mm g path d=m 20,40, 0,-20 80,10 -80,10 style=fill:none;stroke:#00b300;stroke-width:6;stroke-linejoin:round;st roke-miterlimit:10; / /g /svg Steps to reproduce: - - Insert or open SVG - - Break it (right mouse click in graphic - context menu) - - Watch the changing stroking Christina -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJVDSvRAAoJEN/hiApPuw9SRYoH/02+bvPcQbtvtD5d8O48bxgp D1el7g9SLHHY4p0byFq16F56AjZfVNxALyor2gMhUwBSgCOtV1kmbVZlqW8Vc6Pw PbhtaNg+SrSDzQcN+nPdl1GmT13NbsEM6Vojzr7GKxagsmE5lUIenhtMdmd3hzrZ FdFpUikMCtWTs65k17dUDLDmE4JTEEMfiE3RbIw+x726LnWJfJtscSupY5MsHpcH MsQs95c3xXmrEeLc9YB4v+9Jufa+y2nKKWygTqNYzjZIXsPX2yhOcG5Qm/UGeD1S fuPXBIcOpuvt0fUx4rtPooG+Ia7I6Ht9Q+jw7J2BQMLVgFWhaltD7Tj8V3dHW0w= =jVyK -END PGP SIGNATURE- ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [EASY HACKS] machine translation of remaining german comments acceptable?
Hi, I had a quick look at the attachment and I fear that the comments that are really quick and easy to translate (like siehe oben - see above) are translated correctly by the software and those which make translating a pain are left as they are. At the moment I translate comments as I come across them, e.g. when replacing String with OUString or removing duplicate pieces of code. Christina -Ursprüngliche Nachricht- Von: Noel Grandin n...@peralex.com Gesendet: Oct 5, 2011 4:54:50 PM An: michael.me...@suse.com Betreff: Re: [Libreoffice] [EASY HACKS] machine translation of remaining german comments acceptable? Hi Michael Meeks wrote: I suspect that some of the comments will not produce good results at all, and of course some of our comments are really rather bogus and un-necessary. Also - it may loose the distinction between carefully translated and cleaned up files and those with machine translated comments. Yeah, the results are clunky. We've had a group of Germans looking at this problem in the past, Christina was one of them - perhaps she has some suggestions, and/or a way to do a quick / bulk review of the resulting diff (?) possibly it is easier reviewing and editing the google-translate output and it may help speed things up a lot there (which would be wonderful). Christina ? The resulting data looks like a unified diff, and it should be reasonably easy to hand-edit to improve. I've attached some example output. Are you using Miklos' bin/find-german-comments :-) No, I've just been grepping for collections of letters that are common in german, but uncommon in english. I'll have a look at that script for ideas. As I said, I have some experience in doing this - I find it easier to make a first-pass translation of my applications myself, and then let the experts fine-tune it. Thanks, Noel Grandin Disclaimer: http://www.peralex.com/disclaimer.html ___ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Patch for libs-gui repo
Hi Julio,Julien Nabet fixed this already. I think he'll push it soon.ChristinaVon: Jlio Hoffimann julio.hoffim...@gmail.comGesendet: 11.04.2011 03:31:41An: LibreOffice libreoffice@lists.freedesktop.orgBetreff: [Libreoffice] Patch for libs-gui repoHi,This patch fix some literals in padmin module.Available under LGPLv3+/MPL.Regards,Jlio.Schon gehrt? WEB.DE hat einen genialen Phishing-Filter in dieToolbar eingebaut! http://produkte.web.de/go/toolbar ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] About the easyhack expunge duplicate enumerations in vcl
Done. Christina -Ursprüngliche Nachricht- Von: Michael Meeks michael.me...@novell.com Gesendet: 08.04.2011 10:24:18 An: Julien Nabet serval2...@yahoo.fr, Christina Roßmanith chrrossman...@web.de Betreff: Re: [Libreoffice] About the easyhack expunge duplicate enumerations in vcl On Thu, 2011-04-07 at 23:23 +0200, Julien Nabet wrote: I'd like to work on the easyhack expunge duplicate enumerations in vcl. Ah - sadly Christina is working on this but (apparently) hasn't updated the wiki to reflect that ... cough Christina ? :-) ATB, Michael. -- michael.me...@novell.com , Pseudo Engineer, itinerant idiot ___ Empfehlen Sie WEB.DE DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.web.de ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] need your help to make my first patch. (conditional formattings with unlimited number of rules)
Hi, git status tells you, which files were modified, git commit -m commit message -a puts those modifications under git control and finally git format-patch HEAD~1 gives you a patch file you can send to the mailing list for review. At least this is the way I create patch files. Make sure that you've configured your real name (don't know the syntax) that it is saved later during git push (executed by some of the more experienced developers) Christina -Ursprüngliche Nachricht- Von: Robert Dargaud l...@bobiciel.com Gesendet: 30.03.2011 00:58:09 An: libreoffice@lists.freedesktop.org Betreff: [Libreoffice] need your help to make my first patch. (conditional formattings with unlimited number of rules) Hi all, I need your help to make my first patch. (conditional formattings with unlimited number of rules). Last week end I've restarted my work on a new clean bootstrap. With these instructions : http://wiki.documentfoundation.org/Development/How_to_build Build was ok Before making changes I've detected a strange bug : cd install/program ./soffice --calc File New Spreadsheet Format Cell Numbers == crash !!! Is-it only on my build ? Michael say to me than many things have changed in source. I've seen ;-) With Kompare, I've applyed manualy my change to the new sources files. After, I've tried to make a patch from bootstrap. With git diff It's not possible ! I think it's only possible on distinct modules ? I add to this message, 2 patch files I've make with : cd sc git diff s file name q cd svx idem When I open these files with Kompare this message is display : The diff is malformed. Some lines could not be parsed and will not be displayed in the diff view. Strange !!! I've try to open with diffuse merge tool and KDiff3. error message are also displayed !!! Is the procedure correct to create patch ? Thank for your help Bob Screen shot : http://archives.bobiciel.com/libo/condfrmt/condfrmt.jpg Test file : http://archives.bobiciel.com/libo/condfrmt/test_condfrmt_100.ods ps: sorry for my googled translation english ... ___ WEB.DE DSL Doppel-Flat ab 19,99 euro;/mtl.! Jetzt mit gratis Handy-Flat! http://produkte.web.de/go/DSL_Doppel_Flatrate/2 ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] git am - German keywords
Hi Martin, no, I didn't. Yesterday I went the emacs - Apply patch way again. Christina -Ursprüngliche Nachricht- Von: Martin Kepplinger martinkepplin...@eml.cc Gesendet: 24.02.2011 15:29:56 An: libreoffice@lists.freedesktop.org Betreff: Re: [Libreoffice] git am - German keywords Am 2011-02-23 21:35, schrieb Kohei Yoshida: On Wed, 2011-02-23 at 21:11 +0100, Christina Roßmanith wrote: Hi, does anybody know whether git am relies on the keywords subject: or is Betreff: (the German equivalent) valid as well? I've saved an e-mail with a patch as recommended with File-Save as and git am told me that Patch format detection failed. Hi Christina, Which email are you trying to save apply? Kohei Hi, did you solve this, and how? thanks! martin -- /***\ | Martin Kepplinger| | | | diaspora handle martinkepplin...@joindiaspora.com | | | | E-Mail IM(jabber) martinkepplin...@eml.cc | | | | GPG Fingerprint 7346 FE02 27C3 3958 813A C351 C100 D7B5 7F2A 1E26 | \***/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice ___ Empfehlen Sie WEB.DE DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.web.de ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Need translation and to define the expected behaviour for fdo#34072
Hi, I've started to translate (and pushed what I've done so far). Maybe it's already useful. Will continue later. Christina -Ursprüngliche Nachricht- Von: Julien Nabet serval2...@yahoo.fr Gesendet: 17.02.2011 08:22:20 An: libreoffice@lists.freedesktop.org Betreff: [Libreoffice] Need translation and to define the expected behaviour for fdo#34072 Hello, This pb is about Protected cells can not be modified using Replace on unprotected cell. I try to understand the process and I found that this error message comes from : sc/source/ui/view/viewfun2.cxx in the function SearchAndReplace. It could be helpful to have the english translation of the german comments of this function. Perhaps we need to define the behaviour we expect exactly in the different cases : - no cell with the search pattern - all the cells which have the search pattern are protected (certainly we must differentiate the writing protection and the reading protection) - some cells which have the search pattern are protected, some are not,.. - etc. Julien. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice ___ WEB.DE DSL Doppel-Flat ab 19,99 euro;/mtl.! Jetzt mit gratis Handy-Flat! http://produkte.web.de/go/DSL_Doppel_Flatrate/2 ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
