Re: [blfs-support] Font issues
On 06-11-2014 04:21, Simon Geard wrote: > On Wed, 2014-11-05 at 17:34 -0600, Bruce Dubbs wrote: >> https://github.com/libical/libical/ >> >> There are glyphs for Issues, Pull Requests, Pulse, Graphs, Folders >> (F016), Regular files (F011), and a few other things. >> >> In any case, it's definitely a browser version thing on my every day >> system. On my development system I've got SM 2.29 and it's fine there. > > Basically, those byte ranges are reserved for private use - essentially, > for arbitrary symbols that don't map to regular unicode characters... > things like symbol fonts. > > That's what's happening here - they're using some CSS tricks to first > insert one of these odd characters immediately before (e.g a F016 for a > folder name), and using a special font which contains the relevant > characters. > > Info (if you're interested) at https://octicons.github.com/ > > > If it's not working for you, it's probably the age of your browser... I > think the ability to use font resources from the web is relatively > new... the past year or so. That is true! I had seen it before, didn't think about. FF and SM (both latest) did not give me the images, just the squares with codes, as Bruce has. But Midori *did* show me the folders and squares with lines (text) instead of codes. There are other images there, too, like one for .md file. It is a surprising result. -- []s, Fernando -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Font issues
On 05-11-2014 20:35, Ken Moffat wrote: > On Wed, Nov 05, 2014 at 08:20:38PM -0300, Fernando de Oliveira wrote: >> On 05-11-2014 19:36, Bruce Dubbs wrote: >>> Fernando de Oliveira wrote: On 05-11-2014 18:20, Bruce Dubbs wrote: >>> >>> I may have to break down and update SM. >> >> In SM: >> >> Edit -> Preferences -> Appearance -> Fonts >> >> All options but Proportional, I choose DejaVu LGC: >> >> serif >> sans >> serif >> serif >> sans mono >> > On any application which uses fontconfig, providing you have a font > which provides the glyph then fontconfig will start by looking at > your specified font, and then fall back to whatever it can find. Of > course, what it finds might not match the rest of the page. > > ĸen > Thanks, ĸen, always learning with you. -- []s, Fernando -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Font issues
On Wed, 2014-11-05 at 17:34 -0600, Bruce Dubbs wrote: > https://github.com/libical/libical/ > > There are glyphs for Issues, Pull Requests, Pulse, Graphs, Folders > (F016), Regular files (F011), and a few other things. > > In any case, it's definitely a browser version thing on my every day > system. On my development system I've got SM 2.29 and it's fine there. Basically, those byte ranges are reserved for private use - essentially, for arbitrary symbols that don't map to regular unicode characters... things like symbol fonts. That's what's happening here - they're using some CSS tricks to first insert one of these odd characters immediately before (e.g a F016 for a folder name), and using a special font which contains the relevant characters. Info (if you're interested) at https://octicons.github.com/ If it's not working for you, it's probably the age of your browser... I think the ability to use font resources from the web is relatively new... the past year or so. Simon. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Font issues
On Thu, Nov 06, 2014 at 12:30:55AM +, Ken Moffat wrote: > > And there, as the second image, I see > 78&tbm=isch&tbo=u&source=univ&sa=X&ei=Wb9aVMr8CebZ7gajyoGQCA&ved=0CDoQsAQ#facrc=_&imgdii=_&imgrc=AdQPJByul3CELM%253A%3Bn4ffvtnU8l5qsM%3Bhttp%253A%252F%252Fi.imgur.com%252F0RUI6iY.png%3Bhttp%253A%252F%252Fforums.mozillazine.org%252Fviewtopic.php%253Ff%253D38%2526t%253D2725913%3B386%3B390 > > which shows boxes that turn out to contain F024, F130, and perhaps > F087 (that last one is hard to read even after using the maximum > Ctrl+ blow-up. > > That issue is _old_ (last entry July lat year), but there are a > number of suggestions. > I seem to have lost some of that when I pasted it. It linked to http://forums.mozillazine.org/viewtopic.php?f=38&t=2725913 Hopefully, that link will not get trashed. The initial post has a link to a thread which does not look very useful, but perhaps the poster's checks/actions there are worthwhile : I guess that for you to this is not a language setting issue. ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Font issues
On Thu, Nov 06, 2014 at 12:21:43AM +, Ken Moffat wrote: > On Wed, Nov 05, 2014 at 05:34:54PM -0600, Bruce Dubbs wrote: > > Ken Moffat wrote: Change of plan. https://www.google.co.uk/?gws_rd=ssl#q=seamonkey+problem+displaying+github+icons Near the top of _my_ results for that I get: Images for seamonkey problem displaying github https://www.google.co.uk/search?q=seamonkey+problem+displaying+github+icons&biw=1255&bih=678&tbm=isch&tbo=u&source=univ&sa=X&ei=Wb9aVMr8CebZ7gajyoGQCA&ved=0CDoQsAQ And there, as the second image, I see 78&tbm=isch&tbo=u&source=univ&sa=X&ei=Wb9aVMr8CebZ7gajyoGQCA&ved=0CDoQsAQ#facrc=_&imgdii=_&imgrc=AdQPJByul3CELM%253A%3Bn4ffvtnU8l5qsM%3Bhttp%253A%252F%252Fi.imgur.com%252F0RUI6iY.png%3Bhttp%253A%252F%252Fforums.mozillazine.org%252Fviewtopic.php%253Ff%253D38%2526t%253D2725913%3B386%3B390 which shows boxes that turn out to contain F024, F130, and perhaps F087 (that last one is hard to read even after using the maximum Ctrl+ blow-up. That issue is _old_ (last entry July lat year), but there are a number of suggestions. ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Font issues
On Wed, Nov 05, 2014 at 05:34:54PM -0600, Bruce Dubbs wrote: > Ken Moffat wrote: > > > > U+F011 and U+F051 are NOT valid unicode. Hmm, I think you prefer > >to use legacy (ISO-8859-x) encodings ? If so, try UTF-8. > > > > If you are already using UTF-8, please read on. > > Changed to UTF-8, but no change. > > > For _obscure_ latin-alphabet/common characters I install the gnu > >free fonts (FreeSans, FreeSerif, FreeMono for a term) and let > >fontconfig fall back to them. Perhaps this is some uncommon > >punctuation (recent DejaVu seems to cover everything I specifically > >need or want to use). > > Comparing to konqueror, the characters (glyphs really) are things like > folders icons or file icons. konqueror has them about 16x16 pixels. > > > > Two questions: > > > >1. How are you determining those codes ? When I first discovered > >that I needed more than Bitstream Vera (a long while ago, in > >mid-life gnome-2.2) all I could see was four dots. If you do a hex > >dump, decoding unicode is *fun* - on x86 the bytes are swapped. > >Wikipedia has the basics (convert to binary, check the initial bits > >of each byte are valid, then assemble the bits from the "payload" to > >get the hex digits. > > The codes actually show up in the glyphs. Like > > f0 > 20 > > The size is pretty small -- about 5x5 pixels all with a single pixel black > border. > > >2. Do you have an example page, please, with a guide to where you > >see the problem ? > > https://github.com/libical/libical/ > > There are glyphs for Issues, Pull Requests, Pulse, Graphs, Folders (F016), > Regular files (F011), and a few other things. > > In any case, it's definitely a browser version thing on my every day system. > On my development system I've got SM 2.29 and it's fine there. > > -- Bruce > OK, I can see the images, but I cannot paste them. I had assumed those were graphics, they do not show at all in links. In firefox I cannot, apparently, 'view source'. [ omit my initial attempts to descript these, and to then fail to find them in e.g. unicode dingbats ] Ah, if I use arora, I can view the page source (black and red-ish on white : yeugh!). This is what the source has for 'cmake', which is the first directory: https://assets-cdn.github.com/images/spinners/octocat-spinner-32.gif"; width="16"> cmake From that, I think you either cannot display gifs on that system, or else you are blocking them. But I have no idea why that would make them display the same as "unavailable glyph" characters. If I _type_ that octocat-spinner-32.gif URI into firefox [ pasting decides to convert 'special' characters such as ':' and '/' and drops me at a search in my current default search engine (!) ] I get a gif with something vague in the centre, and a ring around it which appears to have something moving clockwise around it. Nothing like what I actually see on the page. Dunno, http is too complex! ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Font issues
On Wed, Nov 05, 2014 at 08:20:38PM -0300, Fernando de Oliveira wrote: > On 05-11-2014 19:36, Bruce Dubbs wrote: > > Fernando de Oliveira wrote: > >> On 05-11-2014 18:20, Bruce Dubbs wrote: > > > > I may have to break down and update SM. > > In SM: > > Edit -> Preferences -> Appearance -> Fonts > > All options but Proportional, I choose DejaVu LGC: > > serif > sans > serif > serif > sans mono > On any application which uses fontconfig, providing you have a font which provides the glyph then fontconfig will start by looking at your specified font, and then fall back to whatever it can find. Of course, what it finds might not match the rest of the page. ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Font issues
Ken Moffat wrote: On Wed, Nov 05, 2014 at 04:36:18PM -0600, Bruce Dubbs wrote: Fernando de Oliveira wrote: On 05-11-2014 18:20, Bruce Dubbs wrote: I am increasingly seeing font issues. What is being displayed in my browser is small squares with 4 hex digits instead of a character. For instance F011 or F051. An example of this is on most any github page. I took a look at the html source and this behavior is tied up in complex unformatted .css files. The first one I looked at is 200K in size. I suspect it is just a matter of loading the right font. Any ideas which one? -- Bruce I use DejaVu ttf and DejaVu LGC ttf. http://sourceforge.net/projects/dejavu/files/dejavu/2.33/dejavu-fonts-ttf-2.33.tar.bz2 http://sourceforge.net/projects/dejavu/files/dejavu/2.33/dejavu-lgc-fonts-ttf-2.33.tar.bz2 I had dejavu-fonts-ttf-2.33 installed. Installed dejavu-lgc-fonts-ttf-2.33 also using: $SUDO install -v -m755 -d/usr/share/fonts/dejavu && $SUDO install -v -m644 ttf/*.ttf /usr/share/fonts/dejavu && $SUDO mkdir -p /usr/share/fontconfig/conf.avail && $SUDO install -v -m644 fontconfig/*.conf \ /usr/share/fontconfig/conf.avail && $SUDO fc-cache -v/usr/share/fonts/dejavu But it didn't seem to make any difference. I also reinstalled dejavu-fonts-ttf-2.33. Still no difference. Old client maybe? Seamonkey-2.10.1. Konqueror seems a little better. I may have to break down and update SM. -- Bruce U+F011 and U+F051 are NOT valid unicode. Hmm, I think you prefer to use legacy (ISO-8859-x) encodings ? If so, try UTF-8. If you are already using UTF-8, please read on. Changed to UTF-8, but no change. For _obscure_ latin-alphabet/common characters I install the gnu free fonts (FreeSans, FreeSerif, FreeMono for a term) and let fontconfig fall back to them. Perhaps this is some uncommon punctuation (recent DejaVu seems to cover everything I specifically need or want to use). Comparing to konqueror, the characters (glyphs really) are things like folders icons or file icons. konqueror has them about 16x16 pixels. Two questions: 1. How are you determining those codes ? When I first discovered that I needed more than Bitstream Vera (a long while ago, in mid-life gnome-2.2) all I could see was four dots. If you do a hex dump, decoding unicode is *fun* - on x86 the bytes are swapped. Wikipedia has the basics (convert to binary, check the initial bits of each byte are valid, then assemble the bits from the "payload" to get the hex digits. The codes actually show up in the glyphs. Like f0 20 The size is pretty small -- about 5x5 pixels all with a single pixel black border. 2. Do you have an example page, please, with a guide to where you see the problem ? https://github.com/libical/libical/ There are glyphs for Issues, Pull Requests, Pulse, Graphs, Folders (F016), Regular files (F011), and a few other things. In any case, it's definitely a browser version thing on my every day system. On my development system I've got SM 2.29 and it's fine there. -- Bruce -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Font issues
On 05-11-2014 19:36, Bruce Dubbs wrote: > Fernando de Oliveira wrote: >> On 05-11-2014 18:20, Bruce Dubbs wrote: >>> I am increasingly seeing font issues. What is being displayed in my >>> browser is small squares with 4 hex digits instead of a character. For >>> instance F011 or F051. >>> >>> An example of this is on most any github page. >>> >>> I took a look at the html source and this behavior is tied up in complex >>> unformatted .css files. The first one I looked at is 200K in size. >>> >>> I suspect it is just a matter of loading the right font. >>> >>> Any ideas which one? >>> >>>-- Bruce >> >> I use DejaVu ttf and DejaVu LGC ttf. >> >> >> http://sourceforge.net/projects/dejavu/files/dejavu/2.33/dejavu-fonts-ttf-2.33.tar.bz2 >> >> >> http://sourceforge.net/projects/dejavu/files/dejavu/2.33/dejavu-lgc-fonts-ttf-2.33.tar.bz2 >> > > I had dejavu-fonts-ttf-2.33 installed. Installed > dejavu-lgc-fonts-ttf-2.33 also using: > > > $SUDO install -v -m755 -d/usr/share/fonts/dejavu && > $SUDO install -v -m644 ttf/*.ttf /usr/share/fonts/dejavu && > $SUDO mkdir -p /usr/share/fontconfig/conf.avail && > $SUDO install -v -m644 fontconfig/*.conf \ >/usr/share/fontconfig/conf.avail && > $SUDO fc-cache -v/usr/share/fonts/dejavu > > But it didn't seem to make any difference. I also reinstalled > dejavu-fonts-ttf-2.33. Still no difference. > > Old client maybe? Seamonkey-2.10.1. Konqueror seems a little better. > > I may have to break down and update SM. In SM: Edit -> Preferences -> Appearance -> Fonts All options but Proportional, I choose DejaVu LGC: serif sans serif serif sans mono Perhaps you could send a link for a problematic page, so I might discover the problem is more general? -- []s, Fernando -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Font issues
On Wed, Nov 05, 2014 at 06:58:58PM -0300, Fernando de Oliveira wrote: > On 05-11-2014 18:20, Bruce Dubbs wrote: > > I use DejaVu ttf and DejaVu LGC ttf. > > > http://sourceforge.net/projects/dejavu/files/dejavu/2.33/dejavu-fonts-ttf-2.33.tar.bz2 > > http://sourceforge.net/projects/dejavu/files/dejavu/2.33/dejavu-lgc-fonts-ttf-2.33.tar.bz2 > I did not pay any attention to this part (I started by looking for the codepoints in my font analysis files, then realised my matches were only for _part_ of the codepoint [ U+F011x and U+F051x codepoint exist - egyptian hieroglyphs ]. BUT - The -lgc- fonts are a subset (latin greek cyrillic : hey, that is a catchy combination ;) so you do not need those if you have already installed the full version. And 2.34 is the latest. ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Font issues
On Wed, Nov 05, 2014 at 04:36:18PM -0600, Bruce Dubbs wrote: > Fernando de Oliveira wrote: > >On 05-11-2014 18:20, Bruce Dubbs wrote: > >>I am increasingly seeing font issues. What is being displayed in my > >>browser is small squares with 4 hex digits instead of a character. For > >>instance F011 or F051. > >> > >>An example of this is on most any github page. > >> > >>I took a look at the html source and this behavior is tied up in complex > >>unformatted .css files. The first one I looked at is 200K in size. > >> > >>I suspect it is just a matter of loading the right font. > >> > >>Any ideas which one? > >> > >> -- Bruce > > > >I use DejaVu ttf and DejaVu LGC ttf. > > > > > >http://sourceforge.net/projects/dejavu/files/dejavu/2.33/dejavu-fonts-ttf-2.33.tar.bz2 > > > >http://sourceforge.net/projects/dejavu/files/dejavu/2.33/dejavu-lgc-fonts-ttf-2.33.tar.bz2 > > I had dejavu-fonts-ttf-2.33 installed. Installed > dejavu-lgc-fonts-ttf-2.33 also using: > > > $SUDO install -v -m755 -d/usr/share/fonts/dejavu && > $SUDO install -v -m644 ttf/*.ttf /usr/share/fonts/dejavu && > $SUDO mkdir -p /usr/share/fontconfig/conf.avail && > $SUDO install -v -m644 fontconfig/*.conf \ >/usr/share/fontconfig/conf.avail && > $SUDO fc-cache -v/usr/share/fonts/dejavu > > But it didn't seem to make any difference. I also reinstalled > dejavu-fonts-ttf-2.33. Still no difference. > > Old client maybe? Seamonkey-2.10.1. Konqueror seems a little better. > > I may have to break down and update SM. > > -- Bruce U+F011 and U+F051 are NOT valid unicode. Hmm, I think you prefer to use legacy (ISO-8859-x) encodings ? If so, try UTF-8. If you are already using UTF-8, please read on. For _obscure_ latin-alphabet/common characters I install the gnu free fonts (FreeSans, FreeSerif, FreeMono for a term) and let fontconfig fall back to them. Perhaps this is some uncommon punctuation (recent DejaVu seems to cover everything I specifically need or want to use). Two questions: 1. How are you determining those codes ? When I first discovered that I needed more than Bitstream Vera (a long while ago, in mid-life gnome-2.2) all I could see was four dots. If you do a hex dump, decoding unicode is *fun* - on x86 the bytes are swapped. Wikipedia has the basics (convert to binary, check the initial bits of each byte are valid, then assemble the bits from the "payload" to get the hex digits. 2. Do you have an example page, please, with a guide to where you see the problem ? ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Font issues
Fernando de Oliveira wrote: On 05-11-2014 18:20, Bruce Dubbs wrote: I am increasingly seeing font issues. What is being displayed in my browser is small squares with 4 hex digits instead of a character. For instance F011 or F051. An example of this is on most any github page. I took a look at the html source and this behavior is tied up in complex unformatted .css files. The first one I looked at is 200K in size. I suspect it is just a matter of loading the right font. Any ideas which one? -- Bruce I use DejaVu ttf and DejaVu LGC ttf. http://sourceforge.net/projects/dejavu/files/dejavu/2.33/dejavu-fonts-ttf-2.33.tar.bz2 http://sourceforge.net/projects/dejavu/files/dejavu/2.33/dejavu-lgc-fonts-ttf-2.33.tar.bz2 I had dejavu-fonts-ttf-2.33 installed. Installed dejavu-lgc-fonts-ttf-2.33 also using: $SUDO install -v -m755 -d/usr/share/fonts/dejavu && $SUDO install -v -m644 ttf/*.ttf /usr/share/fonts/dejavu && $SUDO mkdir -p /usr/share/fontconfig/conf.avail && $SUDO install -v -m644 fontconfig/*.conf \ /usr/share/fontconfig/conf.avail && $SUDO fc-cache -v/usr/share/fonts/dejavu But it didn't seem to make any difference. I also reinstalled dejavu-fonts-ttf-2.33. Still no difference. Old client maybe? Seamonkey-2.10.1. Konqueror seems a little better. I may have to break down and update SM. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Font issues
On 05-11-2014 18:20, Bruce Dubbs wrote: > I am increasingly seeing font issues. What is being displayed in my > browser is small squares with 4 hex digits instead of a character. For > instance F011 or F051. > > An example of this is on most any github page. > > I took a look at the html source and this behavior is tied up in complex > unformatted .css files. The first one I looked at is 200K in size. > > I suspect it is just a matter of loading the right font. > > Any ideas which one? > > -- Bruce I use DejaVu ttf and DejaVu LGC ttf. http://sourceforge.net/projects/dejavu/files/dejavu/2.33/dejavu-fonts-ttf-2.33.tar.bz2 http://sourceforge.net/projects/dejavu/files/dejavu/2.33/dejavu-lgc-fonts-ttf-2.33.tar.bz2 -- []s, Fernando -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
