Quick reply because I don't have time to commit, and it'll be useful for translators to at least have some answers.

(In reply to comment #0)
> i wonder about many strings in libwnck and how to translate them properly/if
> they should be marked for translation.
> yes, i did take a look at the translations of metacity and gnome-panel before.
> :)
> 
> 
> "viewport" is a very techie term. i found it in a tech dic, but a "translators:
> 'viewport' is the area that one can see" would be cooler.

Nod. It might also be useful to explain that viewport can be used to implement workspace (and give compiz as example).

> 
> "set"
> "<unset>"
> "<name unset>"
> are these verbs or adjectives?

It's "adjective" as in "the name is unset". It's not an adjective, but a past form or something like this (don't ask me about how this is called ;-))

> "number" sometimes means one number (e.g. the number of the workspace), and
> sometimes means "amount" (like in "Number of Windows:"). it can be confusing, i
> hope i did it right.

Do you think comments would help? I don't find this confusing, but, well, I wrote the strings ;-)

> 
> "%1$s%2$s%3$s" and ","
> i still don't get these ones. what the hell is the usecase here? :)

I explained to Andre on IRC. Maybe giving an example on how this can be useful (like to get "c:b:a" instead of "a, b, c") would help.

> what are "pagers" (several times), and how can i translate this properly?

A pager is the technical term for the workspace switcher. It's a representation of all workspaces with windows inside it.

> "tasklist" - is this the list of running applications? because "tasks" means
> something totally different in evolution, you know, and the transation would
> also be very different... ;-)

Yes. That's the window list, but again, it's the technical term for this :-)

> "class group" - what is a "class" here? and a "class leader"?
> also "ressource class"

Heh. Hard to explain. A class is like a "family". All gvim windows are of the same class.

A group leader is the window that is the "owner" of a group of windows, ie: if you have multiple windows in one application, one window has some information about the application (like the application name).

"Resource class" is the name used to identify a class.

> "Transient for: %lu\n"
> i know what transient means, but what's the context here?!

A window can be transient for another window: it means it's on top of it and it has the focus instead of the other window.

> "make above"
> "make below"
> does this once again refer to the window positions and whether to put the
> windows above/below the other ones?

Yes.

> i also have problems to perfectly translate "pin" and "stick".

Basically, the end result is the same, but it's a bit different in the implementation: you use stick when you use a viewport (compiz) and pin when you use virtual desktops (metacity). So, stick means the window always have the same position on the viewport while pin means the window is on all virtual desktops.

One or two random comments and clarifications...

> > "viewport" is a very techie term. i found it in a tech dic, but a "translators:
> > 'viewport' is the area that one can see" would be cooler.
> 
> Nod. It might also be useful to explain that viewport can be used to implement
> workspace (and give compiz as example).

Yeah, viewport is going to be hard to translate given that metacity doesn't use no stinkin' viewports (nor does Kwin, IIRC), and therefore many users will be unfamiliar with their behavior.  Andre's summary, 'the area that one can see', can be misinterpreted as well ("oh, that's just my current workspace?" -- that's only an accurate meaning for compiz's viewports...).

> A window can be transient for another window: it means it's on top of it and
> it has the focus instead of the other window.

on top, yes.  focus instead of -- no (at least not with any window manager I'm aware of; I guess one could implement that).  There are often dialogs (dialogs are the most common case of transients) that are showing but allow the user to interact with the main window.  If the dialog always has focus while showing and the user can't interact with the main app, then the dialog is also modal.  transiency does not imply modality.

> > i also have problems to perfectly translate "pin" and "stick".
> 
> Basically, the end result is the same, but it's a bit different in the
> implementation: you use stick when you use a viewport (compiz) and pin when
> you use virtual desktops (metacity). So, stick means the window always have
> the same position on the viewport while pin means the window is on all
> virtual desktops.

Well...the end result isn't always the same.  If you allow viewports to be shifted in smaller increments, then the result is a bit different.  Compiz (last I heard) basically only shifts by amounts equal to the monitor resolution (which is why their implementation makes viewports so similar to workspaces), but other window managers (e.g. sawfish, vtwm...) would allow the user to shift by any arbitrary pixel amount.  Displaying parts of multiple adjacent workareas in a way that tries to make it look like the viewport *is* a normal workarea is rather annoying.

In the general case of viewports, libwnck 'stick' means roughly 'stuck to the glass' -- a shift of viewport causes normal windows to shift relative to the change in viewport, but a 'sticky' window's coordinates will shift to keep the window from moving when the viewport does.

Also, the pin/stick wording in libwnck also sucks, because metacity and lots of other places use 'stick' to mean what libwnck's 'pin' means.


I haven't looked closely at the new wnckprop.c file; so maybe this is obvious and I just need to take a look to find out, but does all this stuff really need to be translated?

minefields...
thanks pals, will try to commit some translator comments and announce that to i18n ml within the next hours.

(In reply to comment #2)
> One or two random comments and clarifications...

Thanks :-)

> I haven't looked closely at the new wnckprop.c file; so maybe this is obvious
> and I just need to take a look to find out, but does all this stuff really need
> to be translated?

Well, it doesn't *need* to be translated, but I thought it'd be nice to have the tool in your language. It's a command line tool, so it's clearly low-priority.

Created attachment 94065 [details] [review]
patch to add translator comments

sent an email to gnome-i18n; closing as fixed