[scribus-dev] Scribus documentation translations temporarily removed from builds

Louis Desjardins louis.desjardins at gmail.com
Mon Nov 29 16:14:53 CET 2010

2010/11/29 Gregory Pittman <gpittman at iglou.com>

> On 11/28/2010 10:23 PM, Louis Desjardins wrote:
>> 2010/11/28 Gregory Pittman <gpittman at iglou.com <mailto:gpittman at iglou.com
>> >>
>>    I think that when we get some translators on board for the docs, the
>>    screenshots aren't so hard to do. If we knew we had them, I could be
>>    making dialog screenshots in various languages as I go...
>> Good evening Greg,
>> The issue here is to have material readily available to whoever wants to
>> translate any part of the documentation without even having to ask for
>> it.
> I disagree. The issue is getting translators on board actually working on
> the translations. The raw material they need is present in the 1.3.9svn
> version of Scribus. Witness our Italian friend Alevati feverishly working on
> Italian translations for the wiki pages, and it doesn't seem he is inhibited
> by the use of English-language screenshots.

I guess this mostly depends on the skills of the translator. I am still on
the opinion that if we’d have an automated way of outputting those
screenshots, it would be helpful. Mind you, we don’t need to run the script
all the time. But from time to time, when for instance a stable version is
released, then we can produce the screenshots for all.

> One of the big problems we had with the printed manual was getting output
> from those who told us they would contribute. I can step in and begin making
> screenshots showing the content pertinent to the text, in whatever language.
> It may be that some translators won't mind or would prefer to make their
> own.
> There is not quite so much work as it would seem, since there is still
> quite a bit of content that Christoph and I agree is quite out of date, and
> wrong to varying degrees, with screenshots that make little sense in the
> context of current Scribus versions.

I am not talking about wrong or outdated content but I am looking ahead to
see how we could improve the translation of the doc. To me, it is *not* a
success so far. We have outdated French translation, and I don’t know the
status for German. Do we have other translations for the doc? Now I am happy
to read we’re going to have an Italian version. We have 49 languages in the
GUI list. When we call up the online help, we are sent to:


where we have currently 3 languages. This is short, don’t you think ?

The screenshots of this doc seem outdated for most of what I see after a
quick overview — however much of this information is still valuable as the
program has evolved but we are still in DTP... and the basic principles are
covered. Anyway, this needs to be updated too.

If the doc was available for translation as a wikipedia article for
instance, and we could merge automatically — when the developers think it is
time to do it — the screenshots, then I think we could see more action on
the translation front.

Do you know how many screenshots we have in the Manual ?

Of course, don't get me wrong, I don’t think it is only a matter of
screenshots... of course.

I am looking for a solution. To me, one book in English and online help in 2
more languages is a signal that something needs to be improved. I don’t say
my solution is the best but I think it’s worth digging a bit in that
direction. Only showing the work is already started can convince someone to
step in and give a hand.


> Greg
> _______________________________________________
> scribus-dev mailing list
> scribus-dev at lists.scribus.net
> http://lists.scribus.net/mailman/listinfo/scribus-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scribus.net/pipermail/scribus-dev/attachments/20101129/cdfe1557/attachment.htm>

More information about the scribus-dev mailing list