Welcome to!Usage of the spoiler tag: This is a spoiler.(/spoiler):Whineposting'Whineposting' is allowed in some cases, if you want to 'whinepost' your post has to be constructive, debate-able and have a positive influence on the sub. Also your title has to be constructive.Do not speak about a droughtUnless an official statement is made by Kairosoft about timelines, please do not make any posts purely about the length of time since their last English game. We are all avid Kairosoft fans here, we already know.No Modded/HackedYou may not request a hacked or Modded game nor discuss them in any way.Language FilesIf you have a language file ready to be shared, make a post AND modmail so it can be added to the listFriendIDsFriendIDs must be submitted in at the right threadFlair UsagePosts about new releases have to be flaired using one of the flairs supplied. Currently Available:.:JP: -:android: Release.:EN: -:android: Release.:JP: -:iOS: Release.:EN: -:iOS: Release.:JP: -:NSwitch: Release.:EN: -:NSwitch: ReleaseOther posts can use the following flairs:. Discussion. QuestionFor more info,Community AdvertisingIf you want to advertise your community, please modmail the team.
Please keep this post in mind. If your advertisement has been approved, post it and modmail with a link to the post so it can be flaired accordingly by one of the mods.Links of Interest:.Other Subreddits:.Part of the Community:.Get the Apps:.Awards:.
.Some text in save data created before installing a language pack will be in the original language. Start a new game to have the language change reflected.Kairosoft bears no responsibility for any issues or damages incurred through the use of Kairosoft games or Language Pack.The Language Pack service may be discontinued without notice. Read somewhere that you have to install the language pack before running Search/Cortana (which fails with a 'Not available in your region' error, presumably because the wrong speech pack is installed.
OverviewYou have numerous options to tackle language packs when deploying Windows 10. These include:. Install language packs offline/online during reference image creation.When dealing with a large number of languages, this will dramatically increase your install.wim size. Install languages packs offline with DISM manuallyThe same goes as above, imagine supporting 20 languages, that’s a lot of bloat in your image. Create one image per languageThis is a terrible idea and you really shouldn’t do it. Install languages packs online during OSDThis is the most dynamic way to achieve this, why install languages you do not need?In any case you have two primary functions here.
Installation and configuration of the language(s) per region.Installing only the languages you actually want makes a lot of sense. Furthermore, its important to note that Windows 10 is an agile OS, you will be supporting at the very least two releases per year, so you really want to be able to remove as much manual work as possible.Remember, language packs are specific to each Windows release.
A 1607 LP will not work on a 1703 release.Note: Windows 10 in-place upgrades only support the same base system language, you cannot upgrade a Windows 10 en-GB base system language with Windows 10 en-US media.System Language:Note: This post was revised a number of times with updates (including screenshots) to cover bug fixes, therefore references to languages in each step may be mixed.None of the steps i will outline below are particularly ground-breaking (or new) but I feel it’s useful to hash over the particulars. Additionally, this method of language application is very useful when you have a number of languages to support. We want to be able to easily add language packs to support the next OS release without reinventing the wheel each time.PreparationAs stated previously, each OS release has a particular language pack. In the below examples, you will see references for Windows 10 1703 and Windows 10 LTSB 2016 (this is the 1607 build).
Language packs are downloadable from the Volume Licensing page, see here for more information on downloading the correct LP ISO.The link above describes downloading media for just the base languages, if you want language features (OCR, handwriting, Text-To-Speech) these are located in the ‘Features on Demand’ downloads, also found on the VLSC.Mount the downloaded ISO, create a language pack folder in your SCCM source folder, and then create a folder based from the release name (1703, 1607) and architecture (x86, x64). Create subsequent subfolders with the language ID (en-GB, fr-FR, de-DE etc).
This folder structure isn’t critically important, but it makes sense to be neat.Language packs are no longer simply called ‘ lp.cab‘ as they used to be, the naming format is now ‘ Microsoft-Windows-Client-Language-Packx64fr-fr.cab‘. In each language ID, you should place the base language file, and any of the ‘Features on Demand’ if this is applicable.Create a basic Package in ConfigMgr for each language pack, your source path should be the root directory for each language ID. Do not create a program, name the packages accordingly.We will be installing language packs based off a user selection during OSD. This definition can be made in many ways, you could have a UI for choosing a language (as i do), you could set collection variables on your OSD collections, or you could get be really clever and automate language selection based off a region (network range). It doesn’t really matter, the goal here is to simply define what language we want to actually end up with.As mentioned, I use an excellent UI solution called. The built in MDT driven UDI will also work fine as well, all we want to do here is prompt for selection of a language.You can choose to define all variables (UILanguage, Keyboard, TimeZone etc) within UI (or any other UI) or you can use the dynamic variables step used later in this post.If you already use UI, the selection is simply.
The Variable we are defining here is ‘ Location‘. This selection will be referenced later in the Task Sequence to dynamically assign the specific language pack we require.We need a way to install and set language preferences per build, a very popular method is to dynamically populate the unattended xml with language values, see this post for information on this approach:The method in this post uses a separate answer file which is called by the utilising the command rundll32.exe shell32,ControlRunDLL intl.cpl,/f:”C:WindowstempUI-Settings.xml”– this command sets the values defined in the Multilingual User Interface control panel applet. See here for more information on the MUI.aspxI found this really helpful script originally written by, which has now been modified. The script itself will install the language pack and then associate that language as default based off the values retrieved from the task sequence. This script should be saved into a generic OSD scripts folder, it does not need to be stored with the language pack reference files.
The benefit of this is there is one script to control all language packs, regardless or version.