Developping for the translation industry RSS 2.0



 Tuesday, 04 May 2010

Some people are really language gymnasts. Georges Perec, who could write a whole 300 pages novel without ever using the letter e, also wrote a palindrome of more than 6000 characters. At the time of this writing, it can also be found at http://graner.net/nicolas/salocin/ten.renarg//:ptth (which is, of course, a palindromic URL, in case you did not notice). This is the palindrome in French. Enjoy:

Trace l'inégal palindrome. Neige. Bagatelle, dira Hercule. Le brut repentir, cet écrit né Perec. L'arc lu pèse trop, lis à vice versa.

Perte. Cerise d'une vérité banale, le Malstrom, Alep, mort édulcoré, crêpe porté de ce désir brisé d'un iota. Livre si aboli, tes sacres ont éreinté, cor cruel, nos albatros. Être las, autel bâti, miette vice versa du jeu que fit, nacré, médical, le sélénite relaps, ellipsoïdal.

Ivre il bat, la turbine bat, l'isolé me ravale : le verre si obéi du Pernod -- eh, port su ! -- obsédante sonate teintée d'ivresse.

Ce rêve se mit -- peste ! -- à blaguer. Beh ! L'art sec n'a si peu qu'algèbre s'élabore de l'or évalué. Idiome étiré, hésite, bâtard replié, l'os nu. Si, à la gêne secrète -- verbe nul à l'instar de cinq occis --, rets amincis, drailles inégales, il, avatar espacé, caresse ce noir Belzebuth, oeil offensé, tire !

L'écho fit (à désert) : Salut, sang, robe et été.

Fièvres.

Adam, rauque ; il écrit : Abrupt ogre, eh, cercueil, l'avenir tu, effilé, génial à la rue (murmure sud eu ne tire vaseline séparée ; l'épeire gelée rode : Hep, mortel ?) lia ta balafre native.

Litige. Regagner (et ne m'...).

Ressac. Il frémit, se sape, na ! Eh, cavale ! Timide, il nia ce sursaut.

Hasard repu, tel, le magicien à morte me lit. Un ignare le rapsode, lacs ému, mixa, mêla : Hep, Oceano Nox, ô, béchamel azur ! Éjaculer ! Topaze !

Le cèdre, malabar faible, Arsinoë le macule, mante ivre, glauque, pis, l'air atone (sic). Art sournois : si, médicinale, l'autre glace (Melba ?) l'un ? N'alertai ni pollen (retêter : gercé, repu, denté...) ni tobacco.

Tu, désir, brio rimé, eh, prolixe nécrophore, tu ferres l'avenir velu, ocre, cromant-né ?

Rage, l'ara. Veuglaire. Sedan, tes elzévirs t'obsèdent. Romain ? Exact. Et Nemrod selle ses Samson !

Et nier téocalli ?

Cave canem (car ce nu trop minois -- rembuscade d'éruptives à babil -- admonesta, fil accru, Têtebleu ! qu'Ariane évitât net. Attention, ébénier factice, ressorti du réel. Ci-gît. Alpaga, gnôme, le héros se lamente, trompé, chocolat : ce laid totem, ord, nil aplati, rituel biscornu ; ce sacré bedeau (quel bât ce Jésus !). Palace piégé, Torpédo drue si à fellah tôt ne peut ni le Big à ruer bezef.

L'eugéniste en rut consuma d'art son épi d'éolienne ici rot (eh... rut ?). Toi, d'idem gin, élèvera, élu, bifocal, l'ithos et notre pathos à la hauteur de sec salamalec ?

Élucider. Ion éclaté : Elle ? Tenu. Etna but (item mal famé), degré vide, julep : macédoine d'axiomes, sac semé d'École, véniel, ah, le verbe enivré (ne sucer ni arrêter, eh ça jamais !) lu n'abolira le hasard ?

Nu, ottoman à écho, l'art su, oh, tara zéro, belle Deborah, ô, sacre ! Pute, vertubleu, qualité si vertu à la part tarifé (décalitres ?) et nul n'a lu trop s'il séria de ce basilic Iseut.

Il à prié bonzes, Samaritain, Tora, vilains monstres (idolâtre DNA en sus) rêvés, évaporés : Arbalète (bètes) en noce du Tell ivre-mort, émeri tu : O, trapu à elfe, il lie l'os, il lia jérémiade lucide. Pétard ! Rate ta reinette, bigleur cruel, non à ce lot ! Si, farcis-toi dito le coeur !

Lied à monstre velu, ange ni bête, sec à pseudo délire : Tsarine (sellée, là), Cid, Arétin, abruti de Ninive, Déjanire...

Le Phenix, ève de sables, écarté, ne peut égarer racines radiales en mana : l'Oubli, fétiche en argile.

Foudre.

Prix : Ile de la Gorgone en roc, et, ô, Licorne écartelée, Sirène, rumb à bannir à ma (Red n'osa) niére de mimosa : Paysage d'Ourcq ocre sous ive d'écale ; Volcan. Roc : tarot célé du Père.

Livres.

Silène bavard, replié sur sa nullité (nu à je) belge : ipséité banale. L' (eh, ça !) hydromel à ri, psaltérion. Errée Lorelei...

Fi ! Marmelade déviré d'Aladine. D'or, Noël : crèche (l'an ici taverne gelée dès bol...) à santon givré, fi !, culé de l'âne vairon.

Lapalisse élu, gnoses sans orgueil (écru, sale, sec). Saluts : angiome. T'es si crâneur !

* * *

Rue. Narcisse ! Témoignas-tu ! l'ascèse, là, sur ce lieu gros, nasses ongulées...

S'il a pal, noria vénale de Lucifer, vignot nasal (obsédée, le genre vaticinal), eh, Cercle, on rode, nid à la dérive, Dèdale (M... !) ramifié ?

Le rôle erre, noir, et la spirale mord, y hache l'élan abêti : Espiègle (béjaune) Till : un as rusé.

Il perdra. Va bene.

Lis, servile repu d'électorat, cornac, Lovelace. De visu, oser ?

Coq cru, ô, Degas, y'a pas, ô mime, de rein à sonder : à marin nabab, murène risée.

Le trace en roc, ilote cornéen.

O, grog, ale d'elixir perdu, ô, feligrane ! Eh, cité, fil bu ! ô ! l'anamnèse, lai d'arsenic, arrérage tué, pénétra ce sel-base de Vexin. Eh, pèlerin à (Je : devin inédit) urbanité radicale (elle s'en ira...), stérile, dodu.

Espaces (été biné ? gnaule ?) verts.

Nomade, il rue, ocelot. Idiot-sic rafistolé : canon ! Leur cruel gibet te niera, têtard raté, pédicule d'aimé rejailli.

Soleil lie, fléau, partout ire (Métro, Mer, Ville...) tu déconnes. Été : bètel à brasero. Pavese versus Neandertal ! O, diserts noms ni à Livarot ni à Tir ! Amassez.

N'obéir.

Pali, tu es ici : lis abécédaires, lis portulan : l'un te sert-il ? à ce défi rattrapa l'autre ? Vise-t-il auquel but rêvé tu perças ?

Oh, arobe d'ellébore, Zarathoustra ! L'ohcéan à mot (Toundra ? Sahel ?) à ri : Lob à nul si à ma jachère, terrain récusé, nervi, née brève l'haleine véloce de mes casse-moix à (Déni, ô !) décampé.

Lu, je diverge de ma flamme titubante : une telle (étal, ce noir édicule cela mal) ascèse drue tua, ha, l'As.

Oh, taper ! Tontes ! Oh, tillac, ô, fibule à reve l'Énigme (d'idiot tu) rhétoricienne.

Il, Oedipe, Nostradamus nocturne et, si né Guelfe, zébreur à Gibelin tué (pentothal ?), le faiseur d'ode protège.

Ipéca... : lapsus.

Eject à bleu qu'aède berça sec. Un roc si bleu ! Tir. ital. : palindrome tôt dialectal. Oc ? Oh, cep mort et né, mal essoré, hélé. Mon gag aplati gicle. Érudit rossérecit, ça freine, benoit, net.

Ta tentative en air auquel bète, turc, califat se (nom d'Ali-Baba !) sévit, pure de -- d'ac ? -- submersion importune, crac, menace, vacilla, co-étreinte...

Nos masses, elles dorment ? Etc... Axé ni à mort-né des bots. Rivez ! Les Etna de Serial-Guevara l'égarent. N'amorcer coulevrine.

Valser. Refuter.

Oh, porc en exil (Orphée), miroir brisé du toc cabotin et né du Perec : Regret éternel. L'opiniâtre. L'annulable.

Mec, Alger tua l'élan ici démission. Ru ostracisé, notarial, si peu qu'Alger, Viet-Nam (élu caméléon !), Israël, Biafra, bal à merde : celez, apôtre Luc à Jéruzalem, ah ce boxon ! On à écopé, ha, le maximum

Escale d'os, pare le rang inutile. Métromane ici gamelle, tu perdras. Ah, tu as rusé ! Cain ! Lied imité la vache (à ne pas estimer) (flic assermenté, rengagé) régit.

Il évita, nerf à la bataille trompé.

Hé, dorée, l'Égérie pelée rape, sénile, sa vérité nue du sérum : rumeur à la laine, gel, if, feutrine, val, lieu-créche, ergot, pur, Bâtir ce lieu qu'Armada serve : if étété, éborgnas-tu l'astre sédatif ?

Oh, célérités ! Nef ! Folie ! Oh, tubez ! Le brio ne cessera, ce cap sera ta valise ; l'âge : ni sel-liard (sic) ni master-(sic)-coq, ni cédrats, ni la lune brève. Tercé, sénégalais, un soleil perdra ta bétise héritée (Moi-Dieu, la vérole !)

Déroba le serbe glauque, pis, ancestral, hébreu (Galba et Septime-Sévère). Cesser, vidé et nié. Tetanos. Etna dès boustrophédon répudié. Boiser. Révèle l'avare mélo, s'il t'a béni, brutal tablier vil. Adios. Pilles, pale rétine, le sel, l'acide mercanti. Feu que Judas rêve, civette imitable, tu as alerté, sort à blason, leur croc. Et nier et n'oser. Casse-t-il, ô, baiser vil ? à toi, nu désir brisé, décédé, trope percé, roc lu. Détrompe la. Morts : l'Ame, l'Élan abêti, revenu.

Désire ce trépas rêvé : Ci va ! S'il porte, sépulcral, ce repentir, cet écrit ne perturbe le lucre : Haridelle, ta gabegie ne mord ni la plage ni l'écart.

 

Great stuff!

 

Other posts:

Once in a while, stop and pay attention...

List of Crazy Laws in the United States

SQL Injection humor

Facts and Figures about the Language Industry

Tuesday, 04 May 2010 14:25:37 (Eastern Standard Time, UTC-05:00)  #    Comments [0] -
General
 Friday, 19 March 2010
Some people don’t like the idea of Google having any data about them. Unfortunately, if you visit a site tracked by Google Analytics (and chances are you hit several each day), you have no choice. But soon, you might.

Google is testing a browser-based opt-out solution for Google Analytics, they briefly note today on the Google Analytics blog. Specifically, this would be a “global browser based plug-in to allow users to opt out of being tracked by Google Analytics.” They note that engineers are finalizing and testing the funtionality.

How exactly this will work globally across all browsers remains to be seen. While Firefox and Chrome allow for easy use of plug-ins, Internet Exploerer and Safari are a bit more complicated. Still, if you’re a user who really cares about Google not tracking this information about you, it will probably be worth it to you to install this thing.

Of course, the other question is what this means for site owners. While it’s unlikely that a lot of users would install something like this, what if they did? That could drastically cripple the entire point of Google Analytics.

Source: Techcrunch

Other posts:

Big news in security: 1024-bit RSA encryption cracked

US Investigators Pinpoint Author Of Google Attack Code

Google Translator Hacked

How to use the Robots.txt file

Friday, 19 March 2010 08:16:00 (Eastern Standard Time, UTC-05:00)  #    Comments [0] -
News
 Thursday, 18 March 2010
InnovationHere are some tips to spot people who are likely innovators.  In this way, you can identify them more quickly, and choose to hire them if you want to be more innovative, or you can ignore and avoid them if the status quo is more your thing.  Good luck with that strategy, by the way.

Identifying people who are innovators is actually relatively easy.  They are the ones who don't actually seem to belong the organization in the first place.

Innovators tend to:

  1. Reject the standard framing of a problem and restate the problem or opportunity.  Rather than work within the given constructs or framing, many innovators want to toss out the framing and start anew.  Just like Galileo, this may require working against an orthodoxy, yet nonetheless, it moves and so must we.  Those folks who are so problematic about wanting to change or expand the framing of a problem?  Probably good innovators.
  2. Be optimistic.  They are almost always the glass half full people.  Pessimistic people will focus far too much energy on the "problem" while innovators will acknowledge the problem and move on to find interesting solutions.  They believe the problems are merely temporary barriers to more interesting solutions.
  3. Look to the future for signals rather than to the past.  In most businesses, many people will ask "has this been done before" and "what can we learn from that success or failure.  Innovators want to know "can we be the first" and what signals in the market or environment give us indications that we'll be successful
  4. Care about solving unmet or poorly understood challenges.  Often innovators are going beyond the obvious, ordinary problems to uncover deeper unmet or poorly understood issues.  If your team is captivated by solving an obvious and incremental problem, they aren't innovators.
  5. Network with people different than they are.  Evidence suggests that the best innovators are people who read outside of their industry, interact with people from many different backgrounds and interests and seek to bring solutions from outside their industry to the table.  People who are very deep in one industry but ignore signals and solutions from other industries are usually not very innovative.
  6. Are proactive.  Innovators actively seek change while many executives are content to wait and react to what other firms do.
  7. Are dissatisfied with the status quo and willing to change it rather than simply accept the status quo and merely complain.
  8. Are very comfortable learning, trying and failing, and then trying again.  They aren't stymied by a single failure and are usually very determined to start again, reframe the problem and try a new tack or approach, learning from previous failures and incorporating that knowledge.
So, if you are in the market to hire someone and want to know if he or she is likely to be an innovator, look for these signs:

  • Ask them about an existing problem that you have.  See if they are perfectly willing to accept your framing, or if they request the opportunity to reframe or change the frame entirely.  If the latter, a likely innovator.
  • Ask them about existing societal problems or corporate problems or challenges.  Listen to how they approach the problem and their willingness to suggest changes or alternatives and the possibilities they suggest for change.
  • In the context of a problem, what information do they seek - external, future oriented or internal information about the past?
  • Can they name a big failure in their lives and demonstrate what they learned and how that failure helped them gain more insight into an eventual solution?
  • Can they name five people in relatively senior positions they interact with on a regular basis who are from different industries?  Can they demonstrate an active network outside of their "home" industry?

The kinds of answers you get with these questions will tell you how strong the "innovation" force is within the candidate, and whether you should hire that person or turn the Force against them.

Photo source: vermininc

 

Other posts:

Once in a while, stop and pay attention...

Meetings

What Are Customers Saying About You Online?

Hiring and managing geeks

Thursday, 18 March 2010 10:48:53 (Eastern Standard Time, UTC-05:00)  #    Comments [0] -
Hiring | Management
 Wednesday, 10 March 2010

First off: no, it’s not a joke! April 1st is in three weeks.

Since 1977, RSA public-key encryption has protected privacy and verified authenticity when using computers, gadgets and web browsers around the globe. Only the most brutish of brute force efforts (and 1,500 years of processing time) could manage to bypass its 768-bit variety.

Now, three eggheads (or Wolverines, as it were) at the University of Michigan claim they can break it simply by tweaking a device's power supply. By fluctuating the voltage to the CPU such that it generated a single hardware error per clock cycle, they found that they could cause the server to flip single bits of the private key at a time, allowing them to slowly piece together the password. With a small cluster of 81 Pentium 4 chips and 104 hours of processing time, they were able to successfully hack 1024-bit encryption in OpenSSL on a SPARC-based system, without damaging the computer. That's why they're presenting a paper at the Design, Automation and Test conference this week in Europe, and that's why -- until RSA hopefully fixes the flaw -- you should keep a very close eye on your server room's power supply.

From the article on techworld:

RSA authentication is susceptible, they say, to changes in the voltage supply to a private key holder. The researchers – Andrea Pellegrini, Valeria Bertacco and Todd Austin - outline their findings in a paper titled “Fault-based attack of RSA authentication”  to be presented 10 March at the Design, Automation and Test in Europe conference.

Quite scary…

 

Other posts:

US Investigators Pinpoint Author Of Google Attack Code

Google Translator Hacked

What is LDAP injection?

Tips to enhance your SQL Server security

Password aren't a good defense?

Wednesday, 10 March 2010 09:32:52 (Eastern Standard Time, UTC-05:00)  #    Comments [0] -
News | Security
 Wednesday, 24 February 2010

The SQL Server functions ISNULL and COALESCE seem to occupy the same space in terms of functionality. The only difference is that ISNULL is restricted to only two parameters, while COALESCE can take any number of parameters. So why ever use ISNULL?

First of all, the simple answer for why to prefer ISNULL over COALESCE when given the choice is that ISNULL tends to produce query plans that are more efficient than COALESCE's. Examine the query plans for the two queries given below to see the difference:

SELECT a.au_id, 
       Isnull
((SELECT price
               FROM   titles
               WHERE  title_id = ta.title_id),0)
FROM   authors a
       JOIN titleauthor ta
         ON a.au_id = ta.au_id

————————————

SELECT a.au_id, 
       Coalesce((SELECT price
                 FROM   titles
                 WHERE  title_id = ta.title_id),0)
FROM   authors a
       JOIN titleauthor ta
         ON a.au_id = ta.au_id

The first query uses one less nested loop in it’s execution plan than the second, resulting in a lower overall cost. Note that I would never recommend writing queries that nest subqueries within functions. This example was only intended to show you the difference between the two generated execution plans, not to recommend a certain T-SQL coding style.

The other bit that most people don't know about ISNULL and COALESCE is that the return data type for ISNULL is guaranteed to be the same as the data type of the first parameter. However, the return data type of COALESCE is determined by data type precedence rules (see the Books Online topic "Data Type Precedence"). Therefore, the following queries will produce two different outputs:

DECLARE  @Example CHAR(2)
SET @Example = NULL

SELECT Isnull(@Example,'abcde'),
       Coalesce(@Example,'abcde')

In this example, the first expression using ISNULL will return 'ab', which is the declared datatype of the first parameter, a char(2). The second expression using COALESCE will return the highest precedence data type, which is the longer string 'abcde.'

To summarize:

  • When you only need to coalesce two arguments, use ISNULL instead because it performs better.
  • When using COALESCE, you may want to use explicit casting to ensure you get a consistent return data type.

Other posts:

5 ways to generate random numbers with a T-SQL query

How to remove leading zeros from the results of an SQL Query

How to get the list of object modifications in SQL Server

How to use derived tables to boost SQL performance

Good Joke on SQL Injection

Wednesday, 24 February 2010 10:15:13 (Eastern Standard Time, UTC-05:00)  #    Comments [0] -
Code Snippet | SQL
 Tuesday, 23 February 2010

China-us-flagsThe big news over the past few months were the Aurora attacks and how they seemed to originate from China, last month Microsoft took the unusual step and released an Out-Of-Band patch for the IE6 0-Day vulnerability used in the attacks.

It was always thought the exploit originated from China due to parts of the code only being discovered on Chinese language sites, the latest news is that the actual origin of the code has been discovered by US investigators.

US investigators have pinpointed the author of a key piece of code used in the alleged cyber attacks on Google and at least 33 other companies last year, according to a new report.

Citing a researcher working for the US government, The Financial Times reports that a Chinese freelance security consultant in his 30s wrote the code that exploited a hole in Microsoft’s Internet Explorer browser. The report also says that Chinese authorities had “special access” to this consultant’s work and that he posted at least a portion of the code to a hacking forum.

According to The Financial Times report, the unnamed security consultant who wrote the exploit code is not a full-time government worker and did not launch the attacks himself. In fact, the FT says, he “would prefer not to be used in such offensive efforts.”

The reports says that when he posted the code to the hacking forum, he described it as something he was “working on.”

With a January blog post, Google announced that attacks originating from China had pilfered unspecified intellectual property from the company, and Microsoft later said the attack had exploited a hole in its Internet Explorer 6 browser. According to security researchers, at least 33 other companies were targeted by similar attacks.

Put simply, this means that the “consultant” who created the code posted a proof of concept for this exploit on a hacking forum. Then someone took this proof of concept, turned it into a working exploit and attacked 33 US based companies.

It will be interesting to watch how this story will unfold after this and if it’s going to increase the tension between the US and China governments. The whole cyberwar has been going on for quite a while now with both sides trying to secretly steal information from each other.

So far the author of the code has not been named and his real identity or purpose is still a little vague.

Source: The Register

 

Other posts:

Google Will Pay 500$ Bounty For Each Chrome Browser Bugs You Find

Google Translator Hacked

Password aren't a good defense?

In the news: Google negotiating cooperation with the NSA

Some tips to enhance your SQL Server security

How To: Create an Outlook 2003 addin using VSTO SE and Visual Studio 2005

Tuesday, 23 February 2010 10:33:37 (Eastern Standard Time, UTC-05:00)  #    Comments [0] -
News | Security
 Monday, 22 February 2010

Scott Hanselman recently has published the survey results of : What .NET Framework features do you use?

Quite interesting numbers! It interesting to see that such a high percentage of the respondants still use winforms. It’s also interesting to note that the number of Silverlight users is higher than the number of WPF users.

The survey also shows that WebForms, Ajax, WCF and Linq2SQL are clearly the technologies of choice as of now.

 

Other posts:

How-To: hiring and managing geeks

Sorting strings for real people - A human-friendly IComparer

How to set NTFS permissions using C# 2005

How to Use Active Directory to authenticate users in C#

How to find monday of the current week using T-SQL

Monday, 22 February 2010 11:13:35 (Eastern Standard Time, UTC-05:00)  #    Comments [0] -
General
 Wednesday, 10 February 2010

PhotographerI like to use to use images to help illustrate the theme or point of a blog post. It’s a proven “best practice” in blogging and I highly recommend that every blogger do it.

One trick for easily finding and properly using images in your blog posts is to search the creative commons licensed photos on the photo sharing site Flickr.

So, what’s Creative Commons?

Creative Commons is a non-profit organization that has created a standardized set of tools for granting various levels of permission for people to use creative works freely. The author or in this case photographer of the works designates a type of license and then Flickr allows you to sort through and find only photos that are free to be used for blog posts. I choose to use photos that carry the attribution/share alike license. This means that I may use the image here as long as I attribute the image to the Flickr user’s account where I found it. Here’s Flickr’s description of CC licenses.

So, here’s how to find and grab great images.

  1. Surf to the Flickr Creative Commons Search Page – all images you search for here are free to use with proper attribution
  2. Search for a specific phrase or concept and choose the image that fits
  3. Click on “all sizes” and choose the size you wish to post on your blog
  4. Right click the image and choose “copy image location” – use this path to paste into your blog post where you want the image to appear
  5. Somewhere in your post add the words – Image credit and the link to the Flickr account where you found the image (see at the bottom of the post)

To be a good photo user make sure you add your own images and make the available through the proper CC license – you can make this a default Flickr account setting.

Image credit: dashitnow

Other Posts:

The Best Damn Web Marketing Checklist, Period!

What Are Customers Saying About You Online?

8 easy tips to drive traffic from search engines to your site

Wednesday, 10 February 2010 09:35:46 (Eastern Standard Time, UTC-05:00)  #    Comments [0] -
General

Navigation
Advertisement
About the author/Disclaimer

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

© Copyright 2017
Stanislas Biron
Sign In
Statistics
Total Posts: 135
This Year: 0
This Month: 0
This Week: 0
Comments: 1
All Content © 2017, Stanislas Biron