| Area | Behavior after language switch | |------|-------------------------------| | (doors, windows, objects) | Parameters remain original language. A French "Porte" won’t become "Door". | | Template files (.tpl) | Keep original language for attributes, layer names, and saved views. | | Schedules/Interactive Schedules | Column titles, criteria, and expression names are UI-based and do change. Property names (user-created) stay as typed. | | GDL objects | 2D/3D text inside scripts is not translated. | | BIMx data | Language is set at export (UI language at that moment). | | Renovation filters | Filter names remain as created. Default filter names (e.g., "Existing") may change if they come from UI strings. |
No. The UI changes, but the existing data structure does not auto-translate. archicad language pack work
Starting in Archicad 28, Graphisoft introduced , simplifying cross-border collaboration: | Area | Behavior after language switch |
Even if you use a different language version, the project’s standards (default sizes, pens, and surfaces) are often tied to the Template (.tpl) file used when the project was created. USA Template : Default settings use imperial units (e.g., feet/inches). INT/GER Template : Default settings use metric units (e.g., cm/m). Migration Tip | | BIMx data | Language is set
: A reference list that identifies which specific library packs are included in various localized versions like GER, USA, and INT. Graphisoft Community Practical Implementation Resources Global Library Localization Preferences