Page 1 of 1

Non-English Language issue about Find function.

Posted: Thu Jun 17, 2021 12:03 am
by defcon8808
Dear Supporters :)

i found issue one.

firstly, Let's see below it plz.
find_issue.gif
Editor SDK Version is lastest of V8.

Thank you.

Re: Non-English Language issue about Find function.

Posted: Thu Jun 17, 2021 8:42 am
by Tracker Supp-Stefan
Hello defcon8808,

The Editor is currently at V9. Can you please try build 354 and see if RTL text input is still the same for you there?

Kind regards,
Stefan

Re: Non-English Language issue about Find function.

Posted: Thu Jul 15, 2021 12:03 am
by defcon8808
Tracker Supp-Stefan wrote: Thu Jun 17, 2021 8:42 am Hello defcon8808,

The Editor is currently at V9. Can you please try build 354 and see if RTL text input is still the same for you there?

Kind regards,
Stefan
Hi stefan.

i had check this issue at build 355 of V9.1 Editor SDK. This issue still occurs. not RTL text input for my case.

maybe i think that same issue occuring at korean, japanese, chinese. plz detail check to this issue.

* PS - This issue not occur to end-user version of Editor. only Editor SDK version occurs.

Re: Non-English Language issue about Find function.

Posted: Fri Jul 16, 2021 2:31 pm
by Tracker Supp-Stefan
Hello defcon8808,

I've asked a colleague from the dev team to take a look and we will post an update here as soon as I have their feedback!

Kind regards,
Stefan

Re: Non-English Language issue about Find function.

Posted: Wed Aug 18, 2021 5:34 am
by defcon8808
Tracker Supp-Stefan wrote: Fri Jul 16, 2021 2:31 pm Hello defcon8808,

I've asked a colleague from the dev team to take a look and we will post an update here as soon as I have their feedback!

Kind regards,
Stefan
Hi. stefan,

How processing about it? i have been waiting your feedback.

Re: Non-English Language issue about Find function.

Posted: Fri Sep 24, 2021 1:34 am
by defcon8808
defcon8808 wrote: Wed Aug 18, 2021 5:34 am
Tracker Supp-Stefan wrote: Fri Jul 16, 2021 2:31 pm Hello defcon8808,

I've asked a colleague from the dev team to take a look and we will post an update here as soon as I have their feedback!

Kind regards,
Stefan
Hi. stefan,

How processing about it? i have been waiting your feedback.
Hello? :?: :?: knock knock

Re: Non-English Language issue about Find function.

Posted: Fri Sep 24, 2021 3:23 pm
by Tracker Supp-Stefan
Hello defcon8808,

Apologies for dropping the ball on this one!
I did hear back from our devs - it has been passed to the correct person for investigation and fixing, but unfortunately at the time we passed it - it was too late for the fix to be included in build 356. I will now check to confirm it has been fixed for 357.

Kind regards,
Stefan

Re: Non-English Language issue about Find function.

Posted: Tue Jan 25, 2022 11:41 am
by defcon8808
Hello

i had been receive additionally issue about it from our user.

i did typing word and then input enter key.

* Case 1 - In C# demo sample, removed last character after input enter key.
Removed last character in C# Sample
Removed last character in C# Sample
* Case 2 - In Delphi demo sample, not removed last character after input enter key.
Not removed last character in C# Sample
Not removed last character in C# Sample
* Case 3 - In C# demo sample, crashing application.
crash application
crash application
* Case 4 - In Delphi demo sample, only crashing control.
crash control
crash control
i will hope fix it as soon as possible. and I wonder how long it will take fix it.

* I will send to sample pdf file to e-mail.( To. support@pdf-xchange.com )

Re: Non-English Language issue about Find function.

Posted: Tue Jan 25, 2022 12:11 pm
by Tracker Supp-Stefan
Hello defcon8808,

Thanks for the sample file.
The issue is with the font and how it is embedded in your sample. There is enough information for the text to be displayed on screen, but the rest that is needed for this to be searcheable and extractable is missing, and not only our Editor but other PDF tools are also unable to search for or extract text from this file. Please check your e-mail for some further screenshots illustrating the issue.

Kind regards,
Stefan

Re: Non-English Language issue about Find function.

Posted: Thu Feb 03, 2022 12:30 am
by defcon8808
Tracker Supp-Stefan wrote: Tue Jan 25, 2022 12:11 pm Hello defcon8808,

Thanks for the sample file.
The issue is with the font and how it is embedded in your sample. There is enough information for the text to be displayed on screen, but the rest that is needed for this to be searcheable and extractable is missing, and not only our Editor but other PDF tools are also unable to search for or extract text from this file. Please check your e-mail for some further screenshots illustrating the issue.

Kind regards,
Stefan
Thanks for quickly reply. We had been check again about case 3. see below table.
image.png
I understood that text data is wrong and not be searchable it. but, I hope to not be forced exit application for error.

plz, check about case 3 in detail.

and then, i wondering approximate schedule about fix case 1,2.

Re: Non-English Language issue about Find function.

Posted: Thu Feb 10, 2022 2:27 am
by Vasyl-Tracker Dev Team
Hi defcon8808.

Thanks for the detailed report. We will try to fix that issues soon..

Cheers.

Re: Non-English Language issue about Find function.

Posted: Thu Feb 10, 2022 5:39 am
by Paul - Tracker Supp
Hi defcon8808,

Support ticket RT#5953: Non-English Language issue about Find function. has been created.

If possible a fix will be in the next build currently slated for the end of the month, if not a subsequent one.

Re: Non-English Language issue about Find function.

Posted: Thu Feb 10, 2022 7:33 pm
by Vasyl-Tracker Dev Team
Hi defcon8808.

Some details about crash-cases. The document you provided has tens of thousands of very tiny inline images (mostly - just white rectangles) on pages and loading many pages content causing overusing of memory. This may cause out-of-memory exception on 32-bit system. In the new upcoming build we will dramatically reduce the memory usage for this specific case (thanks for good sample doc), so I guess it will solve such crashes as well.

About the issue with typing hieroglyphs inside the find-control - that is the known issue caused by some internal code inside .NET framework. For unknown reasons that code removes the last recognized hieroglyph from the app's events queue, even we use the standard IME-input. And at the moment we haven't a proper solution for this or even a workaround. But in the near future we plan to reimplement our IME-input handling to solve this annoying problem at all.

Cheers.