peterfri Posted June 22, 2021 Share Posted June 22, 2021 you write: RTF Export - improved support for Unicode characters above 64k- RTF Export - wasn't closing small caps correctly but how can I export rtf, I don‘t find it. Thank you Peter Link to comment Share on other sites More sharing options...
walt.farrell Posted June 22, 2021 Share Posted June 22, 2021 1 minute ago, peterfri said: you write: RTF Export - improved support for Unicode characters above 64k- RTF Export - wasn't closing small caps correctly but how can I export rtf, I don‘t find it. Thank you Peter It's referring to copying text in Publisher, and then pasting into Word or other application that reads RTF format from the clipboard. -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
peterfri Posted June 22, 2021 Author Share Posted June 22, 2021 ok then I have to say it does not work fine, all the german characters are lost. Link to comment Share on other sites More sharing options...
thomaso Posted June 25, 2021 Share Posted June 25, 2021 On 6/22/2021 at 8:27 PM, peterfri said: german characters are lost. I can't notice a difference between v193 & beta v1098. Copy/paste umlauts (ä, ö, ü) from APub works in macOS TextEdit.app - but not in MSWord, regardless of the Affinity version: ... macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 Link to comment Share on other sites More sharing options...
peterfri Posted June 30, 2021 Author Share Posted June 30, 2021 yes the problem is the same. I hoped it would be solved with 1.10 Link to comment Share on other sites More sharing options...
garrettm30 Posted June 30, 2021 Share Posted June 30, 2021 Edit: Walt helpfully pointed out that this is a beta-specific issue, so what I originally said below, while still true generally, is not relevant for this thread. I am sorry for the confusion, and I thank Walt for helping by pointing that out. ---------- 5 hours ago, peterfri said: yes the problem is the same. I hoped it would be solved with 1.10 If this is not a beta-specific issue, then it is best to post in the bugs section of the forum rather than the beta section, which is intended only for issues specific to the betas. I guess this is why thomaso said this: On 6/25/2021 at 8:41 AM, thomaso said: I can't notice a difference between v193 & beta v1098. Link to comment Share on other sites More sharing options...
walt.farrell Posted June 30, 2021 Share Posted June 30, 2021 3 minutes ago, garrettm30 said: If this is not a beta-specific issue, then it is best to post in the bugs section of the forum rather than the beta section, which is intended only for issues specific to the betas. The Release Notes for beta 1.10.0.1085 indicated the problem was fixed. garrettm30 1 -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
Staff Jon P Posted June 30, 2021 Staff Share Posted June 30, 2021 Thanks for the feedback, I've logged the fact some characters are still missing or being replaced when pasted into MSWord Serif Europe Ltd. - www.serif.com Link to comment Share on other sites More sharing options...
Recommended Posts