Created attachment 113604 [details] LibreOffice Writer cannot use these two fonts The fonts "Ahuramazdanew" and "AhuramazdaPlusTranslit" are to be used in LibreOffice only in Microsoft's operating systems Windows XP and Windows 8.1 but not in Ubuntu versions, e.g. in Ubuntu 14.10. AbiWord in Ubuntu 14.10 however does use these two fonts "Ahuramazdanew" and "AhuramazdaPlusTranslit". I think there must be something like a bug in Ubuntu's LibreOffice versions? Please cf. the screenshots "in AbiWord.jpeg" and "in LibreOffice.jpeg" Regards, Ernst Tremel
On which LO version are you in both envs?
Version: 4.3.3.2 Build-ID: 430m0(Build:2)
Thank you for your feedback, I put it back to UNCONFIRMED.
In addition to this description: On my homepage http://www.skytower.org/~ernstjtremel/Ahuramazda/AvestanToLatinAndViceversa.htm I made two Macros http://www.skytower.org/~ernstjtremel/Ahuramazda/Makro-AnleitungTAB.pdf a) one for for transforming Avesten script into LatinTranscription script b) the other for transforming LatinTranscription into Avestan script. Both are working fine in OpenOffice Writer. But only Macro b) is working in LibreOffice Writer Version: 4.3.3.2 Build-ID: 430m0(Build:2) wheras Macro a) is not working in LibreOffice Writer Version: 4.3.3.2 Build-ID: 430m0(Build:2). The reason is that LibreOffice Writer Version: 4.3.3.2 Build-ID: 430m0(Build:2) cannot handle the font "AhuramazdaPlusTranslit".
Where is the Abiword screenshot? How exactly does the problem manifest itself? I installed the fonts in Win & Ubuntu: http://www.skytower.org/~ernstjtremel/Ahuramazda/Ahuramazda-Avestan-Font-1.zip MitAvestanAhuramazdaPlusTranslit.ttf from here: http://www.skytower.org/~ernstjtremel/Ahuramazda/AvestplusTranscrFonts.zip In your page I didn't find Ahuramazdanew, btw. or AhuramazdaPlusTranslit without mitavestan in the front. In Ubuntu, I could do Insert - Special character just great. In Win, I inserted chars, but some of them did not show or showed a rectangle, but I guess I'm lacking some Windows character pack or something. Please add a new report for your macro problem. Thanks. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided more information. Win 7 Pro 64-bit, LibO Version: 4.4.1.2 Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432 Locale: fi_FI Ubuntu 14.10 64-bit Version: 4.4.1.2 Build ID: 40m0(Build:2) Locale: en_US
Created attachment 113780 [details] in LibreOffice
"Ahuramazdanew" is not yet published. But "AhuramazdaPlusTranslit" may be found and downloaded at http://www.skytower.org/~ernstjtremel/Ahuramazda/AvestanToLatinAndViceversa.htm Concerning Avestan display in different operating systems you may resd the following text (cf. below uder (*) and it's discussion at https://social.msdn.microsoft.com/Forums/windowsapps/en-US/15190304-467c-4a02-8ff0-2ae69109430f/windows-and-unicode-display-hex10000-ff?forum=windbg (*) Display of fonts with glyphs of Unicode ranges from hex-10000 upwards. (Example glyphs of Unicode ranges from hex-10b00 to hex-10b3f (Avestan) and from hex-10b78 to hex-10b7f (Inscriptional Pahlavi)) Are they been displayed correctly in Microsoft features like Word or managed in Keyboard Layout Creator? If so where? In Unicode Code Charts-7.0.0 there are many glyphs from ranges hex-10000 (Linear B Syllabary) up to hex-e01ef (Variation Selectors Supplement). If so in which features are they worked out e.g. in Word or Keyboard Layout Creator etc.? As far as I can see the above mentioned problems are not yet solved neither in Windows 8.1 nor in the newest version of Windows 10. What's the matter? Why these difficulties with these Unicode Code ranges? In Ubuntu versions there are no problems!!!? Do Tavultesoft Keyboard Layouts support these above described Unicode ranges ? E.g. Keyboards for Avestan, Inscriptional Pahlavi, Linear B Syllabary so on? Does Office 365 support these above described Unicode ranges ? E.g. Keyboards for Avestan, Inscriptional Pahlavi, Linear B Syllabary so on? The fonts "Ahuramazdanew" and "AhuramazdaPlusTranslit" are to be used in LibreOffice only in Microsoft's operating systems Windows XP and Windows 8.1 but not in Ubuntu versions, e.g. in Ubuntu 14.10. AbiWord in Ubuntu 14.10 however does use these two fonts "Ahuramazdanew" and "AhuramazdaPlusTranslit". I think there must be something like a bug in Ubuntu's LibreOffice versions? Please cf. the screenshots "in AbiWord.jpeg" and "in LibreOffice.jpeg" Regards, Ernst Tremel in AbiWord.jpeg a in LibreOffice.jpeg lo
Created attachment 113781 [details] abiword and libreOffice
Created attachment 113795 [details] in Abiword
I still do not understand the problem. Are you unable to insert the glyphs as special characters in Ubuntu? Please explain how we can reproduce the problem in clear steps.
please read this and you will understand the Problem https://social.msdn.microsoft.com/Forums/windowsapps/en-US/15190304-467c-4a02-8ff0-2ae69109430f/windows-and-unicode-display-hex10000-ff?forum=windbg
(In reply to E.Tremel from comment #11) > please read this and you will understand the Problem > > > https://social.msdn.microsoft.com/Forums/windowsapps/en-US/15190304-467c- > 4a02-8ff0-2ae69109430f/windows-and-unicode-display-hex10000-ff?forum=windbg That's about Windows and not about the title of this report: "fonts not usable in Ubuntu 14.10 LibreOffice Writer"
Created attachment 113815 [details] shows itself
Created attachment 113816 [details] shows itself
Created attachment 113817 [details] shows itself
Created attachment 113818 [details] shows itself
Created attachment 113819 [details] shows itself
pleaase have a look at these four attachments and you will see that LibreOffice Writer cannot show and handle the fots neither "Ahuramzdanew" nor "AhuramzdaPlus Translit"
Caolan: thought you might be interested in this bugtracker since it concerns font rendering problems
Ok, setting back to UNCONFIRMED. No comments from me.
Please don't set your own priority - this was horribly over prioritized. Critical bugs are saved for major crashes and serious data loss. This does not qualify.
please give an update of the bug status with latest LibO 5.2.3.3 set status to UNCONFIRMED if bug is still present or RESOLVED WORKSFORME if bug is gone. NEEDINFO until then
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20170628
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20170727