Hi, Some Greek character not change shape when us‑ing upper‑case / lower‑case !!! - ϙ / Ϙ - Ϻ / ϻ - Ϸ / ϸ - Ͷ / ͷ Tʰang 帑 كتأنجى you. Kanth كانث you...
Confirmed. Format - Text - Change case. Win 7 Pro 64-bit Version: 5.2.0.0.alpha0+ Build ID: f0841c6c86c8c8403eb1d78a1bd43a8adac75e3a CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2016-01-15_00:01:41 Locale: fi-FI (fi_FI) Regarding ϙ: https://en.wikipedia.org/wiki/Koppa_%28letter%29 "The Unicode character encoding standard originally (since version 1.1 of 1993), had only a single codepoint for Koppa, which was marked as uppercase and could be used either for an epigraphic or a numeral glyph, depending on font design. A lowercase form was encoded in version 3.0 (1999)." Regarding Ϻ: https://en.wikipedia.org/wiki/San_%28letter%29 "In the electronic encoding standard Unicode, a pair of uppercase and lowercase forms of the letter was introduced in version 4.0 (2003). For this purpose, new lowercase forms for modern typography, for which no prior typographic tradition existed, had to be designed." Regarding Ϸ: https://en.wikipedia.org/wiki/Sho_%28letter%29 "Ϸ was added to Unicode in version 4.0 (2003), in an uppercase and lowercase character designed for modern typography." Regarding Ͷ: https://en.wikipedia.org/wiki/Digamma#Pamphylian_digamma "In some local (epichoric) alphabets, a variant glyph of the letter digamma existed that resembled modern Cyrillic И. In one local alphabet, that of Pamphylia, this variant form existed side by side with standard digamma as two distinct letters. It has been surmised that in this dialect the sound /w/ may have changed to labiodental /v/ in some environments. The F-shaped letter may have stood for the new /v/ sound, while the special И-shaped form signified those positions where the old /w/ sound was preserved." http://scriptsource.org/cms/scripts/page.php?item_id=character_detail&key=U000376 http://scriptsource.org/cms/scripts/page.php?item_id=character_detail&key=U000377
These letter not varg to : - Ͳ ͳ - Ͱ ͱ - Ͻ ͻ - Ͼ ͼ - Ͽ ͽ - Ϳ ϳ - Ϗ ϗ - Ϲ ϲ (this one is strange change to "Σ" instead of "Ϲ" (U+03F9) and if lower became "σ" (standard sigma), like like "ϵ" who change to "Ε" (standard Epsilon) and after lower "ε" (standard epsilon) !!! Correct this plêase my vriênd !!! Until Epsilon lunar is added in Unicode Greek (I will make the request), use "Є" (Ukrainian in Cyrillic range) or at least, no one (standard epsilon is not a good choice)...
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
Dear nemzag, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear nemzag, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Also in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 3070091c9eafc964ebb3f53d3b44124b40571fd8 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded
Khaled Hosny committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/9eb88d78c8bc9e942814eb6fc4fe06a4e5736256 tdf#96343, tdf#134766, tdf#97152: Fallback to ICU for case mapping It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Khaled Hosny committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/88790291ddc00bfa18d3f7bcc0825b1ce14cb490 tdf#97152: Fix upper case mapping of lunate sigma (U+03F2) It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.