Bug 1020281 - Installer: make sure that translations use correct branding
Summary: Installer: make sure that translations use correct branding
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Localization
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: jboss-set
QA Contact: Nikoleta Hlavickova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-17 11:27 UTC by Petr Kremensky
Modified: 2019-08-19 12:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:45:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1007833 0 unspecified CLOSED Installer: Missing translations for EAP 6.2 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1016026 0 unspecified CLOSED Several branding issues in EAP 6.2.0 installer 2021-02-22 00:41:40 UTC

Internal Links: 1007833 1016026

Description Petr Kremensky 2013-10-17 11:27:50 UTC
Description of problem:
 Product name has changed for EAP 6.2.0. 

Full product name: "Red Hat JBoss Enterprise Application Platform"
Approved abbreviated form: "JBoss EAP"

We've found some branding issues in English langpack (see BZ1016026). We must make sure, that translated texts won't contain same issues (currently they do).

Version-Release number of selected component (if applicable):
 EAP 6.2.0.ER6

Additional info:
 I wonder if there is any synchronization between changes made to installer during testing cycles and localization. eg. in ER5 testing cycle we change meaning of some error message, is there any chance that translated texts will contain same error message not the old one?

Comment 2 Petr Kremensky 2013-11-01 11:57:44 UTC
BZ1016026 is verified now (EAP 6.2.0.ER7), but other langpacks still contain strings like txt="Scripts da janela de solicitação do JBoss JBoss EAP UNIX.", this should be fixed.


Note You need to log in before you can comment on or make changes to this bug.