In Hebrew, the Geresh character (׳) is used for abbreviations, unlike English which uses the period (.).
Thus if in English, 123 Oak Street may be abbreviated as 123 Oak St., in Hebrew,
רחוב האלון 123 becomes רח׳ האלון 123. The Geresh character is _not_ supposed to be used for in single-quotation marks (well, if you do your typesetting right, anyway). There's a separate character for that which is / is based on Mercha.
Both Geresh and Mercha have their doublings, i.e. Gershaim and Merchaot. Gershaim is used to denote acronyms, e.g. דרישת שלום is a ד״ש.
In practice, however, Hebrew keyboard lacks keys for Geresh and for Gershaim (and for Mercha and Merchaot), so people use apostrophe (') and double-quotes (") instead of Geresh/Mercha and Gershaim/Merchaot/bottom Merchaot respectively: רח' האלון 123 and ד"ש.
Now, the auto-correction feature sometimes (rarely? perhaps only when importing Word documents or from a previous LO version?) mistakes a single apostrophe character, at the end of an abbreviated word and before a space, a period, a comma and so on, for a single quotation mark, and replaces it with, well, I'm not sure exactly what - probably a stylized quotation mark for the non-CTL font. It should never do that.
Also, even if it doesn't make the replacement - it should actually replace the apostrophe with a Geresh character (or replace on condition that the Hebrew font has a glyph for it).
Steps to Reproduce:
1. Set your CTL font to a Hebrew font with a clear difference between a single (opening) quotation mark and a Geresh.
2. Enable single-quote autocorrect
3. Switch paragraph direction to Hebrew
4. Switch the input language to Hebrew
5. Type in רח' האלון 123.
The apostrophe either stays as-is (U+0x27), or is replaced with a single opening quotation mark (U+0x2019)
The apostrophe is replaced with a Geresh (U+0x5F3)
User Profile Reset: No
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
While this bug is a real one, I'm setting the priority to low as this doesn't prevent anyone from using LibO. Also, Hebrew has more important usability and language support issues.
** 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 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!
Created attachment 147775 [details]
Document facilitating reproduction and identificaiton of the bug
The attached document has some fonts and directions set manually, and a region for you to reproduce the bug by typing רח' האלון 123 while single-quote autocorrect is on. It also has the ideally-expected and actually-expected results below the region intended for typing.
This issue still manifests with:
Build ID: d1b41307be3f8c19fe6f1938cf056e7ff1eb1d18
CPU threads: 4; OS: Linux 4.9; UI render: default; VCL: gtk3;
Locale: en-US (en_IL); UI-Language: en-US
and will continue to manifest forever unless something is done about it, because it's a mis-feature rather than a bug.