Description: LOWER(), UPPER(), PROPER() functions does not work correctly on Turkish character capital 'i' (İ). Correct Turkish letters in lower and upper order and from top left to bottom right keys(QWERTY TR keyboard): ıIğĞüÜşŞiİöÖçÇ Steps to Reproduce: 1.LOWER(ıIğĞüÜşŞiİöÖçÇ) 2.UPPER(ıIğĞüÜşŞiİöÖçÇ) 3.PROPER(ıIğĞüÜşŞiİöÖçÇ) Actual Results: After LOWER -> ıiğğüüşşiİööçç After UPPER -> IIĞĞÜÜŞŞIİÖÖÇÇ After PROPER -> Iiğğüüşşiİööçç Expected Results: After LOWER -> ıığğüüşşiiööçç After UPPER -> IIĞĞÜÜŞŞİİÖÖÇÇ After PROPER -> Iığğüüşşiiööçç Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: LibreOffice 7.0.0.2 c01aa64b6c3d89ebe5fe69c28c7adb24eb85249c
Created attachment 163368 [details] Formula screenshot
Reproduced with Turkish UI on Windows 10: Version: 7.0.0.2 (x64) Build ID: c01aa64b6c3d89ebe5fe69c28c7adb24eb85249c İşlemci süreçleri: 2; İşletim Sistemi:Windows 10.0 Build 18363; UI gerçekleyici: Skia/Raster; VCL: win Locale: zh-CN (zh_CN); UI: tr-TR Calc: threaded This feels like a l10n issue to me. The character "i" should be coverted to "I" by UPPER() in most locales, and Turkish environment is an exception. Since there is no way to label a string as specific language (that I know of) in Calc, using the UI locale seems a reasonable choice.
Also reproduced in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
Let's give a try with https://gerrit.libreoffice.org/c/core/+/99255
It's really not sure the patch is ok so let's unassign just in case someone would have the right fix.
Just for info, I abandoned the patch, too much complicated.
@Ali: to make sure, are you running LibreOffice in a Turkish locale? Otherwise the I->ı and i->İ can not happen. Note that is *not* related to UI language (and should not be). See output of Help->About, it should contain tr-TR for Locale.
Dear Ali Geyik, 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
Dear Ali Geyik, 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-FollowUp