Re: [fossil-users] Couple of beginner questions

2017-04-05 Thread Warren Young
On Apr 4, 2017, at 7:02 PM, Ross Berteig wrote: > > So I accidentally wrote a blog post about the experiment. Thank you for doing the research, and writing it up. Bottom line for the Fossil end of things, UTF-8 is a thing of such pragmatic beauty that it is almost never the reason you cannot m

Re: [fossil-users] Couple of beginner questions

2017-04-05 Thread Roberto Henriquez
On Thu, 30 Mar 2017 08:49:49 -0600 Warren Young wrote: > > Solutions are available, if you go looking. Hi! Long time lurker here. Just my 2c regarding input, X11 gives several options. In my case (spanish speaking but program using US layout), I have ES and US layouts, switchable using a key c

Re: [fossil-users] Couple of beginner questions

2017-04-04 Thread Ross Berteig
On 3/31/2017 2:04 PM, Shal Farley wrote: Warren wrote: > Someone brought up TECO. I don’t expect anyone’s TECO implementation > to handle UTF-8, That was me... Hmm... I was going to say in jest that the DECUS swap tapes have a version written in C, were anyone nuts enough to take a crack at

Re: [fossil-users] Couple of beginner questions

2017-03-31 Thread Shal Farley
Warren, > Someone brought up TECO. I don’t expect anyone’s TECO implementation > to handle UTF-8, Hmm... I was going to say in jest that the DECUS swap tapes have a version written in C, were anyone nuts enough to take a crack at it. However Google reveals that it is closer at hand than I thou

Re: [fossil-users] Couple of beginner questions

2017-03-31 Thread Warren Young
On Mar 31, 2017, at 1:42 PM, Andy Bradford wrote: > > You could have continued on the way you were > doing things. No need to change anything except tell your browser that > the content is not Unicode, but is instead ``Western'' or ISO-8895-1 or > something else. That only fixes one browser

Re: [fossil-users] Couple of beginner questions

2017-03-31 Thread Andy Bradford
Thus said The Tick on Thu, 30 Mar 2017 14:35:22 -0500: > Goodness! All I wanted was to have a comment contain a copyright > character. Did you see my response? You could have continued on the way you were doing things. No need to change anything except tell your browser that the conten

Re: [fossil-users] Couple of beginner questions

2017-03-30 Thread Stephan Beal
On Fri, Mar 31, 2017 at 12:14 AM, Scott Robison wrote: > "Okay, so 640K of RAM isn't enough memory, but 64K code points will > definitely encode more characters than we'll ever possibly need. You > have my word on it!" > > True story. ;) He apparently didn't foresee 0x1F4A9 - the "pile of poo"

Re: [fossil-users] Couple of beginner questions

2017-03-30 Thread Scott Robison
On Thu, Mar 30, 2017 at 3:17 PM, Ross Berteig wrote: > The large part of the world stuck with MS products can and should exert some > pressure to get better compliance from MS with many standards, not just > Unicode. They change at glacial speeds, but they do change. A good first > step would be f

Re: [fossil-users] Couple of beginner questions

2017-03-30 Thread Ross Berteig
On 3/30/2017 12:35 PM, The Tick wrote: Goodness! All I wanted was to have a comment contain a copyright character. Thanks to the people who were kind enough to take the time to respond to my questions. Now my commit messages are no longer a big blob of text, my .vimrc is modified, I've gotten

Re: [fossil-users] Couple of beginner questions

2017-03-30 Thread bch
On Mar 30, 2017 12:35, "The Tick" wrote: Goodness! All I wanted was to have a comment contain a copyright character. Thanks to the people who were kind enough to take the time to respond to my questions. Now my commit messages are no longer a big blob of text, my .vimrc is modified, I've gotten f

Re: [fossil-users] Couple of beginner questions

2017-03-30 Thread The Tick
Goodness! All I wanted was to have a comment contain a copyright character. Thanks to the people who were kind enough to take the time to respond to my questions. Now my commit messages are no longer a big blob of text, my .vimrc is modified, I've gotten fossil to stop complaining about my file

Re: [fossil-users] Couple of beginner questions

2017-03-30 Thread Joerg Sonnenberger
On Thu, Mar 30, 2017 at 04:34:57PM +0200, Stephan Beal wrote: > On Thu, Mar 30, 2017 at 4:30 PM, Warren Young wrote: > > > I don’t think it’s fair to notable Fossil users like Jörg Sonnenberger > > that we misspell their names simply because we refuse to give up > > ASCII-centrism. > > > > OTOH,

Re: [fossil-users] Couple of beginner questions

2017-03-30 Thread Stephan Beal
On Thu, Mar 30, 2017 at 5:00 PM, Warren Young wrote: > happens when you try to “cd ~/foo”. I have to fix that every time I > re-flash my Raspberry Pi with Raspbian, which defaults to expect a British > English keyboard. I suppose they think that’s fair revenge for the decades > of software fro

Re: [fossil-users] Couple of beginner questions

2017-03-30 Thread Warren Young
On Mar 29, 2017, at 2:47 PM, The Tick wrote: > > I also understand that a program script or, say, C source file can use the > utf-8 escape sequence to generate these characters when the program is run. > That is not possible in comments tho. I put © in C++ comments all the time. Every time I

Re: [fossil-users] Couple of beginner questions

2017-03-30 Thread Warren Young
On Mar 30, 2017, at 8:38 AM, Warren Young wrote: > > On Mar 29, 2017, at 2:48 PM, The Tick wrote: >> >> I've been using vi for 40 years so that's not going to change. > > I’ve “only” been using vi for about 37 years Ooops, I can’t math, apparently. “Only” 27-28 years. I first used vi in 198

Re: [fossil-users] Couple of beginner questions

2017-03-30 Thread Warren Young
On Mar 30, 2017, at 8:34 AM, Stephan Beal wrote: > > On Thu, Mar 30, 2017 at 4:30 PM, Warren Young wrote: > I don’t think it’s fair to notable Fossil users like Jörg Sonnenberger that > we misspell their names simply because we refuse to give up ASCII-centrism. > > OTOH, Joerg can't (IMO!) exp

Re: [fossil-users] Couple of beginner questions

2017-03-30 Thread Warren Young
On Mar 29, 2017, at 2:48 PM, The Tick wrote: > > On 3/29/2017 3:25 PM, Warren Young wrote: >> >> Any text editor or compiler that can’t cope with UTF-8 in 2017 is broken or >> can be ignored. > > I've been using vi for 40 years so that's not going to change. I’ve “only” been using vi for abou

Re: [fossil-users] Couple of beginner questions

2017-03-30 Thread Stephan Beal
On Thu, Mar 30, 2017 at 4:30 PM, Warren Young wrote: > I don’t think it’s fair to notable Fossil users like Jörg Sonnenberger > that we misspell their names simply because we refuse to give up > ASCII-centrism. > OTOH, Joerg can't (IMO!) expect the majority to change keyboard mappings or use app

Re: [fossil-users] Couple of beginner questions

2017-03-30 Thread Warren Young
On Mar 29, 2017, at 8:54 PM, Andy Bradford wrote: > > Thus said Warren Young on Wed, 29 Mar 2017 14:25:34 -0600: > >> Any text editor or compiler that can't cope with UTF-8 in 2017 is >> broken or can be ignored. > > I rarely use any editor but nvi. It doesn't support UTF-8. According t

Re: [fossil-users] Couple of beginner questions

2017-03-29 Thread Marc Simpson
On Wed, Mar 29, 2017 at 7:54 PM, Andy Bradford wrote: > Maybe one day nvi will have UTF-8 support, but I'm not counting on it > any time soon. :-) You may want to check out https://github.com/lichray/nvi2. ___ fossil-users mailing list fossil-users@l

Re: [fossil-users] Couple of beginner questions

2017-03-29 Thread Andy Bradford
Thus said The Tick on Wed, 29 Mar 2017 15:47:32 -0500: > If I edit the file, of course the utf-8 copyright symbol is garbled. > Furthermore, there is no way I can insert a utf-8 character. My editor (nvi) allows me to insert UTF-8 characters by typing the ASCII character, then by pressing ctrl-

Re: [fossil-users] Couple of beginner questions

2017-03-29 Thread Andy Bradford
Thus said Warren Young on Wed, 29 Mar 2017 14:25:34 -0600: > Any text editor or compiler that can't cope with UTF-8 in 2017 is > broken or can be ignored. I rarely use any editor but nvi. It doesn't support UTF-8. Here is what utf16le.txt (from Fossil test directory) looks like to me: \xff

Re: [fossil-users] Couple of beginner questions

2017-03-29 Thread Ross Berteig
On 3/29/2017 1:05 PM, The Tick wrote: On 3/29/2017 2:36 PM, Richard Hipp wrote: Most of the world is using UTF-8 now. I'm wondering how that can be for programming language source files. I managed to put the "bom" in front of a one-line tcl script: puts "This is a copyright symbol: ©." whe

Re: [fossil-users] Couple of beginner questions

2017-03-29 Thread sky5walk
the.tick - "Where and how would I use the above?" Browse a fossil ui of your repo and edit the skin - CSS page: http://localhost:8082/setup_skinedit?w=0 On Wed, Mar 29, 2017 at 5:18 PM, The Tick wrote: > On 3/29/2017 4:03 PM, sky5w...@gmail.com wrote: > >> Doh! It was my CSS. I was using a test

Re: [fossil-users] Couple of beginner questions

2017-03-29 Thread The Tick
On 3/29/2017 4:21 PM, Martin Gagnon wrote: About gvim and UTF-8 files without BOM, my vim is set with set encoding=utf-8 set fileencoding=utf-8 and everything works like a charm. Also, If I edit a ascii file that doesn't contain any special character, it remain ascii. I didn't know I co

Re: [fossil-users] Couple of beginner questions

2017-03-29 Thread Martin Gagnon
On Wed, Mar 29, 2017 at 03:47:32PM -0500, The Tick wrote: > On 3/29/2017 3:04 PM, Stephan Beal wrote: > >On Wed, Mar 29, 2017 at 9:52 PM, >> wrote: > > > >Yes, change your text files to UTF-8 with BOM(unsure without BOM) > >and Fossil respects °, ±, ©, ®, special

Re: [fossil-users] Couple of beginner questions

2017-03-29 Thread The Tick
On 3/29/2017 4:03 PM, sky5w...@gmail.com wrote: Doh! It was my CSS. I was using a test repo without my modified CSS. Now it works. I think this is the 2nd time I tripped on this. :( // from CSS // /* THIS DOES NOT WORK - Enable Check-in comments to respect linefeeds. */ span.checkinComment { f

Re: [fossil-users] Couple of beginner questions

2017-03-29 Thread sky5walk
Doh! It was my CSS. I was using a test repo without my modified CSS. Now it works. I think this is the 2nd time I tripped on this. :( // from CSS // /* THIS DOES NOT WORK - Enable Check-in comments to respect linefeeds. */ span.checkinComment { font-family: Consolas; white-space: pre; } /* THI

Re: [fossil-users] Couple of beginner questions

2017-03-29 Thread Stephan Beal
On Wed, Mar 29, 2017 at 10:47 PM, The Tick wrote: > I took my u.tcl file, removed the 'bom' and now both tclsh and wish work. > :). That reminds me of a website outage at a company i once worked for, caused by someone's editor inserting a[n invisible] BOM in a PHP file, and PHP crashes silently

Re: [fossil-users] Couple of beginner questions

2017-03-29 Thread The Tick
On 3/29/2017 3:25 PM, Warren Young wrote: On Mar 29, 2017, at 2:05 PM, The Tick wrote: On 3/29/2017 2:36 PM, Richard Hipp wrote: Most of the world is using UTF-8 now. I'm wondering how that can be for programming language source files. Any text editor or compiler that can’t cope with

Re: [fossil-users] Couple of beginner questions

2017-03-29 Thread The Tick
On 3/29/2017 3:04 PM, Stephan Beal wrote: On Wed, Mar 29, 2017 at 9:52 PM, mailto:sky5w...@gmail.com>> wrote: Yes, change your text files to UTF-8 with BOM(unsure without BOM) and Fossil respects °, ±, ©, ®, special characters. Actually, UTF8 does not typically use a BOM because byte o

Re: [fossil-users] Couple of beginner questions

2017-03-29 Thread Warren Young
On Mar 29, 2017, at 2:05 PM, The Tick wrote: > > On 3/29/2017 2:36 PM, Richard Hipp wrote: >> Most of the world is using UTF-8 now. > > I'm wondering how that can be for programming language source files. Existence proof: https://tangentsoft.com/pidp8i/artifact/9c629c82ae71862a All text files

Re: [fossil-users] Couple of beginner questions

2017-03-29 Thread Donald Griggs
Regarding " ...It needs to show as a real copyright symbol..." As a slight aside, and if you happen to be in the U.S., the United States used to be unusual in that we required items with reserved rights to be marked with the copyright symbol, or, equivalently, with (c) and the year. In 1976, we

Re: [fossil-users] Couple of beginner questions

2017-03-29 Thread The Tick
On 3/29/2017 2:36 PM, Richard Hipp wrote: Most of the world is using UTF-8 now. I'm wondering how that can be for programming language source files. I managed to put the "bom" in front of a one-line tcl script: puts "This is a copyright symbol: ©." where the '©' was previously converted to u

Re: [fossil-users] Couple of beginner questions

2017-03-29 Thread Richard Hipp
On 3/29/17, sky5w...@gmail.com wrote: > > Side note: > I have all Timeline Display Preferences unchecked and my v2.1 Timeline does > not respect new lines in my check-in comment? > v1.37 showed newlines in the Timeline for identical setup. > Is this intentional change? > No. Can you show us a te

Re: [fossil-users] Couple of beginner questions

2017-03-29 Thread Stephan Beal
On Wed, Mar 29, 2017 at 9:52 PM, wrote: > Yes, change your text files to UTF-8 with BOM(unsure without BOM) and > Fossil respects °, ±, ©, ®, special characters. > > Actually, UTF8 does not typically use a BOM because byte order is meaningless with UTF8 (the standard allows a BOM but does not req

Re: [fossil-users] Couple of beginner questions

2017-03-29 Thread sky5walk
Yes, change your text files to UTF-8 with BOM(unsure without BOM) and Fossil respects °, ±, ©, ®, special characters. Side note: I have all Timeline Display Preferences unchecked and my v2.1 Timeline does not respect new lines in my check-in comment? v1.37 showed newlines in the Timeline for ident

Re: [fossil-users] Couple of beginner questions

2017-03-29 Thread Richard Hipp
On 3/29/17, The Tick wrote: > 1) When I did a commit, I formatted the commit message very nicely. > After the commit, it's just a big blob of text. That certainly defeats > the purpose of making a commit message of any detail. > > What is the standard practice with this? Keeping a separate > "chan

[fossil-users] Couple of beginner questions

2017-03-29 Thread The Tick
1) When I did a commit, I formatted the commit message very nicely. After the commit, it's just a big blob of text. That certainly defeats the purpose of making a commit message of any detail. What is the standard practice with this? Keeping a separate "changelog.txt" where the details are lis