Wie TV-Sportlern wahrscheinlich bereits aufgefallen ist, verwenden deutsche Sportreporter seit einiger Zeit den Ausruf à la bonne heure!, häufig auch: Chapeau! À la bonne heure! (Eventuell auch: À la bonheur!)

Wie es dazu kam, was der Ausdruck im Französischen und im Deutschen (vielleicht) bedeutet, wie er zu übersetzen ist - diesen Fragen ist Creative Translations für Sie nachgegangen:

1. Vermutete Entstehungsgeschichte
Nachdem seit ungefähr 2003 die Ausrufe Chapeau! und Chapeau bas! zunächst während der Tour de France, dann auch bei Sportarten ohne direkten Frankreichbezug nicht mehr ins Deutsche übersetzt worden waren, hatten sie sich im Jahr 2005 abgenutzt und mussten durch einen weiteren französischen Begriff verstärkt werden. Die Wahl fiel auf à la bonne heure!

2. Bedeutung im Französischen
Im Französischen bedeutet à la bonne heure! einfach nur rechtzeitig und wird meistens sogar abwertend im Sinne von endlich, das war höchste Zeit! verwendet.

3. Bedeutung im Deutschen
Die Bedeutung von à la bonne heure! im Deutschen konnte bisher nicht vollständig geklärt werden. Es handelt sich jedoch um einen Ausruf der Anerkennung.

4. Übersetzung
Vom Französischen ins Deutsche: rechtzeitig oder endlich.
Bei der Übersetzung vom Deutschen ins Französische sind zwei Fälle zu unterscheiden:
- Steht à la bonne heure! im Deutschen alleine, rät Creative Translations zu Chapeau! oder Chapeau bas!
- Wird à la bonne heure! im Deutschen zusammen mit Chapeau! verwendet (also: “Chapeau! À la bonne heure!“), empfehlen wir:

“Oh là là là là là là là là là là là là là là!”

mit freundlicher Genehmigung von creative-translations

Romanverfilmung von und mit George Clooney. Machenschaften des CIA mit Nebenwirkungen.

Handlung

Bob hat als CIA-Agent schon bessere Tage gesehen, es scheint alles an ihm vorbeit zu laufen. Seine Vorgesetzten begegnen ihm mit Misstrauen und geben ihm nur widerwillig einen neuen Auftrag. Der Film hat zwei Nebenhandlungen: Matt Demon als engagierter Berater und die Rekrutierung von Selbstmordattentätern.

Warum sollte man den Film sehen?

Wegen George Clooney.

Was nervt?

Die Nebenhandlungen stören eher und ziehen den Film in die Länge, dadurch leidet die Kohärenz der Story. Weniger wäre mehr gewesen. Der Film schafft es nie die Breite der Themen auszuschöpfen, alles bleibt fragmentarisch.

Once upon a time the was a search engine called Google. It had been a friendly search-machine and everyone liked it - not everyone of course , there was this nasty Giant of Redmond that was feared by everyone but also disliked by everyone.

End of the fairy-tale.

Google wants to make more money and “the next big thing” is localized services - if one believes the web to-point-”Ohh!” evangelist - formerly knows as the guys who didn’t get a word a Starbuck’s right and used them as brand names instead - who needs vowels, especially the ‘e’ is largely overrated (See G. Perec La disparition /A Void).
No google.de etc. are fully localized (to target you with more adspam). Also they provide more top-listed sites (It depends which google you talk about)… If I had the choice, they can do so, but what really bothers me is that it ignores whenI search with english or french terms: I still get only german pages… unless NO pages exists in german on the topic. Even if there is a single hit in german all other 200.000.000 hits are ignored…

Don’t say that I have to change my language preferences - they don’t have any effect on that: If you search you have to know now the language domain you want to investigate. My girl-friend is completly fucked: She mainly works translating french texts and when I say french I mean texts in french from France. Sadly Google now prefers Canada (Blame Canada!)…
Well perhaps they’ll improve on that, but actually it is a loss. All google sites looked the same because they were merely portals to the world’s information. The “global village” was too “.” O tied to Google to keep it connected. Now we go back to some regions (and some white(?) spots).
I have nothing against translations and reasonably ranked content, but I don’t like to revise all the weeks if I can still trust my dictionary. The rules must be transparent. The google-quirk can be circumvented (when using english) by querying google.com, but IBM and (guess who?) Microsoft made it worse: They use your IP-address to redirected you to localized content. This is very useful when you are in France and french is your third language (or 5th, 6th if computer languages count). At Microsoft it is just a bit annoying, but there is always the link to the translation (and the (english) original) on the same page and when you navigated a local site you won’t be dispatched without any notice while browsing it (I don’t except nobody to translate any bit of information immediately). IBM nows better: The transferred their mainframe-attitude to the 21st century. You can change your preferences, but you have to navigate away from the current page and you’ll never find the desired content…

So, it seems that it works.
I used the JdbcsRealm from the glassfish bug.parade (written by bjb), tweaked a bit antlr, etc and I can show my blogs. But not for long. After 8 or so calls the server hangs - perhaps it has something to do with the encoding handling or whatever.
Deploying on an appserver became more complicated that making C-code going on UNIX. Tomcat/MySQL define the “Windows” here: Everything works (somehow, not as expected) and glassfish reminds my here of the the early UNIX: The aimed for MULTICS, but ran out of money. ClassLoader-problems - library conflicts strange interdependencies between Security-Layers - give me a break. This stuff sucks. Perhaps it is Roller’s fault and I should have tried something other before (I did, and all worked fine). The point is that you have to “buy” a new appserver for a new app, while keeping the old one for the existing ones.
Sounds familiar? Yes this is what we all laughed about about in stories like when Microsoft was an airline, etc.
Same thing with “browsers-based”. I spoiled some weekends to make a simple site look right in different browsers. After getting it right (with some dirty tricks) on Firefox, Opera and IE6&7 I learned that Safari had another understanding (after reading the specs I have to admit that all other browser seem to get it wrong there).
To sum up I’d say that computing actually got fucked up during the last 10 years.
BTW: Does anyone still remember XWindows? If think implemented the todays needs very nicely
PS: I beg for an excuse that I didn’t spice up this post with some links, see next post for the reason of this

Arghs.
This was a stupid one. Running roller on Oracle (9.2) is actually not as difficult as it seems:

1. org.hibernate.dialect.Oracle9Dialect in hibernate.cf.xml
2. Make the Realm connected to your oracle-DB:

<realm classname=”org.apache.catalina.realm.JDBCRealm” debug=”99″ drivername=”oracle.jdbc.driver.OracleDriver” connectionname=”roller” connectionpassword=”roller” connectionurl=”jdbc:oracle:thin:@lxoracle:1521:devlpt” usertable=”rolleruser” usernamecol=”username” usercredcol=”passphrase” userroletable=”userrole” rolenamecol=”rolename”> </realm>

3. For a true transactional DB:
   <parameter><name>defaultAutoCommit</name>
   <value>false</value>
   </parameter> (otherwise the BasicDataSourceFactory’s default enforces autocommit.

Not that this will only work with the new Oracle-drivers ojdbc14.jar for Oracle 10g! The older version cannot handle CLOBs as Strings and so the hibernate-mapping for the roller_properties is wrong.
Next thing to do: Get this also going on a Mustang/Glassfish. (There is a nice description which just misses that WEBLOGENTRY.pubtime must be nullable)