I am planning to do a little housecleaning in CVS, but particularly the
"docs-common" module. We have a number of areas in that module in which
rendered content is saved along with source data, when this content
could be produced on an "as-needed" basis by the user. Here are some
examples:
1. Eliminate PNG and EPS files from docs-common/images/ and
docs-common/stylesheet-images/, instead saving only SVG (XML) and using
PO and librsvg2 to generate new PNG files. Include a single fallback
watermark so that users do not need to install librsvg2 (and drag in
GNOME) to test document builds.
+ Saves >800 KB of d/l bandwidth for users.
+ po/ directory should pick up ACL mask for translators.
2. Eliminate repetitive XML files from docs-common/common/ and
docs-common/common/entities/, again using PO instead, and adapting build
tools to use PO on-the-fly rather than requiring users to download
unused files.
+ Saves >600-700 KB of d/l bandwidth for users.
+ No additional tools required other than what is already used (xml2po)
3. I also see there is some chaff in the
docs-common/stylesheet-images/, particularly a "titlepage.png" and
"titlepage.eps" that were probably there for testing the press release
stuff back in the day. I will probably remove those to the attic; SVG
gladly accepted to replace them if desired.
+ Saves 1 MB (!) of d/l bandwidth for users.
Although a simple "du -sk" command shows that docs-common is over 6.5 MB
in size, that's a bit misleading, as we're seeing *disk block usage*.
That number reflects 50-75% overhead for many of the small (< 4KB) files
in use. "du -sbc" shows a much more reasonable ~3.3 MB. The savings
above should cut that down to just several hundred KB.
Discussion?
--
Paul W. Frields, RHCE http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
Fedora Project: http://fedoraproject.org/wiki/PaulWFrieldsirc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

I am planning to do a little housecleaning in CVS, but particularly
the
"docs-common" module. We have a number of areas in that module in which
rendered content is saved along with source data, when this content
could be produced on an "as-needed" basis by the user. Here are some
examples:

I laid some groundwork for this tonight by updating both the
Makefile.common and all the document-specific Makefiles. These changes
will allow users to do either single-module or full repo checkouts and
have their documents build properly.
If you have anything checked out from CVS, you need to update, including
your copy of docs-common.
--
Paul W. Frields, RHCE http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
Fedora Project: http://fedoraproject.org/wiki/PaulWFrieldsirc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

On Sat, 2007-03-10 at 11:22 -0500, Paul W. Frields wrote:
> Discussion?
None required here, your ideas rock.
I particularly like that we can have SVG + PO to make localized images
very easy ... right?
What do we do about screenshots and other raster images? In terms of i)
common files (when needed), and ii) l10n.

Well, these are all on a module-by-module (doc-by-doc) basis. We want
to rely on SVG as much as possible. There's really no way to
"translate" raster images; we have to rely on three things:
1. We only use screenshots where absolutely necessary
2. Users can always fall back to en_US as a crutch since the UI should
remain relatively constant
3. The build tools already allow for other l10n versions of screenshots
Did I interpret your question right?
--
Paul W. Frields, RHCE http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
Fedora Project: http://fedoraproject.org/wiki/PaulWFrieldsirc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug