Re: Firefox problem printing big fonts [SOLVED]
Christoph Moench-Tegeder writes: > ## Andrea Venturoli (m...@netfence.it): > >> > Uh, define "illegible crap". Wrong glyphs? Bad rendering (blocky pixels, >> > blurry?)? >> More "something blocky, vaguely, *really* vaguely, resembling the >> indended text": something you can read only if you already know what >> it says. > > That sounds familar, but... > >> Deleting all X.org 75-dpi and 100-dpi fonts solved this. > > I drop this into fonts/conf.d/, and it helps: > > > > > > >false > > > > > > I have no idea where I got that from (looks like a late-night fix, git log > is not that helpful here), and it really looks somewhat overly broad, but > I can avoid breaking dependencies with that. Should find a real fix... See also https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225744 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeCAD 0.17 - is anyone using it?
## Torfinn Ingolfsen (tin...@gmail.com): > updated the ports tree again, and tried upgrading the FreeCAD port, > but the build fails as before. > I've put the build output and CMakeOutput.log (there is no > CMakeError.log) at > https://sites.google.com/site/tingox/asus_m5a78l_usb3_freebsd > in case it helps. Dams, it says -- Checking for module 'Coin' -- Found Coin, version 3.1.3 and then it explodes. I didn't get around to analyse this very deeply - instead I upgraded FreeCAD to 0.18 - does that change anything? Regards, Christoph -- Spare Space. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox problem printing big fonts [SOLVED]
## Andrea Venturoli (m...@netfence.it): > > Uh, define "illegible crap". Wrong glyphs? Bad rendering (blocky pixels, > > blurry?)? > More "something blocky, vaguely, *really* vaguely, resembling the > indended text": something you can read only if you already know what > it says. That sounds familar, but... > Deleting all X.org 75-dpi and 100-dpi fonts solved this. I drop this into fonts/conf.d/, and it helps: false I have no idea where I got that from (looks like a late-night fix, git log is not that helpful here), and it really looks somewhat overly broad, but I can avoid breaking dependencies with that. Should find a real fix... Gruss, Christoph -- Spare Space. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox problem printing big fonts [SOLVED]
On 3/17/19 7:03 PM, Christoph Moench-Tegeder wrote: Uh, define "illegible crap". Wrong glyphs? Bad rendering (blocky pixels, blurry?)? More "something blocky, vaguely, *really* vaguely, resembling the indended text": something you can read only if you already know what it says. My bookmark for "X11/Printing/Font Problems" is Arch Linux' page on that topic: https://wiki.archlinux.org/index.php/font_configuration Thanks a lot!!! My problem is the one described under the paragraph "Helvetica font problem in generated PDFs". Deleting all X.org 75-dpi and 100-dpi fonts solved this. Now, this also deinstalled net/tightvnc, but I guess I can find a replacement. bye & Thanks av. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Need Committer for PR 236113
Hi, I tested and submitted a patch via PR 236113 to unbreak sssd. Is there a committer that can commit the patch? — Rick -- Take care Rick Miller ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Fwd: FreeBSD ports you maintain which are out of date
On Sun, Mar 17, 2019 at 10:48:12AM +, Dima Pasechnik wrote: > > I just got an email from portscout about > www/squidclamav/ port. Indeed, it has no maintainer: > https://www.freshports.org/www/squidclamav/ > > but the point of this email is a total mystery, probably just an > error, no? I never touched this port, for sure... > > I think it's OK if once upon a time an email listing all the > un-maintained ports is sent around, > but otherwise it's merely spam. > You're subscribed to po...@freebsd.org mailing list, so you also receive portscout's mails to this address. Unmaintained ports have it as MAINTAINER address. Portscout only sents out a single mail when it finds a new upstream version, so it's no spam. Many ports unmaintained ports have received updates and some even got a new maintainer because of portscount's mails to this mailing list. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ www/squidclamav | 6.16| 7.1 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
