Can iPhone data be saved to my Fedora-21 computer and be transferred to another iPhone. This seems to be a common problem in this family when they get new phones. Apparently they are putting the stuff on an iCloud server and that raises hell with my bandwidth usage numbers ... It seems to me it should be possible to store it locally?
Bob
On 23.12.2014 16:18, Bob Goodwin wrote:
Can iPhone data be saved to my Fedora-21 computer and be transferred to another iPhone. This seems to be a common problem in this family when they get new phones. Apparently they are putting the stuff on an iCloud server and that raises hell with my bandwidth usage numbers ... It seems to me it should be possible to store it locally?
Bob
On 12/23/14 10:52, poma wrote:
I found this:
[root@box10 bobg]# yum install libimobiledevice Loaded plugins: langpacks Package libimobiledevice-1.1.7-1.fc21.x86_64 already installed and latest version Nothing to do
But apparently that does not include everything needed?
Bob
not sure what you are missing... check the web page, it shows & mentions other packages... libgpod, then under 15.10.2014:
* 15.10.2014: Release spree! libplist-1.12.tar.bz2 http://www.libimobiledevice.org/downloads/libplist-1.12.tar.bz2, libusbmuxd-1.0.10.tar.bz2 http://www.libimobiledevice.org/downloads/libusbmuxd-1.0.10.tar.bz2, usbmuxd-1.0.9.tar.bz2 http://www.libimobiledevice.org/downloads/usbmuxd-1.0.9.tar.bz2, libimobiledevice-1.1.7.tar.bz2 (unstable) http://www.libimobiledevice.org/downloads/libimobiledevice-1.1.7.tar.bz2, ideviceinstaller-1.1.0.tar.bz2 http://www.libimobiledevice.org/downloads/ideviceinstaller-1.1.0.tar.bz2 and libideviceactivation-1.0.0.tar.bz2 http://www.libimobiledevice.org/downloads/libideviceactivation-1.0.0.tar.bz2have been officially released.
On 12/23/14 10:52, poma wrote:
I found this:
[root@box10 bobg]# yum install libimobiledevice Loaded plugins: langpacks Package libimobiledevice-1.1.7-1.fc21.x86_64 already installed and latest version Nothing to do
But apparently that does not include everything needed?
Bob
http://www.qrz.com/db/W2BOD box10 Fedora-21/64bit Linux/XFCE
On 12/23/2014 09:18 AM, Bob Goodwin wrote:
Can iPhone data be saved to my Fedora-21 computer and be transferred to another iPhone. This seems to be a common problem in this family when they get new phones. Apparently they are putting the stuff on an iCloud server and that raises hell with my bandwidth usage numbers ... It seems to me it should be possible to store it locally?
Hey, can you turn off the HTML mail? white on black is really really hard to read.
Anyhow, the phones don't back themselves up to iCloud unless their locked and on WiFi, so it shouldn't be hitting your wireless data usage plan.
Otherwise, use iTunes... it runs nicely on XP in VirtualBox.
On 12/23/14 12:42, Steven Stern wrote:
Hey, can you turn off the HTML mail? white on black is really really hard to read.
Anyhow, the phones don't back themselves up to iCloud unless their locked and on WiFi, so it shouldn't be hitting your wireless data usage plan.
Otherwise, use iTunes... it runs nicely on XP in VirtualBox.
I am curious about the HTML, this is F-21 with Thunderbird 31.3.0 and I have found no option to kill the HTML to the list. I have set it to send plain text to fedoraproject.org and I am careful to remove text styles, etc. from every message I send to the list.
I did observe that it appears to be sending both however. When I view the "source" it is sending plain text followed by the HTML. I have not found a way to change it back as it was where I could select plain text only before sending. It looks like a new "feature?"
I am open to suggestions.
Bob
On 12/23/2014 01:00 PM, Bob Goodwin wrote:
I am curious about the HTML, this is F-21 with Thunderbird 31.3.0 and I have found no option to kill the HTML to the list. I have set it to send plain text to fedoraproject.org and I am careful to remove text styles, etc. from every message I send to the list.
I did observe that it appears to be sending both however. When I view the "source" it is sending plain text followed by the HTML. I have not found a way to change it back as it was where I could select plain text only before sending. It looks like a new "feature?"
under options-Delivery format-plain text..
under the folders, folder-properties I have Unicode (UTF-8) and check the box so apply encoding to all messages in the folder..
On 12/23/14 13:17, Paul Cartwright wrote:
under options-Delivery format-plain text..
Dunno where you have this, I don't?
Most of my e-mail correspondence is with Windows users and HTML is the norm. This is the first complaint I have had about HTML with F-21, I exchange a lot of text messages with the iPhones and send one in HTML and I get complaints immediately! So far there have been none.
I suppose someone like my self who has Thunderbird set to receive HTML e-mail might display the HTML version?
As for the white on black I have had retinal vein occlusions in both eyes which leaves me with only limited vision in one eye and looking at a white screen is difficult at best. So I force all messages to display white on black including those I receive from the list.
under the folders, folder-properties I have Unicode (UTF-8) and check the box so apply encoding to all messages in the folder..
I think we have the same settings here.
Bob
-- Paul Cartwright Registered Linux User #367800 and new counter #561587
On 12/23/2014 01:42 PM, Bob Goodwin wrote:
under options-Delivery format-plain text..
Dunno where you have this, I don't?
when you hit reply, in the reply window menus, there is options-delivery format, then the drop-down includes plain text.
someone else mentioned an easy way, go to your addressbook, select fedora-users-change "Prefers to receive messages formated as: and it has a drop-down menu, from which you select "Plain text"
Most of my e-mail correspondence is with Windows users and HTML is the norm. This is the first complaint I have had about HTML with F-21, I exchange a lot of text messages with the iPhones and send one in HTML and I get complaints immediately! So far there have been none.
your emails look just like my Mate-terminal, black with white letters.. I keep wanting to click on your emails with my mouse & start typing!!
On 12/23/2014 10:42 AM, Bob Goodwin wrote:
On 12/23/14 13:17, Paul Cartwright wrote:
under options-Delivery format-plain text..
Dunno where you have this, I don't?
Allegedly, on or about 23 December 2014, Bob Goodwin sent:
As for the white on black I have had retinal vein occlusions in both eyes which leaves me with only limited vision in one eye and looking at a white screen is difficult at best.
I'm curious, now. On at least some desktops you can change the look to be black on white (or other things), that should cause all decent programs to display that way, including email and webpages. Does this not work for you? Is it only a partial solution?
On 12/24/14 06:18, Tim wrote:
I'm curious, now. On at least some desktops you can change the look to be black on white (or other things), that should cause all decent programs to display that way, including email and webpages. Does this not work for you? Is it only a partial solution?
Yes, wherever possible I select the options that provide a screen with white text on a black background. In some cases it's simply a matter of selecting a "theme."
That certainly works for me except at times where a web page wants a response and it shows what I type in black text on black. Then I have to switch to a conventional color scheme, highlight the text, or simply have faith that I typed it right!
That considered white on black is still the best option for me and I accept the few problems I have with it. I've been doing this for a long time and made adjustments over the years. The only problem encountered was a complaint when someone saw white on black in a message and protested and I think I know how to prevent that from happening now, although it seems like nit picking to me.
On 24.12.2014 15:34, Bob Goodwin wrote:
On 12/24/14 06:18, Tim wrote:
I'm curious, now. On at least some desktops you can change the look to be black on white (or other things), that should cause all decent programs to display that way, including email and webpages. Does this not work for you? Is it only a partial solution?
Yes, wherever possible I select the options that provide a screen with white text on a black background. In some cases it's simply a matter of selecting a "theme."
That certainly works for me except at times where a web page wants a response and it shows what I type in black text on black. Then I have to switch to a conventional color scheme, highlight the text, or simply have faith that I typed it right!
That considered white on black is still the best option for me and I accept the few problems I have with it. I've been doing this for a long time and made adjustments over the years. The only problem encountered was a complaint when someone saw white on black in a message and protested and I think I know how to prevent that from happening now, although it seems like nit picking to me.
What theme it is? $ xfconf-query -c xsettings -p /Net/ThemeName
$HOME/.mozilla/firefox/<PROFILE>/chrome/userContent.css /* * * Use this css file to eliminate problems in Firefox * * when using dark themes that create dark on dark * * input boxes, selection menus and buttons. Put this * * in the ../firefox/default/chrome folder or your * * individual user firefox profile chrome folder. * */ input { border: 2px inset white; background-color: white; color: black; -moz-appearance: none !important; } textarea { border: 2px inset white; background-color: white; color: black; -moz-appearance: none !important; } select { border: 2px inset white; background-color: white; color: black; -moz-appearance: none !important; } input[type="radio"], input[type="checkbox"] { border: 2px inset white ! important; background-color: white ! important; color: ThreeDFace ! important; -moz-appearance: none !important; } *|*::-moz-radio { background-color: white; -moz-appearance: none !important; } button, input[type="reset"], input[type="button"], input[type="submit"] { border: 2px outset white; background-color: #eeeeee; color: black; -moz-appearance: none !important; } body { background-color: white; color: black; display: block; margin: 8px; -moz-appearance: none !important; }
On 12/24/14 10:03, poma wrote:
What theme it is? $ xfconf-query -c xsettings -p /Net/ThemeName
[bobg@box10 ~]$ xfconf-query -c xsettings -p /Net/ThemeName HighContrast
$HOME/.mozilla/firefox/<PROFILE>/chrome/userContent.css /*
- Use this css file to eliminate problems in Firefox
- when using dark themes that create dark on dark
- input boxes, selection menus and buttons. Put this
- in the ../firefox/default/chrome folder or your
- individual user firefox profile chrome folder.
................. snip ....
I can't locate "/chrome/userContent.css"
I do find a number of directories/files like: /home/bobg/.mozilla/firefox/2kkjzlsa.default/extensions/artur.dubovoy@gmail.com/chrome/content/
Perhaps I need to add it somewhere in that area, if so where?
On 24.12.2014 17:12, Bob Goodwin wrote:
On 12/24/14 10:03, poma wrote:
What theme it is? $ xfconf-query -c xsettings -p /Net/ThemeName
[bobg@box10 ~]$ xfconf-query -c xsettings -p /Net/ThemeName HighContrast
http://goo.gl/Gm4ffO SRPMS.tar
$ tar xf SRPMS.tar $ rpmbuild --rebuild SRPMS/Themes/blackbird-0.4-2.git20130320.fc21.src.rpm $ su -c 'yum install $(ls /home/<USER>/rpmbuild/RPMS/noarch/blackbird-[gx]*-theme-0.4-2.git20130320.fc20.noarch.rpm)' $ xfconf-query -c xsettings -p /Net/ThemeName -s Blackbird
Fits for you?
On 12/24/14 10:03, poma wrote:
$HOME/.mozilla/firefox/<PROFILE>/chrome/userContent.css /*
- Use this css file to eliminate problems in Firefox
- when using dark themes that create dark on dark
- input boxes, selection menus and buttons. Put this
- in the ../firefox/default/chrome folder or your
- individual user firefox profile chrome folder.
- */
input { border: 2px inset white; background-color: white; color: black; -moz-appearance: none !important; }
............. snip ...
Don't know where to put this stuff, can't find any of the places suggested. So I tried copy/paste into profiles.ini but that does not seem to have any observable effect.
There is so much written about profiles and what can be done there but I can't relate any of it to anything I can find in the firefox files?
What am I doing wrong? This is making me feel stupid and about to say I don't care I'll continue to use it as it is!
Bob
On 12/24/2014 02:47 PM, Bob Goodwin wrote:
Don't know where to put this stuff, can't find any of the places suggested. So I tried copy/paste into profiles.ini but that does not seem to have any observable effect.
There is so much written about profiles and what can be done there but I can't relate any of it to anything I can find in the firefox files?
What am I doing wrong? This is making me feel stupid and about to say I don't care I'll continue to use it as it is!
here : /.mozilla/firefox/rrrwrzrv.default/chrome$ ls -l total 8 -rw-r--r--. 1 pbc pbc 1165 Jul 10 2013 userChrome-example.css
yours will be /.mozilla/firefox/SOME_WIERD_NAME.default/chrome$ cat userChrome-example.css
it says: Edit this file and copy it as userContent.css into your * profile-directory/chrome/
so the existing file says: userChrome-example.css
copy that file to userChrome.css
and add those lines into it..
On 12/24/14 14:53, Paul Cartwright wrote:
here : /.mozilla/firefox/rrrwrzrv.default/chrome$ ls -l total 8
The chrome directory does not exist. Am I supposed to create it? It just seems to me it should be there by default ... if it is I can't find it:
[bobg@box10 ~]$ ll /home/bobg/.mozilla/firefox/2kkjzlsa.default/chrome ls: cannot access /home/bobg/.mozilla/firefox/2kkjzlsa.default/chrome: No such file or directory
Bob Goodwin:
The chrome directory does not exist. Am I supposed to create it?
poma:
Yep.
And, of course, swap the whites and blacks around in the CSS file. Years ago, I made a similar CSS file for reading web pages with sore eyes. I did a wildcard for make *everything* black on grey (which suited me better), rather than making tons of clauses for specific HTML elements. Then just added a few additional clauses for things like making links still different from plain text, normalising all the fonts, and adding spacing around things for clarity.
/* * "Sore eyes" * * A style sheet for sore eyes, and irritating websites. * * It normalises most of the rendering of webpages, removing * annoying colours, styles, etc. Shows certain elements in * consistent manners (e.g. bolder headings). * * I use this as a user-stylesheet in my own web browsers to * view badly styled websites. * * It takes the colour out of everything that you read, * and uses normal fonts: */
body { margin: auto !important; padding: 0.5em 1em 1em 1em !important; max-width: 45em !important; }
* { color: black !important; background: #ddd !important; font-family: serif !important; font-size: 1em !important; line-height: 1.4em !important; }
/* Makes the headings different (than the body), * but not too different: */
h1, h2, h3, h4, h5, h6 { font-family: sans-serif !important; font-size: 1.5em !important; }
/* Show up links, and make them easier to read: */
a:link { color: #0000aa !important; }
a:visited { color: #550099 !important; }
a:link, a:visited { background: inherit !important; text-decoration: underline !important; }
a:hover[href], a:active[href], a:focus[href] { color: #000 !important; background: #eee !important; text-decoration:none !important; }
/* Add padding around things that are often squashed together: */
p + h2, p + h3, p + h4, p + h5, p + h6, div + h2, div + h3, div + h4, div + h5, div + h6, table + h2, table + h3, table + h4, table + h5, table + h6, ul + h2, ul + h3, ul + h4, ul + h5, ul + h6, ol + h2, ol + h3, ol + h4, ol + h5, ol + h6, hr + div { margin-top: 2em !important; }
dt { padding-bottom: 0.5em !important; font-weight: bolder !important; font-family: sans-serif !important; }
dd { padding-bottom: 0.5em !important; }
legend, caption { font-size: larger !important; }
legend, caption, th { font-weight: bolder !important; font-family: sans-serif !important; }
th, td { padding: 0.3em !important; }
code, pre, tt { font-family: monospace !important; font-style: normal !important; }
a, span { font-family: inherit !important; font-weight: inherit !important; font-size: inherit !important; }
On 25.12.2014 06:29, Tim wrote:
Bob Goodwin:
The chrome directory does not exist. Am I supposed to create it?
poma:
Yep.
And, of course, swap the whites and blacks around in the CSS file. Years ago, I made a similar CSS file for reading web pages with sore eyes. I did a wildcard for make *everything* black on grey (which suited me better), rather than making tons of clauses for specific HTML elements. Then just added a few additional clauses for things like making links still different from plain text, normalising all the fonts, and adding spacing around things for clarity.
Global dark style - changes everything to DARK https://userstyles.org/styles/31267/global-dark-style-changes-everything-to-...
Batman flying around.
In addition, this is a good starting point http://kb.mozillazine.org/UserContent.css
On 12/25/14 15:12, poma wrote:
Global dark style - changes everything to DARK https://userstyles.org/styles/31267/global-dark-style-changes-everything-to-...
Batman flying around.
After fiddling with this for a few days I finally have home/bobg/.mozilla/firefox/iexecg9r.default/chrome/userContent.css. However finding the right parameters to change there is difficult to the point where I can better spend my time doing other things.
Fortunately I find that clicking a box with the meaningless [to me] name of "Form Enhancement" in the "Add On" BYM, another non-descriptive name, causes the unreadable lines to be displayed in reverse video which pretty well solves my display complaint.
"FT DeepDark" is probably the best add-on for the appearance that I want, how ever "BYM" Is still required to get the white text on black that I need, should anyone care about all of this.
Now I can get back to my original effort, saving the data from ios devices for installation in a new Iphone, iPad, iWhatever.
I've learned a few things from this, mainly that the directory "chrome" has to be added along with the .css file and it's there for me to experiment with.
Thanks for the help,
Bob.
On Sat, 2014-12-27 at 03:36 -0500, Bob Goodwin wrote:
After fiddling with this for a few days I finally have home/bobg/.mozilla/firefox/iexecg9r.default/chrome/userContent.css. However finding the right parameters to change there is difficult to the point where I can better spend my time doing other things.
If you wish to pursue it, try just using this bit from my example CSS, as a starting point:
* { color: white !important; background: black !important; }
That makes *everything* white on black (the * wildcard applies it to all elements), so the whole page, all gadgets, etc., should all be painted that way.
"color" set the foreground colour, white, in this case.
"background" sets the background colour (and/or background image), black, in this case.
The "!important" keyword means that your specifications are more important than the websites, so you override them.
There's a chance that you can add the same stylesheet to your mail client, too, if you use one that uses HTML formatting (which can include plain text mail, if the client renders them using its HTML engine).
On 12/27/14 09:11, Tim wrote:
If you wish to pursue it, try just using this bit from my example CSS, as a starting point:
{ color: white !important; background: black !important; }
That makes*everything* white on black (the * wildcard applies it to all elements), so the whole page, all gadgets, etc., should all be painted that way.
"color" set the foreground colour, white, in this case.
"background" sets the background colour (and/or background image), black, in this case.
The "!important" keyword means that your specifications are more important than the websites, so you override them.
There's a chance that you can add the same stylesheet to your mail client, too, if you use one that uses HTML formatting (which can include plain text mail, if the client renders them using its HTML engine).
-- tim@localhost ~]$ uname -rsvp
I created a .css file using only the lines you suggest:
{ color: white !important; background: black !important; }
That seems to provide white on black although I had to select those colors under Preferences? And I need the add-on "BYM" to display text [in reverse video] in the web page boxes requiring entry of a response.
I'll try this for a while and see how it works on different pages, so far it looks good.
Thanks,
Bob
Allegedly, on or about 27 December 2014, Bob Goodwin sent:
I created a .css file using only the lines you suggest:
{ color: white !important; background: black !important; }
The asterisk is needed, too.
The syntax is the name of the HTML elements to affect, in my example an asterisk as a wild card for them all, and the thing to do to those elements inside the braces.
e.g. The following rules would effect everything, then one that only affected H1 headings, then another that only affected paragraphs:
* {color: white;} h1 {color: green;} p {color: red;}
That seems to provide white on black although I had to select those colors under Preferences? And I need the add-on "BYM" to display text [in reverse video] in the web page boxes requiring entry of a response.
Sounds like it's not working properly, then. According to the cascading rules ("cascading" referring to rules applied on top of rules), your user style sheet should have higher precedence than a browser's own style rule set, and the website authors style rules. And the "!important" keyword just stamps that in harder with a bigger hammer (they could have used an !important style that overrided an unimportant one of yours, but they can't override an important rule of yours).
So, a user stylesheet that says style everything this way, ought to have the absolute last say in things. You shouldn't have to do anything else.
Double-check for typing errors (word spelling and all the punctuation, but spacing and formatting don't matter), the rules stop being applied the moment there's a syntax error.
* { color: white !important; background: black !important; }
I've forgotten, by now, which browser you're trying to apply this too. I've seen notes that Google Chrome is fouling this up, lately (moron coders at Google not understanding how CSS is supposed to be done). I don't know if Firefox is fouling it up at the moment (and I'm using the wrong computer to test it).
On 12/28/14 03:52, Tim wrote:
Sounds like it's not working properly, then. According to the cascading rules ("cascading" referring to rules applied on top of rules), your user style sheet should have higher precedence than a browser's own style rule set, and the website authors style rules. And the "!important" keyword just stamps that in harder with a bigger hammer (they could have used an !important style that overrided an unimportant one of yours, but they can't override an important rule of yours).
So, a user stylesheet that says style everything this way, ought to have the absolute last say in things. You shouldn't have to do anything else.
Double-check for typing errors (word spelling and all the punctuation, but spacing and formatting don't matter), the rules stop being applied the moment there's a syntax error.
- { color: white !important; background: black !important; }
I've forgotten, by now, which browser you're trying to apply this too.
Firefox 34.0 in an updated Fedora-21 64 bit XFCE etc.
The following .css file:
[bobg@box7 chrome]$ cat userContent.css # !/bin/bash # /home/bobg/.mozilla/firefox/xx34clzp.default/chrome/userContent.css
{ color: white !important; background: black !important; }
I moved it to userContent.css.xxx and deleted the working file to test with/without.
There is no perceptible difference with the .css file running. I even tried testing with add-ons disabled which puts it in "test mode," and saw no difference, however that might disable the .css file too?
These tests were done on box7 a second Fedora-21 computer, not this one which I have been using for this until now. This one, my main box is "home made," the other an old [Optiplex 755] Dell computer but both are set up nearly identical with Fedora-21.
Looking at Fox News I see what looks to me like gray text, some headings in red, on a white background. I expect it to be white text on black ... So the .css file is not doing what it should.
Bob
On Mon, 2014-12-29 at 12:57 -0500, Bob Goodwin wrote:
Firefox 34.0 in an updated Fedora-21 64 bit XFCE etc.
Here, Firefox 34.0 on up to date Fedora 20.
The uname -rsvp in my signatures (I couldn't resist putting the options in that order) is a script that always shows the specs of whatever computer I am writing my emails on.
The following .css file:
[bobg@box7 chrome]$ cat userContent.css # !/bin/bash # /home/bobg/.mozilla/firefox/xx34clzp.default/chrome/userContent.css
{ color: white !important; background: black !important; }
What's with the # !/bin/bash and other stuff? It's not an executable script, and CSS comments need delimiting in a different way.
CSS files are just a set of styling rules, the same as used in webpages and websites. So reduce that test file down to the bare minimum that I demonstrated, and it works for me.
* { color: white !important; background: black !important; }
The file just needs to be readable, nothing else.
If you want to add comments, to remind you of things in the file, you can do so using /* comment */ delimiters (begin with slash asterisk, end with asterisk slash, like I've done in prior emails).
I created a "chrome" directory inside my ~/.mozilla/firefox/vge7ihf.default/ directory, and saved that (above) four-line example as a userContent.css file, inside it.
There are plenty of other CSS tricks you can do, if needed, but just start off with getting the bare basics to work, first. Bearing in mind that if you try to do something sensible like force all fonts to be a useful readable size, you can get hamstrung by pages which shrunk the fonts to fit in the spaces they left between graphics, and they'll no-longer fit.
I've just noticed that border colours seem to need separately forcing, else some things that have borders around them may use a colour that's the same as your background choice (and they'll disappear), so you may want to add a border-color: red !important; clause in there, too (or some other more useful to you colour). And you may need to separately force input boxes, too, with a -moz-appearance: none !important; (to take away a browser built in style). Looks like the everything wildcard isn't quite everything.
e.g. Try this as your entire userContent.css file:
* {color: white !important; background: black !important; border-color: red !important; -moz-appearance: none !important;}
It's not "run," as such. But when the browser fires up, it reads that file, and applies the page styling rules on top of whatever rules already came with the browser, and the website. No plug-ins required, it's a basic thing of how browsers are supposed to do CSS.
One gotcha is that the browser only seems to read this file as it's fired up. If you change the file, you need to completely quit and restart the browser before the CSS file will be reloaded.
The Opera web browser used to be extremely flexible in letting you mess with stylesheets, but I haven't used it for some years to see what state it's in, now. Google-chrome has become designed-broken by not properly implementing a user-configurable user style sheet. But Firefox still seems to do its tricks, properly.
On 12/30/14 06:47, Tim wrote:
There are plenty of other CSS tricks you can do, if needed, but just start off with getting the bare basics to work, first. Bearing in mind that if you try to do something sensible like force all fonts to be a useful readable size, you can get hamstrung by pages which shrunk the fonts to fit in the spaces they left between graphics, and they'll no-longer fit.
I've just noticed that border colours seem to need separately forcing, else some things that have borders around them may use a colour that's the same as your background choice (and they'll disappear), so you may want to add a border-color: red !important; clause in there, too (or some other more useful to you colour). And you may need to separately force input boxes, too, with a -moz-appearance: none !important; (to take away a browser built in style). Looks like the everything wildcard isn't quite everything.
e.g. Try this as your entire userContent.css file:
- {color: white !important; background: black !important; border-color: red !important; -moz-appearance: none !important;}
It's not "run," as such. But when the browser fires up, it reads that file, and applies the page styling rules on top of whatever rules already came with the browser, and the website. No plug-ins required, it's a basic thing of how browsers are supposed to do CSS.
One gotcha is that the browser only seems to read this file as it's fired up. If you change the file, you need to completely quit and restart the browser before the CSS file will be reloaded.
I've tried the suggested lines on both computers:
[bobg@box10 ~]$ cat /home/bobg/.mozilla/firefox/iezecg4r.default/chrome/userContent.css
{ color: white !important; background: black !important; border-color: red !important; -moz-appearance: none !important;}
This seems to do most of what I want. I see that photographic images are still presented in color so many pages still contain everything but are more easily read with the white text on a black background and the red border shows that it's working.
However I've been tracking an airline flight [UAL 4215] on Flightaware.com and most of the information on map presentation as well as the graph of altitude and speed have lost most of their detail. e.g. the map shows a line from KORF to KORD and nothing else.
So I guess the simplest thing would be to be able to switch the .css presentation on and off as desired else I might be continuously revising it as I discover deficiencies. Really the map in this case is not very important but I may be missing other stuff that I'm not aware of yet?
This is interesting and helpful and I will use it as is for a while to see what else is affected.
Bob
On Tue, 2014-12-30 at 16:33 -0500, Bob Goodwin wrote:
[bobg@box10 ~]$ cat /home/bobg/.mozilla/firefox/iezecg4r.default/chrome/userContent.css
{ color: white !important; background: black !important; border-color: red !important; -moz-appearance: none !important;}
This seems to do most of what I want. I see that photographic images are still presented in color so many pages still contain everything but are more easily read with the white text on a black background and the red border shows that it's working.
Good to know. A basic re-style is less likely to throw up nasty surprises, but you are still fighting against a webpage's own styling, which may have done all sorts of tricks to make their site work.
The borders should only appear on things that were meant to have borders, so they should help reading things like tables, which would be difficult with no clue as to where the table cells were, for example.
Images will be handled completely differently, and I'm not aware of any CSS that can be applied to images. So, if you did need to change image rendering, I think you'll need to find some kind of image processing plug-in.
However I've been tracking an airline flight [UAL 4215] on Flightaware.com and most of the information on map presentation as well as the graph of altitude and speed have lost most of their detail. e.g. the map shows a line from KORF to KORD and nothing else.
Yes, that kind of thing is the risk you run when altering a website. Being able to turn it on and off on the fly is probably needed. There is a good chance that some thing will become invisible. Especially on pages where the author set a foreground colour, but never bothered to set a background colour, or vice versa, where they depended on the default being what they expected.
On 12/31/14 05:08, Tim wrote:
On Tue, 2014-12-30 at 16:33 -0500, Bob Goodwin wrote:
[bobg@box10 ~]$ cat /home/bobg/.mozilla/firefox/iezecg4r.default/chrome/userContent.css
{ color: white !important; background: black !important; border-color: red !important; -moz-appearance: none !important;}
This seems to do most of what I want. I see that photographic images are still presented in color so many pages still contain everything but are more easily read with the white text on a black background and the red border shows that it's working.
Good to know. A basic re-style is less likely to throw up nasty surprises, but you are still fighting against a webpage's own styling, which may have done all sorts of tricks to make their site work.
The borders should only appear on things that were meant to have borders, so they should help reading things like tables, which would be difficult with no clue as to where the table cells were, for example.
Images will be handled completely differently, and I'm not aware of any CSS that can be applied to images. So, if you did need to change image rendering, I think you'll need to find some kind of image processing plug-in.
However I've been tracking an airline flight [UAL 4215] on Flightaware.com and most of the information on map presentation as well as the graph of altitude and speed have lost most of their detail. e.g. the map shows a line from KORF to KORD and nothing else.
Yes, that kind of thing is the risk you run when altering a website. Being able to turn it on and off on the fly is probably needed. There is a good chance that some thing will become invisible. Especially on pages where the author set a foreground colour, but never bothered to set a background colour, or vice versa, where they depended on the default being what they expected.
Thank you for the help, this has filled in a big gap for me; I now have a section Firefox > .css in my Notecase-pro notes.
Bob
On 12/23/2014 10:00 AM, Bob Goodwin wrote:
I am curious about the HTML, this is F-21 with Thunderbird 31.3.0 and I have found no option to kill the HTML to the list. I have set it to send plain text to fedoraproject.org and I am careful to remove text styles, etc. from every message I send to the list.
Go to the Account settings for this email address and uncheck the box that tells it to compose messages in HTML. And, while you're at it, tell it to start your message below the quoted text because top posting is an abomination.
On 12/23/14 13:17, Joe Zeff wrote:
Go to the Account settings for this email address and uncheck the box that tells it to compose messages in HTML. And, while you're at it, tell it to start your message below the quoted text because top posting is an abomination.
"uncheck the box that tells it to compose messages in HTML"
That's about like me telling you to go check that box! I exchange many more html messages than plain text and I want it this way. Until this version of Thunderbird I had the ability to click on plain text only and it went that way. If this becomes a major issue I will have to change to something else, perhaps Seamonkey?
However I just noticed "Options" at the top of the mail composition window and there I can once again select plain text! I did that for this message. I just did not see that before, wont miss it now that I know it's there. Dunno if that will eliminate the color complaint?
Respond below the quoted text has been the Fedora Thunderbird default for quite some time now and I have only done it that way for years since to me it is logical. I used to get complaints from Windows users but they have given up on me!
Thanks for the help,
Bob
On 12/23/2014 11:50 AM, Bob Goodwin wrote:
That's about like me telling you to go check that box! I exchange many more html messages than plain text and I want it this way. Until this version of Thunderbird I had the ability to click on plain text only and it went that way. If this becomes a major issue I will have to change to something else, perhaps Seamonkey?
*Shrug!* Email is for communication and html is for making things look pretty. I'm on one mailing list where the software removes all html, leaving only text. Every now and then there's a post containing nothing but a notice that the html part was removed and much merriment ensues.
On 12/23/14 14:55, Joe Zeff wrote:
*Shrug!* Email is for communication and html is for making things look pretty. I'm on one mailing list where the software removes all html, leaving only text. Every now and then there's a post containing nothing but a notice that the html part was removed and much merriment ensues.
To me it is an unimportant issue, sometimes the text size varies but I select the text style and color of what I view. I would have to check the "Source" to know what mode you are sending. It certainly does not warrant filtering, I have never understood that attitude. As you say, *Shrug!*
On 12/23/2014 02:50 PM, Bob Goodwin wrote:
However I just noticed "Options" at the top of the mail composition window and there I can once again select plain text! I did that for this message. I just did not see that before, wont miss it now that I know it's there. Dunno if that will eliminate the color complaint?
that did it.. now nicely plain text. it worked!
On 12/23/2014 11:00 AM, Bob Goodwin wrote:
On 12/23/14 12:42, Steven Stern wrote:
Hey, can you turn off the HTML mail? white on black is really really hard to read.
Anyhow, the phones don't back themselves up to iCloud unless their locked and on WiFi, so it shouldn't be hitting your wireless data usage plan.
Otherwise, use iTunes... it runs nicely on XP in VirtualBox.
I am curious about the HTML, this is F-21 with Thunderbird 31.3.0 and I have found no option to kill the HTML to the list. I have set it to send plain text to fedoraproject.org and I am careful to remove text styles, etc. from every message I send to the list.
I did observe that it appears to be sending both however. When I view the "source" it is sending plain text followed by the HTML. I have not found a way to change it back as it was where I could select plain text only before sending. It looks like a new "feature?"
I am open to suggestions.
Bob
Hi Bob, since as you say you are using Thuderbird, then what you do is click on Contacts (the blue book-like icon) and edit the fedora users contact and change "Prefers to receive messages formated as: and it has a drop-down menu, from which you select "Plain text"
After that, all you emails to the list will be in plain text.
Cheers,
JD