[ 
https://issues.apache.org/jira/browse/CAMEL-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372673#comment-14372673
 ] 

Claus Ibsen commented on CAMEL-7621:
------------------------------------

Thanks for the patch. But for the source code files, we need to use unicode 
values for foregin chars. So the source code works for all around the world. eg 
use \u1234 for those non ascii values.

> Two new properties to StringFormat through DataField: toUppercase and 
> mapToASCII
> --------------------------------------------------------------------------------
>
>                 Key: CAMEL-7621
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7621
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-bindy
>            Reporter: Bruno Fontana
>         Attachments: 
> Adding-properties-to-mapToASCII-and-to-convert-to-Up.patch
>
>
> We faced many times the need of converting string fields to uppercase and get 
> rid of non-ASCII characters when interacting, using fixed-length files, with 
> COBOL banking cores.
> So we decided to patch our own version of camel-bindy to add two new 
> properties to DataField annotation:
> toUpperCase=<true|false> which converts, if its a String type field, content 
> to uppercase.
> mapToASCII=<true|false>  which maps, if its a String type field, content to 
> 7-bit ASCII character mapping. Extended characters are currently mapped like 
> this
> ä,â,á,à -> a (same for all vowels)
> ß -> b
> ç -> c
> ñ -> n
> Conversion uses a lookup table so it could be easily extended to other chars. 
> This conversion only applies when marshalling. This feature has proven very 
> useful to us when interacting with banking cores and one that repeatedly has 
> to be recoded or reused. We love the annotation-driven model of bindy so 
> decided to patch our own version and submit the patch hoping it would be as 
> useful to others as it is to us.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to