- Inkscape Devel - Inkscape Mailman

Inkscape, Pango, Language Tags and Marshallese
by Jeremy Tan 22 Feb '16

22 Feb '16

Hello all. It is well-known that Inkscape uses Pango for text rendering. What I have found is that it doesn't yet support language tags for locale-specific rendering of glyphs. The context for this is a font I'm now developing that has separate glyphs for the Marshallese language <https://en.wikipedia.org/wiki/Marshallese_language>. It has five problematic letters – L, M, N, O with cedilla and N with macron; in particular M-cedilla, O-cedilla and N-macron aren't even in Unicode yet and while the other two characters are in, they usually display commas for Latvian, which is considered unacceptable for Marshallese. My font has the proper glyphs. SVG is a kind of XML and so the xml:lang attribute can be used to set the language of a certain piece of text. For example, if you wanted to say that some text is Polish you would put xml:lang="pl" as an attribute of the text (not tspan) object that contains the Polish text. These are ISO 639 two-letter codes that are used here, so for Marshallese the letters mh would be used. To ensure that the proper glyphs are displayed for the language in question, OpenType has the localised forms feature, which substitutes one glyph for another if the text is in a particular language. For my case, my font substitutes the replacements used by the online Marshallese–English dictionary (see here <https://en.wikipedia.org/wiki/Marshallese_language#Display_issues> for the replacements) with the typographically correct glyphs. So far, so good. But then I concocted an SVG demo with two sets of the replacement characters, one of which had xml:lang="mh" so it would display correctly in Marshallese. It worked fine in my browser, but the language tag was ignored when I opened it in Inkscape (see the attachment). I am not in a hurry over this, but I would appreciate it if someone could add support for the as-yet-unsupported OpenType features to Inkscape. Pango itself is perfectly capable of handling these features, so I'm suspecting it won't be hard. Parcly Taxel, Princess of Science

2 1

How does font size work?
by Tobias Ellinghaus 20 Feb '16

20 Feb '16

Hi, in IRC there was a discussion about the font size setting and I have to admit that I don't understand it. The tooltip says the value is in pt, which (according to the CSS specs) is 1/72th of an inch. Inkscape now uses a DPI of 96 to convert to/from pixels. When I type some text in 72 pt and then select the object the control bar tells me it's size was 6.72 mm, which would be 0.264566929134 inch [0] and that is 25.4 pixel [1], which is what I can see in the XML being stored. The part I don't understand is how that value relates to the initial 72 pt? And is it a coincidence that the final result of 25.4 is the conversion factor inch/mm? Some clarification or links to documentation would be appreciated. Tobias PS: Would it be possible to fix the font size box to show "nice" values and not some rounded numbers? Maybe just storing the pt value typed by the user along the converted px value and showing that? Or doing it the right way and putting the pt verbatim into the SVG as it used to be done? Currently it's really hard to do any serious work that involves text. [0] 6.72 / 25.4 = 0.264566929134 [1] 0.264566929134 * 96 = 25,3984251969 ~ 25.4

7 10

Competition News
by Martin Owens 18 Feb '16

18 Feb '16

Dear Inkscapers, A competition to design a t-shirt has been announced: https://inkscape.org/en/news/2016/02/18/fossasia-and-openclipart-t-shirt-de… I'd like to use this as a test of our media handling network capabilities. If you look after our facebook, twitter, google+ deviantArt accounts, please post the news above and send me a personal email when complete. (some of these accounts are in the shared password file, but I'm interested in people's ability to post news) Website and Mailing Lists have been completed. Best Regards, Martin Owens

2 2

unable to commit to lib2geom, or maybe just confused
by alvinpenner 18 Feb '16

18 Feb '16

I was attempting to correct a minor logic error that was causing LP Bug 1545632 see : https://bugs.launchpad.net/inkscape/+bug/1545632/comments/2 - so I did a bzr pull on lib2geom in order to synch. - I got an error message saying the branches had diverged and I could not pull - so I did a 'bzr pull lp:lib2geom --overwrite' - this 'worked' but now the version-info is wrong: C:\Users\Alvin\AppData\Roaming\lib2geom>bzr version-info revision-id: git-v1:8c1148600de95edb26f6d6fd45c849a62ed77b88 date: 2016-02-10 23:24:32 -0800 build-date: 2016-02-18 07:37:01 -0500 revno: 2499 branch-nick: lib2geom According to : https://code.launchpad.net/~lib2geom-hackers/lib2geom/trunk the correct version number is 2483 on Feb 5, not 2499 on Feb 10. - also the committer is git, not sure why So now I am reluctant to proceed any farther because I do not know which version is correct, I will make the appropriate change in Inkscape trunk instead. confused, Alvin -- View this message in context: http://inkscape.13.x6.nabble.com/unable-to-commit-to-lib2geom-or-maybe-just… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

2 3

Web Chat Review
by Martin Owens 18 Feb '16

18 Feb '16

Dear Users and Developers, I've put together an integrated tutorial for the irc chat on inkscape.org and I'd like a few users and support contributors to give it a review: https://inkscape.org/en/*users/chat/ You should see a few things are different now: * You must be logged in to use the chat, previously you could be anonymous. You even must have an email configured, so facebook and twitter logins must update their user profile before chatting. * There is the above guide which add the can_irc permission to a user's account. Confirming they've seen every page (I shorted it to 4 pages). * There's a new IRC bot that offers these new commands: - webbot: whois [username] ; will tell you who a user is and a link to their website profile, in case someone joins the chat asks a question and then leaves without waiting. - webbot: tell [username] [msg] ; will send an alert to the user with a possible response. The default for website message alerts is to email them too. So you can respond to someone who just left. - Get Latest Art ; a bit of fun to return the latest item in the Artwork category on the live site. Returns the link. - If you want further integrations between irc and the website, this is now possible. (maybe good for meetings in the future) I'm hoping these tools will allow users to feel comfortable chatting with us and also provision support contributors with what they need when in chat. The exact text of the above tutorial is up for review here. Please let me know your suggestions by email on list. Thanks everyone! Best Regards, Martin Owens

4 5

updated to rev 14658, problem in the make
by mathog 18 Feb '16

18 Feb '16

Hi, On a Ubuntu box just did: bzr update make it ran through configure (with no obvious problems) and began compiling but failed with: make[3]: *** No rule to make target `2geom/viewbox.cpp', needed by `2geom/viewbox.o'. Stop. The file 2geom/viewbox.o is still there from the last build a month ago. There is no viewbox.cpp in the 2geom directory. Just me? How to unjam this? I think it was at 14619 before the update, and it built with no issues. Thanks, David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech

2 1

Feedback needed: Fallback for 'arc's line join.
by Tavmjong Bah 17 Feb '16

17 Feb '16

Hi, The currently specified fallback for the 'arcs' line join is a 'miter' join. It has be noted that this is not a very good fallback. I've implemented three different alternative fallback strategies in trunk as part of the 'Join Type' LPE in trunk. The SVG WG has agreed to change the fallback to one of these depending on user input. Here is your chance to help influence the SVG 2 specification! For a quick introduction, see: http://tavmjong.free.fr/SVG/LINEJOIN_STUDY/#arcs To test: 1. Create a path with a number of corner nodes. 2. Open the LPE dialog (Path->Path Effects, CTRL-SHIFT-7) 3. Click on the '+' button, select 'Join Type', and click the 'Add' button. 4. Increase the 'Line width' to some number (~20 to ~100) 5. Select the various "Extrapolated arc" 'Join' types. 6. Move the handles around and observe the line join shape. Note: There are a number of bugs, for example, setting the Miter limit doesn't always work. Also, if the radius of curvature of the path is very small you might get strange artifacts. For this exercise, please ignore these. Thanks, Tav

4 6

C++11 configure fix
by Krzysztof Kosiński 16 Feb '16

16 Feb '16

If anyone has a distribution that requires C++11 to compile against gtkmm, please test this fix: https://code.launchpad.net/~tweenk/inkscape/cpp11-configure-fix Best regards, Krzysztof

2 15

Travis CI + Inkscape
by Krzysztof Kosiński 16 Feb '16

16 Feb '16

https://travis-ci.org/tweenk/inkscape/builds/109310104 The build takes 15 minutes with Clang and 21 minutes with GCC, so we have considerable headroom (the limit for OSS projects is 50 minutes). I have the dependencies figured out for OSX, but a configure fix is needed, because the glibmm shipped by homebrew is already C++11-only. Best regards, Krzysztof

2 4

Create releases more regularly
by Sebastian Zartner 15 Feb '16

15 Feb '16

Hi there, I initially asked at inkscapeforum.com<http://www.inkscapeforum.com/viewtopic.php?f=22&t=15755&p=63224>and was told to better post my request to this mailing list. I wonder if it wouldn't be possible to create releases more regularly. Currently there are many months or even years between each release of Inkscape. Bug fixes should get out more quickly and it should be possible to try out new features of upcoming versions. Most users don't have the possibility to build Inkscape by their own, so they have to wait for the next release. Unfortunately the provided development downloads are not synchronized, hosted on different third-party web sites and out of date (currently especially the Windows version). So I suggest to create a (more or less) fixed fast release cycle for normal releases (e.g. every two or three months) and periodically (e.g. every one or two weeks) create alpha versions. Alpha versions should be built (maybe even automatically) for all supported OSes and hosted directly on inkscape.org. Sebastian

17 40