colorsgugl.blogg.se

Kindle match svg inherit font color
Kindle match svg inherit font color











kindle match svg inherit font color

CSS is injected to target iBooks and use a filter to invert Viewer doesn't render it, but Firefox does for example.) Which has spotty support in some SVG renderers.

kindle match svg inherit font color

The hanging power cord in the SE logo isĭefined using stroke, and that stroke is set to `currentColor` For most systems this should just be #000, and anĮreader that supports SVG and is smart enough to change theĭefault fill/stroke color for the SVG when night mode turns on canĬhange it to #FFF. SVGs no longer define a fill color, leaving it to theĭefault. `epub:type="se:color-depth.black-on-transparent"` as a signal to OK, I've done a test build for some of these concepts. At the very minimum I think that would be one That would be an explicit OK from theĮbook author to allow the reading system to set a readable colorįor the image.

Kindle match svg inherit font color how to#

SVGs are another great candidate, and I think it would be reallyĮxcellent if the reader knew how to invert them if their color was Something unsemantic like `epub:type="invert-me-please"`. Invertible, and we add rich semantic information instead of saying That would be anĮxplicit OK from the ebook author that those images are `epub:type="black-on-transparent line-art"`. Line art, maybe some subclass of etchings. So obviously invertible images are things like images of text, Rich greyscale images, which we also would not want to invert.) (Note that you could have, for example, a monochrome green image,Īnd inverting that would not be correct and you can also have In the general case are black-on-transparent line-art images. Well, just about the only kinds of images we would want to invert Would understand as being able to be inverted for night mode? How could we add semantics to images that a smart reading system `class="night-mode-ok"` attribute on every tag. Invert text color because we included a (for example) Today, you can turn on night modeĪnd reading systems know to invert the text color and backgroundĬolor, because that's how the document is laid out.

kindle match svg inherit font color

So with that in mind, going back to night mode, I think the bestĪpproach would be to leave night mode styling to the reading Mind that HTML was originally designed to mark up documents for The tools we need to make it happen today. The general web for quite some time, and HTML5 and CSS give us all This switch to semantics-based development has been brewing in Then reading systems style the content based on that description. One where epub authors use semantics to describe the content, and A Reading System might ship with one night mode (white on black) then add another one (white on gray), etc., and this is definitely something we’d better take into account from the start.Īs I mentioned a little upthread, I think the best approach is gray background in iBooks) and you can’t necessarily have the same styles for each night mode, especially when it comes to filters.

  • Night mode is plural, it’s night modes (cf.
  • don’t support alt stylesheets, I would most definitely not bet money on 100% of CSS authors providing an alt stylesheet for night mode
  • alternate stylesheets have been discussed but there’s millions of books who won’t have an alt stylesheet (that’s some kind of debt we must take into account and see how we can manage that at the Readium 2 level).
  • people have been trying to hack their way to invert images in night modes for a while (using reserved attributes for the Reading System, gaiji metadata in iBooks, etc.) so there’s clearly an urgent need but hacks can have severe impacts at the reading system level.
  • Consequently the colors used in the baseline will not necessarily be the same in each Reading System using the CSS
  • we’re making a baseline, which means implementers will be able to customize it.












  • Kindle match svg inherit font color