涅槃 is valid as simplified Chinese. Although 槃 may be simplified as 盘 in some cases, but it should remain the same in 涅槃.
Where does this happen? Spell checker? Autocorrect?
Sorry, I was assuming it's obvious. It's about Chinese conversion from Traditional to Simplified Chinese.
It's in tool / language / Chinese conversion
Also, what OS and Desktop are you using--and which build of LibreOffice?
涅槃 (Nièpán) "Nirvana" is a concept and proper name from 佛教 (Fójiào) Buddhism, and my simplified dictionary shows it retains the traditional form of the name. Imagine there is a whole class of literary and liturgical terms that should not be simplified--but I have no idea how that is organized, or even what external module (i.e. Hunspell or LanguageTool or ???) provides the Chinese lexical support/conversion.
(In reply to V Stuart Foote from comment #4) > Also, what OS and Desktop are you using--and which build of LibreOffice? I believe the issue is unrelated to these. I thought "unspecified" is the right thing to specify, but come to think of it "Inherited form OOo" is more accurate. Sorry about that. I'm not a coder, but I wonder if having a look at Bug 46182 might help to find a solution to this. Can we mark this as NEW?
→ NEW it goes
Created attachment 128382 [details] OOo era design document for the Chinese language conversion tool (In reply to Kumāra from comment #6) > (In reply to V Stuart Foote from comment #4) > > Also, what OS and Desktop are you using--and which build of LibreOffice? > > I believe the issue is unrelated to these. I thought "unspecified" is the > right thing to specify, but come to think of it "Inherited form OOo" is more > accurate. Sorry about that. > As the project's code is modified to function on each OS--knowing the OS and Desktop environment (where applicable) helps us to confirm and reproduce issues. And importantly to identify where/when in the source things change. > > I'm not a coder, but I wonder if having a look at Bug 46182 might help to > find a solution to this. > Yes looks like "Inherited from OOo" is correct. The word lists provided for Chinese in stc_char.dic and stc_word.dic have received little adjustment since OOo era. One of the original design documents from 2004 for function of the tool is attached. Line 1176 of the stc_char.dic holds the pán entries for 盘 (U+76d8) and 槃 (U+69c3) What is unclear in the source is the relation between the single character conversion, and the bound form/word listing. Also, the syntax of the character and word list is a little unclear. niè 涅 (U+6d85), or more correctly nièpán 涅槃 has no entry in either the character or the word list--so IIUC the single replacement occurs. But it looks like it may be as simple as adding the literary and liturgical terms to the stc_word.dic with matching simplified and traditional values--as a "place holder"--to ensure that single character substitution does not occur. Of course there would be an upper limit to what the word table could hold. > Can we mark this as NEW? Certainly. =-ref-= http://opengrok.libreoffice.org/xref/core/i18npool/source/textconversion/genconv_dict.cxx http://opengrok.libreoffice.org/xref/core/i18npool/inc/textconversion.hxx http://opengrok.libreoffice.org/xref/core/i18npool/source/textconversion/data/stc_char.dic http://opengrok.libreoffice.org/xref/core/i18npool/source/textconversion/data/stc_word.dic
Thanks. Anything else I can do to help?
I'm changing the importance to minor. Reason: Although in officialdom, 涅槃 is regarded correct, I suspect 涅盘, being just a transliteration of "Nirvana" (Sanskrit) or "Nibbana" (Pali), may eventually be accepted through common usage, mainly due to precisely such a machine conversion.
** 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! Warm Regards, QA Team MassPing-UntouchedBug
I think we can forget this.