Hi Christian,
If I understood you correctly, you already have all data, you just didn't
setup infrastructure to collect them (IP geolocation and UI locale from
header).
When/If you ever decide to collect that data, I don't think real user
number can diviate much from that.
Default setup are weekly pings. My guess is that very few people change
that, it cannot be more then 1-2%.
If you calculate your data on weekly (monday to sunday) basis, after few
months of collecting data, you should know inside few % of statistical
error what is your user count.
Only big difference in numbers can be with large deployments behind
firewall (government?), which will block all ping update requests.
Anyway, do I need to suggest this somewhere or open an bug?
Best regards,
Mihovil
13.10.2014 u 14:34, Christian Lohmaier je napisao/la:
Hi *,
...
i.e. it would be possible to create in future reports for
* geolocation
* UI-locale from request-header
but not
* list of actually installed locales
for that the BundledLanguages parameter would need to change or
additional one would have to be introduced.
ciao
Christian
--
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
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.