Thanks for the info so far guys! I'm actually quite familiar with XML through writing manifests, though I don't imagine this knowledge will really be applicable to documentation editing, as the purposes of the two are very different.
I'll do a bit of research on the workflow to better understand how this all works (is the definitive guide still useful?). In the mean time, if any there's any less-critical work that I could get started on, let me know and I'd be glad to help!On Mon, Oct 23, 2017 at 10:03 AM, Pat David <patdavid@xxxxxxxxx> wrote:
Julien,Is there a list (or maybe off the top of your head you'll know) of a couple of simple places a new contributor could get their feet wet helping out? Maybe something relatively easy to get accustomed to the workflow?Also, is the workflow for participating something we should document on the website somewhere also? I'm happy to help get a page setup with your info!patOn Mon, Oct 23, 2017 at 1:34 AM Marco Ciampa via gimp-docs-list <gimp-docs-list@xxxxxxxxx> wrote:On Sun, Oct 22, 2017 at 12:30:58PM -0400, Morgan Lupton wrote:
> Hey everyone,
>
> I'm a big fan of this project, and I've been a GIMP user for many years.
> I'm by no means a skilled enough developer to contribute in code, but I
> would like to lend a hand by writing, editing, formatting or modifying any
> GIMP documentation that needs extra work.
>
> I've written countless enterprise docs for clients during my employment at
> Red Hat as a consultant, including wikis, procedural guides, and reference
> glossaries. I've recently returned from a position as a site reliability
> engineer over in Europe and am hoping to transition into a technical
> writing role stateside, which I believe is a better fit for my skills and
> experience.
>
> Is there a documentation Github page or taskboard you can point me towards?
> Most of the docs I've written aren't really publicly available, but I do
> have a short procedural doc I can send your way if it's necessary to
> provide a sample.
>
> Let me know if you need anything else, looking forward to helping out the
> GIMP Team!
>
> Best,
> Morgan
Hi Morgan and welcome aboard!
I'm the Italian translator of the manual, so please forgive my bad
English. The GIMP manual is written in docbook-xml, and converted by the
source code present in its repository in PDF and HTML. The strings are
automatically extracted by a series of very smart scripts and Makefiles
into .po files (see the gettext docs) for the use of us -translators-.
Translated strings are then riconverted into docbook by means of the same
scripts to obtain the different languages versions of the docs. The
mechanism is very smart. In this way translators can focus on the
translation and every small modification or update in the original source
text will automatically transmitted to the translations in the form of
marked strings to update/translate.
It is very important to understand the mechanism and keep it working to
permit to translators to work.
Docbook permits also to have "anchors" in the text that make the "context
help" through the pressing of the F1 key work inside GIMP.
Hope this help you clarify matter...
Regards,
--
Marco Ciampa
I know a joke about UDP, but you might not get it.
------------------------
GNU/Linux User #78271
FSFE fellow #364
------------------------
_______________________________________________
gimp-docs-list mailing list
gimp-docs-list@xxxxxxxxx
https://mail.gnome.org/mailman/listinfo/gimp-docs- list
--https://patdavid.net
GPG: 66D1 7CA6 8088 4874 946D 18BD 67C7 6219 89E9 57AC
_______________________________________________
gimp-docs-list mailing list
gimp-docs-list@xxxxxxxxx
https://mail.gnome.org/mailman/listinfo/gimp-docs- list
--
G. Morgan Lupton IV
College of Arts & Sciences '15
Department of Computer Science
College of Arts & Sciences '15
Department of Computer Science
University of Virginia
+1-434-209-0123
_______________________________________________ gimp-docs-list mailing list gimp-docs-list@xxxxxxxxx https://mail.gnome.org/mailman/listinfo/gimp-docs-list
