|
|
|
|
As the team delved deeper, they encountered the third tier of Language Pack work: The Work Environment.
Archicad allows users to customize keyboard shortcuts. The "Work Environment" profile is often saved separately from the project.
The Tokyo team found that their custom hotkeys, set up by the senior partners years ago in English, were now "broken" or pointing to the wrong commands. The Language Pack had remapped the internal command names, causing a disconnect with the old shortcut profiles. archicad language pack work
This revealed a crucial aspect of the "work": Implementation Strategy. A Language Pack is not just a file you install; it is a migration. To do the "work" correctly, the BIM Manager had to go into the Work Environment settings and manually remap the shortcuts to align with the new Japanese UI command names, or force the team to learn the default localized shortcuts.
Back in the Tokyo office, the architects quickly realized that changing the interface was only the beginning. The true power of Archicad lies in BIM—data, not just geometry. As the team delved deeper, they encountered the
This is where the "Language Pack work" becomes critical and often misunderstood.
Archicad projects are stored in .pln files. These files are database containers. A Language Pack does not rewrite the data inside the file. If the Tokyo office opened a project started by an American firm, the internal attribute names were still stored in English in the database. The Tokyo team found that their custom hotkeys,
Here is the problem the team faced: They loaded the Japanese Language Pack, but when they opened the "Attribute Manager," the building materials were still named "Concrete - Cast In Situ."
The Language Pack works on the System Attributes, not the Project Attributes.
This distinction is the source of 90% of confusion regarding Language Packs. It is a translation tool, not a project translator.
The language pack directly impacts IFC (Industry Foundation Classes) export. If you export an IFC file from the German language pack:
As the team delved deeper, they encountered the third tier of Language Pack work: The Work Environment.
Archicad allows users to customize keyboard shortcuts. The "Work Environment" profile is often saved separately from the project.
The Tokyo team found that their custom hotkeys, set up by the senior partners years ago in English, were now "broken" or pointing to the wrong commands. The Language Pack had remapped the internal command names, causing a disconnect with the old shortcut profiles.
This revealed a crucial aspect of the "work": Implementation Strategy. A Language Pack is not just a file you install; it is a migration. To do the "work" correctly, the BIM Manager had to go into the Work Environment settings and manually remap the shortcuts to align with the new Japanese UI command names, or force the team to learn the default localized shortcuts.
Back in the Tokyo office, the architects quickly realized that changing the interface was only the beginning. The true power of Archicad lies in BIM—data, not just geometry.
This is where the "Language Pack work" becomes critical and often misunderstood.
Archicad projects are stored in .pln files. These files are database containers. A Language Pack does not rewrite the data inside the file. If the Tokyo office opened a project started by an American firm, the internal attribute names were still stored in English in the database.
Here is the problem the team faced: They loaded the Japanese Language Pack, but when they opened the "Attribute Manager," the building materials were still named "Concrete - Cast In Situ."
The Language Pack works on the System Attributes, not the Project Attributes.
This distinction is the source of 90% of confusion regarding Language Packs. It is a translation tool, not a project translator.
The language pack directly impacts IFC (Industry Foundation Classes) export. If you export an IFC file from the German language pack:
|
|
|
|
|