FLAM® Issue Tracker

View Revisions: Issue #597 All Revisions ] Back to Issue ]
Summary 0000597: Support of a system translitteration table for best fit mapping
Revision 2014-11-13 12:19 by Falk Reichbott
Description Conversion of non convertable code points on best fit in case of look and feel.

Ideas:

Like Windows best fit mapping from Microsoft.

SEPA conversion table (definition per language)

XML-OEV translitteration has best fit mapping (€ is not defined for ISO8859-1).

First character of standard UNICODE normalisation (translit combined character to nothing (no expansion)).

With or without expansion
Revision 2014-11-13 12:03 by Falk Reichbott
Description Conversion of non convertable code points on best fit in case of look and feel.

Ideas:

Like Windows best fit mapping from Microsoft.

SEPA conversion table (definition per language)

XML-OEV translitteration has best fit mapping (€ is not defined for ISO8859-1).

First character of standard UNICODE normalisation (translit combined character to nothing).

Revision 2014-11-13 11:55 by Falk Reichbott
Description Conversion of non convertable code points on best fit in case of look and feel.

Like Windows best fit mapping from Microsoft.

SEPA conversion table (definition per language)

XML-OEV translitteration has best fit mapping (€ is not defined for ISO8859-1).
Revision 2014-11-13 11:45 by Falk Reichbott
Description Conversion of non convertable code points on best fit in case of look and feel.

Like Windows best fit mapping from Microsoft.


Copyright © 2000 - 2022 MantisBT Team
Powered by Mantis Bugtracker