[PUP-1031] Improve Puppet's handling of non-ASCII character encodings - Puppet Tickets

XML

Word

Printable

Details

Type: Epic
Status: Closed
Priority: Normal
Resolution: Fixed
Affects Version/s: None
Fix Version/s: None
Component/s: None
Labels:
- customer
- i18n
- redmine
- utf-8

Epic Name:
Unicode Encodings
Template:
customfield_10700 21348

CS Priority:
Major
CS Frequency:
2 - 5-25% of Customers
CS Severity:
4 - Major
CS Business Value:
5 - $$$$$$
CS Impact:

Hide
While our international presence is not yet huge we are growing it and seeing a lot of interest. We need to fix this for both our existing customers that are running into it as well as future customers.

The workaround of not using international characters is not an acceptable long term solution.

Show
While our international presence is not yet huge we are growing it and seeing a lot of interest. We need to fix this for both our existing customers that are running into it as well as future customers. The workaround of not using international characters is not an acceptable long term solution.

Description

This is an umbrella bug for issues related to Puppet's handling of non-ASCII character encodings. Many of these issues crop up when running Puppet on Ruby 1.9.x and newer.

See the 'related bugs' field for a full list of issues.