Hmm... I should have checked that before posting. I usually just run my
own build version on Linux,
I just assumed that they would have qtz-builds at least for master, but
it seems they don't. :(
You can however find qtz-builds of 5.0.0.0.beta3:
https://downloadarchive.documentfoundation.org/libreoffice/old/5.0.0.0.beta3/deb/
The KeyIDs should correspond to what is in LibreOffice 5.
I'll ask on IRC tomorrow if there are any KeyID-builds available for
Linux as daily builds,
or if not if there could be in the future.
Don't forget do do a parallel install:
https://wiki.documentfoundation.org/Installing_in_parallel/Linux
Regards,
Niklas Johansson
Den 2015-10-03 kl. 19:47, skrev Mihovil Stanić:
I'm searching for this, but can't find.
Using Linux Mint, would like to get that language pack to get key IDs.
Your script is working perfectly!
24.09.2015 u 14:42, Niklas Johansson je napisao/la:
The dialy builds of LibreOffice should contain the KeyID version (has
the
language code qtz)
http://dev-builds.libreoffice.org/daily/
/Niklas
--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- Re: [libreoffice-l10n] Basic tool to detect duplicate use of accelerator keys in menus (continued)
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.