Description of problem: There are several areas that need i18n'd in the database layer. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
There are a number of issues with i18n in Satellite which need to be addressed. At current we have been tackling a bunch of ISEs in the app code to overcome a deficiency in the database setup. You could probably break this feature up into phases: 1) set database to define varchar2 sizes in characters *NOT* bytes 2) devise an upgrade plan to upgrade existing customers' databases. Once we have database, we can then start to attack the appcode side.