Currently in Archicad, DWG and DWF translators are stored inside the Archicad installation — not in the project file.
This is similar to how Work Environment profiles are handled, and it creates real problems, especially in company workflows.
If a project uses a specific DWG or DWF export setup (for example, for a consultant, contractor, or submission package) and that translator is missing or different on another Archicad installation, the exported files can be incorrect — even if you use the same publisher set.
This is a serious risk when working in teams, across offices, or sharing files externally.
The idea:
Translators for DWG and DWF should be saved inside the project file (or at least embedded optionally, like IFC translators).
That way, when you open a project, you always get exactly the right translator settings — without needing to manually import/export translators, or guess which "version" of the translator you should be using.
Summary:
Making DWG and DWF translators project-dependent (embedded into the .pln or .tpl) would dramatically improve file consistency, reduce errors, and make Archicad publishing workflows much safer and more predictable across teams, companies, and remote work setups.
Open