Greetings,
What is the benefit of enforcing image filename conventions? We label
our images many times by where they exist in the document
(figs/ch/section-name.<ext>). I could even see a format such as
"figs/<lang>/<some-dir-hierarchy>.<ext>". Is the main goal to
simplify
the spec file %files?
Thanks,
James Laska
On Fri, 2005-12-09 at 16:09 -0600, Tommy Reynolds wrote:
Hello, ya'll!
Some folk have their document images in a "figs/" subdirectory tree
under the document directory. Large documents may have additional
"figs/part1" style subdirectories, too.
The lack of a formal filenaming scheme makes selectively copying
files awkward. Below is our current convention:
<filename>-<locale>.<ext>
such as "watermark-ru.png". Simple, eh?
The problem is that some filenames use the "-" minus sign to separate
words in the filename:
this-is-my-picture.png
Is "picture" part of the filename or the language designation? It is
difficult for a shell script to decode this just by looking at the
filename.
I propose a file naming scheme to simplify the selective copying of
files. This will help reduce the complexity of the RPM packaging
tools.
Only three formal rules are needed:
1) The minus sign "-" may not be used as part of the filename
component.
1) The minus sign only introduces the locale for the file.
1) Filenames without a locale component are considered language
neutral.
With these conventions in place:
"foo.png" is a language-neutral graphic.
"foo-it.png" is a graphic with Italian text.
"foo-bar.png" is not permitted usage.
Comments? Alternatives? Bribes?
Cheers
--
fedora-docs-list mailing list
fedora-docs-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-docs-list