French Translation

Great, thank you very much!

There's one translation that jumped into my eyes:

As soon as possible => Immediatement

This is not correct. The emails are sent by cron, and if cron is set to run every hour, it can take that long. It's the admin's call how he wants to design the intervalls, but clearly there's no option "Immediately". Maybe

Le plus vite possible
?

(You don't need to resubmit the file, I can change that easily here.)

Hi,

Yeah, I hesitated over that one and I realize it's not an exact translation. I figured anybody who wanted their notifications ASAP would set their cron job to fire every few minutes! But, if you want a more faithful translation, then 'Dès que possible' is probably better.

Matthew

Ok, committed to 5.x-2.x-dev.

Thanks again!

Le plus vite possible

Hi! A more correct translation would be: "Le plus tôt possible".

It went in as 'Dès que possible'.

Thanks.

Hi,

I should probably point out that, while I live and work in France (which is why I needed the translation) I am a native English speaker so, while I think the translation is pretty good, I make no claims of it being perfect French. Anyway, now that it's in CVS, anybody is welcome to download it and resubmit an improved version.

Thanks again for a very useful module.

Mat

Automatically closed -- issue fixed for two weeks with no activity.

Now would be a good time to update the translation for D6. I've taken care to update the D5 version along with the D6 version wherever possible, so a D6 translation should work quite well for the current D5 version, too.

(Whoever wants to work on it, please assign yourself, to avoid having more than one person doing duplicate work.)

Hi,

OK, now that I've worked out how to merge the new .pot file into the previous translation, so that I can see which strings have been added or updated, I'll have a bash at this. Prod me if you don't hear anything for a while!

Hi,

OK French .po file attached for the D6 version. Hope it's all OK. There were a couple of phrases I hesitated over, but I figure it's best to send it in and see if anybody wants to improve it.

Thank you very much!

I'd like to discuss the following:
I added   to "On updates" and "On comments" to keep them on one line, because wrapping saves little space and it looks ugly. However, "Lors de mises à jour" and "Lors de commentaires" are much longer, and I'm afraid that they increase the table widths too much. What do you think?

I've just changed "Pages" (the label of user/UID/subscriptions/node) to "Pages/Threads". Would "Pages/Fils de discussion" be correct?

There are four other new strings (only visible to the administrator) — sorry...

1. Hide the %Overview page from your users
2. If you hide this page, your users won't be able to change any of these settings. The default is OFF.
3. The list of attached files, one per line, if any, otherwise empty.
4. Note: 'new' and 'update' notifications for %Pages subscriptions use the matching !content_type subscriptions template rather than this one, if allowed; this does not apply to 'comment'-only notifications.

I updated your file to the latest .pot and committed it. Marking NW for the four strings above. Can you give me the translations of those (or get the updated fr.po and put them in there)?

Hi,

Time's a bit tight at the moment to download and edit the .pot - so hope this is OK. I don't have the module installed on a site at the moment (I guess I should, really) so it's not easy to visualize exactly, but I wonder whether you could split the text between the table cells and header, so that it would be something like:

Notifications lors de:
- mises à jour
- commentaires

... which might stop the table cells expanding.

As for the other strings:

1. Cachez la page %Overview de vos utilisateurs

2. (Assuming 'The default is OFF' means 'by default page IS visible')
Par défaut cette page est visible; si vous la cachez, vos utilisateurs ne pourraient modifier aucune de ces options.

3. La liste des fichiers liés - une par ligne, sinon vide.

4. NB: Si autorisé, les notifications de contenu nouveau, ou mise à jour, pour les abonnements aux %Pages utilisent la masque !content_type subscriptions correspondante plutôt que celle-ci; Notifications de commentaires uniquement ne sont pas concernées.

and I just spotted a typo (sorry!) in the previous .pot:
(requires !mail_edit for customizing the templates) should be -> (nécessite !mail_edit pour adapter les masques)

Thank you for the new translations and the correction, I can put them in, no problem.

On the nodes form it's no big deal if the titles are wider (although it doesn't look very nice), but on the Pages form space is very tight. I don't know how to associate text with a checkbox inside a table, and I'm not sure it would be a good idea.

How about

Lors de
mises à jour

and

Lors de
commentaires

?

I don't think it would be wise to force text next to checkboxes in the tables.

As for table headers, it is expected that long titles will wrap on multiple lines; look at the column titled: "Latest activity, authored, commented". So French translation string that get longer, here on the page form, will wrap accordingly.

That being said, I agree completely with the two translations: "Lors de mises à jour" and "Lors de commentaires". :-)

Hi,

Thanks for doing those screen grabs - I see what you mean now. I guess the text will have to wrap, until CSS lets you rotate the text 45 degrees to gain some horizontal space like you might do on a printed table! If space gets really tight, maybe the table headers could be displayed as icons with descriptive title text shown on rollover, but that opens up a debate about whether that enhances or reduces usability...

I was thinking about whether there should be some non-breaking spaces in 'mises à jour' to keep it together, but that would prevent the table cell shrinking and, to be honest, I'm not sure what the typographical rules are for phrases like that anyway (I used to date a French woman who did proofreading for a living - shame she's not around right now!), so maybe it's best to let the browser sort out the wrapping.

I am French, although not a woman. :-)

Yes, it is best to let out the browser do the wrapping here.

Well, at the extreme, the browser might give us 5 lines, like

Lors
de
mises
à
jour

So, I'm proposing Lors de mises à jour. That way, the browser can only break once at most.

Well, at the extreme you will get :

Latest
activity,
authored,
commented

On last column, four lines instead of two. And that not speaking about the French translation.

This argument does not take the road. :-)

Actually no. Try it...

Ça y est, c'est parti. Merci!

Automatically closed -- issue fixed for 2 weeks with no activity.