- Inkscape Devel - Inkscape Mailman

Fix for Font Name Case bug #1818885
by Thomas Worthington 09 Nov '07

09 Nov '07

I've put a diff that fixes this bug at http://www.tww.cx/downloads/fontcase.diff I'd love to say that there must be an easier way but instead I'd like to say that the person that defined the C++ string class without case-changing functions should themselves be strung up! The method used needs to be checked by someone who actually knows C++ to see if it will handle non-ASCII font names. I don't have any such fonts to test it with and I'm not sure enough about how C++'s toupper function works on unicode to even guess whether it will work or not. The diff file also adds some comments to toolbox.cpp. Thanks to Gail for pointing me in the direction of that file, BTW, it would have taken me even longer to come up with a fix without her quick reply to my query. Finally, the diff file has some changes to a pair of makefiles which are a mystery to me; I never touched them, Gov'nor! Thomas

5 5

adding templates
by Alexandre Prokoudine 09 Nov '07

09 Nov '07

Hi, How do we decide if we add new templates? http://understandinglimited.com/2007/10/29/inscape2fontforge/ sounds like a perfect candidate to me :) Also, do we have any policy regarding new extensions - which ones we can bundle with the package and which ones we can't? Alexandre

2 1

Non-programming tasks
by Joshua A. Andler 09 Nov '07

09 Nov '07

Hey all, It seems like a good time to discuss non-programming related items given the icon conversation. I figure we can get some thoughts out on the list and work from there. Basically, let's try and free the people who program from the tasks that the rest of us can do. ;) It's common for people to say "well if I could program I'd...", well, if you can't, but want more programming done on inkscape... here's your chance! The website: Realistically, we should probably have 2 or 3 volunteers that will agree to submit at least 1 news item per month. Bryce shouldn't be the only one. ;) It seems like it should be a fairly minimal commitment. I'm willing to fill one of those spots myself. I'll throw together something before the end of the week that talks about the persistent undo history that the MIT students are working on, and link to their page. Bryce, are you even still interested? On top of that, do you have the time? Either way, it is not difficult to find a couple news worthy items per month. Any other takers? Tutorials: Ryan Lerch and myself started to do some tutorial work for this development cycle a while back. I haven't contributed to this for a couple months as it seemed like there were still a number of changes going on at that point (plus a very busy schedule on my end). Luckily, it appears things are slowing down now on both fronts, so it seems like an opportune time to pick this back up. It's good for us to have more tutorials that focus on using features of inkscape (such as the in-progress clipping/masking/patterns tutorial), rather than tutorials for doing a particular task (easter egg). Do we have any volunteers to help us with tutorial writing/updating? Current discussion and drafts can be found at: http://wiki.inkscape.org/wiki/index.php/TutorialUpdates-0.46 Also, as for tutorial localization and to attempt simplifying our files and the process for translators, I know there was discussion in the past about po2xml. Can anyone enlighten me on if this has change has been done? I've not updated my checkout of the tutorials in quite a while. If not, is this a huge task? Will there be any changes in formatting or the process for tutorial writers? Screenshots: Okay, do we think that artsy screenshots are in order yet? I have one that utilizes a number of filters, but a key piece of filter rendering is not correct (it's using turbulence). I also have an in-progress one that I'm using some filters on, but more importantly going to town with live path effects. Curve stitching is turning out to be my favorite feature in this dev cycle. :) The About screen: I just want to follow up on this. I know we're most likely not ready to go for it yet (as there are a number of filter bugs remaining). But I am just wondering if we think we're getting closer. Also, did Jon Phillips want to host this via ocal or create? Or are we going deviantART again? Just want to coordinate. Bugs & Feature Requests: Another area that generally needs attention is our bug and rfe trackers. It is always a big help if people can go through bug reports & feature requests and try to close duplicates, reproduce bugs, ask for more information where necessary, etc. Unfortunately, people submit items without searching the trackers first, so duplicates are quite common. Also, it's common that people will file a report and the issue is resolved in a development cycle, but they never come back to say that the issue has been fixed for them. Another common issue is anonymous bug reports. These get reported and never followed up on by the original poster as there is no way for us to contact them (these are fairly common to get fixed, but we don't get confirmation from those people). Anyone interested in helping with these that doesn't have access, please let us know. Thank you all for your time. -Josh P.S. Unrelated, is the 3d box tool not going to be activated for the next release?

9 14

Re: [Inkscape-devel] Inkscape demo import
by Bryce Harrington 09 Nov '07

09 Nov '07

On Thu, Nov 08, 2007 at 09:31:11PM -0500, James Henstridge wrote: > On 08/11/2007, Bryce Harrington <bryce@...961...> wrote: > > Bugs appear reported in future > > ------------------------------ > > On this bug (and possibly others), the dates associated with > > buliabyak-users are in the future (2011, 2012). > > > > E.g. https://bugs.demo.launchpad.net/inkscape/+bug/157587 > > This is a case of garbage in, garbage out. Take a look at the > submission date of the source bug: > > http://sourceforge.net/tracker/index.php?func=detail&aid=1218610&group_id=9… Aha, ok our bad. I wonder how this happened. In any case, now that we know it's not caused by the import this issue can be ignored. > > Category mapped to milestones > > ----------------------------- > > For Inkscape, we used the SF Category to tag bugs by type. These appear > > to have been mapped to milestones by the converter, however. Instead, > > can you have the Categories just mapped into LP tags? > > The categories are being mapped to tags. It is the groups that are > being mapped to milestones (this is how Python was using bug groups). > I can certainly update the import to map groups to tags as well > though. That'd be great. Yes, since SF left both these things rather freeform it's not a surprise that different projects used them in different ways. Mapping both cats and groups to tags would be best for Inkscape. > > Missing Attachments > > ------------------- > > In a number of cases the bug attachments didn't come through correctly. > > Here is one example: > > > > SF.net > > http://sourceforge.net/tracker/index.php?func=detail&aid=1816893&group_id=9… > > Launchpad > > https://bugs.demo.launchpad.net/inkscape/+bug/159964 > > This is a display bug with Launchpad where it does not list > attachments associated with the first comment in the main content. > The attachment is visible in the attachments portlet on the left > though. You can also see it when viewing just the initial comment: > > https://bugs.demo.launchpad.net/inkscape/+bug/159964/comments/0 > > I am pretty sure we have a bug open for this, but don't have it handy. Aha, there it is. That would be a good bug to see fixed, but for now we'll just make a note to look in the portlet for attachments. (I hadn't ever noticed that before.) > > Fix Committed State > > ------------------- > > It appears that the 'Pending' state in SF was mapped to 'Fix Committed' > > in launchpad. We never really understood what 'Pending' meant, but > > what we used it for in Inkscape is more like the "Incomplete" state, so > > it should be mapped to that. > > Fair enough. If you have a preferred mapping from SF.net statuses and > resolutions to Launchpad statuses, I can tweak the import to match. Sure, here is how I'd map it, although this is only after a few minutes' thought, so there could be better mappings... Open Closed Deleted Pending None New Fix Released Invalid Incomplete Accepted Confirmed Fix Released Invalid Incomplete Fixed Fix Committed Fix Released Invalid Fix Committed Duplicate Invalid Invalid Invalid Invalid Invalid Invalid Invalid Invalid Invalid Out of Date Invalid Invalid Invalid Invalid Rejected Invalid Invalid Invalid Invalid Won't Fix Invalid Invalid Invalid Invalid Later In Progress Invalid Invalid In Progress Postponed In Progress Invalid Invalid In Progress Remind In Progress Invalid Invalid In Progress Works For Me In Progress Invalid Invalid In Progress > > Inconsistant Bug Stats > > ---------------------- > > The bug numbers in Launchpad show: > > > > Open 1144 > > Critical 43 > > New 809 > > Unassigned 826 > > All bugs ever reported 5536 > > > > while on sf we have: > > > > # Bugs : (801 open / 3,727 total) > > # Patches : (27 open / 828 total) > > # Feature Requests : (1,022 open / 2,183 total) > > > > We're curious how the numbers are arrived at, and what causes the stats > > discrepancies? > > > > (I'm guessing it's just due to terminology differences between SF and LP > > status, but am uncertain how they get mapped through.) > > So the break down I see in the database is: > > NEW: 809 > INVALID: 1993 > CONFIRMED: 312 > INPROGRESS: 5 > FIXCOMMITTED: 18 > FIXRELEASED: 2399 > UNKNOWN: 16 > Total: 5552 > > The counts shown on the Launchpad page omit duplicate bugs which would > account for a small part of the discrepency. The 16 unknowns are > pre-existing bug tasks that have bug watches pointing at SF.net. > > I think the numbers here should be a bit higher, so it does look like > some of the bugs got left out of the dump. I'll investigate and get > back to you on this. Cool, thanks. > > Map priority 5 bugs to New/Undecided status > > ------------------------------------------- > > By default, SourceForge sets the priority of newly reported bugs to 5. > > We found this irritating since it interferes with triaging the > > priorities of bugs. So as a hack-around we decided that priority 5 > > actually means "unprioritized". > > > > Can you set the script to map priority-5 bugs to be New/Undecided? > > We currently map "Open" bugs with no assignee and not in Accepted > state to NEW. So I guess mapping priority 5 to an unset importance > would solve this, right? Yes, that would do it. Thanks again! Bryce

1 0

Methods hiding others
by Jon A. Cruz 08 Nov '07

08 Nov '07

Aside from other warnings, I've spotted some of these. Given that they are around the path effects, there might be something to them. ./live_effects/effect.h:99: warning: 'virtual NArtBpath* Inkscape::LivePathEffect::Effect::doEffect(NArtBpath*)' was hidden ./live_effects/lpe-slant.h:27: warning: by 'virtual void Inkscape::LivePathEffect::LPESlant::doEffect(SPCurve*)' ./live_effects/effect.h:101: warning: 'virtual std::vector<Geom::Path, std::allocator<Geom::Path> > Inkscape::LivePathEffect::Effect::doEffect(std::vector<Geom::Path, std::allocator<Geom::Path> >&)\ ' was hidden ./live_effects/lpe-slant.h:27: warning: by 'virtual void Inkscape::LivePathEffect::LPESlant::doEffect(SPCurve*)' ./live_effects/effect.h:103: warning: 'virtual Geom::Piecewise<Geom::D2<Geom::SBasis> > Inkscape::LivePathEffect::Effect::doEffect (Geom::Piecewise<Geom::D2<Geom::SBasis> >&)' was hidden ./live_effects/lpe-slant.h:27: warning: by 'virtual void Inkscape::LivePathEffect::LPESlant::doEffect(SPCurve*)'

4 7

Re: [Inkscape-devel] Inkscape demo import
by Bryce Harrington 08 Nov '07

08 Nov '07

On Wed, Nov 07, 2007 at 12:59:05PM -0500, James Henstridge wrote: > Hi Bryce, > > I've completed the demo import of Inkscape bug reports. You can view > the results here: > > https://bugs.demo.launchpad.net/inkscape/ Hi James, We've had some time to review the demo site and poke around a bit. In general it looks really good, however some people spotted a few things that look incorrect. Thanks, Bryce Bugs appear reported in future ------------------------------ On this bug (and possibly others), the dates associated with buliabyak-users are in the future (2011, 2012). E.g. https://bugs.demo.launchpad.net/inkscape/+bug/157587 Category mapped to milestones ----------------------------- For Inkscape, we used the SF Category to tag bugs by type. These appear to have been mapped to milestones by the converter, however. Instead, can you have the Categories just mapped into LP tags? Missing Attachments ------------------- In a number of cases the bug attachments didn't come through correctly. Here is one example: SF.net http://sourceforge.net/tracker/index.php?func=detail&aid=1816893&group_id=9… Launchpad https://bugs.demo.launchpad.net/inkscape/+bug/159964 Fix Committed State ------------------- It appears that the 'Pending' state in SF was mapped to 'Fix Committed' in launchpad. We never really understood what 'Pending' meant, but what we used it for in Inkscape is more like the "Incomplete" state, so it should be mapped to that. Inconsistant Bug Stats ---------------------- The bug numbers in Launchpad show: Open 1144 Critical 43 New 809 Unassigned 826 All bugs ever reported 5536 while on sf we have: # Bugs : (801 open / 3,727 total) # Patches : (27 open / 828 total) # Feature Requests : (1,022 open / 2,183 total) We're curious how the numbers are arrived at, and what causes the stats discrepancies? (I'm guessing it's just due to terminology differences between SF and LP status, but am uncertain how they get mapped through.) Map priority 5 bugs to New/Undecided status ------------------------------------------- By default, SourceForge sets the priority of newly reported bugs to 5. We found this irritating since it interferes with triaging the priorities of bugs. So as a hack-around we decided that priority 5 actually means "unprioritized". Can you set the script to map priority-5 bugs to be New/Undecided?

1 0

Launchpad Inkscape demo
by Bryce Harrington 08 Nov '07

08 Nov '07

Hi all, The Launchpad crew have run the import scripts and set up our info on the Launchpad demo site: https://demo.launchpad.net/inkscape I'll post some tips and tricks for getting good use out of Launchpad later on, but for now please just review the bugs and see if you spot any major issues with the import. Bryce ----- Forwarded message from James Henstridge <james@...1829...> ----- Date: Wed, 7 Nov 2007 12:59:05 -0500 From: James Henstridge <james@...1829...> To: bryce@...1798... Subject: Inkscape demo import Hi Bryce, I've completed the demo import of Inkscape bug reports. You can view the results here: https://bugs.demo.launchpad.net/inkscape/ As I mentioned previously, the demo server uses a whitelist to filter outgoing email traffic. I can add addresses on request. For developers who already have Launchpad accounts, it will be necessary to merge the $USER@...58... account with their existing one. This can be done at: https://demo.launchpad.net/people/+requestmerge I've added two of your bryce@...961... and bryce@...58... accounts to the whitelist so you can test this. Just enter the users.sourceforge.net email into the form and you should get an email to confirm the merge. Developers/users without a Launchpad account can register with their users.sourceforge.net account to claim their bugs. They can then add additional email addresses to the account as normal. James. ----- End forwarded message -----

5 7

Bad markup found in translation. (SVN Build 16449)
by Frank Stützer 08 Nov '07

08 Nov '07

Hi, i want to build the svn version on OS X 10.5. But i get an error: make[3]: Nothing to be done for `all'. make[3]: Nothing to be done for `all-am'. Making all in po file=`echo km | sed 's,.*/,,'`.gmo \ && rm -f $file && /sw/bin/msgfmt -o $file km.po file=`echo sk | sed 's,.*/,,'`.gmo \ && rm -f $file && /sw/bin/msgfmt -o $file sk.po LC_ALL=C ./intltool-merge -d -u -c ./po/.intltool-merge-cache ./po inkscape.desktop.in inkscape.desktop Found too-old cached translation database Generating and caching the translation database Merging translations into inkscape.desktop. km.po: parsing error for `<khoemsokhem@...1503...> Auk Piseth <piseth_dv@...1761....1503... > Eng Vannak <': #. TRANSLATORS: Put here your name (and other national contributors') #. one per line in the form of: name surname (email). Use \n for newline. #: ../src/ui/dialog/aboutbox.cpp:336 msgid "translator-credits" msgstr "Khoem Sokhem <khoemsokhem@...1503...> Auk Piseth <piseth_dv@...1830...... > Eng Vannak <evannak@...1503...)" WARNING: Bad markup found in translations. Please consider fixing the above problems. thanks for help, Frank

1 0

Fwd: Launchpad Inkscape demo
by bulia byak 08 Nov '07

08 Nov '07

---------- Forwarded message ---------- From: bulia byak <buliabyak@...400...> Date: Nov 7, 2007 5:42 PM Subject: Re: [Inkscape-devel] Launchpad Inkscape demo To: Bryce Harrington <bryce@...961...> On 11/7/07, Bryce Harrington <bryce@...961...> wrote: > Hi all, > > The Launchpad crew have run the import scripts and set up our info on > the Launchpad demo site: > > https://demo.launchpad.net/inkscape How the different bug categories got translated? it has: Open 1144 Critical 43 New 809 Unassigned 826 All bugs ever reported 5536 while on sf we have: # Bugs : (801 open / 3,727 total) # Patches : (27 open / 828 total) # Feature Requests : (1,022 open / 2,183 total) The numbers do not match somehow. Please clarify. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

3 2

Exception catching?
by unknown＠example.com 08 Nov '07

08 Nov '07

Have a look at the code below: (ui/dialog/filedialogimpl-gtkmm.cpp, lines 208 and onwards) Glib::RefPtr<Gdk::Pixbuf> img(NULL); try { img = Gdk::Pixbuf::create_from_file(fileName); } catch (Glib::FileError e) { g_message("caught Glib::FileError in SVGPreview::showImage"); return; } catch (Gdk::PixbufError e) { g_message("Gdk::PixbufError in SVGPreview::showImage"); return; } This should catch the Gdk::PixbufError, right? Or add catch(...) for good measure. Both do *not* catch Gdk::PixbufError. What is happening? Please have a look at: http://sourceforge.net/tracker/index.php?func=detail&aid=1679218&group_i d=93438&atid=604306 Thanks for clearing this out, Johan

1 0