Hi Paulo,
Thanks for the answer:
Le 2011-06-15 07:40, Paulo de Souza Lima a écrit :
2011/6/15 Simos Xenitellis<simos.lists@googlemail.com>
<snip>
I think it's a great idea to have a LibreOffice magazine, created
using LibreOffice.
=) We have done that for a long time already. Texts are made in Writer.
Design is made in Draw. Only a few details, like image editing, are made
in
Gimp.
There are smaller FLOSS communities that manage to use XeLaTex (!)
effectively to create shiny magazines, so this should be doable.
For marketing purposes, it would be nice to make available the source
of the magazine
along with the PDF version. The users would be confident that they can
create a quality
magazine of their own.
All sources (ODF and ODG files) are available in the wiki. You can check
out
for files contained in cathegory "Revista" and "PT-BR". Unfortunately (and
I
personally don't agree with that), there are no references to the sources
of
the older contents.
+100
Re: use of Latex: It would be quite an unfortunate event, if we were to
produce and publish in Latex rather than using our own LibreOffice suite and
in our own format ODF which we market as being able to to all of this.
BrOffice has proven quite well how LibreOffice CAN and IS used to produce a
high quality magazine. BrOffice IS the example to follow and to emulate for
all of us.
This is the kind of marketing event that marketing departments drool over.
All of my deepest congratulations to the BrOffice team who have shown what
LibreOffice is able to do when applied in a high quality publishing
environment.
For the possible localisation of the magazine, it's up to each
LibreOffice localisation team
to take up the task.
Ideally, the translatable text in the magazine document would be
marked with a certain paragraph style, and then the text would be
extracted in PO files suitable for translation. Then, once the PO
files are translated, the reverse process would create back the
localised magazine.
That's a great idea! People from local communities could also choose what
contents they would use in their local magazines. All contents would be
available in one source. Our concern on that always was: Are there
volunteers enough to do that?
We have already covered this from the last conversations on this topic ...
but ... if we have matured enough, and, if we can have some people commit to
the localization and collecting of news articles for their own language
groups, then great! The frequency of publication would not have to be the
same for each locale, some could be published on a monthly basis, every two
months, every 6 months or even annually for some groups.
IMHO, as the BrOffice team have more than proven their ability in producing
a high quality magazine using our LibreOffice suite and in our format ODF,
the production process is already there, the production team is there, the
commitment is there, then, all we need are for the different localization
teams (those interested in participating in such a project) to join the
BrOffice team.
I believe that the BrOffice team had earlier shown an interest in leading
this kind of venture. I don't know if this commitment is still there. I hope
it is.
The challenge of publishing an international LibreOffice magazine has always
really been a matter of getting the different NL groups to step up and
organize their localizing and news gathering teams. If the NL groups are
able to do this, then yes, we could organize a truly international
LibreOffice publication.
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.