Am 30.05.2011 10:30, schrieb Mario Sanchez Prada: > Hi! > > On Sun, 2011-05-29 at 20:22 +0200, Claude Paroz wrote: >> Le dimanche 29 mai 2011 à 18:10 +0200, Łukasz Jernaś a écrit : >>> 2011/5/29 Mario Blättermann <mari...@freenet.de>: >>>> Hello, >>>> >>>> the frogr module [1] has a Mallard based manual. It isn't complete yet, >>>> but already worth translating (currently 56 strings, including 4 >>>> pictures). Please would somebody add it to the D-L view? >>> >>> Hi Mario! >>> >>> If you add the help files to the build system they should get included >>> on D-L as far as I remember, the attached patch should help. >> >> Not always, it depends on how the initial setup of the module has been >> done in D-L. I just added the missing bit. >> >> However you're right in that the build system is currently broken for >> the help part of frogr. >> I wonder if it wouldn't be better to use the new itstool based build >> system, as Shaun has recently done with gnome-user-docs [1]. >> >> [1] http://git.gnome.org/browse/gnome-user-docs/commit/?id=c12275f8 >> >> Claude > > The addition of those new files to frogr is still work in progress, in > the way that we just added the .page files (and some pictures) to the > source tree and we still lack some needed changes to integrate them into > the build process for the project, as you have noticed. > > The plan so far was that Pierre (the contributor who filed the bug and > provided the initial .page files) provided those needed changes to > integrate it in the build process, which is something that he already > did (see [1])... but now you mentioned this about a new build system for > the documentation perhaps that patch he proposed would need more > changes. > > Thing is that, as I have no idea about these kind of (help related) > topics, I'm not sure about what would be the good next step to make so, > so it would be awesome if someone with more knowledge could take a look > to the bug currently tracking down these new additions to frogr, and > comment on the patches that Pierre are sending there: > https://bugzilla.gnome.org/show_bug.cgi?id=651337 > > Also, as I said Pierre in there, please feel free to commit whatever you > want to frogr related to the addition of these new documentation related > files. That probably would be faster (and safer) that relying on me to > review and commit changes :-) (after all, I don't have the proper > knowledge for that yet) > > Last, but not least, please accept my apologies if adding these new > files without integrating them into the build+translations machinery > annoyed you in some way. If that's a problem because of some reason (I > don't know, perhaps it broke something in the l10n machinery), we could > always withdraw those files by now, keep iterating in the bug, and apply > them back once an "atomic" patch is ready. > Due to that the *.page files are already committed, the patch won't become that big. In any case I would prefer the "bleeding edge" way by using itstool. The new gnome-user-docs (master) is an example.
@Łukasz: Would you have a look at it? Although I've migrated some docs to the gnome-doc-utils workflow, I'm not familiar yet with yelp-tools and the appropriate utilities. Perhaps we should ask for help in the gnome-doc-list anyway (CC'ed). Best Regards, Mario _______________________________________________ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
