Hebrew in Development
time to read 2 min | 290 words

This is a plea to all those developers who are speaking a langauge with a non-latin character set and wants to use non-english names during development. If the database support Unicode names, use them. If it doesn't use the correct trasnlation to English. The most confusing database schema that I saw was Hebrew words spelled in English. And this one had a twist, it was abberviated Hebrew words.

If you want to have a column that would store the date of birth, you can call it DateOfBirth, of if you really want to use Hebrew, call it: "ת. לידה". Both are very clear. Taleda is not. It's a worse sin when these abominations creeps out of the database and contaminate your business objects. It may be okay if you're using the latin character set. But if not... just don't do it. If you're really tied to the hebrew names, you can use them in Hebrew inside your code. The following example compiled and execute cleanly on all version of C#:

using System;
public class UnicodeClass
{
 public static DateTime תאריך_לידה;
 
 public static void Main(string [] args)
 {
  תאריך_לידה = DateTime.Now;
  System.Console.WriteLine(תאריך_לידה);
 }
}

Hell, Reflector display it correctly, so you've got all your bases covered. Of course, you may be taken to the wood shed over it, as well.

Tweet Share Share 0 comments
Tags: