So - while we don't make a major decision about the roadmap (hello LGM :-) ), or have a branch to work on changes for GIMP -2.10 - do we have at least a wiki page where we can take notes of things that should go into the manual?
(I'd be for creating a "2.10" branch and start editing the XML english SRC there - there will be quite a lot of news for this release, and it would be said to have to wait over an year for the manual to catch-up when it is out). I remebered this e-mail thread because I added some changes to the "align" tool yesterday, which would make for 1 or 2 paragraphs in the manual - but also, now, looking at the logs I saw just this: """ commit dd648b1c1264a70ade137276293e827b40954eca Author: Michael Natterer <mi...@gimp.org> Date: Sun May 19 22:21:38 2013 +0200 ...skipping... Don't allow tool operations on invisible items, just like we do for group layers or locked items. Cleaned up and enhanced the patch a bit --Mitch """ Which means: trying to paint in an invisible, active, layer works up to GIMP 2.8, but is a NOp in GIMP Master. It is there for over an year, and I had not taken note - yet, it should be mentioned in the manual, as it is in some aspects a big change in the way GIMP used to work. (And I see no drawbacks in it) js -><- On 12 February 2014 00:21, Roman Joost <romanof...@gimp.org> wrote: > Dear RyoTa, > > On Fri, Feb 07, 2014 at 11:52:13PM +0900, RyoTa SimaMoto wrote: >> Hi, >> >> I am warry about to use Publican. >> >> Publican prohibits to use <link linkend="...">WORD(S)</link> tag >> then allows <xref linkend="..."/> tag only for internal hyperlink. >> (xreflabel is also disallowed.) >> http://jfearn.fedorapeople.org/en-US/Publican/3.2/html/Users_Guide/appe-Users_Guide-Disallowed_elements_and_attributes.html >> >> That means we need revise whole text so that each targeted section >> has a <title>. In much cases on our document, we use <link> with >> verb/noun for representing an action, a filter, or a tool of GIMP >> instead of using its title in the reference section. To replace it >> with <xref>, almost links may be reformed in 'see also' style, >> because it cannot be replaced with other adjusted phrase for inline >> context at referring text. > Cheers for pointing this out. It seems that this needs to be looked at > closer in order to figure out the best way to go about it. A migration > seems to be quite costly... > >> >> I presume some translators may unwelcome this restriction especially >> for languages that have conjugation and/or declension, when <xref> >> tag happens in the middle of text structure. > Thanks for this valuable pointer. To keep the discussion for this topic > in one place, would you mind moving this to the associated bug? > > https://bugzilla.gnome.org/show_bug.cgi?id=723512 > > Cheers! > -- > Roman Joost > www: http://www.romanofski.de > email: romanof...@gimp.org > _______________________________________________ > gimp-docs-list mailing list > email@example.com > https://mail.gnome.org/mailman/listinfo/gimp-docs-list _______________________________________________ gimp-docs-list mailing list firstname.lastname@example.org https://mail.gnome.org/mailman/listinfo/gimp-docs-list