View Single Post
Old 08-11-2009, 02:20 PM   #3
Jellby
frumious Bandersnatch
Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.
 
Jellby's Avatar
 
Posts: 7,516
Karma: 18512745
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
Quote:
Originally Posted by kovidgoyal View Post
1. Created by and Whenever you pass now fixed. AUTHORS etc can'tbe fixed for technical reasons (they're in a library used by calibre, not in the calibre code)
Really? It's strange. Some headers (shown in blue in my terminal) are localized (OUTPUT OPTIONS), others aren't (LOOK AND FEEL). As for the option values (in green), since some of them look specific for Calibre (--page-breaks-before=PAGE_BREAKS_BEFORE) I'd guess the uppercase part is auto-generated from the option name, in lower case. But you know better than I how it works

Quote:
2. Not sure what you mean? You mean you put & into the Spanish strings when they weren't in the English strings? That wont work. I've now added the & to the English strings so it should be fine in the next release.
Yes, that's what I did, because first I translated the strings without any & and then I added the &s while looking at the dialogs, to avoid hotkeys conflicting. In some cases I see I've added & when there was none in the English strings (so hotkeys didn't work there), the result is hotkeys still don't work and the strings with & are rendered verbatim, and not with the letter after & underlined, as intended. Thanks for fixing it

Quote:
3. Difficult to do since I have no real fixed pattern for calibre releases. Basically whenever I encounter a critical bug or I feel that a lot of new minor bugs/features have been fixed/implemented, I go ahead and make a release.
I understand that. What I was thinking is maybe making the strings available for translation at launchpad one or two days before the release (which in practice means delaying the relase one or two days ). Or perhaps "exporting" them more in real time, and not only when a new release is ready, so that when the release comes out, some new strings might already be translated. Yet another possibility could be upgrading a release with new translations as soon as they are available (I mean, when they reach 100%), without really changing the version, just the strings.

I admit I don't really know how the Calibre source code and the translations at launchpad are interconnected, though, so the above might all be nonsense
Jellby is offline   Reply With Quote