Language Pack Work Verified | Archicad

For working with Archicad language packs, the most helpful documentation and "papers" focus on the introduction of Library Packages (libpacks) and the MUI Resource Technology used for add-ons. Essential Technical Guides How to Create Multi-Language Add-Ons

: This is the definitive technical paper for developers. It explains the MUI (Multilingual User Interface)

resource technology, which separates executable code from language-neutral resources into specific files stored in language-ID folders. How to Create Templates Using Library Packages

: A critical guide for Archicad 28 and newer. It details the shift from monolithic libraries to modular

, allowing users to access library content from all language versions (e.g., using German doors in an International version). Default Library Packs in Each Archicad Language Version

: 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 archicad language pack work

: A step-by-step workflow for managing a multilingual work environment. It guides you through the "Edit GDL Library Parts" toolbar to set desired languages for your library objects. Unable to Change Language in Archicad

: This support document clarifies that the interface language is hard-coded into the installation. If you need a different UI language, you must install that specific language version separately. Managing Multiple Language Installations

: A community guide on how to successfully install and run multiple language versions (e.g., INT and USA) on the same machine without settings overwriting each other. Graphisoft Community Key Concepts for Language Work Description .mui Files

Language-specific resource files handled by the system based on user settings. Global Library

Introduced in Archicad 28, it allows modular "libpacks" from any language to be used in any project. For working with Archicad language packs, the most

Template files that should be package-based to properly support the new global library language features. converting a custom template to support the new global library packages? Global library language and multilingual work environment

Phase 2: The Database Layer (The Real Work)

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." System Attributes: The default library that ships with

The Language Pack works on the System Attributes, not the Project Attributes.

• System Attributes: The default library that ships with the software. The Language Pack automatically translates default surface names (e.g., "Glass" to "ガラス") because these are referenced in the String Tables.
• Project Attributes: Custom data created by users. The Language Pack cannot touch this because it doesn't know what the user typed.

This distinction is the source of 90% of confusion regarding Language Packs. It is a translation tool, not a project translator.

Does a Language Pack Affect File Export (IFC, DWG, PDF)?

Short answer: It depends on the export settings.

• IFC Export: The IFC file contains both Name (localized) and Description (raw). If you export a wall named “Bearing Wall” in English, a German user opening the IFC in a German pack will see “Tragwand” only if their software translates the Name tag. Most IFC viewers ignore the language pack.
• PDF/DWG: These are visual exports. The text on the drawing is drawn as geometry, not as active text strings. So, a PDF exported from a French ArchiCAD will say “Plan de Masse” (Site Plan) permanently, even if opened in an English OS.

What actually works:

1. Spell check dictionaries – You can add multiple languages.
2. User interface (menus, dialogs, tooltips) – This requires a full localized version downloaded from Graphisoft, not an add-on pack.
3. Library objects – Some region-specific libraries (e.g., German, US, UK) can be downloaded separately.

Conclusion: Should You Use an Archicad Language Pack?

Use a language pack if:

• You are starting a new project in a new country.
• You are a student learning BIM in your native tongue.
• Your local building code requires specific classification systems (e.g., you cannot use Archicad in Spain without the CTE pack).

Do NOT switch language packs mid-project if:

• You are on a Teamwork server with international colleagues.
• You have 500+ custom objects with hard-coded English names.
• You need to send IFC files to global stakeholders regularly.

Issue 1: “The menus changed, but my library objects are still in English.”

Why: The library wasn’t re-loaded. Solution: Go to File > Libraries and Objects > Manage Libraries. Remove the old library and re-add the localized version (usually found in C:\Program Files\Graphisoft\ArchiCAD [Version]\Libraries\[Language Code]\).

Translating project content vs UI

Language packs localize the interface and packaged content but do not automatically translate user-entered project text (labels, notes, schedules). For project translation:

• Use bilingual templates or manual translation for key text.
• Export schedules or text to CSV for bulk translation, then re-import.
• Consider using MIF/XML export pipelines and CAT tools for large documentation sets.