Date: prev next · Thread: first prev next last
2016 Archives by date, by thread · List index


Hello @ll,
after stumbling upon 
https://bugs.documentfoundation.org/show_bug.cgi?id=104410, I was 
wondering if there are any plans to update the help files to fit the 
new changed menu entries at any time in the near future. 

After a short search in Bugzilla, I found Regina's bug 
(https://bugs.documentfoundation.org/show_bug.cgi?id=92825) which 
seems to become some kind of meta bug ... :( And then I found 
https://wiki.documentfoundation.org/Documentation/RecentStringChanges,, 
but both does not say about any plans to adapt the help files as 
well (and especially when this will happen, so we translators can 
prepare for the next flood of strings adequately ... ;) ).

Does anybody of you know a little bit more and can enlighten me, 
please? So I am able to answer something like "This will be fixed in 
x.y.z" to one of the next bugs I may find the next time ... ;)
TIA
Thomas.

-- 
I can't understand why people are frightened of new ideas.  I'm 
frightened of the old ones.
                -- John Cage


-- 
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


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.