Localization of a sql table to Japanese language

Question

Post reply

Localization of a sql table to Japanese language

karthik82.vk

SSCrazy

Points: 2002
More actions
July 15, 2015 at 5:40 am

#305870

Hi All,
I have a table called country that will store all the country related details in it. Below is the screenshot of my country table.
I want to localize this table to Japanese language. I googled out and found out that a new table needs to be created for storing the data in localized language.
If that's the case do we need to manually translate the text in the country table for each and every country?
Is there any automated process for that? Just like not translating the text manually for each and every rows..
This is because I have few more tables in which the text are not static. they will get loaded on a daily basis. So i will not be able to translate them every day..

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Phil Parkin SSC Guru Points: 246716 More actions · Answer 1

If that's the case do we need to manually translate the text in the country table for each and every country?

Only if you need it.

Are you thinking that SQL Server has some in-built language translator?

If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

karthik82.vk SSCrazy Points: 2002 More actions · Answer 2

Hi,

Is there any way to do it in sql itself?

Are there any tools outside SQL that can be used for this?

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 3

karthik82.vk (7/15/2015)
Is there any way to do it in sql itself?

No. SQL is a database engine, not a language processor

Are there any tools outside SQL that can be used for this?

Get a good translator to help you write the localised text, if you try translating things using something like google translate, you're likely to get at least a few translations which are wrong or look like they were done by a computer.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

karthik82.vk SSCrazy Points: 2002 More actions · Answer 4

Hi,

Based on the discussion, I came to know that it needs to be a manual process. I found out a tool called sisulizer to get the translation done however that too needs a manual work by translating the text into that software.

Can anyone provide me a sample schema and how the tables needs to be created?

I have nearly 20 tables and i need to replicate the tables in a separate design. I will not be able to have the language in the same table as i will have more than 20k rows in each table.

Steve Jones - SSC Editor SSC Guru Points: 734552 More actions · Answer 5

20k rows isn't much. If you do this for 20 languages, you're are 400k rows. Again, not a lot. You could easily add a "language" column that helps an application or user understand which localized value is there.

Alternatively, you could do something like.

tbl_country_japanese

for the name. Note, I think tbl_ as a prefix is silly, and unnecessary, but it's your model. I would just name this "country".

You could also use schemas for this, perhaps having

us.tbl_country

japanese.tbl_country

spanish.tbl_country

etc.

There's no magic here. You design the table to hold the data, regardless of collation and content. If you want to separate out different types of content for a reason, those a new entities, that would look like the existing ones. You can certainly script out the existing tables and use find/replace to add to the values with a schema or prefix/suffix.