#252 Fedora flyer
Closed: Complete Opened by alciregi.

First of all, excuse me but I recently joined the Fedora community.
Looking at https://fedoraproject.org/wiki/Marketing_Fedora_flyer, I took the initiative to translate and adapt the flyer linked there.
Only later I had the news that such page is a bit outdated, even in regard to colors and logo.

I think that, during some events, having a more or less generic flyer ready to print could be useful in order to advertise Fedora. I like the foldable format, so as said before, I took the initiative to create an italian version.But maybe I did not do the right thing.

I've also spotted that there are old (circa two years ago) and closed tickets about flyers, and I have seen that @ankursinha created a Latex verison of the flyer, but it is outdated as well.
Could we discuss again about the flyer? Or do you think that it is a dead topic?

Thanks
A.


I'd created the LaTeX version hoping that that would make translation easier - LaTeX sources are plain text files and with everything on a Github repository, I thought people could submit translations easily too. The basic idea was to break the text and design into two independent systems, which LaTeX does quite well since you can include text from other sources and so on. A bit of makefile magic would work build the finished PDF quite easily.

Over the years, the flyer has usually been created in Libreoffice (or Scribus?), and I do not know enough about either of these to say if it is possible to have various translated versions of the same flyer in one unified document. :(

PS: I think there's a ticket somewhere on updating the flyer already. I just can't find it at the moment. Maybe the design pagure repo?

I think that having a LaTeX document should not be a problem as far as the changes to perform are related only to the text to translate.
I think that an updated and unified, easily translatable flyer would be of value.

I think that having a LaTeX document should not be a problem as far as the changes to perform are related only to the text to translate.
I think that an updated and unified, easily translatable flyer would be of value.

Sure - the obvious limitation with LaTeX is that it isn't design friendly - as in, there's only so much one can modify. It certainly isn't a tool that the design team uses.

I had briefly looked into Scribus and the scripting support it provides: https://wiki.scribus.net/canvas/Category:Scripts

Here's some hacking I had done for a start - a simple script: http://ankursinha.in/blog/2015/06/26/scripting-in-scribus.html

The idea, again, is to describe everything in the script, and use translated text sources to publish the various variants. With scribus, the design team can come up with a layout that can be reproduced in a script with the required text. So:

  • the design team comes up with a layout
  • the marketing team comes up with the text
  • community members come up with translations
  • a script puts all this together to generate the various pdfs

Just my opinion of course - if someone's aware of a better/simpler way, we should certainly look into it. :)

the design team comes up with a layout
the marketing team comes up with the text
community members come up with translations

Agree. There are rules that must to be follwed. Not simply related to the text to edit but rules about design (logo, colours), about mktg sentences and about translations.

We absolutely agree when someone is taking care of tasks, and we encourage to go ahead.

The correct way is to involve the community, so we will discuss this ticket in the next meeting.

Thanks for the head up.

Gabri

As briefly discussed during today meeting, I asked to the design team what they think about a flyer: https://pagure.io/design/issue/526

Metadata Update from @x3mboy:
- Issue tagged with: meeting

Metadata Update from @jflory7:
- Issue untagged with: meeting
- Issue priority set to: no deadline
- Issue set to the milestone: Future releases
- Issue tagged with: blocked, outreach

Since this was redirected, I will close this issue as fixed.

Metadata Update from @x3mboy:
- Issue close_status updated to: Complete
- Issue status updated to: Closed (was: Open)

Metadata