Good to know Tim, thanks! Since you copy-pasted, my guess would be you copied the invisible LF ending from the e-mail, which Notepad now dutifully honors, and now you’ve shown by experiment that it also retains that line ending even when editing the file. That’s good news.
When you have a few minutes, for completeness, can you test what happens if you create a new file in Notepad and *type* the multi-line rule instead of copy-paste? (be certain to rename or move your current .css file out of that directory and restart GnuCash) That would definitively establish that Notepad has moved to LF only line endings and can be used to write CSS. I’ll then add this info to the wiki page on GTK3. Regards, Adrien > On Apr 5, 2019, at 12:30 PM, Timothy B. Taylor <[email protected]> wrote: > > Apologies if this seems to be getting a little off topic. Yesterday when I > was experimenting, I found no mess. It just worked. > > Started by cutting and pasting the three lines * { ... } from the email into > a blank notepad file. Saved it with the appropriate name in the appropriate > place. Opened GnuCash, it worked. > > Closed GnuCash, opened Notepad again, deleted the line breaks to make it just > one line, resaved it, it still worked. > > Closed GnuCash, opened Notepad again, hit return at the appropriate spots to > recreate the three-line file, saved it, it still worked. > > Tried various capitalized and lower-case font names, and "px" and "pt" and > various numbers for the font size. It always worked. I settled on 10pt > Verdana. Others may end up elsewhere. > > GnuCash 3.5 Windows Pro 10 v 1803 > > No complaints at all from me. Thanks for making this easy. Tim > > > On Fri, Apr 5, 2019 at 1:07 PM Adrien Monteleone > <[email protected]> wrote: > Good call. Since it was a one-line file it might still fly. While I haven’t > written CSS on Windows in years, I seem to recall needing to download a > separate editor because Notepad couldn’t do it. (and I think that was one of > the early reasons why Notepad++ was released) I don’t have a Win10 > installation to test if MS changed the line-ending behavior or at least added > the Unix/Linux option. > > Update - before sending this I did a little web search. It seems MS sort of > fixed this in Win10. Notepad will now correctly *open* an existing file saved > with LF or CR only endings created by apps in Unix/Linux. BUT, for newly > created files, will default to the traditional CR+LF endings Windows Notepad > has always used. No info on if they ever added a preference to default to LF > or CR for new files however. Also no info on if you open an existing > Unix/Linux file and edit it, which ending will be used. (mixed endings? what > a mess!) > > In addition to Notepad++ there is also an app called Notepad2, both of which > can be set to use either LF by default for new files. (among many other > editors of course) > > Regards, > Adrien > > > On Apr 5, 2019, at 3:18 AM, Liz <[email protected]> wrote: > > > > On Thu, 4 Apr 2019 13:49:20 -0400 > > "Timothy B. Taylor" <[email protected]> wrote: > > > >> For what it's worth ... Notepad worked just fine for me ... GnuCash > >> 3.5, Windows 10 Pro version 1803 ... > >> > >> After trying a few variations ... various fonts and sizes ... I ended > >> up with > >> > >> * { font: 10pt verdana, arial, sans-serif; } > >> > >> ... and by the way it works fine on one line ... Thanks! Tim > > > > However, if you had tried to split the line, you may not have had the > > same success. > > Could you try with the original > > > > > > * { > > font: 12px arial, sans-serif; > > } > > > > > > using notepad? > > > > Liz _______________________________________________ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
