TRichView.com

Hi.

Is it possible to show 2 or more SRVs vertically - at design time - but to show the document like it is loaded into just 1?
The document should be "split" in equal parts in the SRVs and recomposed when saving.

Or maybe a better internal item indexing can be made.
The current one is not so fast for large rtf's - like the ones outputted by Abby Finereader after converting the pdf scan of a hole book.
I can try to make one - but I will need a few pointers...

Thank you.

KInd regards,
Cosmin.

Sorry, this feature is not supported, and I think it cannot be implemented efficiently without serious changes in source code.

OK.
But, if you may change your mind in the future, how much it will cost to implement?
Just in case I find a sponsor xdxd.



As you may know, Abby FineReader is used for converting graphic text to normal (computer) text.
Unfortunately is not so good - especially on non english languages.

We (me and friends) added and developed a new feature in the AutoCorect app called OCR Plus (based on another feature called Multiple Replacements).
In a few min (depending of the size of the text), it clears/fixes most of the problems. The rest can be easily fixed manually.
For now is only for romanian language. But it can be extended to another languages too.

Can you explain, why do you want to display two parts of documents in different TSRichViewEdits?
I do not understand how it helps in OCR.

Right now I am trying to increase the speed of the OCR Plus function, composed by dozens of Multiple Replacement with large dictionaries + other custom ones.
On my computer (AMD processor 3.2 GHz, DDR3, 3 cores) it reaches even to 30 min.
And I need a faster way so I could use bigger dictionaries to increase the correction.
One way is to use multiple separate threads. I'm working on it.
But after this, the next bottleneck would be... srv.

I noticed the speed of srv is not a linear function of the 1/RtfLength.
But is not also a ^2 function.
It's something in between.
For example if the rtflength is half, the speed of srv should be between 2 and 4 (* previous speed). Closer to 4 I think...

If you use a lot more srvs, it will be faster. Well, in theory.
But it will be a nightmare synchronizing all of them.

I am sure that 2 parts of document will not be processed faster than the whole document.

Ok.

Sorry, I forgot to mention something: the srv's should be in different threads to work.

A few years ago a Beta tester from AutoCorect (so with the old version of RV and SRV) tested with two sessions of the app in the same time.
He says it worked faster than with one session (~ +20..30%).

I will test again with the old and new version and come back with the results.

Sorry, formatting in threads is not supported.