| | <<<Back 1 day (to 2018/04/10) | 20180411 |
| tor8 | sebras: LGTM. | 09:46.17 |
| sebras | tor8: thanks. | 10:15.12 |
| | tor8: done! :) | 10:15.20 |
| | tor8: wow. did you see 699207, it seems we've got a _pascal_ bug..?! | 10:19.55 |
| | I'm guessing this is the wrapper https://github.com/blestan/lazmupdf | 10:21.47 |
| Robin_Watts | Which relies on sumatraPDF to make the DLL | 10:22.47 |
| | and I bet that's not our current version. | 10:22.54 |
| sebras | Robin_Watts: probably not. | 10:23.09 |
| Robin_Watts | yeah, the bindings are 5 years old. | 10:23.22 |
| sebras | Robin_Watts: yup, just noticed. | 10:23.29 |
| Robin_Watts | So this ain't going to be current code? | 10:23.38 |
| | Version 1.12. | 10:23.57 |
| | sebras: Are you replying to that bug? | 10:35.13 |
| | (or investigating it?) | 10:35.27 |
| | If not, I'll put a quick note on it. | 10:35.34 |
| sebras | Robin_Watts: I'm first sending a license issue thing to the maintainer of the glue library. does this sound correct to you? https://pastebin.com/raw/W8n7dJUn | 10:40.43 |
| Robin_Watts | sebras: Only my standard "GNU AGPL" rather than "AGPL" objection. | 10:41.48 |
| | And is there any such thing as AGPLv3? | 10:42.02 |
| | I thought the GNU AGPL was always based on the GNU GPL v3 ? | 10:42.26 |
| sebras | added GNU | 10:42.28 |
| | Robin_Watts: there was an AGPLv2 | 10:42.55 |
| Robin_Watts | Otherwise looks good. | 10:42.56 |
| | Was there? I stand corrected then. thanks. | 10:43.05 |
| sebras | Robin_Watts: and AGPLv1 | 10:43.06 |
| | Robin_Watts: I think one of the issues the fixed licensingwise with GPLv3 and AGPLv3 was to make them compatible in one direction while GPLv2 vs AGPLv2 was not. | 10:43.50 |
| Robin_Watts | sebras: I wonder if a version of that text is worth us keeping in the twiki somewhere. | 10:44.06 |
| sebras | Robin_Watts: but I'm having a serious cold, so this could be my coming fever talkinig... ;) | 10:44.12 |
| Robin_Watts | So we can just cut/paste it rather than recreate it each time. | 10:44.28 |
| Robin_Watts | is having visions of constructing a set of progressively insistent template emails stuff like the welcome message(s) the heart of gold gets as it approaches Magrathea. | 10:46.04 |
| sebras | Robin_Watts: on open to suggestions/edits: https://twiki.ghostscript.com/do/view/MuPDF/Licensing | 10:55.18 |
| | Robin_Watts: if I put it in an incorrect location, I might need advice on how to move it, and where to. | 10:55.49 |
| Robin_Watts | That looks like a good place. | 10:57.05 |
| | "it would be easiest for you to distribute *it*" | 10:57.20 |
| | what "it" are you talking about? The project, or the compiled binary? | 10:57.36 |
| sebras | their project. | 10:57.48 |
| Robin_Watts | Cos it reads like "it" = "the compiled version of MuPDF" | 10:58.02 |
| | s/it/your entire project/ | 10:58.15 |
| sebras | Robin_Watts: refresh. :) | 10:58.22 |
| | Robin_Watts: I was replacing it as you suggested the new text. :) | 10:58.42 |
| Robin_Watts | nice. | 10:58.43 |
| | :) | 10:58.53 |
| sebras | Robin_Watts: I need some advice. | 11:31.18 |
| | Robin_Watts: I found a fork of the previous repo over at https://github.com/n1tehawk/lazmupdf but the user is using a no-reply github address for all commits in his repos. and there doesn't seen to be any way to register an issue. | 11:31.52 |
| | Robin_Watts: he is however also hosting a mirror of the mupdf repo on his account (correctly licensed under AGPLv3) https://github.com/n1tehawk/mupdf | 11:32.28 |
| Robin_Watts | So, the user in question is n1tehawk ? | 11:32.56 |
| sebras | Robin_Watts: yes. | 11:33.02 |
| | Robin_Watts: I can't come up with a way to contact him to mention the license issues in his lazmupdf clone. | 11:33.21 |
| Robin_Watts | I can't see any address for him at all. Where are you seeing the "no-reply" one ? | 11:34.01 |
| sebras | Robin_Watts: I cloned several of his repos and did git log | 11:34.21 |
| | Robin_Watts: comes up as NiteHawk <n1tehawk@users.noreply.github.com> | 11:34.36 |
| | some googling told me that this is the result of setting your github repo to some kind of private e-mail asetting. | 11:34.57 |
| Robin_Watts | Well, if we can't email him, and we can't raise an issue on a tracker, that leaves us few options. | 11:37.03 |
| | Either we could report the user's behaviour (which isn't really appropriate, cos I think that's for abusive behaviour) | 11:39.31 |
| | Or we could file a DMCA takedown. | 11:39.41 |
| | https://github.com/contact/dmca-notice | 11:39.47 |
| sebras | Robin_Watts: so some of his repos are related to sunxi-based platforms. the sunxi IRC channel is on freenode and somone named n1tehawk or NiteHawk has frequented these channels. and there is a NiteHawk looged in on freenode right now. perhaps I have a way after all. :) | 11:40.02 |
| Robin_Watts | fab. | 11:40.10 |
| Robin_Watts | pops for lunch. | 11:40.35 |
| tor8 | Robin_Watts: sebras: a number of commits on tor/master for review. how many should go into the release is up for debate. | 11:51.22 |
| sebras | tor8: "Fix output paths in VS2005 project files." I'm having a hard time having an opnion on. | 12:10.22 |
| | tor8: in "Rework how we handle DynaLab tricky fonts in freetype." we no longer call FT_Set_Char_Size() from fz_outline_ft_glyph(). | 12:13.51 |
| tor8 | FT_LOAD_NO_SCALE means to ignore FT_Set_Char_Size | 12:14.24 |
| sebras | would forcing FT_FACE_FLAG_TRICKY cause something similar..? | 12:14.25 |
| kens | sebras did you see the warning about gbat being uninitialised in your jbig2dec commits ? | 12:14.59 |
| sebras | kens: I did not. | 12:15.08 |
| tor8 | if force_hinting was set, we used to set a char_size and ask for hinting | 12:15.14 |
| | otherwise ask for an unscaled unhinted outline | 12:15.22 |
| kens | sebras: | 12:15.28 |
| | Ghostscript: | 12:15.29 |
| | new cppcheck warnings (Cppcheck 1.72): | 12:15.29 |
| | jbig2dec/jbig2_generic.c:761: error: Uninitialized variable: gbat | 12:15.29 |
| | http://miles.ghostscript.com:8080/artifex/c0f89bd215d700339429da4375a4eaf89445f872/gs-cppcheck.txt | 12:15.29 |
| tor8 | to work around FLAG_TRICKY not being set | 12:15.32 |
| kens | commit c0f89bd215d700339429da4375a4eaf89445f872 | 12:15.45 |
| sebras | kens: that code only changes whitespace for the line that uses gbat. | 12:16.50 |
| kens | yeah I wondered if it was an old warning being flagged | 12:17.11 |
| sebras | kens: not only that: http://git.ghostscript.com/?p=ghostpdl.git;a=blob;f=jbig2dec/jbig2_generic.c;h=714dc5658dc09c8eec30bb0e1b4c435211b30793;hb=HEAD#l714 | 12:18.37 |
| | kens: how on earth can gbat be uninitialized? | 12:18.44 |
| kens | possibly the code changed after that warning, and the line number is incorrect | 12:19.20 |
| | still looks unlikely though | 12:19.46 |
| sebras | kens: oh I see it now. in some locations params->gbat is populated with some entries, but perhaps not all, but here we print them all. | 12:20.39 |
| kens | Ah, you beat me to it. Is it at all worth worrying about ? | 12:20.58 |
| sebras | kens: we print a random data pointer value in our debug messages, i.e. if you raise the log level high enough it might crash. | 12:21.41 |
| kens | It seems like its only a debug print | 12:21.46 |
| sebras | it is, but I think you can coax jbig2dec from the commandline to print it anyway. | 12:22.09 |
| kens | but its not a problem for a print if the memory is uninitialised | 12:22.47 |
| sebras | kens: oh, we're just printing uninitialized values, that wouldn't result in a crash. | 12:22.48 |
| | no, I just realized. | 12:22.56 |
| kens | :-) | 12:23.00 |
| | So I think its not worth worrying about | 12:23.06 |
| sebras | kens: thanks for pointing it out though, it might have been something serious. | 12:25.14 |
| kens | Its an automated email | 12:25.31 |
| | I'm surprised you don't get it :-) | 12:25.39 |
| sebras | kens: same as last time. :) | 12:29.54 |
| kens | :) | 12:30.04 |
| sebras | tor8: right, so we're forcing FT_FACE_FLAG_TRICKY to be se to make freetype do hinting. | 12:43.27 |
| tor8 | sebras: in essence, yes. | 12:52.55 |
| | 'tricky' fonts are ones that abuse the truetype font hinting bytecode to do more than just hinting | 12:53.13 |
| bilabila | Hi, I found I can't use fcitx in mupdf's search input. But in 'zathura-pdf-mupdf' I can | 14:27.07 |
| | my version is 1.12.0-2 | 14:35.48 |
| wwarner | hello | 23:07.39 |
| mubot | Welcome to #mupdf, the channel for MuPDF. If you have a question, please ask it, don't ask to ask it. Do be prepared to wait for a reply as devs will check the logs and reply when they come on line. | 23:07.39 |
| wwarner | i'm using mupdf draw to produce bounding boxes over an image | 23:08.07 |
| | Forward 1 day (to 2018/04/12)>>> | |
Log of #mupdf at irc.freenode.net.