Re: [Gimp-docs] unclear sentence

2017-11-21 Thread Marco Ciampa via gimp-docs-list
On Tue, Nov 21, 2017 at 02:47:59PM +0300, Alexandre Prokoudine wrote:
> Sure, it's just a missing word. Go ahead and apply the patch :)
> 

Done: commit a00af04c3b9657dc20d45274609683d43a30cf64

Thanks,

--


Marco Ciampa

___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


[Gimp-docs] unclear sentence

2017-11-20 Thread Marco Ciampa via gimp-docs-list
Hello Authors,
my humble opinion is that this sentence is a bit unclear:

src/filters/blur/linear-motion.xml:41(para)
msgid ""
"This filter creates a linear in a direction determined by the Angle option. The default direction is horizontal to the right (0.000 "
"degree)."

I would change it in: 

"This filter creates a linear blur in a direction determined by the 
Angle option. The default direction is horizontal to the right (0.000 "
"degree)."

Do you agree?
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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


[Gimp-docs] during warp transform translation editing I have seen...

2017-10-30 Thread Marco Ciampa via gimp-docs-list
Hello devs,
I may be wrong but I think that this page:

https://docs.gimp.org/2.9/en/gimp-tool-warp.html

should be edited since I have not seen any "Black, White>" (and the ">"
in the end is weird...) in the actual dev gimp tool ...

src/toolbox/transform/warp-transform.xml:268

TIA

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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Help Needed for Documentation Writing?

2017-10-23 Thread Marco Ciampa via gimp-docs-list
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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] gimp-docs-list Digest, Vol 57, Issue 9

2017-09-28 Thread Marco Ciampa via gimp-docs-list
On Thu, Sep 28, 2017 at 12:00:53PM -, JOHN BULLOCK wrote:
> I am in the process of consolidating my two e-mail addresses.  I will be
> deleting my jbull...@usa.net e-mail address after January 1, 2018.  Please
> correct your contact information for me.
> Thank You,
> John Bullock
> johnjamesbull...@gmail.com

Please ban this email...

-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] GEGL .mo files

2017-09-25 Thread Marco Ciampa via gimp-docs-list
On Mon, Sep 25, 2017 at 01:22:28PM +0300, Alexandre Prokoudine wrote:
> On Mon, Sep 25, 2017 at 9:58 AM, Julien Hardelin wrote:
> > I use the gimp-2.9.7 ppa of Ubuntu, and there is no /usr/local/share/locale
> > directory and no gegl-0.3.mo in my system.
> 
> How about '$ locate gegl.mo'?

Better:

locate gegl|grep .mo

-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] GEGL .mo files

2017-09-25 Thread Marco Ciampa via gimp-docs-list
On Mon, Sep 25, 2017 at 08:58:48AM +0200, Julien Hardelin wrote:
> I use the gimp-2.9.7 ppa of Ubuntu, and there is no /usr/local/share/locale
> directory and no gegl-0.3.mo in my system.
> 
> I did not succeed in installing gimp from source. On which system did you
> install gimp from source?
> 
> 
> >I compile from source and it installs in
> >
> >/usr/local/share/locale/fr/LC_MESSAGES/gegl-0.3.mo
> >

Ubuntu 16.04 64bit

-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] GEGL .mo files

2017-09-24 Thread Marco Ciampa via gimp-docs-list
On Sun, Sep 24, 2017 at 09:23:53PM +0200, Julien Hardelin wrote:
> I translated gegl in a po file.
> 
> I validated this po file with msgfmt and got a messages.mo file.
> 
> I want to apply this .mo file to gimp-2.9.7 (many filters are gegl
> dependent).
> 
> There is no gegl .mo file in usr/share/locale/fr/LCMESSAGES.
> 
> Where is this messages.mo (renamed) to be placed ?
> 
> I use Ubuntu.
> 

I compile from source and it installs in 

/usr/local/share/locale/fr/LC_MESSAGES/gegl-0.3.mo



-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] GEGL .mo files

2017-09-24 Thread Marco Ciampa via gimp-docs-list
On Sun, Sep 24, 2017 at 08:10:35AM +0200, Julien Hardelin wrote:
> Hi all,
> 
> I cann't remember (nor find) where the .mo files for GEGL are.
> 
> Please, could you tell me the path to them.

Please explain:

1) are you really sure you search for .mo files instead of the .po files?
2) given that you really search for the .mo files for which platform 
   (Mac/Windows/Linux) are you searching these files?
3) why are you searching for the GEGL .mo files?

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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] moving notes.png?

2017-08-15 Thread Marco Ciampa via gimp-docs-list
On Wed, Jul 12, 2017 at 10:40:58AM +0200, Kolbjørn Stuestøl wrote:
> Den 12.07.2017 07:51, skreiv Julien Hardelin:
> >I better understand the problem (that does not exist in French).
> >
> >I think the only wise solution is to replace this icon  with a neutral
> >graphism, something like  the attached one (I am not an artist).
> Artist or not is a question of definition :-)
> I think you are right that this is the best solution.
> If peoples in this list agree, I'll replace the original with your
> suggestion.

+1 I like it very much!

-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Text on images

2017-05-16 Thread Marco Ciampa via gimp-docs-list
On Tue, May 16, 2017 at 04:40:16PM +0200, Kolbjørn Stuestøl wrote:
> I am translating the eminent help articles on color management. But some of
> the (example) images has English text over the image. (Example: 
> menus/image/color-management/enable-cm-gimp-built-in-perceptual-srgb-color-space-enabled-disabled.png).
> Is it possible to add all text as a caption beneath or above the image or
> save a .xcf copy somewhere with the text as a separate layer possible to
> edit?
> I know it is possible to translate the text on the images by manipulating
> them in GIMP, but this is time consuming.
> 

Agree!!!

-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Feedback on first pushed commits

2017-04-28 Thread Marco Ciampa via gimp-docs-list
On Fri, Apr 28, 2017 at 10:44:25AM -0400, Elle Stone wrote:
> On 04/28/2017 04:35 AM, Marco Ciampa via gimp-docs-list wrote:
> 
> >Is this right?
> >
> >src/menus/colors/desaturate/desaturate.xml:108(phrase)
> >
> >The shades of gray will be calculated as
> >  
> >
> >  
> >
> >  Lightness (HSL)) =   (max(R,G,B) + 
> > min(R,G,B))
> >
> >  
> >
> >  
> >
> >
> 
> If you mean the formula for Lightness, it's correct:
> 
> From 2.8 docs:
> Lightness
> 
> The graylevel will be calculated as
> Lightness = ½ × (max(R,G,B) + min(R,G,B))
> 
> From posted 2.9 docs:
> Lightness (HSL)
> 
> The shades of gray will be calculated as
> Lightness (HSL)) = ½ × (max(R,G,B) + min(R,G,B))
> 
> From Wikipedia (https://en.wikipedia.org):
> In the HSL "bi-hexcone" model, lightness is defined as the average of the
> largest and smallest color components (fig. 12c).
> 
> From GIMP code (app/operations/gimpoperationdesaturate.c):
> case GIMP_DESATURATE_LIGHTNESS:
>   /* This is the formula for Lightness in the HSL "bi-hexcone"
>* model: https://en.wikipedia.org/wiki/HSL_and_HSV
>*/
>   while (samples--)
> {
>   gfloat min, max, value;
> 
>   max = MAX (src[0], src[1]);
>   max = MAX (max, src[2]);
>   min = MIN (src[0], src[1]);
>   min = MIN (min, src[2]);
> 
>   value = (max + min) / 2;
> 
> Not to be confused with LAB/LCH Lightness, which is calculated from XYZ, not
> from RGB (http://brucelindbloom.com/index.html?Eqn_XYZ_to_Lab.html).

Many thanks Elle! Sorry for the noise!

Just a very minor typo: I think there is a spurious parenthesis after HSL
...

bye

--


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Feedback on first pushed commits

2017-04-28 Thread Marco Ciampa via gimp-docs-list
On Thu, Apr 06, 2017 at 02:22:06PM -0400, Elle Stone wrote:
> On 04/05/2017 08:54 AM, Elle Stone wrote:
> >
> >Actually I'd suggest holding off on translating any of the color
> >management menu pages as there are two more pages to write for the color
> >management menu. These pages all go together, so likely I'll make minor
> >changes to the "already done" pages while writing the "not yet done" pages.
> 
> I made some changes to the XML, and many thanks to Julien for the feedback -
> I think I have the indentation figured out now.
> 
> I simplified the Enable Color Management page and finished the last two
> items for the color management menu. So the Image/Color Management menu
> pages are ready for translating if anyone is so inclined.

Is this right?

src/menus/colors/desaturate/desaturate.xml:108(phrase)

The shades of gray will be calculated as
  

  

  Lightness (HSL)) =   (max(R,G,B) + min(R,G,B))
        
  

  


-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Preferences documentation

2017-04-04 Thread Marco Ciampa via gimp-docs-list
Hello Elle!

On Tue, Apr 04, 2017 at 10:57:21AM -0400, Elle Stone wrote:
> On 04/04/2017 10:38 AM, Elle Stone wrote:
> >Hi All,
> >
> >Most of the documentation devoted to "Enrich my GIMP" is actually
> >documentation for Preferences.
> >
> >The Preferences page is huge, too large for users to easily navigate.
> >
> >What do you all think about reorganizing as follows?
> >

IMHO...

> >* Make Preferences a stand-alone section with the base URL
> >https://docs.gimp.org/2.9/en/gimp-preferences. 
> >
> >Or probably better, put Preferences under the Edit menu, 
> >to correspond to where Preferences is located on the Menu bar.

like it

> >* Break the Preferences documentation into smaller chunks corresponding
> >to the Preferences subsections (System Resources, Color Management, etc).

like this too

> I forgot to say, I can make these changes if the consensus is that it's a
> good thing to do.

I think it is a good thing to do, thanks!

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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Colors/Desaturate/Desaturate documentation

2017-03-26 Thread Marco Ciampa via gimp-docs-list
On Sun, Mar 26, 2017 at 12:07:18PM -0400, Elle Stone wrote:
> On 03/26/2017 11:34 AM, Marco Ciampa via gimp-docs-list wrote:
> >>But the build ("make -j4 install") ends in an error message:
> >try without -j4:
> >
> >make html-en
> 
> That works - thanks! Where did this "html-en" option come from?

>From the autogen tool.

Try:

make validate-NN
make status-NN
make html-NN

where NN is the language code like en, it, de, etc.

Under linux install the bash-completion package and try typing:

make  

for possible completitions...

bye

-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Colors/Desaturate/Desaturate documentation

2017-03-26 Thread Marco Ciampa via gimp-docs-list
On Sun, Mar 26, 2017 at 11:17:23AM -0400, Elle Stone wrote:
> On 03/26/2017 10:58 AM, Elle Stone wrote:
> >
> >FWIW, I succeeded in compiling gimp-help with the modified desaturate
> >XML file. I'll send some questions in another email.
> 
> Regarding autogen.sh:
> 
> 1. This "autogen.sh" command succeeds in generating the requisite files
> for compiling:
> 
> ./autogen.sh --prefix=/home/elle/code/gimp-help/install/ --without-gimp
> 
> But the build ("make -j4 install") ends in an error message:

try without -j4:

make html-en

-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Colors/Desaturate/Desaturate documentation

2017-03-24 Thread Marco Ciampa via gimp-docs-list
On Fri, Mar 24, 2017 at 03:09:13AM +, Pat David wrote:
> Hi Elle!
> 
> I can't  answer the other questions, but 2.9 can be found here:
> 
> https://docs.gimp.org/2.9/en/
> 
> pat
> 

Thank you Pat!

A suggestion: why not a link on the main site?

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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] can someone clarify me this?

2017-03-22 Thread Marco Ciampa via gimp-docs-list
On Wed, Mar 22, 2017 at 08:43:17PM +0100, Julien Hardelin wrote:
> Hi Marco,
> 
> I return to my first idea: the image window can be bigger than the image and
> we have "Fit image to window".
> 
> The name "Zoom to selection" is rather weird. It should be "Fit selection to
> image".
> 
> Unless there is sometthing I have not understood.

You probably missed that the original message is this:

> #: src/menus/view/zoom.xml:161(para)
> msgid ""
> "This command zooms the image so that the selection fills the smallest "
> "dimension of the image."

"smallest"?

Anyway IMHO this is wrong.

--


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] can someone clarify me this?

2017-03-22 Thread Marco Ciampa via gimp-docs-list
On Wed, Mar 22, 2017 at 07:57:57AM +0100, Julien Hardelin wrote:
> Hello,
> 
> What do you mean by "screen" ?
> 
> How do you describe the results in the attached file?
> 
> Julien
> 

Hi Julien!
I see your point... lets say "image window" 

"This command zooms the image so that the selection fills the image window."

> 
> 
> >
> >#: src/menus/view/zoom.xml:161(para)
> >msgid ""
> >"This command zooms the image so that the selection fills the smallest"
> >"dimension of the image."
> >
> >in
> >
> >menus/view.po
> >
> >I would have written:
> >
> >"This command zooms the image such as all the selection is visible."
> >
> >or
> >
> >"This command zooms the image such as all the selection is visible"
> >"occupying the most part of the screen."
> >
> >or
> >
> >"This command zooms the image such as all the selection is visible"
> >"fitting all the screen."
> >
> >but my English is not so good so I could be wrong of course.
> >
> >Regards,
> >
> 


> ___
> gimp-docs-list mailing list
> gimp-docs-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/gimp-docs-list


-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] can someone clarify me this?

2017-03-21 Thread Marco Ciampa via gimp-docs-list
On Tue, Mar 21, 2017 at 04:13:21PM +, Pat David wrote:
> Just guessing, but perhaps
> 
> "This command zooms the image so that the selection fills the screen."
> 
> ?

Yes, even better and simpler. Thanks.

Can we use this instead of:

#: src/menus/view/zoom.xml:161(para)
msgid ""
"This command zooms the image so that the selection fills the smallest "
"dimension of the image."

?


-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


[Gimp-docs] can someone clarify me this?

2017-03-21 Thread Marco Ciampa via gimp-docs-list


#: src/menus/view/zoom.xml:161(para)
msgid ""
"This command zooms the image so that the selection fills the smallest "
"dimension of the image."

in

menus/view.po

I would have written:

"This command zooms the image such as all the selection is visible."

or

"This command zooms the image such as all the selection is visible"
"occupying the most part of the screen."

or

"This command zooms the image such as all the selection is visible"
"fitting all the screen."

but my English is not so good so I could be wrong of course.

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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Gimp-2.9.5 - Select border

2017-03-19 Thread Marco Ciampa via gimp-docs-list
On Sat, Mar 18, 2017 at 12:34:37PM -0400, Ell via gimp-docs-list wrote:
> 
> 
> On 03/18/2017 12:20 PM, Ell wrote:
> >...  while "smooth" grows the original selection by half
> >the radius, shrinks the original selection by half the radius, and
> >subtracts the shrunk selection from the expanded one.
> 
> Oops, should just be "radius", not "half the radius".
> 
> --
> Ell

Anyway, very well written, Ell!

-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Gimp-2.9.5 - Select border

2017-03-19 Thread Marco Ciampa via gimp-docs-list
On Sun, Mar 19, 2017 at 08:34:41AM +0100, Julien Hardelin wrote:
> Hi Marco,
> 
> >On Sat, Mar 11, 2017 at 06:37:14PM +0100, Julien Hardelin wrote:
> >>Hello all,
> >>
> >>Please, what do you get when using select/border? I cann't see any
> >>difference between the three options of "Border Style': Hard, Smooth and
> >>Feather.
> >For the feather style, you do have an alpha layer when you make the
> >selection, don't you?
> 
> Yes I have.
> >
> >For the smooth style, use high values with a rectangular selection to see
> >the smooth (round) effect ...
> >
> >...and re-select the selection to make any change in settings effective.
> What do you mean by "re-select the selection"?

I mean that if you change style after given the effect you see no changes.
You have to re-select the selection with the desired selection/border style and 
then
you can see any difference, but perhaps I am to prosaic in saying this ... 
sorry 

>  In this example :
>   https://mon-partage.fr/f/RgBYJtjb/
> I understand what happens : the border command wih feathered option feathers
> both borders of the border selection , but this is not visible in the left
> image of course. This becomes visible if  I Edit/Clear the selection (on the
> right).

Right!

I won't produce any example since the Ell explanation and example is hard
to beat! :-)

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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Gimp-2.9.5 - Select border

2017-03-17 Thread Marco Ciampa via gimp-docs-list
On Sat, Mar 11, 2017 at 06:37:14PM +0100, Julien Hardelin wrote:
> Hello all,
> 
> Please, what do you get when using select/border? I cann't see any
> difference between the three options of "Border Style': Hard, Smooth and
> Feather.

For the feather style, you do have an alpha layer when you make the
selection, don't you?

For the smooth style, use high values with a rectangular selection to see
the smooth (round) effect ...

...and re-select the selection to make any change in settings effective.

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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] GIMP_HELP_2_8_2 is ambiguous

2017-02-17 Thread Marco Ciampa via gimp-docs-list
On Fri, Feb 17, 2017 at 11:03:46PM +0100, Michael Schumacher wrote:
> 
> 
> On 02/17/2017 04:54 PM, Kolbjørn Stuestøl wrote:
> 
> > "remote: error: refname 'GIMP_HELP_2_8_2' is ambiguous"
> > 
> > A minute later the three files showed up in
> > https://git.gnome.org/browse/gimp-help-2/log/. All seems OK.
> > 
> > As it does not seem to be a serious error, I am just curious why this
> > occurs. Perhaps it can be fixed in some way?
> 
> There's both a tag and a branch called GIMP_HELP_2_8_2, see
> https://git.gnome.org/browse/gimp-help-2/refs/
> 
> The tag has been made on that same branch, so I'm reluctant to try to
> fix this.

How about deleting the tag? What was useful for anyway?

-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


[Gimp-docs] validate error on reference xml english version

2017-02-14 Thread Marco Ciampa via gimp-docs-list
If I do a:

$ make xml-en

I got this:

Copying images (en) ... 1703
Cleaning up 'en' xml files ...
marco@lap3-ciampix:~/git/gnome/gimp-help-2$ make validate-en
-:1235: element sect1: validity error : Element sect1 content does not
follow the DTD, expecting (sect1info? , (title , subtitle? ,
titleabbrev?) , (toc | lot | index | glossary | bibliography)* ,
(((calloutlist | glosslist | itemizedlist | orderedlist | segmentedlist |
simplelist | variablelist | caution | important | note | tip | warning |
literallayout | programlisting | programlistingco | screen | screenco |
screenshot | synopsis | cmdsynopsis | funcsynopsis | classsynopsis |
fieldsynopsis | constructorsynopsis | destructorsynopsis | methodsynopsis
| formalpara | para | simpara | address | blockquote | graphic |
graphicco | mediaobject | mediaobjectco | informalequation |
informalexample | informalfigure | informaltable | equation | example |
figure | table | msgset | procedure | sidebar | qandaset | task | anchor
| bridgehead | remark | highlights | abstract | authorblurb | epigraph |
indexterm | beginpage)+ , (refentry* | sect2* | simplesect*)) | refentry+
| sect2+ | simplesect+) , (toc | lot | index | glossary |
bibliography)*), got (title para variablelist variablelist variablelist
variablelist variablelist variablelist variablelist variablelist
varlistentry )

^
(You will find log and xml files in log/.)

--


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] missing image

2017-02-12 Thread Marco Ciampa via gimp-docs-list
On Wed, Feb 01, 2017 at 12:01:18PM +0100, Marco Ciampa via gimp-docs-list wrote:
> I do not know how much is it old this message but...
> doing the classic
> 
> ./autogen
> make
> make validate
> 
> cicle I stumbled in this message:
> 
> Warning: image file 'images/menus/windows/dockable-dialogs.png' not found.
> 
> and in /src doing a
> 
> grep -ri "dockable-dialogs.png" *
> 
> I get this:
> 
> menus/windows-show-docks.xml: fileref="images/menus/windows/dockable-dialogs.png"
> 
> ...
> 
> searching the web for old copies (yes I know that you can get the same using 
> git...)
> I get this image:
> 
> ftp://213.85.246.177/pub/FreeBSD/ports/russian/gimp-help/work/gimp-help-2/html/ru/images/menus/windows/dockable-dialogs.png
> 
> why is missing?
> 
> Was it important?
> 
> Do we have to restore it?
> 
> TIA
> 

The missing image link is always there...

$ make status-it
[POT] pot/preface.pot
[POT] pot/glossary.pot
[POT] pot/menus.pot
Warning: image file 'images/menus/windows/dockable-dialogs.png' not found.
[PO]  po/it/menus.po
97 messaggi tradotti.
[POT] pot/menus/layer.pot
[POT] pot/menus/colors.pot
[POT] pot/menus/colors/auto.pot
[...]

-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Automatic builds now serve online help for GIMP 2.8.x and GIMP 2.9.x

2017-02-08 Thread Marco Ciampa via gimp-docs-list
On Wed, Feb 08, 2017 at 11:17:15PM +0100, Michael Schumacher wrote:
> 
> Hi,
> 
> the automatic builds for the gimp-help-2 branches are now serving the
> online help for GIMP 2.8.x and GIMP 2.9.x, respectively:
> 
>   gimp-help-2-8
>   https://docs.gimp.org/2.8/
> 
>   (https://docs.gimp.org/ are file-system links into there)
> 
> and
> 
>   master
>   https://docs.gimp.org/2.9/
> 
> This means that from now on, anyone using the online help in GIMP 2.8.x
> and GIMP 2.9.x will receive up-to-date help that has been built from the
> corresponding branches, according to the following schedule:
> 
> - gimp-help-2-8 is set up to build daily at 03:00
> - master is set up to rebuild hourly at minute 23
> 

Very, very good indeed!

Thanks! Great job!

-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Automatic builds for gimp-help-2-8 branch and master branch

2017-02-07 Thread Marco Ciampa via gimp-docs-list
On Tue, Feb 07, 2017 at 02:25:53AM +0100, Michael Schumacher wrote:
> Hi all,
> 
> we have finally managed to set up automatic builds for the gimp-help-2-8
> and master branches of gimp-help-2.

Congrats, it was about time!
A very useful move, many thanks!

-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


[Gimp-docs] missing image

2017-02-01 Thread Marco Ciampa via gimp-docs-list
I do not know how much is it old this message but...
doing the classic

./autogen
make
make validate

cicle I stumbled in this message:

Warning: image file 'images/menus/windows/dockable-dialogs.png' not found.

and in /src doing a

grep -ri "dockable-dialogs.png" *

I get this:

menus/windows-show-docks.xml:ftp://213.85.246.177/pub/FreeBSD/ports/russian/gimp-help/work/gimp-help-2/html/ru/images/menus/windows/dockable-dialogs.png

why is missing?

Was it important?

Do we have to restore it?

TIA

-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] I would like to update doc page

2016-10-08 Thread Marco Ciampa
On Sat, Oct 08, 2016 at 09:19:37AM -0400, Roger Goodman wrote:
> All,
> While looking at the documentation, I found a page that I would like to
> try to improve the translation on:
> 
> http://docs.gimp.org/2.8/en/gimp-introduction-whats-new.html
> 
> I am looking to improve the wording/grammer, to make it more understandable
> in US english.  Who do I contact?  Where to send changes?
> Thanks,
> Roger
> (I am in digest mode, so it may take some time before I see the reply, but
> thank you for your replies)

Write here your corrections and I will apply those corrections to the manual.
In this way if someone wants to comment your corrections, he/she is welcome.

Sorry for my bad English...

--


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] bugzilla project updated

2016-06-13 Thread Marco Ciampa
On Mon, Jun 13, 2016 at 04:23:08PM +0300, Alexandre Prokoudine wrote:
> Hi,
> 
> 'GIMP-manual' product on bugzilla now has v2.10 version that bug
> reports can be filed against.
> 
> At this point I need your input. Since the work on updating the user
> manual should start about now, which of the options below would you
> prefer?
> 
> 1. Use http://wiki.gimp.org/wiki/Release:2.10_changelog to create bug
> reports on every missing feature or update, then 'take' a bug (needs
> developer status on bugzilla for the product), and close it as
> RESOLVED FIXED once it's done.
> 
> 2. Create a new wiki page similar to
> http://wiki.gimp.org/wiki/Hacking:Porting_file_plugins_to_GEGL and
> track the progress there (needs a wiki account).
> 
> Maybe there's an even better option? Please let me know.
> 
> Alex

I prefer the 2nd option and the 1st for real "bug"s (defects on the
manual) but IMHO it is not much fundamental ...

-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] gimp-help-2-8 branch created

2016-06-05 Thread Marco Ciampa
On Sat, Jun 04, 2016 at 09:23:53PM -0300, Joao S. O. Bueno wrote:
> Ok.
> 
> Any more talks on moving on with the transition from docbook to some
> other markup?

I will create a test/example for asciidoc but maybe it is wise to not for this
upcoming version?

-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Translation of gegl

2016-04-29 Thread Marco Ciampa
On Wed, Dec 16, 2015 at 08:26:47AM +0200, ΔΗΜΗΤΡΗΣ Σ wrote:
> Hi,
> 1) Could somebody verify or write in english the following abbreviations in
> full form:
> bufsize = ? buffersize, keyint-min = ? keyinternal-min, q(min, max,
> compress, blur) = ? quantum (min, max, compress, blur), gop = Graphics
> Output Protocol or Group of pictures or ?, me_range = , me_subpel_quality =
> , subpel =, max-qdiff = , i-quant-factor = , i-quant-offset = , max - b -
> frames =
> 2) Could it be possible a notice to be added with the full form of these
> abbreviations in the appropiate .po file?
> Thanks

2) I totally agree!


--


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] git commit problems

2016-01-13 Thread Marco Ciampa
On Wed, Jan 13, 2016 at 09:48:26PM +0100, Kolbjørn Stuestøl wrote:
> As this question is related to the GIMP UI I posted this in
> developers forum (gimp-developer-l...@gnome.org) a couple of days
> ago but get no answers. Hoping someone in this list are able to
> answer me. I guess it has something with "git config" to do.
> 
> When committing my translation all looks well on my local copy. But
> my translations do not shows up in the
> https://git.gnome.org/browse/gimp/ site. Where is my translations
> gone?
> 
> I downloaded my copies using "git clone  username]@git.gnome.org/git/gimp>".
> Updated and translated some po files and then:
> 
>$ git commit -m "Updated Norwegian (nn) translations"
>[master 7b2f8a5] Updated Norwegian (nn) translations
>  5 files changed, 13801 insertions(+), 9813 deletions(-)
>  mode change 100644 => 100755 po-plug-ins/nn.po
>  mode change 100644 => 100755 po-python/nn.po
> 
> My local git log shows:
> 
>$ git log
>commit 7b2f8a5cff63bdea6db76b642445cfb8a11d1b0b
>Author: kolbjoern <kolbjo...@git.gnome.org>
>Date:   Mon Jan 11 21:19:53 2016 +0100
> 
> Updated Norwegian (nn) translations
> 
>commit 97ea600623b780fc9dba4abbaa45db44e626a10e
>Author: Michael Natterer <mi...@gimp.org>
>Date:   Mon Jan 11 20:35:32 2016 +0100
> 
> app: s/Default/Color/ in the testing icon theme Makefile rules
>…
> 
> My commit must obviously go somewhere but I have no idea where.
> How to get it to upload (git push) to the correct gimp repository?
> 
> Last time I uploaded my files (2016.01.07) I got the error message
> "remote: error: refname 'GIMP_HELP_2_8_2' is ambiguous" (but the
> "git push" succeeded) and I was told to run "git config --global
> push.default matching" and/or
> "git config --global push.default simple". I did this in that order.
> No error messages.

Strange because:

1) looking on the commit 97ea600623b780fc9dba4abbaa45db44e626a10e you are
   currently on master

2) if you do a log and you see your changes you made that seems to me
   that you did not push that commit at all. You probably are in a 
   detached HEAD state.

Trivial and primitive way to exit this situation.

1) save your translated files somewhere out of git repo

2) reset --hard your git to commit 97ea600623b780fc9dba4abbaa45db44e626a10e

3) git pull

4) replace files with your saved copies

5) commit & push

bye

-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] git commit problems

2016-01-13 Thread Marco Ciampa
On Wed, Jan 13, 2016 at 09:48:26PM +0100, Kolbjørn Stuestøl wrote:
> As this question is related to the GIMP UI I posted this in
> developers forum (gimp-developer-l...@gnome.org) a couple of days
> ago but get no answers. Hoping someone in this list are able to
> answer me. I guess it has something with "git config" to do.

Sorry Kolbjørn for the late answer...

> When committing my translation all looks well on my local copy. But
> my translations do not shows up in the
> https://git.gnome.org/browse/gimp/ site. 

wrong repo... it is gimp-help-2 ...

> Where is my translations gone?

here?

https://git.gnome.org/browse/gimp-help-2/log/

I hope this helps...

--


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] git commit problems

2016-01-13 Thread Marco Ciampa
On Wed, Jan 13, 2016 at 10:41:30PM +0100, Marco Ciampa wrote:
> On Wed, Jan 13, 2016 at 09:48:26PM +0100, Kolbjørn Stuestøl wrote:
> > As this question is related to the GIMP UI I posted this in
> > developers forum (gimp-developer-l...@gnome.org) a couple of days
> > ago but get no answers. Hoping someone in this list are able to
> > answer me. I guess it has something with "git config" to do.
> 
> Sorry Kolbjørn for the late answer...

[...]

Super sorry, I was totally wrong ... just a moment, let me see...

-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


[Gimp-docs] RFC: unclear paragraph

2015-12-28 Thread Marco Ciampa
This:

src/toolbox/text.xml:326


  [...]
  We will 
  limit description to commands that has not been transferred.


I think it should means something like (forgive my bad English):

"We will describe the limits of the commands that has not been transferred."

or something similar...

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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] gimphelp-id

2015-12-13 Thread Marco Ciampa
On Fri, Dec 11, 2015 at 09:21:25PM +0100, Julien Hardelin wrote:
> Sorry, this will be corrected in my next commit.
> 
> Julien
> 
> Le 11/12/2015 16:43, RyoTa SimaMoto a écrit :
> >Hi,
> >
> >I noticed the recent commit that removes id="gimp-layer-text-along-path".
> >Please do not remove entirely such XML attribute.  These kind of tag is
> >defined on the source code file app/widgets/gimphelp-ids.h so that user
> >can get a proper page of GIMP's F1-key help system.  It is necessary that
> >this tag exists at least once in the help document source tree, otherwise
> >user would see the "Eeek! There is Missing Help" page instead of the
> >"The Text Commands" section of gimp-layer-text-commands.html. :(
> >
> >SimaMoto,RyōTa <liangtai@gmail.com>

To RyōTa, Stuest, Julien.

That id was duplicated and it blocked the pdf compilation.

I updated the Italian translation, deleted one of the two ids, deleted
some other dirty things, here and there.

Now it should compile for every language.

In the next days I will replace the "..." three point char that was added
in the reference sources, I do not know why, with the real three single
char dots.

If there is a reason for keeping that strange not ascii code char in the
sources, please explain (Julien?).

BTW it seems that was a Julien to blame for such errors on reference
sources.

PLEASE: before committing changes on reference sources _BE SURE_ that
least it compiles (i.e. validate it!)

bye

-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Validation error

2015-09-16 Thread Marco Ciampa
On Mon, Sep 14, 2015 at 11:15:30PM +0200, Kolbjørn Stuestøl wrote:
> I tryed to update Julien's latest (and as usual excellent) enhances,
> but when validating my translation I got this error messages:
> 
> Command: make validate-nn
> From log file:
> 
>-:41998: namespace error : Namespace prefix xi on include is not defined
>   
> ^
>-:41998: element xi:include: validity error : No declaration for
>attribute href of element xi:include
>   
> ^
>-:41998: element xi:include: validity error : No declaration for
>element xi:include
>   
>   ^
>-:42077: element sect1: validity error : Element sect1 content does
>not follow the DTD, expecting (sect1info? , […] )
>
> ^
> 
> I think I once fixed such messages myself, but alas it is a long
> time and a few computers ago and I have forgotten how I did it. No
> logs either.
> Someone remember?
> There are two main errors:
> 1. line 41998: namespace error etc.
> 2. line 43077: sect1 validity error
> 
> I run make xml-en and then make validate-en.
> No errors.
> 
> Kolbjørn

Hi Kolbjørn, sorry for being late!
Have you tried to "make clean" or "make distclean" it first?

--


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Error git push

2015-08-03 Thread Marco Ciampa
On Mon, Aug 03, 2015 at 11:13:26PM +0200, Kolbjørn Stuestøl wrote:
 Strange?
 https://git.gnome.org/browse/gimp-help-2 shows that GIMP_HELP_2_8_2
 master has accepted my updating 24 hours ago.  So the address is not
 *that* ambiguous :-).
 Looks like there is no need to change anything in my settings for git.
 Kolbjørn

Yes strange.

Apparently GIMP_HELP_2_8_2 is a tag that is actually also master. If you
are set onto that tag it should prompt the infamous message of detached
HEAD like this:



git checkout GIMP_HELP_2_8_2 
Note: checking out 'GIMP_HELP_2_8_2'.

You are in 'detached HEAD' state.You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

HEAD is now at 8529155... Added link to 2.8.2 release



redoing git checkout master fix it:



git checkout master
Previous HEAD position was 8529155... Added link to 2.8.2 release
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.



So I cannot explain that previous error message.
Anyway it is all ok so... no problem! :-)

PS: I'll stay off-line for a week or so for holydays in London...

--


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Error git push

2015-08-03 Thread Marco Ciampa
On Sun, Aug 02, 2015 at 11:15:21PM +0200, Kolbjørn Stuestøl wrote:
 I was trying to update my translation this night using git push, but
 get the error message
 remote: error: refname 'GIMP_HELP_2_8_2' is ambiguous.
 To ssh://[my_username]/git/gimp-help-2
 
 It's a long time since I pushed something to the translation, so
 perhaps I have forgotten something.
 How and where do I set the correct refname?

Why are you not working on master? Is there a reason?
Save your work somewhere on your disk or git stash it away then try:

git checkout master
git pull

--


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Accessibility documentation request

2015-06-23 Thread Marco Ciampa
On Tue, Jun 02, 2015 at 07:12:38PM +, Sarah Hunter wrote:
 This email is to request appropriate accessibility documentation for
 purchases from your company.
[...]

1) this is _not_ a company, GIMP is not on sale, so this email is 
   misplaced at least.

2) we already answered to this email on another mailing list of the same
   project, please do not continue to ask the same questions over and over.

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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] cannot search GNU Image Manipulation Program: User Manual on mac? help please!

2015-04-11 Thread Marco Ciampa
On Sat, Apr 11, 2015 at 12:53:12PM +0200, Marco Ciampa wrote:
 On Thu, Apr 09, 2015 at 12:56:39AM -1000, Zariah Art wrote:
  So please,
  
  does anyone have any ideas?
  
  What have i not tried? …or what am i not understanding?…
  
  Thanks so much,
  Coatli
 
 Where did you get the manual? How many pages?

Have you tried this:

http://gimp.linux.it/www/meta/gimp-en.pdf

??

--


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Broken Links on the pt_BR version of the manual

2015-02-16 Thread Marco Ciampa
On Sat, Feb 14, 2015 at 09:25:11AM -0200, Joao S. O. Bueno wrote:
 Hi -
 
 there are some broken links on the online version of the manual.
 
 I just noticed that http://docs.gimp.org/pt_BR/gimp-tool-clone.html -
 for example,
 yields a 404 error.
 
 I double-checked, and the page is generated, with a correct content,
 in the local copy.
 
 Could someone check what is going on? Maybe it i justa matter of
 regenerating the online copy.
 
 regards,

Simply you are missing that now, correctly, the GIMP Manual is versioned.
So what you probably wanted to see is this:

http://docs.gimp.org/2.8/pt_BR/gimp-tool-clone.html

Right?

-- 


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@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Documentation for who work with Gimp

2015-01-08 Thread Marco Ciampa
On Wed, Jan 07, 2015 at 08:29:26PM -0200, Filipi Maciel wrote:
 Hello everyone,
 
 I started to work as a Android Developer and i would like to use Gimp for
 my apps, games, and other things. Gimp is a freely software, but i imagine
 it is necessary some documents for can i sell my apps, arts, games, that
 were made using Gimp.

Would you have needed any documents if you had chosen for example
Photoshop instead of GIMP?

 Documents to explain for a firm like Steam about how
 i make my game and that allows me to sell on Steam firm.

You are free to sell or to do what you want with the output of GIMP.
The licence of GIMP is just about GIMP in itself.

See the licence of GIMP if there is any reference to the documents produced.

BTW this question is really apt for inserting in the GIMP FAQ:
http://www.gimp.org/docs/userfaq.html


-- 


Marco Ciampa

I know a joke about UDP, but you might not get it.

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++

___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Downloading the user manual

2015-01-03 Thread Marco Ciampa
On Sat, Jan 03, 2015 at 04:25:40PM +1000, Roman Joost wrote:
 Dear Eric,
 
 tl;dr: we're not providing PDFs for download.
 
 On Fri, Jan 02, 2015 at 08:28:05PM -0600, Eric Westfall wrote:
  I can't seem to find a way to download the user's manual, as with most
  manuals (in PDF), as opposed to having to use it manually online.
  
  Am I missing something, or is that just a Gimp fact of life?
 We provided PDF versions of the manual for a while. The process involved
 never became stable and made it out of the work-in-progress state. That
 is, we can create PDFs for most latin languages, but there is no
 automated process available to provide them on our homepage for
 download. The PDFs are somewhat usable (readable, printable), but far
 from perfect.
 
 Therefore you see only HTML versions of the manual.
 
 If you can spare some free time I encourage you to have a look at our
 project with a git clone. If all dependencies are installed, a simple:
 
 ./autogen.sh
 make pdf
 
 will start creating PDFs. Keep in mind that this is for user manual
 developers only and not supposed to be run by an end-user (-reader).
 
 Kind Regards,

Some (english and italian) already made pdf versions of the manual you
can download from here:

http://gimp.linux.it/www/meta/gimp-it.pdf
http://gimp.linux.it/www/meta/gimp-en.pdf

bye

-- 


Marco Ciampa

I know a joke about UDP, but you might not get it.

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++

___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] OT: experimenting with docbook-xml

2014-09-22 Thread Marco Ciampa
On Mon, Sep 22, 2014 at 12:20:23PM +1000, Roman Joost wrote:
 Dear Marco,
 
 On Sun, Sep 21, 2014 at 03:18:14AM +0200, Marco Ciampa wrote:
  Since I want to understand a bit more about the gimp build sistem
  I am trying to do the things by hand.
  
  I do not know automake/autotool so I do not really know how html, for
  instance, files are created.
  
  I copied all xml dir outside gimp tree dir and tried to build html by
  hand and failed miserably.
  
  I do not know docbook-xml either and I now know I was a bit naive
  thinking that a mere
  
   docbook2html it/gimp.xml
  
  will suffice.
  
  Can anyone help me understand? What I am missing?
 It's just a matter of tooling. I'm not sure what the outcome of your
 docbook2html attempt was, but I assume it was negative.

yes because it does not include anything

 We chose to split up our manual into separate files according to the
 help ID GIMP uses. Each file is tied into the manual with include
 statements (xi:includes) to make up the book.

yes I knew this, the question is: why the command do not recognize the
include command?

 Furthermore, translations are separated into separate files. You'll need
 to basically compile a translated version of the manual in order to
 generate a translated HTML version out of it.

yes, this too, but I want to make a step at a time... and recreate a GIMP
build script from scratch just to understand better how the things works,
without all that automake/autoconf confusing (for me) matter...

 Potentially your tool will work. Look for --xinclude parameters in order
 to build the manual. You'll have to find a way though, to create new
 *translated* docbook files if you want anything else than English.

there are no --xinclude parameters in docbook2html command. I am not even
sure if it is really this the command that gimp makefiles trigger. 

Sorry I am not able to read make/automake scripts and this is my first
problem...

 Feel free to ask more questions if you want.

I do not want to boring you with trivial questions but I do not know whom
to ask about ...

Many thanks.

-- 


Marco Ciampa

I know a joke about UDP, but you might not get it.

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++

___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] OT: experimenting with docbook-xml

2014-09-22 Thread Marco Ciampa
On Mon, Sep 22, 2014 at 07:58:18PM +0200, Ulf-D. Ehlert wrote:
 On Sun, Sep 21, 2014 at 03:18:14AM +0200, Marco Ciampa wrote:
  Since I want to understand a bit more about the gimp build sistem
  I am trying to do the things by hand.
  
  I do not know automake/autotool so I do not really know how html, for
  instance, files are created.
  
  I copied all xml dir outside gimp tree dir and tried to build html by
  hand and failed miserably.
  
  I do not know docbook-xml either and I now know I was a bit naive
  thinking that a mere
  
   docbook2html it/gimp.xml
  
  will suffice.
  
  Can anyone help me understand? What I am missing?
 
 A simple way to see what's happening is
 
 make --dry-run what_ever | less

Many thanks! Without your hint I would never thought that --dry-run could
printout the commands (a quick look at the manual page confirmed it but
--- who read the manuals anyway? ;-)

 So in the gimp-help directory try e.g.
 
 make --dry-run html-en | less
 
 to see how the English html manual is built, while   
 
 make --dry-run html-it | less
 
 will show you how to build a translated manual.

Done, very instructive!

 You will see that the main tool is xsltproc; I don't know
 docbook2html and can't tell you if (and how) it can be used to
 create html. 

xsltproc will suffice, thanks...

...

a quick look at che stylesheets included ... what a nightmare!


 ___
 gimp-docs-list mailing list
 gimp-docs-list@gnome.org
 https://mail.gnome.org/mailman/listinfo/gimp-docs-list


-- 


Marco Ciampa

I know a joke about UDP, but you might not get it.

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++

___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


[Gimp-docs] OT: experimenting with docbook-xml

2014-09-20 Thread Marco Ciampa
Since I want to understand a bit more about the gimp build sistem
I am trying to do the things by hand.

I do not know automake/autotool so I do not really know how html, for
instance, files are created.

I copied all xml dir outside gimp tree dir and tried to build html by
hand and failed miserably.

I do not know docbook-xml either and I now know I was a bit naive
thinking that a mere

 docbook2html it/gimp.xml

will suffice.

Can anyone help me understand? What I am missing?

Thanks!

-- 


Marco Ciampa

I know a joke about UDP, but you might not get it.

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++

___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


[Gimp-docs] update of translation tools - for Roman Joost

2014-09-09 Thread Marco Ciampa
Hi Roman, I am afraid of being a bit off topic (see below).
I am wondering about this:

http://wiki.gimp.org/wiki/Documentation:Main
https://bugzilla.gnome.org/show_bug.cgi?id=723512

Why are you choosing this tool (publican)?
Have you considered po4a[1] eventually with the aid of sisu[2]

[1]
http://po4a.alioth.debian.org/

[2]
http://www.jus.uio.no/sisu/sisu_markup/
http://en.wikipedia.org/wiki/SiSU
http://www.sisudoc.org/

I am considering these tools for another project (KiCad) but I think that
GIMP too could gain from these, as you pointed out, only I want to
discuss pros and cons with someone more skilled than me. :-)

Maybe we can catch two birds with one stone analizing these two tools for
the two projects that IMHO have similar goals.

What do you think?

-- 


Marco Ciampa

I know a joke about UDP, but you might not get it.

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++

___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Gimp 2.8 Help has been downloaded installed but Gimp cannnot find it

2014-07-24 Thread Marco Ciampa
On Thu, Jul 24, 2014 at 11:05:55AM +0100, Richard Prangnell wrote:
 Platform: PC
 OS: Windows 7 Ultimate 64 bit
 
 I have downloaded the Help for Gimp 2.8 (en-GB) and it installed itself to:
 c:\program files\GIMP 2\Share\gimp\2.0\help\en_GB, which I presume is
 correct?
 However, Gimp keeps telling me that help is not installed on this
 computer.
 I have tried copying the Help structure to higher level folders without
 success, even to the corresponding location below c:\program files (x86)\...
 
 So if anyone knows what is happening here, I'd be grateful for the
 work-around.
 
 Thank you!

The only question I have (I do not have Windows 7) is: are you sure of
the GIMP installation directory? In Windows XP it works well.

Eventually try changing in the preferences the language and set
it not automatic but english british...

Report if it worked...

-- 


Marco Ciampa

L'utopia sta all'orizzonte. Mi avvicino  di due passi, lei si allontana
di due  passi. Faccio dieci  passi e  l'orizzonte si allontana  di dieci
passi.  Per quanto cammini, non la raggiungerò  mai. A cosa serve
l'utopia? A questo: serve a camminare.  Eduardo Galeano

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++

___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Gimp 2.8 Help has been downloaded installed but Gimp cannnot find it

2014-07-24 Thread Marco Ciampa
On Thu, Jul 24, 2014 at 11:35:09AM -0400, Vitaly Lomov wrote:
 Try renaming en_GB to en in your help install folder. That worked for me.

nice to know a workaround...

 I have win7 64bit in en_CA locale. I couldn't get Gimp to recognize en_GB
 folder. I changed system locale to UK, default location to UK, language to
 English(United Kingdom) but still no luck. 

Ok I do not think you had to do it anyway...

 When Gimp starts for me, it's
 automatically set to system language for UI settings, 

Yes but if I do: 

Edit-Preferences-Interface-Language-

I see: English[en_GB]

bye

-- 


Marco Ciampa

L'utopia sta all'orizzonte. Mi avvicino  di due passi, lei si allontana
di due  passi. Faccio dieci  passi e  l'orizzonte si allontana  di dieci
passi.  Per quanto cammini, non la raggiungerò  mai. A cosa serve
l'utopia? A questo: serve a camminare.  Eduardo Galeano

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++

___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] [Gimp-developer] Gimp Manual Roadmap proposal

2014-02-08 Thread Marco Ciampa
On Fri, Feb 07, 2014 at 11:07:25AM -0200, Joao S. O. Bueno wrote:
 Hi Roman -
 when you talk about a 3.0 manual version in 3.0 - I am with the
 impression that the purposed changes would take place before GIMP 3.0
 itself (as the next version shall be 2.10)
 
 So - it looks like the purposed version numbering would dissociate the
 manual version from GIMP's version - is that so?  I think that might
 be confusing - although on a second thought it could be
 a manageable confusion, if it is clearly specified, inv arious places, that,
 for example, gimp-help-2 3.0 refers to gimp-2.10 .
 
 (As for the idea of going github I am of the same opinion as Jehan.
 We could put a mirror (fork in github parlor) there - but the
 authoritative repository
 should, by the reasons listed and maybe some more,
 be kept in the gnome infrastructure).

I too agree. IMHO gimp-help should follow the gimp versioning convention
for avoid confusion, i.e. the new gimp-help-2 should be gimp-2.10.

-- 


Marco Ciampa

L'utopia sta all'orizzonte. Mi avvicino  di due passi, lei si allontana
di due  passi. Faccio dieci  passi e  l'orizzonte si allontana  di dieci
passi.  Per quanto cammini, non la raggiungerò  mai. A cosa serve
l'utopia? A questo: serve a camminare.  Eduardo Galeano

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++

___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Would like to work on the color management documentation

2014-01-27 Thread Marco Ciampa
On Mon, Jan 27, 2014 at 11:02:39AM -0500, Elle Stone wrote:
 On 01/27/2014 10:11 AM, Andrew Douglas Pitonyak wrote:
 
 I expect that learning to use git and how to build is more of an
 obstacle than learning enough about docbook since the framework is
 already in place. It is a bit more difficult if you add or modify a
 figure, but, if all you do is add / change text, you will probably find
 it straight forward.
 
 Andrew, thanks! for words of encouragement.
 
 Somewhere a document says that the Gimp XML lines should be no more
 than 87(?) characters long. The README says Use any editor you
 want, but you should handle it well. Please keep in mind, that the
 tab width in XML Mode should be 2 spaces.
 
 So any recommendations on an xml editor? Preferably one that can be
 set to automatically use the right line length and tab width? And
 preferably can validate?
 
 From my personal point of view, eclipse (too big), vim (never
 learned), and jedit (I don't like java-based programs) are not
 options. 

I use Emacs...


-- 


Marco Ciampa

L'utopia sta all'orizzonte. Mi avvicino  di due passi, lei si allontana
di due  passi. Faccio dieci  passi e  l'orizzonte si allontana  di dieci
passi.  Per quanto cammini, non la raggiungerò  mai. A cosa serve
l'utopia? A questo: serve a camminare.  Eduardo Galeano

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++

___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] [Gimp-developer] ANNOUNCE: GIMP User Manual 2.8.1 released

2013-11-29 Thread Marco Ciampa
On Fri, Nov 29, 2013 at 03:45:21PM +1000, Róman Joost wrote:
 Hi,
 
 A new version of the user manual for GIMP 2.8 has been released!

Well done!

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


[Gimp-docs] this sentence did not look right... so I patched it with a hack...

2013-11-22 Thread Marco Ciampa
In help-missing.xml:

para
Found a emphasis role=boldcontent error/emphasis or just
something which doesn't look right?
!-- This link is also used to render a small link in the left hand
 side of the footer, to help users filing bug reports.
 Bug: 711318
  --
ulink id=reportbug 
url=https://bugzilla.gnome.org/enter_bug.cgi?product=GIMP-manual;
  Report an error in Bugzilla
/ulink and let us know.
/para

The phrase let us know shows _only_ in the low side of the page so the
phrase looks a bit weird. So I have decided to add this:

!-- repeated to make it appear also in the page. Error in css ?  --
ulink url=https://bugzilla.gnome.org/enter_bug.cgi?product=GIMP-manual;
  Report an error in Bugzilla
/ulink

it is a bit of a hack, I know. If someone knows how to resolve this issue
more elegantly, please commit it!

Anyway now it looks right!

bye

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Possible Release soon?

2013-11-04 Thread Marco Ciampa
On Mon, Nov 04, 2013 at 02:48:58PM +1000, Róman Joost wrote:
 Dear Marco,
 
 On Sun, Nov 03, 2013 at 10:43:17PM +0100, Marco Ciampa wrote:
  Well yes and no, with so much time...
  Cons:
  
   - pdf make is not working very especially with oriental languages
 Mayhaps we should just ditch that target for now...

well, I can ask around for help. If I find some help, why not?
BTW the epub export functionality is another great missing...

   - many important languages are missing, arabic for a start...
   - doc.gimp.org site design is really very poor, it seems to me made in 
  year 2000 ...
 Yeah I know. We should use www.gimp.org as the site design.
 
 If you like, the best way is to file a bug report. I remember that I
 always come back to the list and work on bugs, even if it takes years to
 fix a bug.

You are absolutely right.
I promise you that I'll do my best to use more the wonderful bugzilla...

...starting from now.

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++

___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Possible Release soon?

2013-11-03 Thread Marco Ciampa
On Thu, Oct 31, 2013 at 03:08:42PM +1000, Róman Joost wrote:
 Hi,
 
 I see so many contributions and I haven't prepared a release for ages.
 I'm sorry for that. My good excuse is a daily job and my son which keeps
 his father busy during the day.
 
 Since I'm expecting a daughter at the end of december, I'm determined to
 push out a release before. I can see that Joao and his team is adding
 Portuguese. When would be a best time to release a new tarball?

You keep respawning child (processes) until all resources,
are exhausted! ;-)


 PS: Do you guys realise that we're already working ~ 10 years on this
 manual?? Isn't that awesome?

Well yes and no, with so much time...

Pro:

 - because the docbook-xml + gettext method is one of the best ways I
   saw to keep up multilanguage translation effort is an efficiently manner
 - context help search works out of the box and this is really a good thing
 - the produced HTML is very good and works with every browser I know of

Cons:

 - pdf make is not working very especially with oriental languages
 - many important languages are missing, arabic for a start...
 - doc.gimp.org site design is really very poor, it seems to me made in year 
2000 ...

... the good thing is that I want to address some of these issues
... or die in the try ... ;-)

bye

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] gimp-help

2013-10-24 Thread Marco Ciampa
On Thu, Oct 24, 2013 at 03:27:59PM +0200, leif larsen wrote:
 is a New developer that is slowly learning docbook any one wane look at my
 code and maybe meet on gimp main irc to discus
 best regard leif

Uau the boxer use Linux! ;-)


-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] [Gimp-developer] [Gimp-web] Proposed gimp tutorial

2013-10-14 Thread Marco Ciampa
On Fri, Oct 11, 2013 at 08:59:04PM -0700, Stephen Kiel wrote:
 Marco,
 
 Thanks for all of your help!  Getting the tutorial published was more
 complicated than I originally anticipated, but it was definitely worth it.
 
 I do have a question for you:
 
 If I were to write another tutorial, is there anything that I could do to
 make the release or publication process easier?  I am not sure if there
 were things that you had to fix in order to publish the tutorial.  If I
 made some mistakes, it would be a good time for me to take note of them so
 I don't repeat them.
 
 Stephen Kiel

Right question, I do not really know the answer(s).

I myself have had some difficoulties to have your tutorial published. 

I asked help to a friend of mine for testing in local the gimp site pages
before publication.
I successfully tested your tutorial using the nginx web server instead of 
Apache.
I was NOT able to test it under Apache btw...
Even when local testing went well (without errors) the publication went wrong.
Automatic compilation was blocked by a couple of errors in the tutorial pages.
It seems that my version of python is less picky about small errors in the 
htrw pages so it was not so easy to find the errors in the first place.
Specifically the code into the web pages, the text in pre class=code 
MUST BE QUOTED since there are a couple of  and  inside it that 
confuse it a bit. Once quoted compilation and consequently site update went 
well.

Some developers complained about the scheme code. They say that it
is a bit C like and not really scheme/lisp like and since it
should be a teaching example, it should be rewritten to be a better
code for beginners and students. 

Please forgive my bad english and ... don't shoot the messenger! :-)

bye

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Help building help.

2013-08-18 Thread Marco Ciampa
On Sun, Jul 21, 2013 at 03:13:30AM +0200, Marco Ciampa wrote:
 On Tue, Jun 11, 2013 at 02:41:02PM -0400, john Culleton wrote:
  Elaborate things break more often then simple things. All I want is a
  Gimp Manual in pdf form for version 2.8. I can print this out, put it
  in a ring binder and use it as needed. What I got instead was a
  package with the guts of the manual in xml. I tried autogen, then
  ./configure, and then make.  Consistently I get these error messages:
  
  
  Making all in quickreference
  make[1]: Entering directory
  `/home/safe/Documents/gimp-help-2.8.0/quickreference' make[1]: *** No
  rule to make target `svg/gimp-keys-ca.svg', needed by `svg'.  Stop.
  make[1]: Leaving directory
  `/home/safe/Documents/gimp-help-2.8.0/quickreference' make: ***
  [all-recursive] Error 1
  
  Before I start hacking around eliminating references to the
  quickreference is there a standard solution to my problem?
  
  I don't want to spend days learning about docbook, wonderful though it
  may be. I have a project under way and I need to look some things in
  the manual.
  
  Anyone have a copy they are willing to share? Slackware 14 if anyone
  cares.
  
 
 I have another error:
 
 $make pdf-it
 *** Making PDF (it) ...
 Build the book set list...
 xsltproc -o /tmp/tmpxAwlqk/doclist.txt --xinclude --xincludestyle doclist.xsl 
 /home/marco/git-gnome/gimp-help-2/xml/it/gimp.xml
 Build the listings...
 xsltproc -o /tmp/tmpxAwlqk/listings.xml --xinclude --xincludestyle --param 
 current.dir '/home/marco/git-gnome/gimp-help-2/xml/it' 
 /usr/share/dblatex/xsl/common/mklistings.xsl 
 /home/marco/git-gnome/gimp-help-2/xml/it/gimp.xml
 xsltproc -o gimp.rtex --xinclude --xincludestyle --param current.dir 
 '/home/marco/git-gnome/gimp-help-2/xml/it' --param listings.xml 
 '/tmp/tmpxAwlqk/listings.xml' /tmp/tmpxAwlqk/custom.xsl 
 /home/marco/git-gnome/gimp-help-2/xml/it/gimp.xml
 XSLT stylesheets DocBook - LaTeX 2e (0.3.4-3)
 ===
 literal: default template used in programlisting or screen
 literal: default template used in programlisting or screen
 Don't know what gentext to create for xref to: para (linkend=text-to-path)
 Don't know what gentext to create for xref to: para 
 (linkend=text-along-path)
 Image 'images/toolbox/paths-transform-1.png' not found
 Image 'images/toolbox/paths-transform-2.png' not found
 Image '../images/tool-options/stock-gravity-east-24.png' not found
 Build gimp.pdf
 built-in module xetex registered
 no support found for ifthen
 no support found for ifxetex
 no support found for fontspec
 no support found for xltxtra
 no support found for fontenc
 no support found for ucs
 no support found for inputenc
 no support found for fancybox
 built-in module makeidx registered
 no support found for babel
 no support found for cmap
 no support found for db2latex
 built-in module bibtopic registered
 building additional files...
 checking if compiling is necessary...
 the output file doesn't exist
 xelatex -interaction=batchmode gimp.tex
 
 A possible reason for transformation failure is invalid DocBook
 (as reported by xmllint)
 
 Error: [Errno 2] No such file or directory
 make: *** [pdf/it/gimp.pdf] Errore 1
 
 
 
 but 
  log/it-xmllint.log 
 contains
  it: no errors.
 
 Any hint?

xelatex was not installed but autoconf did not signal the problem ... anyway... 
to me...

make pdf-it

...

no new compilation is needed
running last-compilation scripts...
Character U+E0 (à) not in font 'cmmi10'
Character U+2CB (ˋ) not in font 'URW Palladio L Bold/ICU:mapping=tex-text;'
Character U+2CB (ˋ) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+3B1 (α) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+2245 (≅) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+592A (太) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+5CF6 (島) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+672C (本) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+6768 (杨) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+7EA2 (红) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+826F (良) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+828A (芊) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+8521 (蔡) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+C9C0 (지) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+CD5C (최) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D76C (희) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
'gimp.pdf' successfully built

works ;-)

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Help building help.

2013-08-18 Thread Marco Ciampa
On Sun, Aug 18, 2013 at 04:02:46PM +0200, Marco Ciampa wrote:
[...]
 
 xelatex was not installed but autoconf did not signal the problem ... 
 anyway... to me...
 
 make pdf-it
 
 ...
 
 no new compilation is needed
 running last-compilation scripts...
 Character U+E0 (à) not in font 'cmmi10'
 Character U+2CB (ˋ) not in font 'URW Palladio L Bold/ICU:mapping=tex-text;'
 Character U+2CB (ˋ) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
 Character U+3B1 (α) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
 Character U+2245 (≅) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
 Character U+592A (太) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
 Character U+5CF6 (島) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
 Character U+672C (本) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
 Character U+6768 (杨) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
 Character U+7EA2 (红) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
 Character U+826F (良) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
 Character U+828A (芊) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
 Character U+8521 (蔡) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
 Character U+C9C0 (지) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
 Character U+CD5C (최) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
 Character U+D76C (희) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
 'gimp.pdf' successfully built
 
 works ;-)

and even ...

make pdf-ko



Character U+D6C4 (후) not in font 
'FreeSans/ICU:script=latn;language=DFLT;mapping=tex-text;'
Character U+D6C4 (후) not in font 'URW Palladio L Italic/ICU:mapping=tex-text;'
Character U+D6C4 (후) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D6CC (훌) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D6E8 (훨) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D718 (휘) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D71C (휜) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D720 (휠) not in font 'URW Palladio L Bold/ICU:mapping=tex-text;'
Character U+D720 (휠) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D734 (휴) not in font 'URW Palladio L Bold/ICU:mapping=tex-text;'
Character U+D734 (휴) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D749 (흉) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D750 (흐) not in font 'URW Palladio L Bold/ICU:mapping=tex-text;'
Character U+D750 (흐) not in font 'URW Palladio L Italic/ICU:mapping=tex-text;'
Character U+D750 (흐) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D751 (흑) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D754 (흔) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D761 (흡) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D765 (흥) not in font 
'FreeSans/ICU:script=latn;language=DFLT;mapping=tex-text;'
Character U+D765 (흥) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D769 (흩) not in font 'URW Palladio L Italic/ICU:mapping=tex-text;'
Character U+D76C (희) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D770 (흰) not in font 'URW Palladio L Italic/ICU:mapping=tex-text;'
Character U+D770 (흰) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D788 (히) not in font 
'FreeSans/ICU:script=latn;language=DFLT;mapping=tex-text;'
Character U+D788 (히) not in font 'URW Palladio L Italic/ICU:mapping=tex-text;'
Character U+D788 (히) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D78C (힌) not in font 'URW Palladio L Italic/ICU:mapping=tex-text;'
Character U+D78C (힌) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D790 (힐) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D798 (힘) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D799 (힙) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
'gimp.pdf' successfully built

 ... to you works! ;-)

If you like I can send you a copy...

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] [Gimp-web] Proposed gimp tutorial

2013-07-24 Thread Marco Ciampa
First of all, I am not a git expert.

I am trying to help you in the hope to do and say not too much errors...

On Mon, Jul 22, 2013 at 07:22:07AM -0700, Stephen Kiel wrote:
 [stephen@localhost gimp-web-staging]$ which git
 /usr/bin/git
 [stephen@localhost gimp-web-staging]$ git config --global user.name Stephen 
 Kiel
 [stephen@localhost gimp-web-staging]$ git config --global user.email 
 snick.k...@gmail.com
 [stephen@localhost gimp-web-staging]$ git config --global color.ui auto
 [stephen@localhost gimp-web-staging]$ git clone git://git.gnome.org/gimp-web
 Cloning into 'gimp-web'...
 remote: Counting objects: 16053, done.
 remote: Compressing objects: 100% (6204/6204), done.
 remote: Total 16053 (delta 10709), reused 14402 (delta 9672)
 Receiving objects: 100% (16053/16053), 66.74 MiB | 387.00 KiB/s, done.
 Resolving deltas: 100% (10709/10709), done.
 [stephen@localhost gimp-web-staging]$ cd gimp-web/
 [stephen@localhost gimp-web]$ ls
 about  downloadsinstall.sh   release-notes
 admin  errorirc.htrw robots.txt
 announcements  features linksscreenshots
 archive.htrw   gimp-web.doapmacintoshsource
 books  google33e0e7c6a0a36ade.html  mail_lists.htrw  style
 bugs   images   MAINTAINERS  team.htrw
 ChangeLog  includes Makefile template.htrw
 contestindex.htrw   man  tutorials
 developINSTALL  news unix
 docs   install.config.samplenopatents.html   webmasters.htrw
 donating   install.exclude  programmatic windows

so far so good

 [stephen@localhost gimp-web]$ git branch -r
   origin/2-8-temp
   origin/HEAD - origin/master
   origin/master
   origin/master_svn1715
   origin/old-trunk
   origin/static-html5
   origin/v2.4
   origin/v2.6

so far so good. At THIS point, if you do a 

git branch --all

you must see this like mine:

* master
  remotes/origin/2-8-temp
  remotes/origin/HEAD - origin/master
  remotes/origin/master
  remotes/origin/master_svn1715
  remotes/origin/old-trunk
  remotes/origin/static-html5
  remotes/origin/v2.4
  remotes/origin/v2.6

that means that you have a local branch named master which is a
tracking local branch. That means that if you do just a 

 git pull

it will do a 

git fetch and then a git merge of the remote master branch into the local 
master.

OK

If you prefer you can do a git pull --rebase to do a git fetch followed
by a git rebase of the remote master again into the local master. 

...

 [stephen@localhost gimp-web]$ git checkout -b HEAD origin/HEAD
 Branch HEAD set up to track remote branch master from origin.
 Switched to a new branch 'HEAD'

with this you just create a _new_ local remote tracking branch with name
HEAD but since HEAD is a special name in git I think that this is an
error and you should avoid this. I think that you just followed an
example without undestanding it because that HEAD I think was there just
as an example... it meaning was something like this:

 git checkout -b put_here_the_name_of_your_local_branch 
origin/put_here_the_name_of_the_remote_branch_that_you_want_to_track

but since git clone already set up a local tracking branch you do not
have to do it ...

 warning: refname 'HEAD' is ambiguous.
 warning: refname 'HEAD' is ambiguous.

see? HEAD is not a good name!

BTW I think that it is better for you to just create a patch and post it
here to someone that have write permissions to push it into master
branch ...


-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] [Gimp-developer] [Gimp-web] Proposed gimp tutorial

2013-07-24 Thread Marco Ciampa
On Tue, Jul 23, 2013 at 07:32:57PM -0700, Stephen Kiel wrote:

 I did format the tutorial into web format 

Here you can help me a lot. I have tried to test your tutorial before
committing it to the git-web repo but I was unable to test it.

I have started with trying to test the actual web site without any
additions directly from a git clone command. I have tried both with
makefile and with Apache SSI directly.

Same results: it keeps to create into the git dir a bunch of html files
and install just a few of them into the right installation dir.

There must be something wrong here.

I use Linux Ubuntu 13.04 wich comes with python-2.7 (could be a problem
the python version?)

Any hint?

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] [Gimp-web] OFF-TOPIC (was:Proposed gimp tutorial)

2013-07-24 Thread Marco Ciampa
On Wed, Jul 24, 2013 at 06:21:59PM -0400, Alec Burgess wrote:
 @Marco: Just out of curiosity I follow the Chrome-Blink dev list. In
 it they frequently talk about rebaselining a patch or commit. I've
 been unable to figure out what that term means just from the
 contexts I've seen it in and my attempts to Google for it were not
 fruitful.
 
 Can you explain what rebase or rebaselining means?

rebase is a different kind of merge, sometimes much useful and a
little more intelligent but it should be used cum grano salis.

This explain it very well:

http://stackoverflow.com/questions/1089/whats-the-difference-between-git-merge-and-git-rebase

In practice with merge, your changes are melted toghether with the
changes that could be occured simultaneously in the master branch. 

If there is a conflict, merge or rebase is the same, that conflict must
be resolved manually if the algorithm could not figure out what to do by
itself.

With rebase your changes are recalculated as if applied to the current
master branch even if they were done to an older version of the master
branch. The result is a patch that appears to be applied to the current
master branch automatically.

Rebase is useful for example to keep your branch updated to the current
status of the master branch mantaining your modifications until you
decide to apply those modifications to the master branch in a single
operation.

That will appear as if you would have done the work, all in a single
chunk, to the last commit of the master branch.

Hope this clarify it a little.

-- 

Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] GIMP DOCS, Korean translation patch

2013-07-23 Thread Marco Ciampa
On Mon, Jul 22, 2013 at 05:31:24PM +0900, Jihui Choi wrote:
 Here is the link of my file.
 Sorry for unconvinience.
 
 https://github.com/jihuichoi/gimp-help-ko/blob/master/gimp-help-2-ko.diff.20130722.zip
 

Committed. I just erased almost all entries from po/ko/glossary.po since
I incurred in the same that core dump that you have seen already. I
figured out that that file was heavily corrupted and choosed to discard
it to a safe state until I have seen a 

make validate-ko

without errors.

Please complete one .po file at a time and check for errors. Sometimes
make validate will not suffice since some misplaced xtml tags are tricky
to check automatically.

Keep on with the good work!

bye

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] [Gimp-web] Proposed gimp tutorial

2013-07-23 Thread Marco Ciampa
On Mon, Jul 22, 2013 at 07:22:07AM -0700, Stephen Kiel wrote:
 Roman and Pat,
 
 I have made some progress toward getting my tutorial ready for release, but
 I am at a point now where I have hit a wall, and I would like to ask for
 some advice on how to proceed.
 
 I did do a final edit of the tutorial, format it into xhtml, and add a
 couple of pictures. I downloaded a copy of Bluefish and used it to format
 the material into an xhtml file adding the boilerplate provided in the
 tutorial template by hand. It seemed to render well in the Firefox browser.
 
 I did find a procedure for adding content through git web at
 https://wiki.gnome.org/Git/Developers and followed it as best as I could. I
 was able to clone the gimp-web, check out a branch, make local changes and
 commit them, but then my progress stopped. My questions are:
 
  1) when I performed a 'git branch -r' several branches were listed. I
 guessed and picked HEAD as it appeared to link to origin/master. When I did
 a 'git status' and 'git commit -a' I got a warning message that “refname
 'HEAD' is ambiguous”. Did I pick the wrong branch? Is there another
 problem, or is this warning normal?

HEAD is the generic name for the head of a [your] local branch... see this
for an intro into git:

http://www.sbf5.com/~cduan/technical/git/

what you probably want to do is:

git checkout master

to see _all_ the branches

git branch --all


  2) The guidelines I was looking at seemed to be saying I could either use
 'git-bz' or 'git push' to get my changes back to the main repository.

better to use the second ...

 Neither worked,

have you write rights?

 so I was wondering which technique I should focus on. Would
 rather not debug them both at this time (could use quite a bit of time,
 since I don't know what either is trying to do).
 
  The error message that I go with git-bz was:
 
  bash: git-bz: command not found...

if ubuntu / debian you have to:

apt-cache show git-bzr-ng

but ... are you more confident with bazar? Why you want to insist on use
such an iterface module? I do not suggest you to use such tool ... use
directly git!

 
  The error message from git push –dry-run was:
 
 fatal: Could not read from remote repository.
 
  Please make sure you have the correct access rights

that was what I was saying above...

 
 and the repository exists.
 
  A git pull –rebase right before trying the push seemed to find the
 repository and verify that my current branch is up to date.

ok

 
  I would appreciate any pointers you could give me. I am attaching a copy
 of the transcript from my shell session. I am also attaching a copy of the
 files I was trying to add  modify in case it is relevant or you would like
 to take a look at them.
 

I'll look at those ...

  In the mean time, I will start looking at git-bz in case that is the write
 way to go. It looks like there may be some setup issues, even though the
 error message make it look like it is an installation issue. The options
 for the bz command were not clear to me. The wiki page indicated the syntax
 should be:
 
 git-bz file product/component HEAD
 
 I am guessing the product should be 'gimp-web', but when I look at
 https://bugzilla.gnome.org/buglist.cgi?quicksearch=gimp-web I see the
 component listed as both gimp-web and www.gimp.org. Do you know which it
 should be, or whether it matters? 

git-web

 When it asks for 'file' I am assuming it
 is looking for the results of the local 'commit'. In my case the feedback
 was
 
 [HEAD a97ce5a] Added tutorial Automate Creation fo XCF from JPG
 
 Are they looking for a97ce5a as the file?

see the illuminating above tutorial... that is a header and it is just a
checksum for your branch state

bye

PS: sorry I haven't followed the thread until now... I'll read all
mailing exchanges to give more useful answers ...

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Please check a update file on https://l10n.gnome.org/module/gimp-help-2/

2013-07-21 Thread Marco Ciampa
On Sun, Jul 21, 2013 at 11:02:00PM +0900, Jihui Choi wrote:
 Hi, Marco.
 Thank you for your answer.
 
 I've just gotten source from git and checked validation. I got some errors.
 I didn't do anything after I cloned source from git.
 
 ---
 ubuntu@ubuntu:~/gimp-help-2$ make validate-ko
 [PO]  po/ko/appendix.po
 178 translated messages, 197 fuzzy translations, 370 untranslated messages.
 [XML] xml/ko/glossary/glossary.xml
 /bin/bash: line 1: 22327 Segmentation fault  (core dumped)

That is weird and should not happen.
Are you shure of your linux installation or of your hardware?

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Please check a update file on https://l10n.gnome.org/module/gimp-help-2/

2013-07-20 Thread Marco Ciampa
On Tue, Jul 09, 2013 at 05:27:44PM +0900, Jihui Choi wrote:
 Hello, all.
 I'm Jihui Choi.
 
 I used to translate and maintain korean translation, but for the last
 several years I didn't.
 I'm gonna start again but I don't know where I should start from.
 Now it seems everyone works on l10n.gnome.org, right?

AFAIK no. 

We (I) appear there because the site reflects git commits.

 Btw, I uploaded a updated file on
 https://l10n.gnome.org/vertimus/gimp-help-2/master/appendix/ko
 https://l10n.gnome.org/vertimus/gimp-help-2/master/introduction/ko
 
 Please check these files out and commit. Thank you.

I think that it is better if you use git and then post here a patch
checking for validation of your translations with

make validate-ko

You have to install all the necessary tools to be able to build an html
version of the manual, of course.

If you need some assistance, please ask.

PS: it is easier if you use linux...

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Help building help.

2013-07-20 Thread Marco Ciampa
On Mon, Jul 01, 2013 at 05:36:50PM +1000, Roman Joost wrote:
 On Wed, Jun 26, 2013 at 05:04:10PM +0400, Alexandre Prokoudine wrote:
  On Wed, Jun 26, 2013 at 10:14 AM, Roman Joost wrote:
   On Thu, Jun 13, 2013 at 10:00:12AM +0200, Marco Ciampa wrote:
  
   Anyhow, perhaps it makes more sense to move to a epub/Kindle solution. I
   can relate to Marco here, since I'm also using my Kindle to read most of
   my books now. The Kindle format is even simiar to HTML. Not sure if
   there are already packages out there who go from DocBook to Kindle/epub.
  
  http://sourceforge.net/projects/docbook/files/epub3/
  
  However, note that eInk readers are, in my experience, quite inferior
  for technical reading. Anything that involves tables and color images
  is likely to make your head hurt :) OTOH, EPU is more than just for
  eInk readers. Tablets are OK :)
 Hm... sounds like we need a plan. Perhaps I'll create a bug in Bugzilla
 and we move the discussion there ...
 

Would you please post here the bug id when you have done?

Thanks!

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Help building help.

2013-07-20 Thread Marco Ciampa
On Tue, Jun 11, 2013 at 02:41:02PM -0400, john Culleton wrote:
 Elaborate things break more often then simple things. All I want is a
 Gimp Manual in pdf form for version 2.8. I can print this out, put it
 in a ring binder and use it as needed. What I got instead was a
 package with the guts of the manual in xml. I tried autogen, then
 ./configure, and then make.  Consistently I get these error messages:
 
 
 Making all in quickreference
 make[1]: Entering directory
 `/home/safe/Documents/gimp-help-2.8.0/quickreference' make[1]: *** No
 rule to make target `svg/gimp-keys-ca.svg', needed by `svg'.  Stop.
 make[1]: Leaving directory
 `/home/safe/Documents/gimp-help-2.8.0/quickreference' make: ***
 [all-recursive] Error 1
 
 Before I start hacking around eliminating references to the
 quickreference is there a standard solution to my problem?
 
 I don't want to spend days learning about docbook, wonderful though it
 may be. I have a project under way and I need to look some things in
 the manual.
 
 Anyone have a copy they are willing to share? Slackware 14 if anyone
 cares.
 

I have another error:

$make pdf-it
*** Making PDF (it) ...
Build the book set list...
xsltproc -o /tmp/tmpxAwlqk/doclist.txt --xinclude --xincludestyle doclist.xsl 
/home/marco/git-gnome/gimp-help-2/xml/it/gimp.xml
Build the listings...
xsltproc -o /tmp/tmpxAwlqk/listings.xml --xinclude --xincludestyle --param 
current.dir '/home/marco/git-gnome/gimp-help-2/xml/it' 
/usr/share/dblatex/xsl/common/mklistings.xsl 
/home/marco/git-gnome/gimp-help-2/xml/it/gimp.xml
xsltproc -o gimp.rtex --xinclude --xincludestyle --param current.dir 
'/home/marco/git-gnome/gimp-help-2/xml/it' --param listings.xml 
'/tmp/tmpxAwlqk/listings.xml' /tmp/tmpxAwlqk/custom.xsl 
/home/marco/git-gnome/gimp-help-2/xml/it/gimp.xml
XSLT stylesheets DocBook - LaTeX 2e (0.3.4-3)
===
literal: default template used in programlisting or screen
literal: default template used in programlisting or screen
Don't know what gentext to create for xref to: para (linkend=text-to-path)
Don't know what gentext to create for xref to: para (linkend=text-along-path)
Image 'images/toolbox/paths-transform-1.png' not found
Image 'images/toolbox/paths-transform-2.png' not found
Image '../images/tool-options/stock-gravity-east-24.png' not found
Build gimp.pdf
built-in module xetex registered
no support found for ifthen
no support found for ifxetex
no support found for fontspec
no support found for xltxtra
no support found for fontenc
no support found for ucs
no support found for inputenc
no support found for fancybox
built-in module makeidx registered
no support found for babel
no support found for cmap
no support found for db2latex
built-in module bibtopic registered
building additional files...
checking if compiling is necessary...
the output file doesn't exist
xelatex -interaction=batchmode gimp.tex

A possible reason for transformation failure is invalid DocBook
(as reported by xmllint)

Error: [Errno 2] No such file or directory
make: *** [pdf/it/gimp.pdf] Errore 1



but 
 log/it-xmllint.log 
contains
 it: no errors.

Any hint?

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Help building help.

2013-06-26 Thread Marco Ciampa
On Wed, Jun 26, 2013 at 04:14:42PM +1000, Roman Joost wrote:
 On Thu, Jun 13, 2013 at 10:00:12AM +0200, Marco Ciampa wrote:
  On Wed, Jun 12, 2013 at 10:17:50PM +0200, Ulf-D. Ehlert wrote:
   On Tue, Jun 11, 2013 at 02:41:02PM -0400, john Culleton wrote:
Elaborate things break more often then simple things. All I want is a
Gimp Manual in pdf form for version 2.8. I can print this out, put it
in a ring binder and use it as needed.
   
   Making pdf always was problematic for some languages, the html manual
   is IMO a better choice. BTW, do you really want to print some hundred
   pages?
  
  PDF pages are no longer just for print but a mean to read with computer
  / tablet / ebook reader. I myself use a kindle to read GIMP books in PDF
  in the spare time.
  
  I would not underestimate the importance of the pdf format for a manual.
 Perhaps it would make better sense, to remove the PDF functionality
 (based on dblatex), since it never left a stable stage.
 
 The reason to choose dblatex was that FOP at the time was not mature 
 enough to produce good quality output. I think that has changed. DbLatex 
 worked well for latin content, but always seemed to give us headaches
 with totally different character sets. Perhaps it's not dblatex fault, 
 just the lack investigating a good LaTeX - PDF solution.
 
 Anyhow, perhaps it makes more sense to move to a epub/Kindle solution. I 
 can relate to Marco here, since I'm also using my Kindle to read most of 
 my books now. The Kindle format is even simiar to HTML. Not sure if
 there are already packages out there who go from DocBook to Kindle/epub.

There are powerful converters out there. See for example the Git book
that is written in markdown and the pandoc suite or Calibre.

References:

http://git-scm.herokuapp.com/book
http://git-scm.herokuapp.com/blog/2009/07/28/the-gory-details.html
http://www.slideshare.net/larrycai/write-book-in-markdown
http://johnmacfarlane.net/pandoc/epub.html
http://www.codinghorror.com/blog/2012/10/the-future-of-markdown.html
https://github.com/LaPingvino/markdown-example-book
http://calibre-ebook.com/

bye

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


[Gimp-docs] anyone working on these?

2013-04-24 Thread Marco Ciampa
$ make check-images
[SRC] src/preface/authors.xml
*** Checking image references ... 
parsing XML files ... 
found 1591 references in 635 files

searching images in 'images/C' ...
found 1589 image files

2 broken image references:
BROKEN: images/toolbox/paths-transform-1.png IN 
src/toolbox/transform/common-features.xml
BROKEN: images/toolbox/paths-transform-2.png IN 
src/toolbox/transform/common-features.xml
0 orphaned image files

... if yes please fix!

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


[Gimp-docs] what to do with the orphaned images?

2012-12-02 Thread Marco Ciampa
See the command:

$make check-images-en
[SRC] src/preface/authors.xml
*** Checking image references ... 
parsing XML files ... 
found 1578 references in 634 files

searching images in 'images/C' ...
found 1599 image files

0 broken image references
21 orphaned image files:
ORPHANED: images/C/dialogs/SaveAsCSS.png
ORPHANED: images/C/dialogs/stock-reset-16.png
ORPHANED: images/C/math/dot-for-dot.png
ORPHANED: images/C/menus/windows/dockable-dialogs.png
ORPHANED: images/C/toolbox/FG-select-smoothing1.png
ORPHANED: images/C/toolbox/FG-select-smoothing2.png
ORPHANED: images/C/toolbox/FG-select-smoothing3.png
ORPHANED: images/C/toolbox/brush-dynamics.png
ORPHANED: images/C/toolbox/dynamic-fade-example-curve-color-fade.png
ORPHANED: images/C/toolbox/dynamic-fade-example-curve.png
ORPHANED: images/C/toolbox/dynamic-fade-example.png
ORPHANED: images/C/toolbox/dynamics-options.png
ORPHANED: images/C/toolbox/perspective-clone-options.png
ORPHANED: images/C/toolbox/tool-options-paint-gradient.png
ORPHANED: images/C/using/dialog-highlight-dockbar.png
ORPHANED: images/C/using/dialog-highlight-handle.png
ORPHANED: images/C/using/dock-attached.png
ORPHANED: images/C/using/dock-tab.png
ORPHANED: images/C/using/imagewindow-description.png
ORPHANED: images/C/using/left-vertical-line.png
ORPHANED: images/C/using/standard-setup.png

?

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Regard less in the introduction of Ghostscript

2012-11-02 Thread Marco Ciampa
On Wed, Oct 31, 2012 at 05:09:23PM +0900, RyōTa SimaMoto wrote:
 Oh, I am sorry that I made mistake.
 The subject title should be Regard less AFPL in the introduction of
 Ghostscript.

Good point. Would you correct it or are you just suggesting that the
section must be improved? I hope for the first ;-) ... relax, I will
proofread it, I promise! 

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Added dynamics

2012-10-31 Thread Marco Ciampa
I hope you do not mind if I switch this tread publicly...

On Tue, Oct 30, 2012 at 09:36:27PM +0100, Kolbjørn Stuestøl wrote:
 Den 30.10.2012 16:39, skreiv Marco Ciampa:
 On Mon, Oct 22, 2012 at 10:02:13PM +0200, Kolbjørn Stuestøl wrote:
 A few moments ago I added src/toolbox/paint/dynamics.xml to the
 gimp-help-2 repository.
 This is a first sketch. Hoping someone will correct it, add new
 sections etc.
 I have no drawing pad or something like that so it is impossible for
 me to write about using it.
 Of course this is not the only way of describing the dynamics. Only
 meant as a start point. As usual: Feel free to make changes.
 Kolbjoern
 I do not understand this:
 
 Mostly moving to the right and moving downward the color is picked from
 the left side of the gradient and the other directions get the color
 picked from the right half of the gradient
 Not so strange. It is obviously wrong.
 
 Mostly? Would you clarify this passage, please?
 
 Sorry my english is not very good...
 Looks fine to me.

Yeah grammatically but I meant a different thing so you see that I was
not able to explain it clearly... so it is my fault.

In that passage I was in trouble in understanding what you actually was
trying to say and not arguing on the behaviuor of the function that only
accidentally works in a different manner of you was describing...

 
 PS: very good work!
 Thank you
 
 
 Most of the work has been done by using the trial and error method.

I understand... and it is not an easy job...

 A few found on internet. I obviously did a bad job here running too
 few tests on the subject.

Not your fault... there is no docs on the subject... devs expecting docs
writers to be able to read sources, that means that they ask for
programmers, not writers / translators...

 As a consequence of your mail today I tried the color-direction
 dynamics again. With some different results!

Non tibi hoc soli ... ;-)

 It looks like the colors are chosen not as systematically as I first
 found out, but at more or less by random.  Or do you have another
 explanation? I would be grateful to know.

Please ask devs!

 As I said, this is an attempt to get other people engaged in writing
 this chapter. The lack of description of the dynamics is a great
 loss to many people using GIMP.

I perfectly agree...

 Adding one of my many attempts to figure out how the color-direction works.
 Btw: This time I used GIMP 2.8.2 on Windows 7.

I use (almost always) GIMP under Linux :-)

 Thank you for drawing my attention on this fault.

Thank you for affording this task for all us.

PS: a note on style. Every time you write  in the toolbox I think you
mean  in the tool options panel or  in the tool option dialog, right?
IHMO it is better, when in doubt, to use the more verbose but clearer form...


-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] How about a shared TODO list ?

2012-09-25 Thread Marco Ciampa
On Mon, Aug 27, 2012 at 03:43:20AM +0900, RyōTa SimaMoto wrote:
 2012/8/27, Marco Ciampa ciam...@libero.it:
  On Mon, Aug 27, 2012 at 12:44:59AM +0900, RyōTa SimaMoto wrote:
  Hi,
 
  I think it would be better for us to have a shared TODO list for
  completing and keeping updated the GIMP documentation.
  Here are known issues:
 [snip]
 
  At http://wiki.gimp.org/, are there any pages for the documentation
  team?  I will read them first if they exist.
 
  RyōTa is right, we need a wiki and need it badly.
 
   - We used to have a space for describe how to build a gimp help
 compilation environment in various platform.
 
   - We need some sort of (simple!) way to organize our work, IMHO a
 simple table could go with:
 
 problem | who work on it | time (planned)
 
 I agree.  Almost management knowledge of documents in Docbook or
 Mallard are common in gnome projects and should go to
 live.gnome.org, but to store project specific notes and logs of
 GIMP Documentation Team, wiki.gimp.org must be suitable.
 
 Several months ago before October of the last year, I sent a mail
 to this list that suggests to add a page about directory location
 and usage in most popular platforms.  Though it was not responded
 and unfortunately all letters including my mail are not stored in
 the archive of the current mailing-list server, I do still not
 disappointed because someone possibly might remembered it and has
 ideas about it.  Like a collaboration chart as you illustrated,
 if we have conclusion sheet of discussion at ML, planning table,
 or priority ordered list, it will be also distinct what is going
 or rejected about such drafted proposals.

Please reply, RyōTa and I are still waiting (from august) yes or not
(and why)...

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Drop HTML creation of untranslated languages

2012-09-20 Thread Marco Ciampa
On Thu, Sep 20, 2012 at 03:54:01PM +1000, Roman Joost wrote:
 Hi,
 
 I'm currently in the process of adding support for:
 
 https://bugzilla.gnome.org/show_bug.cgi?id=168256
 Help pages should have links to corresponding pages in other
 languages
 
 which brought me to our damned lies page. I think we should drop
 creating HTML for language codes which currently don't provide any
 translation. (Remove the language codes from the ALL_LINGUAS option in
 configure.ac)
 
 Perhaps a more prominent link on our homepage to the damned lies page
 will help getting new translators, but currently as I see it, we can
 savely drop building HTML for:
 
 * Catalan
 * Danish
 * Croatian
 * Finnish
 * Lithuanian
 * Polish
 
 Any objections? With that I'll update the links to the work in progress.

Mine, obviously, not. Go on.


-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] How about a shared TODO list ?

2012-08-26 Thread Marco Ciampa
On Sun, Aug 26, 2012 at 08:50:34PM +0400, Alexandre Prokoudine wrote:
 On Sun, Aug 26, 2012 at 8:19 PM, Marco Ciampa wrote:
 
  At http://wiki.gimp.org/, are there any pages for the documentation
  team?  I will read them first if they exist.
 
  RyōTa is right, we need a wiki and need it badly.
 
 What's the problem with wiki.gimp.org? Need accounts?

Yes please. BTW found an error on 1st page:

 Whose is it?

This wiki is currently maintained by some GIMP developers, so if you
have any comments, feel free to contact LightningIsMyName or
Alexia_Death via the the GIMP IRC (irc://irc.gimp.org#gimp) 
  ^error
the URI is wrong, it will never work, see:

http://ftp.ics.uci.edu/pub/ietf/uri/draft-mirashi-url-irc-01.txt

An irc URL takes the form:

   irc:[ //[ host[:port] ]/[target] [,needpass] ]


So it should be:

irc://irc.gimp.org/#gimp)

bye

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


[Gimp-docs] from dev ml ...

2012-08-23 Thread Marco Ciampa
To German translators...

- Forwarded message from Karl-Heinz Zimmer khzim...@gmail.com -

Date: Thu, 23 Aug 2012 10:50:11 +0200
From: Karl-Heinz Zimmer khzim...@gmail.com
To: gimp-developer-l...@gnome.org
Cc: Marco Ciampa ciam...@libero.it
Subject: Re: [Gimp-developer] gimp 2.8.1 when?
X-Mailer: Sylpheed 3.2.0beta5 (GTK+ 2.24.10; x86_64-unknown-linux-gnu)

On Thu, 23 Aug 2012 01:13:08 +0200
Marco Ciampa ciam...@libero.it wrote:

 On Tue, Aug 21, 2012 at 02:01:41PM -0400, Liam R E Quin wrote:
  On Tue, 2012-08-21 at 13:25 -0400, Christopher Curtis wrote:
  
   But what's involved? GIMP releases are source-only,
  I take it that you don't use the manual... and that you use GIMP in only
  one language, and, further, that the language you use is US
  English... :-)
 
 Please...
 
 Already the gettext toolchain keep all the dirty work done for us and
 the translation work is just a matter to type a couple of commands
 (literally: intltool-update LANG; emacs LANG.po ...) to see the
 untranslated strings and to fix them.
 
 The GIMP manual is completed by a couple of months now and its content
 should not change between any 2.8.x point releases...
 
 The only un-gettexted tool is the windows installer: I have completed
 the italian translation of the installer strings in a couple of hours...
 
 Just report here the language missing or incomplete.
 A translator will pop up.

Hi Mario,

I am not sure if this info is helpfull or not - just referring to your proposal 
to report here:

Parts of the German version manual seem to not be in German yet, e.g.:
http://docs.gimp.org/2.8/de/gimp-tutorial-quickie-jpeg.html

Cheers
Karl-Heinz

- End forwarded message -

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


[Gimp-docs] [w...@ieee.org: Re: [Gimp-user] GIF layers]

2012-08-21 Thread Marco Ciampa
- Forwarded message from Burnie West w...@ieee.org -

 http://docs.gimp.org/en/gimp-dialogs-structure.html#gimp-layer-dialog
 
 Layer visibility
 
  In front of the thumbnail is an icon showing an eye. By clicking on
  the eye, you toggle whether the layer is visible or not.
  (Shift-clicking on the eye causes all other to be temporarily
  hidden.)
The word temporarily is misleading. The other layers remain
hidden until their eye icon is clicked. However, this is hardly worth
a bug report.

- End forwarded message -

Do I just remove the word temporarily?

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] translator wiki

2012-07-30 Thread Marco Ciampa
On Sun, Jul 29, 2012 at 09:50:21PM +0100, Vitaly Lomov wrote:
 Hi,
 
 We need to get the translator one-page wiki back! The steps we follow are
 easy if you know them or memorized them. The newcomers are out of luck in a
 big way.
 
 Vitaly

+1

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


[Gimp-docs] cleanup

2012-07-28 Thread Marco Ciampa
Suggestion:

1) Delete

ChangeLog.pre-2-4
ChangeLog.pre-2-6

from the root dir

2) All the xml comments are old and unapdated. IMHO they only take space
in source. They remain in the old GIT versions for reference but are all
outdated and unused. 

bye

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] release procedure

2012-06-14 Thread Marco Ciampa
On Thu, Jun 14, 2012 at 10:15:54AM +1000, Roman Joost wrote:
 On Wed, Jun 13, 2012 at 05:18:26PM -0300, Joao S. O. Bueno wrote:
  I think some organization to get it going is indeed necessary - and
  this one - two weeks for updating translation  is certainly better than 
  none.
  
  So, +1 from me.
 Sounds good to me as well: +1
 
 Basically that means, for each release we create a branch. Every
 translator has to finish his work on this release branch, until it can
 be tagged and the tarballs are created.

Yes.

 Another possibility is not to create a branch, but simply use an
 announcement mail (which is probably good anyway) to mark the upcoming
 release.

Yes but in this way you force to stop working on the main document.

Instead if you create a branch you freeze for the translator and the
work on HEAD could go forward without messing up the translations.

This is the concept.

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] whats new in GIMP 2.8

2012-05-10 Thread Marco Ciampa
On Sun, May 06, 2012 at 01:52:39AM +0200, Marco Ciampa wrote:
 On Tue, May 01, 2012 at 03:09:15PM +0200, Marco Ciampa wrote:
  3) In case of a replacement, I found it useful to let the old section be
  accessible by web. Now there is a bug in the site, see by yourself:
  
  http://docs.gimp.org
  
  - there is no direct links to the on line HTML 2.6 section, there is
  only the 2.4 and older and the new WIP 2.8. The 2.6 version _is_ accessible 
  but
  only manually editing the web address of your browser replacing the 
  2.8 like
  
  http://docs.gimp.org/2.8/en/
  
  into
  
  http://docs.gimp.org/2.6/en/
  
  4) is the web site version controlled? Why not?
  
  it's enough for now...
 
 Anyone has an answer?

Gosh, it is my destiny to look like a fool...

I see, the site is git controlled inside the gimp manual source...

Ok I can now reformulate che questions:

1) why in the GIMP manual site there are two series of links, one for
2.6.0, and one for 2.6.1? Why not preserving just the last?

2) why there are links to the online html pages for 2.4 but no links to the 2.6?

3) why not insert the links to the online html pages for 2.6?

4) if I do these changes, is there anyone who does not agree?

bye

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-docs-list


[Gimp-docs] manual archive files missing

2012-05-10 Thread Marco Ciampa
All the gimp help archive files 2.6.1 are missing from the ftp.
Are present only the old 2.6.0 files.
All links to the 2.6.1 are, because of this, broken.

I've checked because I was intentioned to purge the html page from the
links to the older revision but I saw that I can't do it since the only
available are the older 2.6.0.

Is there a fix?
Who is responsible of the ftp site?
Is the 2.6.1 really the last of the 2.6 series?

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] whats new in GIMP 2.8

2012-05-05 Thread Marco Ciampa
On Tue, May 01, 2012 at 03:09:15PM +0200, Marco Ciampa wrote:
 3) In case of a replacement, I found it useful to let the old section be
 accessible by web. Now there is a bug in the site, see by yourself:
 
 http://docs.gimp.org
 
 - there is no direct links to the on line HTML 2.6 section, there is
 only the 2.4 and older and the new WIP 2.8. The 2.6 version _is_ accessible 
 but
 only manually editing the web address of your browser replacing the 
 2.8 like
 
 http://docs.gimp.org/2.8/en/
 
 into
 
 http://docs.gimp.org/2.6/en/
 
 4) is the web site version controlled? Why not?
 
 it's enough for now...

Anyone has an answer?

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] whats new in GIMP 2.8

2012-05-04 Thread Marco Ciampa
On Wed, May 02, 2012 at 01:04:34PM +0200, Ulf-D. Ehlert wrote:
 On Tue, May 01, 2012 at 08:52:16PM +0200, Marco Ciampa wrote:
 [...]
  Doing exactly this I just noted that the already translated strings in
  one .po file do not magically ;-) move from one file to another...
  (from introduction to appendix...)
  
  I need a way to avoid to create uneeded work to other translators...how
  can I move all those strings for _all_ the languages .po files?
 
 There's no simple (make) command to do this, but you can try this
 (not tested!):
 
 1. backup appendix.po and introduction.po ;-)
 
 2a. try 'msgmerge' with the '--compendium=FILE' option:
 
   $ msgmerge --quiet --width=79 \
 --compendium=po/xx/introduction.po \
 --output-file=po/xx/appendix.po \
 po/xx/appendix.po pot/appendix.pot
 
 and compare new and old appendix.po.

I've tried this and it is enough for me.

 2b. try it with 'make' using the 'COMPENDIUM' variable:
 
   # save introduction.po:
   $ cp po/xx/introduction.po po/xx/tmp-compendium.po
   $ make po/xx/appendix.po COMPENDIUM=tmp-compendium.po
 
 and, once more, compare new and old appendix.po.
 
 (Remember to always use the original (saved) appendix.po, if you try
 both methods.)

Why should it be different? It launch a different command?

 If this works, you can do it with a simple for-loop for all languages.

It worked very well, thank you Ulf, as usual. 

Done this:

#!/bin/bash

LOCREPO=/home/marco/git-gnome/gimp-help-2
LLIST=da de el es fi fr hr it ja ko lt nl nn pl ru sl sv zh_CN
POSRCS=introduction
PODEST=appendix
#MDEBUG=y


cd $LOCREPO
pwd
for PONAT in `echo $LLIST`
do
  if [ $MDEBUG == y ]; then
echo  msgmerge --width=79 \
   --compendium=po/${PONAT}/${POSRCS}.po \
   --output-file=po/${PONAT}/${PODEST}.po \
   po/${PONAT}/${PODEST}.po pot/${PODEST}.pot
  else
msgmerge --width=79 \
 --compendium=po/${PONAT}/${POSRCS}.po \
 --output-file=po/${PONAT}/${PODEST}.po \
 po/${PONAT}/${PODEST}.po pot/${PODEST}.pot
  fi
done

I've already pushed it (hope it was all right).
The new whats-new page is a work in progress and it is not complete.
Feel free to add, correct, comment, and forgive my many errors, please.

PS: May I ask you a favour Ulf? Can you tell me why the command syntax is that?
Why you have to specify appendix.po(t) three times? 

Looking at the command manual page I would never say that I would have
to put it like this.

From the man page...

man msgmrg

MSGMERGE(1)   GNU  MSGMERGE(1)

NAME
   msgmerge - merge message catalog and template

SYNOPSIS
   msgmerge [OPTION] def.po ref.pot


it seems just a 2 argument command...

TIA

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] whats new in GIMP 2.8

2012-05-04 Thread Marco Ciampa
On Fri, May 04, 2012 at 06:24:00PM +0200, Ulf-D. Ehlert wrote:
 On Fri, May 04, 2012 at 11:36:09AM +0200, Marco Ciampa wrote:
  PS: May I ask you a favour Ulf? Can you tell me why the command syntax is 
  that?
  Why you have to specify appendix.po(t) three times? 
 
 [...]
 
  it seems just a 2 argument command...
 
 Copy-and-paste-and-adapt error. ;-) The command we run via 'make' uses
 a temporary file as output (if I remember correctly, 'msgmerge'
 sometimes produced an empty po file).

That could be the result of a somehow incorrect .po file parsing ... I
did not see any error (lucky me ;-)
 
 So I should have written something like
 
   $ msgmerge ... --compendium=OLD_PO --output-file=TMP NEW_PO POT \
  cp TMP NEW_PO
 
 But I had warned you - I didn't test it! ;-)

Well, it worked, and git is our friend... ;-)

Anyway thank you (and Julien) again for your support!

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] writing a new section: image snapshots

2012-05-02 Thread Marco Ciampa
On Wed, May 02, 2012 at 07:37:47AM +0200, Julien Hardelin wrote:
 
 In wrinting a new section rised in me a question: how to preserve the
 screenshot homogeneity? Is there any?
 
 Once I remind it was a wiki note regarding how to take a screen snapshot.
 There was a system and a theme recomended.
 And now?
 Am I free to use whatever I want?
 
 
 Here is an extract of the How to Contribute I wrote long ago:
 

As usual, many thanks.

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] whats new in GIMP 2.8

2012-05-01 Thread Marco Ciampa
On Mon, Apr 30, 2012 at 08:30:02AM +0200, Marco Ciampa wrote:
 On Mon, Apr 30, 2012 at 07:49:41AM +0200, Julien Hardelin wrote:
  Le 29/04/2012 20:43, Marco Ciampa a écrit :
  Reading the manual from the start, just after the intro, you see
  
  What's New in GIMP 2.6?
  
  Why do not clone it creating a new section
  
  What's New in GIMP 2.8?
  
  I think that this could be a good starting point:
  
  http://www.gimpusers.com/tutorials/gimp-2-8-features-preview-april-2010
  
  Why you don't write it?
 
 With your assistance, I can try to do it.
 My english is poor.
 My knowledge of docbook-xml is inexistant.
 But I know these are excuses... I'll try.
 
 If you don't mind I'll post here my doubts...

First of all, thanks for the encuraging messages I've received.
They warm my heart.

Here we are for the questions.

1) I found that simply modifying this file

 src/introduction/whats-new.xml

is easier than I though

2) I was in doubt if it was better adding a new What's new with GIMP 2.8
   leaving the old section renamed into What was new with GIMP 2.6 but 
   maybe is an overkill...

Please _say_ what you _all_ think about it:

You do prefer to to replace and renew the section or...
You prefer adding a new section?

3) In case of a replacement, I found it useful to let the old section be
accessible by web. Now there is a bug in the site, see by yourself:

http://docs.gimp.org

- there is no direct links to the on line HTML 2.6 section, there is
only the 2.4 and the new WIP 2.8. The 2.6 version _is_ accessible but
only manually editing the web address of your browser replacing the 
2.8 like

http://docs.gimp.org/2.8/en/

into

http://docs.gimp.org/2.6/en/

4) is the web site version controlled? Why not?

it's enough for now...

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] help building help

2012-04-29 Thread Marco Ciampa
On Sun, Apr 29, 2012 at 06:55:09PM +0200, Ulf-D. Ehlert wrote:
 On Sun, Apr 29, 2012 at 04:41:12PM +0200, Marco Ciampa wrote:
  I've just committed two small fix in
  
  src/dialogs/export-file-dialog.xml
  
  how can I make make aware of it?
 
 This should work automatically, 'make' checks the timestamps.
 
  If I do a 
  
  make status-it
  
  it does not update the po files.
 
 Most likely, your po file is newer than the source (xml) file.
 Check it with
 
   $ ls -l src/dialogs/export-file-dialog.xml po/it/dialogs.po
 
  make clean 
  
  does not help.
  
  Any hint?
 
 Simply touch 'src/dialogs/export-file-dialog.xml' and try again:
 
   $ touch -c src/dialogs/export-file-dialog.xml
   $ make po-it
 

Umf perhaps I now understand what is going on here: I have modified the
xml file during the editing of a .po file. I've modified the xml file
and _then_ I've saved the .po file.

Is there a method to reset it all without 'touch'ing all xml files?

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-docs-list


[Gimp-docs] manual bug - dotted lines

2012-04-28 Thread Marco Ciampa
#: src/concepts/imagewindow.xml:322(para)
msgid 
anchor id=\dotted-lines\/indextermprimaryDotted lines/primary/
indextermemphasisDotted lines/emphasis: placeholder-1/ This is a 
feature specific to the single-window mode. These small dotted vertical 
lines, on the left and the right of the image, mark the limit between the 
image area and the panels, from top to bottom. When the mouse pointer passes 
over this line, it turns to a double-arrow. Then, click-and-drag to move the 
limit between image area and panels.

I do not see any dotted line in single window mode... is it a
reminescent of an old GIMP-2.7 single window test mode?

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] make status problem

2012-03-10 Thread Marco Ciampa
On Fri, Mar 09, 2012 at 08:28:37PM +0100, Ulf-D. Ehlert wrote:
 On Fri, Mar 09, 2012 at 07:07:02PM +0100, Marco Ciampa wrote:
  marco@lap2-ciampix:~/git-gnome/gimp-help-2$ make status-it
 [...]
  ERROR matching msgfmt output 'po/it/appendix.po 216107 679 messaggi 
  tradotti.
  '
  make: *** [po-status-it] Errore 29
 
 Maybe po/it/concepts.po (the next file in the list of pofiles) is
 broken; try e.g.
 msgfmt --statistics po/it/concepts.po /dev/null
 or
 msgfmt --check po/it/concepts.po
 
 Ulf
 
 
$msgfmt --statistics po/it/concepts.po /dev/null
982 messaggi tradotti.

(no error)

msgfmt --check po/it/concepts.po

(no message = no error)

make status-it
[SRC] src/preface/authors.xml
Cleaning up 'it' po files ...
ERROR matching msgfmt output 'po/it/appendix.po 216107 679 messaggi tradotti.
'
make: *** [po-status-it] Errore 29

(error still there...)


-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] make status problem

2012-03-10 Thread Marco Ciampa
On Sat, Mar 10, 2012 at 08:46:24PM +0100, Ulf-D. Ehlert wrote:
 On Sat, Mar 10, 2012 at 02:45:59PM +0100, Marco Ciampa wrote:
  $msgfmt --statistics po/it/concepts.po /dev/null
  982 messaggi tradotti.
  
  (no error)
  
  msgfmt --check po/it/concepts.po
  
  (no message = no error)
  
  make status-it
  [SRC] src/preface/authors.xml
  Cleaning up 'it' po files ...
  ERROR matching msgfmt output 'po/it/appendix.po 216107 679 messaggi 
  tradotti.
  '
  make: *** [po-status-it] Errore 29
 
 Then try it with all po files you have edited -- or even with all
 po files:
 find po/it -type f | \
 while read f; do echo $f `msgfmt --check $f`; done
 
 Ulf

Done. No errors. That error number 29 ... who is firing it? Make? Then why and 
what it means?

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] make status problem

2012-03-10 Thread Marco Ciampa
On Sat, Mar 10, 2012 at 10:19:20PM +0100, Ulf-D. Ehlert wrote:
 On Sat, Mar 10, 2012 at 09:26:53PM +0100, Marco Ciampa wrote:
 [...]
  Done. No errors. That error number 29 ... who is firing it?
  Make? Then why and what it means?
 
 Good questions. I don't know why the error number is 29, but the
 error message came from the Perl script that generates the status
 report. So your pofiles are ok, it was a bug (sorry, I should have
 noticed it sooner...).
 
 Try the attached patch - hope it works.

It worked perfectly. I think you can push it. As usual, many thanks.

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] make status problem

2012-03-10 Thread Marco Ciampa
On Sat, Mar 10, 2012 at 11:21:39PM +0100, Marco Ciampa wrote:
 On Sat, Mar 10, 2012 at 10:19:20PM +0100, Ulf-D. Ehlert wrote:
  On Sat, Mar 10, 2012 at 09:26:53PM +0100, Marco Ciampa wrote:
  [...]
   Done. No errors. That error number 29 ... who is firing it?
   Make? Then why and what it means?
  
  Good questions. I don't know why the error number is 29, but the
  error message came from the Perl script that generates the status
  report. So your pofiles are ok, it was a bug (sorry, I should have
  noticed it sooner...).
  
  Try the attached patch - hope it works.
 
 It worked perfectly. I think you can push it. As usual, many thanks.

BTW: has this any sense: tools/create_changelog.py ?

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] User manual 2.7 download

2012-01-30 Thread Marco Ciampa
On Mon, Jan 30, 2012 at 12:19:46PM +0100, Ulf-D. Ehlert wrote:
 On Mon, Jan 30, 2012 at 12:04:19PM +0100, Julien Hardelin wrote:
  Le 25/01/2012 21:10, Alexandre Prokoudine a écrit :
  The plan was to branch Git master for the last 2.6 docs release
  abnd start working on 2.8 docs. Roman said he'd do the job, but I
  guess he's just really busy at work + polishing his newly acquired
  parenting skills :)
  
  Well, I added a new branch, gimp-help-factory,  to the gimp-help-2
  module in the git server.
  It works: I added a new file to this new branch to test it.
  So, we can start writing help for gimp-2.8 without altering the
  gimp-help-2 master.
 
 There is already a branch gimp-help-2-6, so the master branch
 should/could be used for gimp-2.8.

Well done, it was almost time...

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-docs-list


Re: [Gimp-docs] Ping

2012-01-25 Thread Marco Ciampa
On Mon, Jan 23, 2012 at 02:32:54AM +0400, Alexandre Prokoudine wrote:
 2012/1/23 Kolbjørn Stuestøl wrote:
 
  OK. Then we are three still alive :-)
 

pong ;-)

-- 


Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-docs-list


  1   2   >