Comments on: Local vs Localization of Language http://www.techsoapbox.com/local-vs-localization-of-language/ Soapboxing every damn day Thu, 20 Nov 2008 22:27:27 +0000 http://wordpress.org/?v=2.6.2 By: Ahmed http://www.techsoapbox.com/local-vs-localization-of-language/#comment-54277 Ahmed Wed, 25 Jun 2008 04:00:49 +0000 http://www.techsoapbox.com/local-vs-localization-of-language/#comment-54277 Don't ever see it happening. Mostly because there are a few classifications (ala SIC) and also because none of the players are really online focused - its just direct marketing/business analytics forced online. Of course we intend to change that :) Don’t ever see it happening. Mostly because there are a few classifications (ala SIC) and also because none of the players are really online focused - its just direct marketing/business analytics forced online.

Of course we intend to change that :)

]]> By: Joe Davison http://www.techsoapbox.com/local-vs-localization-of-language/#comment-54225 Joe Davison Wed, 25 Jun 2008 00:11:58 +0000 http://www.techsoapbox.com/local-vs-localization-of-language/#comment-54225 Ahmed what do you think about standardizing a taxonomy that everyone in the industry can use. Think W3C -- who will define the standard taxonomy for the global local space? I think standards are important for proper interoperability of API's, etc. Ahmed what do you think about standardizing a taxonomy that everyone in the industry can use.

Think W3C — who will define the standard taxonomy for the global local space?

I think standards are important for proper interoperability of API’s, etc.

]]> By: Ahmed http://www.techsoapbox.com/local-vs-localization-of-language/#comment-54146 Ahmed Tue, 24 Jun 2008 17:18:13 +0000 http://www.techsoapbox.com/local-vs-localization-of-language/#comment-54146 Yep some common ones here - lawyer vs attorney (or in England, barrister or solicitor). And then doctor vs physician too - a biggie. Translating (especially among taxonomies) sure is a headache :) Yep some common ones here - lawyer vs attorney (or in England, barrister or solicitor). And then doctor vs physician too - a biggie.

Translating (especially among taxonomies) sure is a headache :)

]]> By: Dave http://www.techsoapbox.com/local-vs-localization-of-language/#comment-54128 Dave Tue, 24 Jun 2008 15:50:38 +0000 http://www.techsoapbox.com/local-vs-localization-of-language/#comment-54128 Even in English you can have problems- some areas use "lawyers" while others use "attorneys." And if you change the category name to "lawyers and attorneys," you'll get people scratching their heads asking what's the difference? Another issue is when the language "over-differentiates" specialties, or "under-differentiates" them. For example, let's say Elbonian has 5 different classifications of lawyers, according to some strange differentiation that is different from English. English business listings for "lawyers" probably will be impossible to differentiate automatically into the 5 different Elbonian classifications, and manually will be a major chore (and still probably impossible without calling each one and asking what type they are). Going the other direction (Elbonian taxonomy to English taxonomy) is easier- you can easily combine all 5 Elbonian lawyer categories in "lawyers." But what do you do if you want to use the same data simultaneously on an English site and an Elbonian site?? This is actually an issue that we've been running into with our sites and have been (so far) skirting the issue by using English as the defauly taxonomy and forcing the other language to comply with it. But now you've got me thinking that we need to do a better job and utilize separate taxonomies. Sigh. Thanks, Ahmed- you just created several hours of new work for me... :P (Just kidding! Although I may complain about the extra work, I think the resulting preduct will be better for it. But I still get to complain! :) ) Even in English you can have problems- some areas use “lawyers” while others use “attorneys.” And if you change the category name to “lawyers and attorneys,” you’ll get people scratching their heads asking what’s the difference?

Another issue is when the language “over-differentiates” specialties, or “under-differentiates” them.

For example, let’s say Elbonian has 5 different classifications of lawyers, according to some strange differentiation that is different from English. English business listings for “lawyers” probably will be impossible to differentiate automatically into the 5 different Elbonian classifications, and manually will be a major chore (and still probably impossible without calling each one and asking what type they are).

Going the other direction (Elbonian taxonomy to English taxonomy) is easier- you can easily combine all 5 Elbonian lawyer categories in “lawyers.” But what do you do if you want to use the same data simultaneously on an English site and an Elbonian site??

This is actually an issue that we’ve been running into with our sites and have been (so far) skirting the issue by using English as the defauly taxonomy and forcing the other language to comply with it. But now you’ve got me thinking that we need to do a better job and utilize separate taxonomies.

Sigh. Thanks, Ahmed- you just created several hours of new work for me… :P

(Just kidding! Although I may complain about the extra work, I think the resulting preduct will be better for it. But I still get to complain! :) )

]]>