On Calc there is now an option to use the English function names: I think an option to use English names for Greek characters on Math expressions will be useful also, specially for those coming from LaTeX.
Isn't that the same than http://qa.openoffice.org/issues/show_bug.cgi?id=115956 ?
(In reply to comment #1)
> Isn't that the same than http://qa.openoffice.org/issues/show_bug.cgi?id=115956
No. It is just about the possibility to use, on a Spanish intall, %alpha instead of %alfa, or %mu instead of %my, for example. People coming from LaTeX will be thankful...
> No. It is just about the possibility to use, on a Spanish intall, %alpha
> instead of %alfa, or %mu instead of %my, for example. People coming from LaTeX
> will be thankful...
I always use english names for greek letters in OO and LO and have no problem with that. More over %alpha and %mu works for me but russian variants: %альфа and %мю don't work.
I think english names for greek letters is only good way.
Created attachment 42494 [details]
Screenshot for RGB
Screenshot with english names for greek letters.
Created attachment 42496 [details]
Greek character names on Spanish LibO build
At least the Spanish build have all the Greek character names translated... "%alpha" do not work :(
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
The feature requested is not implemented on 3.5 beta2.
*** Bug 55240 has been marked as a duplicate of this bug. ***
*** Bug 78397 has been marked as a duplicate of this bug. ***
Please read this message in its entirety before responding.
Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed.
If you have time please do the following:
1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer).
2) If it is present please leave a comment telling us what version of LibreOffice and your operating system.
3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System
Please DO NOT
1) Update the version field
2) Reply via email (please reply directly on the bug tracker)
3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link:
There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/.
Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material