24 Oct
2014
24 Oct
'14
1:25 p.m.
[snip]
Again, the issue with DCP-o-matic is - should we
help/encourage
people creating DCPs who do not bother reading the documentation
first? ;-)
Absolutely, IMHO :)
Then of course, documentation is very often a weak
point in open
software projects, and the docs for DCP-o-matic are no exception. I
wish there would be an easy way to work on the documentation
collaboratively in all relevant languages. The guys who contacted me
about the problems with single image sequences were not good in
understanding english anyway, and as long as there is no
documentation in other languages, we should keep the localized GUI as
descriptive as possible. Aside from RTFM issues - there is no point
in a GUI being unnecessary cryptic ;-)
I haven't found a good collaborative translation tool for book-type
content. As it stands, I think a translator would be best translating
doc/manual/dcpomatic.xml (DocBook source). Sadly the manual is always
up to date...
Carl - not tyring (;-) to make this issue more
complicated, but
taking up your suggestions, when I choose to import an image sequence
in Quicktime Pro Player, I get this:
Interesting... you can set that up in the "Timing" tab after import.
Maybe it's better to have a dialogue like that so that the user is
forced to think about it...
Best,
Carl