Ansible
PS DSC
Downloads:
542
Downloads of v 2.0.0.0:
542
Last Update:
27 Jul 2020
Package Maintainer(s):
Software Author(s):
- wandersick
Tags:
multilingual mui localization localisation englishise english language windows batch script command cli
EnglishizeCmd
- 1
- 2
- 3
2.0.0.0 | Updated: 27 Jul 2020
Downloads:
542
Downloads of v 2.0.0.0:
542
Maintainer(s):
Software Author(s):
- wandersick
EnglishizeCmd 2.0.0.0
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
Validation Testing Passed
Verification Testing Passed
DetailsScan Testing Resulted in Flagged:
This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.
We recommend clicking the "Details" link to make your own decision on installing this package.
Deployment Method: Individual Install, Upgrade, & Uninstall
To install EnglishizeCmd, run the following command from the command line or from PowerShell:
To upgrade EnglishizeCmd, run the following command from the command line or from PowerShell:
To uninstall EnglishizeCmd, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download englishizecmd --internalize --source=https://community.chocolatey.org/api/v2/ -
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'" - Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade englishizecmd -y --source="'INTERNAL REPO URL'" [other options]See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade englishizecmd -y --source="'INTERNAL REPO URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install englishizecmd
win_chocolatey:
name: englishizecmd
version: '2.0.0.0'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'englishizecmd' do
action :install
source 'INTERNAL REPO URL'
version '2.0.0.0'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller englishizecmd
{
Name = "englishizecmd"
Version = "2.0.0.0"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'englishizecmd':
ensure => '2.0.0.0',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package was approved by moderator AdmiringWorm on 31 Aug 2020.
There often comes a need to use built-in command-line tools in English in non-English Windows, as they are localized to another language which can be difficult for admins who only speak English. 'Englishize Cmd' employs a different technique to 'englishize' CLI tools with a click.
List of Features
- Toggles between English and non-English for many Windows commands
- For English system admins who manages Windows PCs of other languages
- No need to log off; settings are applied immediately
- Comes with a restorer. Apply or restore is as simple as a click
- Better character compatibility than changing DOS codepage
- Many languages and executables are supported. Customizable
- Ensure the outputs which your scripts catch are always in English
- Administrator rights are required. It asks for rights to elevates itself. (Does not elevate over network mapped drives)
- Parameter
/quietcan be used to suppress confirmation messages for unattended usage. (Only works when existing Command Prompt is run elevated) - Supports Windows Vista and later, as well as their server versions only, including Windows 10 or Windows Server 2019
- Portable by default. Optional installer enables
EnglishizeCmdandRestoreCmdcommands globally in Command Prompt and Run Prompt. (The commands including the extensions would beEnglishizeCmd.batandRestoreCmd.bat)
Getting Started
"Englishize Cmd" comes with 4 files:
EnglishizeCmd.batfor changing command line tools from non-English to English.RestoreCmd.batto restore everything back to original language, including original permissions and ownerships._lang_codes.txtis a modifiable list containing all non-English language codes. It includes most languages but in case your language is not there, add it and "Englishize Cmd" will support it._files_to_process.txtis a modifiable list of file names of command-line executables that will be affected in the change. All commands in Windows Vista, 7 and 8.1 should be covered (although it contains much more commands than there actually are, it doesn't matter because it has no effect on commands that don't exist.) If you decide some commands are better left localized rather than being changed to English, remove them from this list before running "EnglishizeCmd.bat". Also, although the list covers command-line executables, you can add GUI – Graphical User Interface - programs such as Paint - mspaint.exe and lots of others to "_files_to_process.txt". There is a limitation here though. Windows comes with both English and non-English .mui files for command-line programs only; by default .mui for GUI programs don't exist in en-US folder until users install the English MUI through Windows Update) or some third-party tool (for non-Ultimate/Enterprise Windows users).
Note: The above files would be located in %ProgramFiles(x86)%\wandersick\EnglishizeCmd (for an all-user setup)
$ErrorActionPreference = 'Stop';
$packageArgs = @{
packageName = 'EnglishizeCmd'
softwareName = 'EnglishizeCmd*'
fileType = 'EXE'
silentArgs = "/programfiles /unattendAZ=1"
validExitCodes= @(0)
}
$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']
if ($key.Count -eq 1) {
$key | % {
$packageArgs['file'] = "$($_.UninstallString)".Substring(0, $_.UninstallString.IndexOf(' /'))
if ($packageArgs['fileType'] -eq 'MSI') {
$packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['silentArgs'])"
$packageArgs['file'] = ''
}
Uninstall-ChocolateyPackage @packageArgs
}
} elseif ($key.Count -eq 0) {
Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
Write-Warning "$($key.Count) matches found!"
Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
Write-Warning "Please alert package maintainer the following keys were matched:"
$key | % {Write-Warning "- $($_.DisplayName)"}
}
Log in or click on link to see number of positives.
- EnglishizeCmd-2.0.0.0_Silent_Installer.exe (2514cdfa1c86) - ## / 71
- englishizecmd.2.0.0.0.nupkg (fec97ba6f991) - ## / 62
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
This package has no dependencies.
Ground Rules:
- This discussion is only about EnglishizeCmd and the EnglishizeCmd package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or EnglishizeCmd, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.