On Sun, Mar 31, 2019 at 11:34:21PM +0100, Ken Moffat via blfs-dev wrote:
> On Sat, Mar 30, 2019 at 07:23:37PM -0500, Bruce Dubbs via blfs-dev wrote:
> > On 3/30/19 6:59 PM, Ken Moffat via blfs-dev wrote:
> >
> > Hmm. I copied that into vim and it was fine for me. Saved it and reopened
> > and it was fine. Looking at my options:
> >
> > :set
> > --- Options ---
> > autoindent helplang=en ruler ttyfast
> > background=dark hlsearch scroll=28 ttymouse=xterm2
> > backspace=2 incsearch shiftwidth=3 viminfo='20,"50
> > expandtab laststatus=2 syntax=diff
> > filetype=diff modified tabstop=3
> > fileencoding=utf-8
> > fileencodings=ucs-bom,utf-8,default,latin1
> > formatoptions=tcql
> >
> > -- Bruce
> >
> Thanks for listing your options.
>
> I might come back to this in a few days - for the moment I have not
> checked my options, reading the changed translations is not especially
> important, it's just annoying when I know that my system ought to be
> able to display some of them.
After finishing my read of the diff (lots of weird and wonderful
things tucked away in it, but mostly not relevant to building FF for
BLFS) I came back to this, and I think I've solved it.
Recall that 'file' thinks the diff is 'data'. The first
non-rendered unicode that I noticed was in a diff starting at line
164552, and the diff also contains changes to graphics files which
clearly do not render. I think several of those are fairly early
on, but immediately before this batch of UTF-8 (localized messages
relating to screenshots) is the removal of a png file (i.e.
no-longer present).
If I copy only those locale messages (a bit over 3600 lines), vim
renders almost all of them, and those it doesn't have 'empty box'
characters for missing glyphs.
The missing language codes are bn_BD (Bengali, Bangladesh), gu_IN
(Gujarati, India), my (Burmese), te (Telugu). Also, for fa (farsi)
vim displays <200c> in several places - that is a zero-width
non-joiner. I am using monospaced fonts in urxvt, so the omission
of those glyphs is not a surprise.
Summary: vim treats the full diff as data because some of it _is_
data, and I guess that telling it to display data as if it were
UTF-8 is discarded as soon as some invalid unicode appears.
ĸen
--
It is said that there are two great unsolved problems in computer
science: naming, cache invalidation, and off-by-one errors.
-- Ben Bullock
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
