https://bugs.freedesktop.org/show_bug.cgi?id=39439
Michael Meeks <michael.meeks@collabora.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
CC| |cloph@cup.uni-muenchen.de
--- Comment #11 from Michael Meeks <michael.meeks@collabora.com> ---
Wow: this is awesome ! :-)
I entered "Format code" (eg. a string from the Calc format dialog) and it took
me straight to the code:
That's awesome =) Thanks 1 Cloph may have some idea of how we can host this -
perhaps put it on the same machine as OoenGrok ?
Is the code hosted somewhere ?
Also - I think we should have a small piece of text that says: F_o_o (with the
o underlined) is mangled as 'F_oo' to help people search for strings with
accelerators.
Because of all the changes and the inital request, I am not sure this is
what you expect. Don't mind to provide use cases so I can improve my work.
Looks brilliant to me ! =)
There are other cases like menu items that we should prolly handle differently:
there we need to search more deeply: in the officecfg to find a string, map
that to a .uno:Foo thing, then map that to an SID_FOO_BAA_URL thing and onwards
to SID_FOO_BAA into the code ...
But this is a great start!
Cloph - whom should we poke wrt. hosting it ? [ and thanks Mat ]
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Bug 39439] Web search for UI strings · bugzilla-daemon
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.