Revit Add-in Localization - localization

Is there a way with the API to convert/translate Revit standard terms such as 'Insulation', '3D view', 'View Templates', 'Detail Level' and other baked-in terms to a given language (such as German, Russian , Chinese, etc.)? I'd like to ensure that the messages I provide in my localized add-in use terms that the user is familiar with (with regard to Revit).

I think Jeremy's answer is probably the way to go for a comprehensive approach.
However - if you're looking for something more self-contained and quick-and-dirty, you could try the LabelUtilities class in the Revit API. :)
The LabelUtilties lets you look up the translated value of all of the thousands of builtin parameters, parameter groups, unit types, etc).
All of the pieces of text that you mentioned above are available as BuiltInParmater translations (although, admittedly, some are not available as plurals).
For example:
LabelUtils.GetLabelFor( BuiltInParameter.RBS_WIRE_INSULATION_PARAM );
==> "Insulation" in English.
(You can see all of the translated English BuiltInParameters in the Revit API reference under the BuiltInParameters page).
Good Luck!
Matt

The Autodesk localisation team uses a cross product corpus database NeXLT for terminology and message translation:
http://langtech.autodesk.com/nexlt
This link is accessible from outside the company and translation companies working with the localisation team around the world make use it for translating products for Autodesk platforms.
This answer is already published with a little more background on The Building Coder blog:
http://thebuildingcoder.typepad.com/blog/2014/10/autodesk-open-source-all-over-germany-and-japan.html#4

Related

Shopify store translate into multiple languages

Is it possible to change the shopify Language in client side.
I have 3 Language locale file. I want to translate based on client choice
is it possible to use below code to change my language.
{% assign shop.locale = 'fr' %}
thanks in advance.
Seems there is no good enough solution, I have built this my own client-rendered solution. My solution provide:
single domain
not reload page on change language
unlimited language
unlimited page view
FREE
https://gist.github.com/Asoul/e5ee0a0f0ed17c93383ff47818b319c4
I open my source code above. I think this is some foundamatal infrastrcuture for an ec website, that's shameful to charge on this.
Hope these code can help some people.
But I think the perfect solution is that Shopify can offer a server-rendered method, not client rendered.
After doing some research, I realized that there was no "Plug and Play" solution available.
Creating one store per language would have been too expensive and requires you to somehow sync your stores.
A JavaScript solution does not supports SEO.
Shopify has a tool called langify using this we can do it but it has monthly recurring price I have added the link for your reference.
Shopyify App store link

Good or Bad for SEO: Keeping URLs in English for a non-english website?

I'm planning to release a community website that doesn't have a PRIMARY audience that is english speaking. This means that URLs that point to /profile /forums and so on will be in english and not in their native language. I'm not concerned if a user is using the website while accessing different URL paths in English, but I am concerned if I were to use non english URLs then would a search engine pickup on pages on the website better or worse?
Anyone care to share their opinions?
In my opinion, it would be better to have URLs that reflect the primary language of your users as it would make them finding your website easier on search engines (supposing they search using their primary language). From a SEO perspective, if possible try to also include in your URLs the relevant search terms you think would be used by your audience. If you have a forum, for example, include in the thread URLs the full thread title if possible, and so on.
Sources: my own experience with building and managing powershell.it and sqlserver.it, two of the most important Italian technology-related communities.
The best place to start on this issue would be Google's Webmaster Central section on Internationalization.
If you will have versions of the same URL in multiple languages, you can connect them using the rel="alternate"mechanism, which is explained at Google's Webmaster Tools page.
1. Summary
Using non-English URLs for non-English websites is fine.
2. Argumentation
Google Senior Webmaster Trends Analyst John Mueller said in a recent SEO snippets video that using non-English URLs for non-English websites is fine and that Google is able to crawl, index and rank them.
This includes non-Latin characters in your URLs. John Mueller said “as long as URLs are valid and unique, that’s fine.” He added, “So to sum it up, yes, non-English words and URLs are fine, and we recommend using them for non-English websites.”
Read full article here.
3. Disclaimer
Data of this answer were relevant in March 2018 and may be obsolete in the future.

translate to multiple languages

I would like to get translation from one ( best - automatically detected) language to 4 different using google-translate. My idea is to wrote a html document which contain 4 frames - in one of them I can find text form and button. After click on it, Internet browser will send demand to google translate and show results in 4 frames.
If you want a self service, hosted service that does translations and content management for you check out Localize.js
This is going to be terribly translated. As someone that speaks English well, Russian poorly, and Spanish even more poorly, I can detect that these auto-translations never come out right.
My recommendation is to serve your page through a basic system that will allow you to respond to submitted form values. Pass in &LANG=two country iso code and then have your backend serve up the correct data.
Have someone that speaks both languages prepare the content for you. Then, whenever you are serving these pages, you can also conditionally adjust CSS to account for differences in format which come from difference in language length.
If you don't have those capabilities available, make 5 pages. One in English and the other 4 in the other languages. You will seriously seem retarded to anyone that speaks those languages well if you use an auto-translate. I think this is a bad idea for any kind of professional page, even if you can work out the technical issues.
-Brian J. Stinar-
Google has an API to its translate tool that will enable you to send it some text and receive back that text translated into any language you choose.
edit: This is now a paid service

Determining language of twitter posts

What is the best way to determine the language of twitter posts.
There is the language parameter that comes with the streaming API but it doesn't really seem to be very accurate. Even many Japanese posts are labelled as English.
What have others done to sort out the langauges?
I've had very good results with this PHP package:
http://pear.php.net/package/Text_LanguageDetect/
It is fast and open source. We use it to select English only posts for a site we run at http://2012twit.com.
google have language detection within their Translate API if using evil external services is a go-er?
http://code.google.com/apis/language/translate/v1/reference.html#detectResult

how is language translation done in facebook?

i would like to know, how is the language translation done in facebook ?
Are they using google translate, or any licensed software ?
I want to enable language translation in my website, and i want similar to that of facebook.
How Can this be done, if at all possible ?
Google has good translation API that will convert your text in to given language. However if you want to translate a larger paragraph you need to go for human translation. Because Google translation is not converting grammar of other languages. Now there are good services available that allow automate the human translation like http://mygengo.com/
Facebook's partner for search and for translate functions is Microsoft Bing.
To use it similarly you need to use the API provided, see 'Translator' here at their Developer page:
http://www.bing.com/dev/en-us/dev-center
Source of my info: several websites including
http://translation-blog.multilizer.com/how-to-use-facebook-translate-button/

Resources