[03:03] good morning [07:11] good morning [07:12] hi jpnurmi [07:12] hi callmepk [07:16] Hi jpnurmi and callmepk [07:16] hi duflu [07:16] hi duflu [07:19] good morning desktoppers [07:19] Morning oSoMoN [07:21] hey duflu [07:21] hi oSoMoN [07:21] hey callmepk [07:33] hi oSoMoN [07:33] hey jpnurmi [07:57] good morning [07:59] Hi didrocks [08:00] hi didrocks [08:01] hey duflu, jpnurmi! [08:03] \_O_/ [08:06] Hi laney [08:31] goood morning desktopers [08:32] Hi seb128 [08:33] hey duflu, how are you? [08:33] seb128, improving thanks. You? [08:34] duflu, I'm alright thanks! [08:42] hey duflu seb128 [08:42] laney, hey, how are you? [08:45] Hi laney [08:57] Hi, I'm bluntly assuming that Deskop-people will know more than myself about fonts [08:57] I ahve a testcase which selects fonts via https://doc.qt.io/qtforpython-5/PySide2/QtGui/QFontDatabase.html?highlight=systemfont#PySide2.QtGui.PySide2.QtGui.QFontDatabase.systemFont [08:57] it asks for a fixed-with and gets "monospace" as identifier [08:57] later on it checks what it is effectively using and gets "Bitstream Vera Sans Mono" [08:58] that sounds like another abstraction layer for the default-monospace-font [08:58] is there a common config which does set the "Bitstream Vera Sans Mono" [08:58] or alternatively is there a general python way to translate this 'monospace' selection into the final "Bitstream Vera Sans Mono" [08:59] so that the test can use the latter for comparison? [09:00] I'm reading myself through /etc/fonts/* now, but even if it is configured there I'd not want to write a new parser for these config files :-) [09:02] Ok, /etc/fonts/conf.avail/45-latin.conf and /etc/fonts/conf.avail/60-latin.conf really seem to be what maps this font to 'monospace' [09:03] now I need a way to derive monospace->"Bitstream Vera Sans Mono" in python ... [09:12] cpaelzer, hey, I'm unsure if my IRC timeouted or not, I've some lag at least. We don't have much people familiar with fonts details but GunnarHj knows his way around so he might be able to help you with those questions [09:13] thanks seb128 [09:13] I'm slowly clawing my way into it, but any hint is welcome [09:14] I'll mention what I found here and if anyone has input let me know [09:14] I can get the object and from there derive some attributes [09:14] like https://doc.qt.io/qtforpython-5/PySide2/QtGui/QFontInfo.html#PySide2.QtGui.PySide2.QtGui.QFontInfo.family [09:14] giving me "Bitstream Vera Sans Mono" [09:15] and styleName() of the same object gives me "Roman" [09:15] but so far I lack a reliable way to get "back to monospace" [09:21] GunnarHj, seems DING has changed to whole version numbers and there's a version 20 now [09:22] monospace is the alias and Bitstream is the the font it selected, but do not try to search for alias/unalias - all you get is if rendering the font should be aliased :-/ [09:23] alias-meaning-overload [09:23] cpaelzer: I dunno exactly what you're testing, but fontconfig is the component that handles those configs you were looking into [09:23] e.g. $ fc-match monospace [09:24] cpaelzer: What does this command return: [09:24] fc-match monospace -a | head -10 [09:24] https://paste.ubuntu.com/p/r4gcqXQvJ5/ [09:24] that is the same direction that python already does from "monospace" -> "Bitstream Vera Sans Mono" [09:24] For the test (trying to fix an autopkgtest atm) to work I need the way back [09:25] "Bitstream Vera Sans Mono" -> "monospace" [09:25] cpaelzer: That's it, isn't it? Looks like you are on a machine without DejaVu. [09:30] I got it working, I needed to stop thinking to reverse it [09:30] instead I instantiated the "expected" result and can use that for the comparions [09:30] thanks GunnarHj, laney and seb128 [09:32] cpaelzer: A test which relies on Bitstream being the preferred monospace font sounds fragile to me. On e.g. standard Ubuntu you'd see "DejaVu Sans Mono". [09:32] GunnarHj: that isn't what it is doing [09:32] it was selecting the default "fixed-font" which gave it "monospace" [09:32] then it used "monospace" to initialize its app [09:33] and eventually it tested if the effective font being used matched that "monospace" [09:33] but since "monospace" was only an alias it might select Bitream, DejaVu or others depending on what is configured and installed [09:34] I had to make the commands that define the "expected font" also to "instantiate" the monospace font [09:34] that way it gets whatever is currently configured for that alias [09:34] and that it can compare the applications behavior against [09:35] I hope I explained it using the right terms, does it make sense to you now GunnarHj ? [09:35] cpaelzer: So if I understand it correctly, you need a way to confirm that the actually used font is a "monospace" one. [09:36] yeah, sort of [09:36] and that in Qt for python if possible :-) [09:37] but as I said, I think I'm good now [09:37] that seems to do it and does not seem too crazy to me https://paste.ubuntu.com/p/B9MQd8pzhx/ [09:38] It is at least enough to open an upstram issue and PR - if they prefer to do it different that is fine [09:40] cpaelzer: Ok, great. I fear that my skill level doesn't suffice to suggest a different way. ;) [09:49] duflu: Hey, 20 came fast, we are effectively on 19 on impish. Would it help to update to 20? [09:52] GunnarHj, no hurry. If the fix I'm working on ends up in the extension then it won't be till at least 21 [09:54] duflu: Ack. Btw, do you have an opinion about those clutter dependencies which was added and then dropped? Do you agree they are redundant? [09:59] duflu: https://gitlab.com/rastersoft/desktop-icons-ng/-/commit/c3afe696 [09:59] Commit c3afe69 in rastersoft/desktop-icons-ng "Remove clutter dependency" [10:03] GunnarHj, I am not familiar with the changes but generally speaking it's the right thing to do [10:13] duflu: Ok. The day before yesterday I made an upload only to add such deps: [10:13] https://launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/0.18.0-0ubuntu3 [10:13] But I can drop them again when doing the next update... :/ [10:17] GunnarHj, I know it's annoying [13:52] https://www.youtube.com/watch?v=o9z8a9loDoc GUADEC is on [19:21] pango tags a4e4364 Marco Trevisan upstream/1.48.7+ds1 * Upstream version 1.48.7+ds1 * https://deb.li/323fG [19:22] pango upstream/latest af0197f Marco Trevisan * pushed 145 commits (first 5 follow) * https://deb.li/NCr1 [19:22] pango upstream/latest 39e3fc3 Matthias Clasen pango/pangofc-fontmap.c * Clarify docs of pango_fc_fontmap_get_config * https://deb.li/igyTN [19:22] pango upstream/latest b7313d6 Matthias Clasen pango/pangofc-fontmap.c * Merge branch 'get-config-docs' into 'master' * https://deb.li/2CcR [19:22] pango upstream/latest bf4050c Matthias Clasen pango/pangofc-fontmap.c * fc: Drop a broken optimization * https://deb.li/3h54v [19:22] pango upstream/latest f4d37b8 Matthias Clasen pango/pangofc-fontmap.c * Merge branch 'drop-broken-optimization' into 'master' * https://deb.li/81yz [19:22] pango upstream/latest a492afd Jan Alexander Steffens (heftig) tests/test-common.c * tests: In attribute_from_string, parse offsets as long long * https://deb.li/3N3Ds [19:22] pango pristine-tar 77ca723 Marco Trevisan (TreviƱo) pango1.0_1.48.7+ds1.orig.tar.xz.delta pango1.0_1.48.7+ds1.orig.tar.xz.id * pristine-tar data for pango1.0_1.48.7+ds1.orig.tar.xz * https://deb.li/R3GI [19:23] seb128: when you've a sec please sync pango (fixes i386) ^ [19:29] Trevinho, yes [19:29] not sure if it's already available for syncing, but well... [20:42] hey, another candidate for syncing might be meson 0.59.0-1 :)