Werner LEMBERG wrote:
I think that `bv' is a good choice for this very special situation in the bash manpage. In case you can't stand the appearance, feel free to adjust the used character either in the file `man.local' or in `troffrc', for example by appending
.if '\*[.T]'utf8' \ . char \[bv] \N'65512'
which maps `\(bv' to U+FFE8 if the output device produces utf-8.
Yes... It is a fairly good choice from the visual *DEPENDING* on the font loaded. One of the features or important aspects of Unicode is having a rich variety of similar looking symbols that retain their semantic meaning even though they may look identical. Think Greek letters and math, for example. U sing semantically correct (or close to it) characters, can be useful for people who might be using software that -- if it cannot display it, might give the literal description (think "blind-reader SW, as a possibility, though there might be more). I felt that something that indicated vertical bar in the description might be better on those grounds and the char I pointed to was about a 75/100 (vs the one that is there probably a 90/100 on looks). But hey, what those blind people can't see won't hurt 'em right? ;-| As for my own usage, I can take a completely obtuse character, dump it in hex, decode it from UTF-8, and check it out. Given how easy it is, I'm sure it wouldn't be a problem for anyone else either!
:-) *cheers*
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org