actually, my suggestion yesterday regarding the language wasn't a good one. (long day)
It may seem more complicated, but a better table structure would be
ItemID - LanguageID - Description
1 - 1 - Dog
1 - 2 - Hund
1 - 3 - Chien
1 - 4 - Perro
2 - 1 - Cat .... etc, and link this to your languages table.
This has the added benefit that if you want to add another language in the future, you just add 1 item in the language table and use this table for the descriptions, (so no changes to database structure).
The unique ID for the above table could be a compound key of ItemID and LanguageID.
Without wanting to sound too prescriptive, don't structure the datbase based upon ease of of data entry.
If you could give me a brief outline of your business and the data you wish to hold, I may be able to help more.