HI…
Not familiar with the English language.
Please check the attached video.
When the copy and paste function Loading Korean fonts in incorrect results is confirmed.
Thank you.
HI…
Not familiar with the English language.
Please check the attached video.
When the copy and paste function Loading Korean fonts in incorrect results is confirmed.
Thank you.
We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.
Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.
Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Hello Lee,
Our RichEditControl supports the Japanese and Korean fonts if these fonts are True Type Fonts. Would you please send us the fonts you installed on your machine and used to record this video.
We will analyze them and try to determine the exact cause of the issue.
I am looking forward to your response.
true-type font… yes…
Microsoft Windows default font… (Korean Version)
2…
3…
Please note the following cases. ^^
https://www.devexpress.com/Support/Center/Question/Details/T276257
Hi Leen,
I have installed the fonts you sent me, however, I did not see Korean fonts neither in the RichEditControl or in MS Word application. Probably, I need to change a system locale to Korean, or something else.
In the meantime, would you please record a video which illustrates how MS Word operates with these fonts on your side? For example, if you copy a text written in English language (a test text from our RichEditControl Demo), paste it into MS Word and change a font, what will be the result?
Add the recorded video.
Hello Leen,
Thank you for your video. I see the issue, however, I was not able to reproduce it on my side yet. We need additional time to investigate your fonts.
We will back to you as soon as we have any results. Please bear with us.
Hello Leen,
I have finally reproduced the issue with incorrect font calculation while copying/pasting a text in the RichEditControl document.
I passed this ticket to our developers for further research. Please bear with us. We will notify you as soon as we make any progress.
As a workaround for this issue, try to paste a copied text using the Paste Special command and selecting the "Formatted Text (XAML)" option from the "Paste Special" dialog.
I have attached a video to demonstrate this workaround in action.
Work to reproduce the error should really think hard work.
Too bad I can not speak fluently in English.
Thanks to hard work. And look forward to good results.
This can be also referred to as the victory of Google Translator. ^^;
You are welcome, Lee!
I am happy to hear that my assistance was helpful to you.
We will update the status of this ticket once we have any results. Please bear with us.
See the attached image.
I wonder whether the issues connected with that issue.
Hello Lee,
I am not quite sure whether or not the issue you illustrated in your last image is related to the original one. I passed this information to our developers so that they can take it into account while working on the original problem.
We will update the status of this ticket once we have any results.