Bug 656139

Summary: Errors when updating a website when terminal locale is not en_US
Product: [Community] Publican Reporter: Ruediger Landmann <r.landmann>
Component: publicanAssignee: Jeff Fearn <jfearn>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 2.3CC: jfearn, mmcallis, publican-list, r.landmann
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 2.4 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-07 22:49:26 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
Spanish labels in Dutch ToC none

Description Ruediger Landmann 2010-11-23 00:24:51 EST
Created attachment 462231 [details]
Spanish labels in Dutch ToC

Description of problem:
When the terminal locale is something other than en_US, website ToCs contain the following errors:

1. The ToC for every language on the site has elements such as "collapse all", "search", "untranslated" presented in the language of the terminal, not the language of the ToC. For example, if the locale in the terminal was es_ES, Spanish labels would appear in the ToC of every language (see attached example of Spanish labels in Dutch ToC)

2. Non-ASCII characters (such as accented Latin characters) would not render correctly (note Estad��sticas and Tecnolog��a in the attached screenshot) 

Version-Release number of selected component (if applicable):
2.3

How reproducible:
100%

Steps to Reproduce:
1. Set the locale in your terminal to something other than en_US. For example:
LANGUAGE=es_ES
2. Install a book on a Publican website with the publican install_book command
3. Look at toc.html in various language directories

Actual results:
ToCs are in the language set in the terminal, non ASCII characters are not rendered correctly.

Expected results:
ToCs are in the target language (if translations are available, otherwise in English), non-ASCII characters are rendered correctly.

Additional info:
Comment 1 Jeff Fearn 2010-11-23 00:56:40 EST
The strings used for the website were being treated as strings for the command line script, so the strings were being incorrectly matched for localisation.

Changed the way the web site strings were being localised so they are treated differently from scrip strings.

Fixed in build: 2.3-0%{?dist}.t50
Comment 2 Jeff Fearn 2010-12-07 22:49:26 EST
Publican 2.4 has shipped with a fix for this issue.