- Inkscape Devel - Inkscape Mailman

tspan Text Starts
by Martin Owens 27 Nov '12

27 Nov '12

hey guys, I'm developing an extension to manage translations (which I do via launchpad and xml2po) but I'm having trouble with tspans. The problem seems to be that inkscape saves multiple values for the x attribute for some (not all) tspan sections. Specifying the letter placements is death to translations as the number and size of letters is guaranteed to be different. Is there any api way to strip out these bumbling attributes or better have them not appear in the first place? Thanks for your time. Best Regards, Martin Owens

2 5

Updated code in SpiroLIve
by Jabiertxo Arraiza Cenoz 27 Nov '12

27 Nov '12

SpiroLive branch update. Fix some redraws problems. Full comented SpiroLive code, in spanish sorry ¿Any tranlator? Regression to original codebase "sp_pen_context_set_polyline_mode" overloading whith a new function "sp_pen_context_set_mode" I want to mark for include in codebase, feedback are welcome. Hi, Jabier.

1 0

Tiling tool
by Tom Lechner 26 Nov '12

26 Nov '12

I was reading that Veronika Irvine's Tiling Tool Summmer of Code project was successful, which is quite exciting. Can this be downloaded somewhere? I can't seem to find reference to it.. -Tom

3 3

Sorin based SpiroLive behabiours
by Jabiertxo Arraiza Cenoz 26 Nov '12

26 Nov '12

Translated by google -------------------------------------------------- -------------------- Hi. I just upgraded to SpiroLive branch as directed by Sorin, with which I agree. Containing historical remains above 11,864 revision behavior. For a lack of knowledge on how to mine working with Bazaar, are not available, this time, the various revisions between one version and another. I made a change to code that I would like, in the files "pen-context.cpp", "pen-context.h", "draw-context.cpp" and "widgets / pencil-toolbar-cpp" is used function called "sp_pen_context_set_polyline_mode" that is developed in the pen-context.cpp file. This function is used to change the mode (polyline, paraxial ...). I have seen fit to extend its scope to also define whether we are in "Spiro" or, in the future, whether we are in "BSpline". To this I added a boolean property to the object "SPPenContext" called "spiro" (pc-> spiro) and changed the name of the function in the three previous files "sp_pen_context_set_polyline_mode" a "sp_pen_context_set_mode". On the use of the tool, I had to update the message status bar with the string "SHIFT for cusp node" and see how they manage the translations. Usage is simple, clicks create SYMM nodes with "SHIFT" are created but are mode CUSP. I ask you to try the code, especially continuing existing lines and / or closing them. Greetings. ---------------------------------------------------------------------- Hola. Acabo de actualizar el branch de SpiroLive siguiendo las indicaciones de Sorin, con las que estoy de acuerdo. Queda como histórico conteniendo el anterior comportamiento la revisión 11864 . Por una falta de conocimientos mios en la manera de trabajar con Bazaar, no están disponibles, esta vez, las distintas revisiones entre una versión y la otra. He realizado un cambio en código que me gustaría comentar, en los archivos "pen-context.cpp", "pen-context.h", "draw-context.cpp" y "widgets/pencil-toolbar-cpp" se utiliza una función llamada "sp_pen_context_set_polyline_mode" que está desarrollada en el archivo pen-context.cpp. Esta función sirve para cambiar el modo (polilinea,paraxial...). He creído conveniente ampliar su alcance para definir también si estamos en modo "Spiro" o para, en el futuro, saber si estamos en modo "BSpline". Para ello he añadido una propiedad booleana a el objeto "SPPenContext" llamada "spiro" (pc->spiro) y he cambiado el nombre de la función en los tres archivos anteriores de "sp_pen_context_set_polyline_mode" a "sp_pen_context_set_mode". En cuanto al uso de la herramienta, me falta actualizar los mensajes de la barra de estado con el string "SHIFT for cusp node" y ver como se gestionan las traducciones. El uso es simple, los clics crean nodos SYMM, con la tecla "SHIFT" se crean pero son de modo CUSP. Os pido que probéis el código, especialmente continuando líneas existentes y/o cerrándolas. Saludos.

1 0

Anyone can confirm if this is really a bug ?
by Guiu Rocafort 21 Nov '12

21 Nov '12

I'm not really sure about this being really a bug so I'm asking before creating a bug report. The bug is checked using Windows 7 64 bits and Inkscape 0.48 The steps for reproducing are: 1. Create empty file. 2. Create a rectangle ( or any other shape ) 3. Open Fill and Stroke menu 4. Select Stroke tab. 5. Grab color picker tool. 6. Select any color in the document. What happens: The fill colour becomes the one picked with the tool. What I think it should happen: Since the stroke tab is selected, the stroke colour should become the one selected with the tool and not the fill colour. So I am missunderstanding Inkscape or is it a real bug ? Thanks -- Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html

5 9

0.49 release status update
by Josh Andler 20 Nov '12

20 Nov '12

Hey All, It's almost time we move on to Feature Freeze, at this point I'm saying let's put it out there as November 30th. I had delayed it to get in a couple new features and the reason I'm not just saying it's today is to leave it open for John Smith for a shortcut editor akin to GIMP's (if it can be completed in time). The current list of bugs milestoned for 0.49 is at 50... and that is quite high. Can people help reduce this number some? My guess is things like the tutorial updates for 0.49 are not likely to make it for example. https://bugs.launchpad.net/inkscape/+bugs?field.searchtext=&orderby=-import… The real issue though is that we currently have 13 blocker bugs, all but one of which are regressions caused by the new renderer or rendering cache. https://bugs.launchpad.net/inkscape/+bugs?field.searchtext=&orderby=-import… In addition to these blockers, we still have a security bug that is blocking 0.48.4 and will also block 0.49. Please focus efforts on fixing bugs rather than enhancing features at this point. The two exceptions to this are for the shortcut editor and the newly committed symbols dialog, polishing things like this is good. String Freeze will go into effect on November 30th at this point, but I HIGHLY recommend translators get started now if they haven't started already (as was previously recommended). Unfortunately, it does not look like we're going to be able to get the release out this year as originally hoped. At the current rate I hope we can get it out in Q1 of next year. Sorry for not giving an update sooner. I hope all is well with everyone! Cheers, Josh

3 3

PDF X-3
by john Culleton 20 Nov '12

20 Nov '12

An Inkscape file can be saved as PDF 3 or PDF 4. What are the prospects for PDF X-3 being added to the list? -- John Culleton Wexford Press Free list of books for self-publishers: http://wexfordpress.net/shortlist.html PDF e-book: "Create Book Covers with Scribus" available at http://www.booklocker.com/books/4055.html

2 1

Cuestion about branches test
by Jabiertxo Arraiza Cenoz 20 Nov '12

20 Nov '12

Hello Krzysztof. Thanks very much. I update the branch and tell in the list the number of the previous branch whith old staff for posibol regression. Hi, Jabier. > On Wed, 2012-11-14 at 13:36 +0100, Jabier Arraiza wrote: >> Im new to develop whith BZR. I develop a branch, and after i made a lot >> of changes on the branch but i want to know what version of code is >> better. >> What i do? 2 branches or update original branch whith the new code. >> The new code is more powerful but im not sure is ok whith the filosophy >> of inkscape, because made more changes to the code and change some >> behviors on usage. > > If you want to compare a branch, to let's say trunk you can do that > using bzr by specifying the branch. So: > > $ bzr diff --new lp:inkscape > > Would compare to trunk. Usually I find it useful to compare to the > common ancestor as the diff is a bit cleaner: > > $ bzr diff -r ancestor:lp:inkscape > > If you'd like to update your branch to include the changes that are on > trunk currently you can just merge them in. No need to worry about > rebasing or anything like that, Bazaar handles it for you. > > $ bzr merge lp:inkscape > $ bzr commit -m "Updating to trunk" > > It's difficult to know which is "better", but hopefully that helps you > figuring out the information you need. This information could be added to our Bazaar tutorial: http://wiki.inkscape.org/wiki/index.php/Working_with_Bazaar Regards, Krzysztof

1 0

sodipodi:linespacing
by mathog 19 Nov '12

19 Nov '12

How does sodipodi:linespacing determine the vertical spacing to the next line? From a bit of experimenting it looks like it starts with this: sodipodi:linespacing="125%" and then looks at the maximum font size in all of the <tspan>'s included under the following <tspan sodipodi:role="line" and multiplies those together. So if the largest is 16pt, it uses 20pt for the linespacing. Is there anything else involved, or is that the entire method? Also, if this is all inside a <text> with style="font-size:32.000000pt;font-style:normal;font-variant:normal;font-weight:400;font-stretch:Normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;text-align:start;text-anchor:start;font-family:Arial;" Changing font-size or line-height makes absolutely no difference in the display. Is that how it should be? Thanks, David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech

1 0

Inkscape 0.48+devel r11870 and Units
by Jelle 18 Nov '12

18 Nov '12

Hi Guys, Testing this recent build. Inkscape 0.48+devel r11870 So far: New stuff: - Love the Symbol manager. It will greatly inprove productivity. I wish that a similar thing could be done with first level grouped objects and using the same CTRL+select for objects within that. Ehm,.. a small note saying Use CTRL+C to copy might help though, as I tried clicking and dragging first. BTW. If it would follow the rule of always paste in place, it would be a great help in templating designs. - The new text edit docker is great! Would have liked to see a list of fonts used in the document though, so you can more easily select from the fonts already chosen, find out missing fonts etc.. Could that be added to a third tab? Old stuff: - It's the old clip an object and get to select the object rather than the clipped area bug. So my clip displays the size of the clipped object rather than the clipping area. Now really...that is something that needs fixing. BTW,.. using the create copy of clipping object to create area rather than the default. Releasing the clip doesn't recreate a copy of the clipping object on the screen, clippath is left in defs. So I guess the function has to be extended with a function to copy that node back to the correct z-order of the objects. Question: - Does Inkscape already support SVG font display (Tiny, not Full)? I know Mozilla doesn't support it and probably never will, but I really would love to use them regardless. I have several use cases in mind that are uniquely possible using SVG fonts and don't care if users will have to use "Modern" browsers like ahem.. the rest. Now we can create Glyphs, but I am not sure if it is possible to display them yet. I'll do more testing during the next few weeks, if there's anything you'd like me to pay attention to, please tell as there are a lot of things, new and old. On the Units discussion: The idea is simple Inkscape uses px as units. In the config we can set the amount of pixels per unit, so we end up with 90dpi (standard screenres in 2000) or just set it to 10px per mm or whatever. That way poor buggers like me that design in mm for print and need to get this used on screen won't have to use a calculator to convert the x,y locations with a 6 decimal precision and make these horrid choices on how to handle the half a pixel sizes. Using 3.50xxxx etc. really does my head in at times. Nowhere in the SVG specs does it implicitly say how many PPI to use, it's arbitrary. However, as it was concieved to be used as a screen format, it became pixels per Inch to follow the industry standard. The latter we can blame on Silicon Valley being the place where the early stages of IT were conducted rather than Bletchly Park or Paris. The whole zoom factor is not the issue. It's having a SVG document that has been converted from mm to Inches and then PPI. If I have a 85x55mm businesscard, I'd love to be able to read that in the SVG file as 850x550 px rather than 309.2xxxxx x 190.1xxxxx. That way I can more easily create guidelines and additional objects on screen in my web application without having to calculate every friggin measurement and ending up with those quirky estimations. Maybe Inkscape development isn't always a bliss, but I think with little effort Development using Inkscape can be made a bliss. Adding a setting for Pixels per Unit will greatly improve my sense of bliss at least. For others it may also be a handy way to solve their problems they encounter with scaling if there was an additional recalculator function added to this scaling. That would be a nice extension maybe. "Change/Convert pixels per unit"... Oh joy! I could reset tonnes of hardly usable SVG code with that..! Well,.. Cheers Jelle

6 6