Anuncios
Welcome to the Revit Ideas Board! Before posting, please read the helpful tips here. Thank you for your Ideas!
cancelar
Mostrando los resultados de 
Mostrar  solo  | Buscar en lugar de 
Quiere decir: 

Auto translation of parameters based on Revit language version

Auto translation of parameters based on Revit language version

On behalf of a customer from Germany let me add the following wish:  make Revit (Revit Add-In) able to translate / display custom parateres in the same language as current Revit language version. 

 

Example: family parameters created in Revit DEU will appear as English if user opens Revit ENU version.

 

Potential workaround: 

Rename parameters with Dynamo

5 Comentarios
ipselute
Advisor

I believe the easiest way is also the simplest, just like in linux: simple *.txt files containing the entire translation of the interface. Revit interface is so vast, parameteres names are so many, i don't think a single person could handle it ALL. Automated translation services (like Google translate) are highly unreliable.

I believe translation should be collaborative by means of online translation management like Weblate, Transifex, Damned Lies for Gnome, etc. There is only one way to translate it: open-source translation by many users around the world. In the linux world this is called localization, and it works great for many famous linuxes.

P.S. I had a very similar problem while using Allplan (a long time ago): the base version interface was in german (NOT english), and many items in the library weren't translated to english. It was the most stupid thing i've ever seen: 50% of the interface was localised (in all european languages), another 30% was in english, and the rest (20%) was exclusively german. Many commands had impossibly long names (translated from german of-course).

Many words should be translated context-wise ! Words without context could make no sense.

The translation file should be like a keynote file: one single *.txt file for each language. For reasonable management manner. E.g. the "width" word -> translate it once, then find&replace it in the entire file (entire interface).

Markus_Hoffmann
Contributor

@ipselute 

You probably thought about  a different issue.

This idea is about using the already existing mechanisms of displaying parameter names in the language that the currently open Revit is configured to. I.e. walls created in an english version of Revit have an out-of-the-box parameter "Base Constraint". If you open files containing those walls in the german version of Revit the parameter name automatically switches to the german name.

I think it really would be great to be able to use this mechanism for custom parameters.

 

hagenreimers
Participant

Exactly as Markus_Hoffmann has stated we just need pointers in Revit. Make the text dependend on the GUID for that Paramter instead of linking it to the actual text.

 

I am having to create ENDLESS .xml files or vast Dynamo Scripts to make basic linkages between multiple different Tools. Not even Navisworks will understand what Revit is doing, when im working in a Multi-Language Environment (As almost all large EU-Based Projects are).

 

This is a major design flaw that could be easily fixed and would actually allow cross-platform design and workflows as BIM suggests. As of right now it takes more time to create all the translation-scripts then the actual work does.

Fix this. 

 

For everyone that has to work around this for the time being. Exporting to Ifc will fix some of these issues, as they use ifcGUID for Types and you could also just link every single object through its Revit-GUID (or Ifc-GUID, but check the box for parameter-saving in the export-options and export once to create these), which is static. Not great, but then you can disregard the design-flaws by Autodesk.

 

At least you gave me a good topic for my thesis. Thank you.

RPTHOMAS108
Mentor

I like the idea also from an API perspective but we need to think more carefully about it. Just because someone has a non-English version of Revit that doesn't mean they don't want to produce documentation in English i.e. it shouldn't be based on UI culture but instead an option you select in the project (or perhaps per view).

 

Shared parameter file is likely the best place to support it i.e. below I use pipe character since you can't use that in parameter names.

 

I used UI culture names below but we could easily replace those with any string to define a user based language setting and then have a fall back to the first item where no value for that language setting exists for a parameter.

 

RPTHOMAS108_0-1693244004891.png

 

andreas_3_weber
Explorer

It should be possible to have multilingual "shared parameters". The Revit internal parameters can do this too. This would be very helpful for us for international projects.

Can't find what you're looking for? Ask the community or share your knowledge.

Enviar idea  

Autodesk Design & Make Report