@Sherif M. ElRoumy Sounds like we might need a ticket for this to investigate fully - but if you are able to add the text OK and it is only the save and retrieval process that fails, first thing to check is if you have the "annotationEncoding" parameter present and set to a valid value (UTF8 us the one I would suggest) since we need such an encoding for handling multi-byte character languages such as Arabic.

If that is all set and still failing, can you raise a ticket for this issue and include screenshots showing annotation before and after and also collect logging as follows:

First enable the "traceAnnotation" parameter set to "true" either in the properties file (if standalone system) or from Admin -> Settings -> Logging -> ViewONE Virtual section (if ICN) then:

1. Load document with no annotations

2. Press and

3. Move to third tab and click on "Console" button

4. Add text annotation and save

5. Download client console and copy to text file for "save" process and clear console

6. Reload document

7. Download client console and copy to text file for "load" process

Send screenshots + logs to us and we can take a closer look at what might be going wrong.

@Sherif M. ElRoumy Hi Sherif - now I've seen the screenshots, this is a known issue since one of my colleagues had a ticket already reporting this exact same problem. So if you can raise a ticket on this, we can link it up together so that you get the fix when it is in place. What you are seeing is that with the initial entry of the text, we use the browser dialog box for the text and this works correctly - but we than have to "transpose" that text to our own proprietary bitmap format for annotation text and this is where the issue comes in.