Forcing the Preferred Language in the Deployment or during Installation

Forcing the Preferred Language in the Deployment or during Installation

david_baldacchino
Contributor Contributor
643 Views
2 Replies
Message 1 of 3

Forcing the Preferred Language in the Deployment or during Installation

david_baldacchino
Contributor
Contributor

Hi,

 

Prior to the web deployment method, we were able to force the preferred language via a switch in the installation string (/language en-us for example). With the web deployment method, the batch files does not include a language switch. Per the documentation on this page, the deployment language is set based on the regional settings of the machine creating the deployment (behavior confirmed; in my case it was set to en-US):

 

davidbaldacchino_0-1645231428328.png

 

When installing from the deployment, I cannot seem to find a way to force the preferred language. I would like Revit shortcuts to be set to "ENU", regardless of regional settings. I believe this was the behavior of the previous deployment method when using the /language switch, which forced the shortcut setting during installation:

 

davidbaldacchino_0-1645233378223.png

 

 

 @danny.polkinhorn might have the answer...is it no longer possible to force this during installation? I discovered the behavior change because our custom Revit.ini files that we copy to the UserDataCache folders (used to seed the user Revit.ini file) have all paths specified under [DirectoriesENU] and since the preferred language has changed (for example some machines are now set to ENG), they complain about template paths.

 

I did a bit more searching and found this page, which does reference the switch "-l <option>", but it states that this is to change the language shown in the installer. It does appear we can no longer force the language, but I'm not 100% sure so any help on this would be greatly appreciated! Thanks.

David Baldacchino
Firmwide Design Technology Manager - HOK
@dourevit
0 Likes
644 Views
2 Replies
Replies (2)
Message 2 of 3

huotger
Alumni
Alumni

Hello, we are aware that the traditional behavior is not functioning as expected and we are looking into solutions to restore this behavior in a future release of Revit.



Gerry Huot

SQA Manager
Message 3 of 3

david_baldacchino
Contributor
Contributor

Thanks Gerry, very much appreciated. Adding back a language switch as in the "classic" deployment install string would be welcomed. In the meantime for anyone reading this thread, my simple workaround is to do a post-install copy of both Revit and Viewer shortcuts in my install script, with the language of choice set in the target field (.lnk files in C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Autodesk\Revit 2022).

David Baldacchino
Firmwide Design Technology Manager - HOK
@dourevit