PNG screenshots were showing up with odd coloration due to incorrect
or malformed color management settings (ICC profiles). In an earlier
commit, thes PNG files were transformed to JPEGs, and this did cause
the coloration problems to go away, but a new problem took its place;
during docbook PDF generation, warnings like the following started
showing up:
An ICC profile is present but it is invalid (Invalid ICC Profile
Data). The color profile will be ignored. (.../quotes-aggregator.jpg)
The solution was to download Seashore (http://seashore.sourceforge.net,
Mac-only) which has an embedded ICC profile editor. Each of the three
offending JPEG images were loaded and re-saved to JPEG format, but
targeting 'web' output which eliminates all ICC profile metadata.
This avoids the issue we were seeing in SI the reference doc PDF where
admon graphics (tip, warning, note, etc) were 'fuzzy' because 24pt
graphics were being blown up to 36pt.
For reasons unknown, most PNG files were showing up in the PDF output
with reverse coloration (or at least significantly shifted. Saving
these files as JPEGs provided a cheap workaround.
Also a number of images were either (a) exceeding the boundaries of the
PDF viewport or (b) scaling down to thumbnail size.
Now using width/contentwidth/scaling attributes in <mediaobject>
elements, as described at http://www.sagehill.net/docbookxsl/ImageSizing.html
to ensure that all images show up correctly scaled in both HTML and PDF
outputs.
Complete:
--------
- src/* documentation resources moved to 'docs' subproject
- docbook sources upgraded to Docbook 5
- formatted all docbook sources to strip tab characters and
eliminate trailing whitespace
- all projects compile and test successfully
- all artifacts upload successfully to s3, static.sf.org, etc.
Remaining:
---------
- documentation L&F needs work. CSS, images, and highlighting aren't
hooked up properly
- spring-integration-jdbc codegen bits in Maven POM need to be
transcribed into gradle
- dependencies that were optional or provided scope in maven are
currently 'compile' scope in Gradle. Need to figure out support
in Gradle to fix this.
- run through Eclipse classpath and project generation scenarios
- delete all Maven artifacts
