Vitaly Lomov skreiv:

Can you not use CSS selectors for that: .caption[lang|=nn]{
font-size:...;
}
That would match any element with 'caption' class and value 'nn' of attribute lang.
I got it from here:
http://webdesign.about.com/od/cssselectors/qt/cssselattribute.htm IE doesn't support that, though.

Vitaly

Thanks, Vitaly.
Yes I know about this, but as it is not supported in all browsers (as usual this means IE below 7) I did not want to use it. There is still some people using Internet Explorer below version 7. At the moment I am in argumentation with an international company not willing to switch to other browsers. They are using IE 6 "of safety reasons" I am told! Nice site you mentioned. I have bookmarked it.

Kolbjoern

Message: 1
Date: Mon, 29 Mar 2010 00:04:37 +0200 From: Kolbj?rn Stuest?l
Subject: [Gimp-docs] gimp-help-custom.css To: GIMP Docs
Message-ID:
Content-Type: text/plain; charset=UTF-8; format=flowed

I would like to add .caption {
font-size : smaller;
font-style : italic;
}
to the style sheets to differ the image text from the body text. Perhaps the not used gimp-help-custom.css file is a good way of doing it, but as this wish may be unique to Norwegian only, how to add a conditional to select languages? (if LANG="nn" then ... else not) As far as I know it is not possible in the style sheet, but is there a clever/simple way of doing this. (Unless we add it to the common style sheets).
It is not very important to me to add this style, only a suggestion/wish. Kolbjoern

I appreciate the e-mails, please keep up the good work.

--- On Thu, 4/1/10, gimp-docs-request@lists.XCF.Berkeley.EDU wrote:

From: gimp-docs-request@lists.XCF.Berkeley.EDU Subject: Gimp-docs Digest, Vol 71, Issue 1 To: gimp-docs@lists.XCF.Berkeley.EDU Date: Thursday, April 1, 2010, 3:00 PM

Send Gimp-docs mailing list submissions to     gimp-docs@lists.XCF.Berkeley.EDU

To subscribe or unsubscribe via the World Wide Web, visit     https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs or, via email, send a message with subject or body 'help' to     gimp-docs-request@lists.XCF.Berkeley.EDU

You can reach the person managing the list at     gimp-docs-owner@lists.XCF.Berkeley.EDU

When replying, please edit your Subject line so it is more specific than "Re: Contents of Gimp-docs digest..."

Today's Topics:

   1. Re: gimp-help-custom.css (Kolbj?rn Stuest?l)    2. New screenshot guidelines (Ulf-D. Ehlert)    3. Re: New screenshot guidelines (Kolbj?rn Stuest?l)

----------------------------------------------------------------------

Message: 1 Date: Thu, 01 Apr 2010 18:29:51 +0200 From: Kolbj?rn Stuest?l
Subject: Re: [Gimp-docs] gimp-help-custom.css To: GIMP Docs
Message-ID:
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi

It looks like the solution I wanted was already incorporated. Ran "make html-nn" and the file /stylesheets/nn/gimp-help-custom.css was copied to the html folder. Thereafter ran "make html-en" and the file stylesheets/nn/gimp-help-custom.css was not copied. I have not tested it on other languages yet. Sorry for being so incompetent. (But it led to an interesting discussion).

(My internet connection was down today (again), therefore a bit late). Kolbjoern

------------------------------

Message: 2 Date: Thu, 1 Apr 2010 18:33:41 +0200 From: "Ulf-D. Ehlert"
Subject: [Gimp-docs] New screenshot guidelines To: gimp-docs@lists.xcf.berkeley.edu Message-ID:
Content-Type: text/plain; charset="us-ascii"

Hi,

I'm about to work out new screenshot guidelines. In short: new screenshots should look like the fantastic screenshots here:

    http://iwatch.sourceforge.net/screenshots.html

Please study these examples carefully and as soon as possible!

Happy GIMPing! Ulf
-------------- next part -------------- A non-text attachment was scrubbed... Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part. Url : /lists/gimp-docs/attachments/20100401/d7c5d824/attachment-0001.bin

------------------------------

Message: 3 Date: Thu, 01 Apr 2010 18:49:06 +0200 From: Kolbj?rn Stuest?l
Subject: Re: [Gimp-docs] New screenshot guidelines To: GIMP Docs
Message-ID:
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Ulf-D. Ehlert skreiv:

Hi,

I'm about to work out new screenshot guidelines. In short: new screenshots should look like the fantastic screenshots here:

    http://iwatch.sourceforge.net/screenshots.html

Please study these examples carefully and as soon as possible!

Happy GIMPing! Ulf
   

:-D 
I agree, this is an example showing how the screenshots should have been. I can wait until the cat get out of the sack or down from the laptop or whatever to see more from this artist. Nice cat by the way. :-D
Kolbjoern

------------------------------

On Sun, Apr 11, 2010 at 09:02:37AM +0100, Vitaly Lomov wrote:

me too :-) . What tripped me up in the beginning was git. Wrapping my head around it (with all the good help and manuals) took me some time, and every time I had git problem, my enthusiasm cooled down a little. Many a times I just backed up my changed files, deleted the local folder and downloaded the repository from scratch. All the while I wasn't translating. The last thing that did it for me was some .gif image that was originally saved as .GIF then somehow became .gif. Git treated them differently and couldn't commit my changes because one file wasn't there, but the file was there with just a different letter case. I am on windows, where case doesn't matter. Deleting or renaming the files just made matters worse. So, take-away point should be consistent case (i.e. all small) for committed files. My guess is the image was created in Paint, which saves the file with capital case extension.

....

I think move to po was a great idea. But I found editor functionality lacking. Tried poedit and lokalize, decided to use lokalize, which has good translation memory management, but crashes if you sneeze at it. If I spend any of little free time researching other editors, I am not translating. On the contributor page recommended software section would be great.

....

how much time wasted using Windows ... sorry I couldn't resist! ;-)

on the contributor pages is it written that Linux is the dev OS of choice? There are plenty of translation tools po-aware on that OS...

me too :-) . What tripped me up in the beginning was git. Wrapping my

head around it (with all the good help and manuals) took me some time, and every time I had git problem, my enthusiasm cooled down a little. Many a times I just backed up my changed files, deleted the local folder and downloaded the repository from scratch. All the while I wasn't translating.

We migrated from xml to po files to make translator's work easier...

Normally, a translator doesn't use git. He downloads po files from DamnedLies http://l10n.gnome.org. He translates them and checks them with gettext commands and then sends them to his language GNOME maintainer.

Only doc creators need git.

Julien

Hi,

I did use Cygwin and felt difficulty on conflict of file names too. It may be a case insensitivity problem caused by the Windows file system. When I Noticed it on using GIT, I made one more clone repository at another directory. Though it is a fresh tree, an warning message was appear soon. The rebase command doesn't work with an error message. With the stash command, saving can be done successfully, but loading process stops with a reason that the tree is dirty, so this command is also unusable.

After back to FreeBSD system, I tried to remove one of two images and it was easy. Then I created a GIT patch on this commit, and went to apply this diff on the Cygwin's tree. Unfortunately, this patch file is not applicable on Windows file system. Therefore, there is no solution of it for Cygwin users.

I can remove the older file if you need, and I hope this issue is cleared, but perhaps it may cause another unexpected problem on Cygwin.

2010/4/11 Vitaly Lomov :

...snip...
The last thing that did it for me was some .gif image that was originally saved as .GIF then somehow became .gif. Git treated them differently and couldn't commit my changes because one file wasn't there, but the file was there with just a different letter case. I am on windows, where case doesn't matter. Deleting or renaming the files just made matters worse. So, take-away point should be consistent case (i.e. all small) for committed files. My guess is the image was created in Paint, which saves the file with capital case extension.

-=-=-=-=-=
SimaMoto,Ry?Ta
http://code.google.com/p/gimp-doc-ja/

On Sun, Apr 11, 2010 at 09:22:21PM +0200, jhardlin wrote:

me too :-) . What tripped me up in the beginning was git. Wrapping my

head around it (with all the good help and manuals) took me some time, and every time I had git problem, my enthusiasm cooled down a little. Many a times I just backed up my changed files, deleted the local folder and downloaded the repository from scratch. All the while I wasn't translating.

We migrated from xml to po files to make translator's work easier...

Is that a statement, an answer or is there more to say? :)

Normally, a translator doesn't use git. He downloads po files from DamnedLies http://l10n.gnome.org. He translates them and checks them with gettext commands and then sends them to his language GNOME maintainer.

Well put. I remember there was some effort spend for the user manual and it's also listed. What does translators keep from following that way?

Cheers,

We migrated from xml to po files to make translator's work easier...

Is that a statement, an answer or is there more to say? :)

... and we didn't get the wanted result.

Normally, a translator doesn't use git. He downloads po files from DamnedLies http://l10n.gnome.org. He translates them and checks them with gettext commands and then sends them to his language GNOME maintainer.

Well put. I remember there was some effort spend for the user manual and it's also listed. What does translators keep from following that way?

In Damned Lies, you can not send translation directly to the git repository. Your work must be controlled by other translators and approved by the language maintainer. GIMP-HELP is an exception, due to its history. Here, translators are not many, are highly motivated and prefer to have a complete control themselves on their work. Managing git, and using Ulf's improvements, is a challenge for them.

Julien

On Tue, Apr 13, 2010 at 07:43:55AM +0200, jhardlin wrote:

In Damned Lies, you can not send translation directly to the git repository. Your work must be controlled by other translators and approved by the language maintainer.

... and this is currently not possible? Why? Because we're not part of the GNOME i18n teams?

As I understood Damned Lies: There are teams which coordinate the translation for each GNOME package. I guess the gimp user manual forms an exception here. Please correct me if I'm wrong.

GIMP-HELP is an exception, due to its history. Here, translators are not many, are highly motivated and prefer to have a complete control themselves on their work. Managing git, and using Ulf's improvements, is a challenge for them.

Well then I wonder, how can we make it easier and not a challenge ...

Cheers,