Text

Answered

Alphanumeric conversion

HI,

We are facing some issue with conversion when we are using the normal text editor.

When we write 1 it converts it to l and sometimes when we write 2 it converts it to Z

When we write 10 sometimes it converts to 10 but when we write 10 mg it converts it to long.

Is there someway we can improve the transcription here?

Thanks,

Piyush


Best Answer

Dear Piysuh,


this would require a special development in our our core technology, which is not planned at present. Nevertheless, I keep this in mind.


Regarding using special characters, this is not possible neither.


Best regards,


Olivier


Answer

Dear Piysuh,


this would require a special development in our our core technology, which is not planned at present. Nevertheless, I keep this in mind.


Regarding using special characters, this is not possible neither.


Best regards,


Olivier

Dear Olivier,

Thank you for all your support. 

However, in case if something does come up, which can take care of this please do let me know.

Is there some sort of special characters that can be used?

Thanks,

Piyush

Dear Piyush,


The way you are mixing digits with letters is in the limits of our technology. I am afraid not much can be done.


Best regards,


Olivier

Hi Olivier,

Is there some sort of hack or something that can be used here?

Thanks,

Hi Olivier,

Thank you for your response. I will send a snapshot soon. One e.g. that comes to my mind is that if i write "i" and  "s" with some gap, it merges the two together to "is".

If i do not use the TEXT resource, it causes more issues as you have mentioned.

The problem that we are facing is mainly when we have numbers along with text. Most other cases is working quite well.

So as you have mentioned above, the model takes into consideration more common usage, and that is where we are facing issues, as the numbers are getting converted to text.

Is there no way that this can be avoided?

Thanks and Regards,

Piyush



Dear Piyush,


Indeed, when writing "1 said", our TEXT resource is using a model that takes into account the context. Basically, as "I said" is more frequent than "1 said", it will give more weight to "I said".

It is not possible to disable this feature from the TEXT resource. The only solution would be than you do not use the TEXT resource, but this may cause more issues than it will solve.


Regarding the spaces, I am still puzzled, as if these are neatly written, they should be properly recognized. Can you please attach a screenshot when a space is not properly recognized?


Best regards,


Olivier

Hi Olivier,

I can give you one more example.

For e.g. 

I started writing 

"1 said"

Initially the engine figured out that i wrote 1. But as soon as I wrote said, it converted it to "I said".

Looks like english takes dominance over the numbers.


1. For 1 got some details

I typed in    "I" ( x cood - 97, y 235 ), then tried to type T (lowercase ) ( 211,214 ) for the vertical stroke . (246,152) for the horizontal stroke.

The engine created the word "It"

Piyush

Dear Olivier,

Thank you for your response.

1. I am leaving a good amount of space between two characters. The engine is still trying to connect the two letters. How do i get the ink samples ( x and y coordinates )

2. currently, I am a bit puzzled previously written are updated when new words are added. Which configuration do you have? Are you still attaching the TEXT resource with your own lexicon? If so, can you please try without the TEXT resource?

By this I mean that if I add more characters, the previous recognized words change automatically. I dont know why. This happens even if we leave a decent amount of space between two words. 

If i remove the TEXT resource and use only my vocabulary, recognition went down, because then the case of the letters is coming into play and causing a problem.

Now I am mainly using the TEXT resource and a few extra words added. 

We are getting 80-90% accuracy. The main problem that we are now facing is what I have mentioned in point 1

3. The content Changed function did not work as it was clearing the whole data.

Thank you for your help. This is the last step in our application before we can start doing some testing.

Thanks and Regards,

Piyush


Dear Piyush,


currently, I am a bit puzzled previously written are updated when new words are added. Which configuration do you have? Are you still attaching the TEXT resource with your own lexicon? If so, can you please try without the TEXT resource?


Also, is there a way that the engine can understand that if we leave a  certain amount of space between two characters then we dont merge those  two characters to make a new word?

>>If spaces are "properly" written , words should not be merged. Indeed, we have an algorithm to determine spaces that has been finely tuned over the years. So, this behavior should not occur if spaces are properly done. Would you have some ink samples (x and y coordinates, no image) that would allow to reproduce?


Best regards,


Olivier

Also, is there a way that the engine can understand that if we leave a certain amount of space between two characters then we dont merge those two characters to make a new word?

Dear Olivier,

I put the code inside the contentChanged function. However, I found that the content Changed function was being called twice and the second time the string was blank so my screen was getting cleared.

Any reason for this?

Regards,

Piyush

Dear Piyush,


can you please try in the contentChanged function?


Neverhtheless, please note that has the contentChanged function is called a lot, this may decrease the app.


Let us know if it works.


Best regards,


Olivier

Hi Olivier,

Where do i put this code?

Piyush

Dear Piyush,


thank you for the update,


Unfortunately, not much can be done to prevent the previous words from not being changed. One solution could consist in exporting the text and import it again. This should help in having a "more stable" result.


Can you please try to proceed as below, and see if it helps:

String exportResult = editorView.getEditor().export_(null, MimeType.TEXT);
editorView.getEditor().clear();
editorView.getEditor().import_(MimeType.TEXT, exportResult, null);


Best regards,


Olivier