![]() ![]() These two blog posts are excellent references: this & this.Īt this point I was confused again, though. After that you’d make a new application which will run a command like setup.exe /config \path\to\this\config.xml. I had missed that initially and was getting “ The language of this installation package is not supported by your system” errors when deploying. Step 2 would be to copy the setup.exe, setup.dll, proofkit.ww, and proofmui.en-us to your ConfigMgr content store to a folder of its own. In the root of that folder is a config.xml file with the following – You can see this doc for a list of language identifiers and languages. Within that you will find folders for various languages. So first step, download the last ISO in the list below (Proofing Tools 64-bit if that’s your case).Įxtract it somewhere. (In retrospect, the screenshot above says so – “dictionaries, grammar checking, and sorting” – but I didn’t notice that initially). ![]() You see, language packs are for the UI – the menus and all that – whereas if you are only interested in spell check and all that stuff what you need is the proofing tools. That is, until I spoke to a colleague with more experience in this and realized that what I am really after is the Office 2016 Proofing Toolkit. I spent a lot of time trying to understand how to proceed with that and even downloaded the huge ISOs from VLSC but had no idea how to deploy them via ConfigMgr. I found this official doc on deploying languages and that talked about modifying the config file in ProPlus.WW\Config.xml. I don’t know much of Office so I didn’t even know where to start with. What they want is for the language to appear in this section of Office: I need to deploy a language pack for one of our offices via ConfigMgr. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |