Re: [libreoffice-l10n] l10n process, en_US version, Help files
Hi Sophie, all, thank you very much for this initiative - it is really needed. My few notes: *After RC1 and l10n integration - we need to know when integration is made after our fixes, there is currently no communication on this This can be found in the log of translations git module: http://cgit.freedesktop.org/libreoffice/translations - but that doesn't solve the several typos that already exist and that are overlooked by the l10n team (e.g in the Character Font Effect dialog, there is Overline _c_olor and Underline _C_olor and this is the same for several dialogs) It would be worth to create a wiki page that summarizes all these rules - LO should use the Gnome rules (AFAIK), but there is a lot of specific issues: for example, descriptions of Calc functions in UI are quite messy because of different wording (Returns..., Calculates..., Value of...) or parameter names (capitalization etc.). Of course the UX team should be also involved. * About the help files - I always wonder why there is a Help button on a new dialog when no help file is appended ;) - more and more functions are undocumented or their help is obsolete. I always think that an undocumented function is lost for the user and a sad thing for a developer because his function will not be used as expected. May be, but I don't know how heavy it would be for developers, the solution would be to open an issue with a special tag like NF for each new feature, with three lines about what the feature is supposed to do. Searching on BZ with this special tag would allow to involve more people in the loop to test it and document it. I would suggest a simpler approach without need for any additional input from developers. We can use release notes wiki pages where all new features are mentioned, create a list of new features and check if they are covered by the help. Best regards, Stanislav -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Re: l10n process, en_US version, Help files
On 2013.12.12. 0:35, Robinson Tryon wrote: On Wed, Dec 11, 2013 at 11:19 AM, Sophie gautier.sop...@gmail.com wrote: *After RC1 and l10n integration - we need to know when integration is made after our fixes, there is currently no communication on this Perhaps documenting the process in some pages on the wiki would help i10n better-understand how this works, and lead to some simple ways to better communicate what's going on elsewhere back to the i10n teams. There is the http://wiki.documentfoundation.org/ReleasePlan Tag is usually made on Tuesday. So translation commit happens about a day before that, let's say on Monday. So your fixes from Sunday will be in. This is how it worked, when I did this job, and AFAIK Cloph does the same. Best regards, Andras -- To unsubscribe e-mail to: l10n+unsubscr...@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
[libreoffice-l10n] Re: l10n process, en_US version, Help files
Hi Andras, all, Le 12/12/2013 11:18, Andras Timar a écrit : On 2013.12.11. 17:19, Sophie wrote: *About the en_US overall quality - the process to rely on the l10n team to fix the en_US version is ok, even if it gives us extra work to understand what is meant before we realized it's a mistake. So it's also error prone for all the translations. Discissions in this mailing list usually helped to clarify the meaning. Failing that, git log / git blame -- find out who the author was and ask him or her. Translators are welcome to test new features, sometimes it is obvious what a function does, despite the confusing UI text. and sometimes not because you may also translate the product without being an experienced user, or simply because you use Writer but not Calc, etc... - but that doesn't solve the several typos that already exist and that are overlooked by the l10n team (e.g in the Character Font Effect dialog, there is Overline _c_olor and Underline _C_olor and this is the same for several dialogs) If it's overlooked by 60+ active translation teams + beta testers, then probably it is not that much important. We can live with it. :) Not sure, as Khaled said, it may be because the load of work on translation is enough to not take care of other things. * About the help files - I always wonder why there is a Help button on a new dialog when no help file is appended ;) Probably it is prescribed by some rule, e.g. Gnome HIG, that every dialog must have a Help button. So dialog creator application puts it there, and the developer leaves it there thinking that someone may write a help page for it later. Well, may be, but unfortunately the help page is never created. - more and more functions are undocumented or their help is obsolete. I always think that an undocumented function is lost for the user and a sad thing for a developer because his function will not be used as expected. As I wrote above, many functions/new dialogs are self-describing. I hated to translate Gnome help 10 years ago, which was full of sentences like this: Click on Close button to close the dialog. So we need to limit the scope here. It would be good, if you could give examples, what needs further clarification in help. They may be self describing for you, but not for most of our users. I've collected some issues where the help needs to be amended or is missing, but it would be better to have a general process and try to include more people in it. May be, but I don't know how heavy it would be for developers, the solution would be to open an issue with a special tag like NF for each new feature, with three lines about what the feature is supposed to do. Searching on BZ with this special tag would allow to involve more people in the loop to test it and document it. The problem is that you cannot enforce any rule to developers. You can write a mail to the list, newcomers will not see it. You can write wiki pages, some people will not read it. You can ask people individually, some will ignore you. That I know :) But I have an idea. What about prolonging the string freeze date of help until the first bug fix release? That would give developers/help authors/translators more time to concentrate on documentation of new features. So we could say, with x.y.0 you get all new features, and x.y.1 will come with updated help. That's a good idea, but we still need help authors. I'm sure some people will jump in, even earlier, if they only know where, hence the proposal for a dedicated issue. As I said in another mail, I don't want to add more processes, rules, etc. But there is some areas that impact more than one team where it would be good to have some worflows. Cheers Sophie -- To unsubscribe e-mail to: l10n+unsubscr...@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
[libreoffice-l10n] Re: l10n process, en_US version, Help files
Hi Sophie, *, On Wed, Dec 11, 2013 at 5:19 PM, Sophie gautier.sop...@gmail.com wrote: [...] *Before updating Pootle: - it's important for l10n team to know the approx load of work that will be needed to achieve the whole work. Time between beta1 and rc1 is short and that will help to better organize this time between translation and proof reading. - depending also on the type of changes, we could use different tools to optimize the work. Don't think this applies to a new minor version, as a new project is created, the old one just renamed, so you immediately see in the new project how much work is left. And only with that info you can decide what meaningful way there is to minimize actual translation work. *When the l10n start: - we need a continuous communication and a planing of the updates made in Pootle, those translating off line are always frightened to lose something in the run. - it's exhausting when you think you are over and to see a new bunch of words coming. Knowing it in advance help to manage the time too Yes, of course, and let me reiterate: I did not update any templates in December. Whoever else did update them did so without prior notice. I fully agree that before templates are updated l10n teams should be warned. (but then again, I don't consider adding a new project as updating templates in this regard - if the new data is wrong, just copy from the old project, no loss, no additional work, no mixup with offline translations) *After RC1 and l10n integration - we need to know when integration is made after our fixes, there is currently no communication on this For every build it is the same: Translations are extracted from pootle on Tuesday and committed before tagging. Deadline for each tag is Monday. So if you add your changes on Monday, all is fine, your translations will be included. If you wait till Tuesday, your changes might be missed. The release schedule overview is available here: https://wiki.documentfoundation.org/ReleasePlan or more detailed for the next relevant releases: https://wiki.documentfoundation.org/ReleasePlan/4.2#4.2.0_release https://wiki.documentfoundation.org/ReleasePlan/4.1#4.1.5_release There you see the dates for the relevant releases, and also in the case of a new feature release the UI and string freeze dates. If you look at the 4.2.0 schedule, you see that English string freeze is next week (Monday, Dec 16) - so that is the week I did plan for updating the templates in pootle. I will grab the translations on Tuesday as for every build, (that way there is a copy of the transations in the sourcecode, in case something goes wrong with updating the templates), and after that would add the new templates to pootle for l10nprojects to update. Then l10n projects have a month to adapt to those late changes. == for these three items, I have asked today to Andras and Christian how we can put that in place and where I can help them to do so, knowing also that Christian is managing this part almost alone now. Yes, 4.2.0 was the first time I did update the projects in pootle, and I personally think it was not a huge desaster. There were two stumbling stones: 1) update_against_templates aborting because of added/renamed files 2) lots of changes in help that only affect metadata (the xml-tag attributes), not the actual translations first was causing only a fraction of the changes to show up, leading to the impression that almost nothing changes, and after that was fixed, the second one caused a huge string count to be displayed, probably making some translators think that suddenly their translations were deleted or something, since after 1) they thought they were almost finished. 2) was fixed with a script shortly afterwards, leaving only the real changes to process. Now what happened in December is a completely different story, esp. that kk project did end up having Greek translation is still a mystery, but not related to any updates. *About the en_US overall quality - [...] - but that doesn't solve the several typos that already exist and that are overlooked by the l10n team (e.g in the Character Font Effect dialog, Those that have been reported on the list have been fixed by Andras or me in the code - and people are very welcome to upload a patch to gerrit themselves. ( https://wiki.documentfoundation.org/Development/gerrit ) - that doesn't solve also the lack of universal vocabulary used in several dialogs (e.g Tab/Pane/Panel/Deck to name the same object or Graphic/Picture/Image). I've nothing to propose here but to define a glossary where developers could pick the good word but I'm not sure it will be used Graphic/Picture/Image is for example one of the changes that have already been somewhat unified for 4.2 - but yes, a terminology/glossary doesn't really exist. * About the help files [...] May be, but I don't know how heavy it would be for developers, the solution would be to open an issue with a special tag
Re: [libreoffice-l10n] Re: l10n process, en_US version, Help files
Hi *, On Wed, Dec 11, 2013 at 7:29 PM, Sophie gautier.sop...@gmail.com wrote: Le 11/12/2013 19:24, Thomas Hackert a écrit : [...] would this discussion not more suitable after the 4.2 release ;? Only answering your question: nope, because 4.3 is already on the radar, so that would be great to have something in place for it :) And of course memory is still fresh, so people remember what bugged them :-)) ciao Christian -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Re: l10n process, en_US version, Help files
Hi Christian, On 2013.12.12. 13:56, Christian Lohmaier wrote: Yes, 4.2.0 was the first time I did update the projects in pootle, and I personally think it was not a huge desaster. There were two stumbling stones: 1) update_against_templates aborting because of added/renamed files 2) lots of changes in help that only affect metadata (the xml-tag attributes), not the actual translations And one issue remained, there are more files in the database, than actually needed, obsoleted files were not cleaned up (e.g. android/ folder). Now what happened in December is a completely different story, esp. that kk project did end up having Greek translation is still a mystery, but not related to any updates. And Greek has Kazakh fuzzies, as Dimitris reported yesterday: Why in the file of Greek sc/source/ui/src, I see so many Cyrillics with work needed? Was there a mistake? When I maintaned Pootle, I was also scared about possible database corruption, and since 2.5.0 we are experiencing mysterious server errors, e.g. when changing permissions on folders. TDF pays a monthly fee to Pootle devs for maintenance. I don't know, if you have worked with them, Christian. (I sent you a mail about Pootle 2.5.1 and/or Django update a few days ago.) Cheers, Andras -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Re: l10n process, en_US version, Help files
Hi Christian, Le 12/12/2013 13:56, Christian Lohmaier a écrit : Hi Sophie, *, On Wed, Dec 11, 2013 at 5:19 PM, Sophie gautier.sop...@gmail.com wrote: [...] *Before updating Pootle: - it's important for l10n team to know the approx load of work that will be needed to achieve the whole work. Time between beta1 and rc1 is short and that will help to better organize this time between translation and proof reading. - depending also on the type of changes, we could use different tools to optimize the work. Don't think this applies to a new minor version, as a new project is created, the old one just renamed, so you immediately see in the new project how much work is left. And only with that info you can decide what meaningful way there is to minimize actual translation work. That doesn't apply to minor version, but for major version where we have only few new strings and the rest is xml manipulations. I've discovered that translation tools handle this very differently so knowing before the new strings versus what we have already in our TM or commented in the po files, etc... imho would help. But this may be simply not possible for you, I'm not enough technical to know, which is why I ask :) *When the l10n start: - we need a continuous communication and a planing of the updates made in Pootle, those translating off line are always frightened to lose something in the run. - it's exhausting when you think you are over and to see a new bunch of words coming. Knowing it in advance help to manage the time too Yes, of course, and let me reiterate: I did not update any templates in December. Whoever else did update them did so without prior notice. I fully agree that before templates are updated l10n teams should be warned. (but then again, I don't consider adding a new project as updating templates in this regard - if the new data is wrong, just copy from the old project, no loss, no additional work, no mixup with offline translations) Yes, and again, this is discussion is by no mean to point somebody mistake, but only to enhance our process and our communication. *After RC1 and l10n integration - we need to know when integration is made after our fixes, there is currently no communication on this For every build it is the same: Translations are extracted from pootle on Tuesday and committed before tagging. Deadline for each tag is Monday. So if you add your changes on Monday, all is fine, your translations will be included. If you wait till Tuesday, your changes might be missed. The release schedule overview is available here: https://wiki.documentfoundation.org/ReleasePlan or more detailed for the next relevant releases: https://wiki.documentfoundation.org/ReleasePlan/4.2#4.2.0_release https://wiki.documentfoundation.org/ReleasePlan/4.1#4.1.5_release There you see the dates for the relevant releases, and also in the case of a new feature release the UI and string freeze dates. If you look at the 4.2.0 schedule, you see that English string freeze is next week (Monday, Dec 16) - so that is the week I did plan for updating the templates in pootle. I will grab the translations on Tuesday as for every build, (that way there is a copy of the transations in the sourcecode, in case something goes wrong with updating the templates), and after that would add the new templates to pootle for l10nprojects to update. Then l10n projects have a month to adapt to those late changes. Ok, I'll add this to our l10n pages so new comers know how it works. == for these three items, I have asked today to Andras and Christian how we can put that in place and where I can help them to do so, knowing also that Christian is managing this part almost alone now. Yes, 4.2.0 was the first time I did update the projects in pootle, and I personally think it was not a huge desaster. me too, be sure and thanks a lot for your work :) There were two stumbling stones: 1) update_against_templates aborting because of added/renamed files 2) lots of changes in help that only affect metadata (the xml-tag attributes), not the actual translations first was causing only a fraction of the changes to show up, leading to the impression that almost nothing changes, and after that was fixed, the second one caused a huge string count to be displayed, probably making some translators think that suddenly their translations were deleted or something, since after 1) they thought they were almost finished. 2) was fixed with a script shortly afterwards, leaving only the real changes to process. ok, thank you for the details Now what happened in December is a completely different story, esp. that kk project did end up having Greek translation is still a mystery, but not related to any updates. *About the en_US overall quality - [...] - but that doesn't solve the several typos that already exist and that are overlooked by the l10n team (e.g in the Character Font
Re: [libreoffice-l10n] l10n process, en_US version, Help files
Hi, 2013/12/12 Andras Timar tima...@gmail.com It is OK to fix new strings, also it is OK to fix obvious typos anywhere. But we should refrain from re-phrasing old messages. It would make a lot of unnecessary work for translators, and loss of translation for unmaintaned languages. IMHO we have more important things to do, than unify (Returns..., Calculates..., Value of...) or (cannot, couldn't, could not) or whatever. I just meant to use rules for new strings, not to make revolution in current translations. At least not for now, when we are frustrated by all the changes due to .ui conversion and when Pootle has no translation memory. However, the current state is far from what you describe: we resubmit translations for options pricing (first letter capitalized), graphics changed to images, change in reset filter... And I'm sorry, but volunteers can't be forced to do more important things - they do what they like/are able to do; and it should be clearly said what is desired and what isn't. Best regards, Stanislav -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Typo in Calc and one question related to Base/Writer
Hi Mateusz, On Monday, 2013-12-09 14:12:21 +0100, Mateusz Zasuwik wrote: Cumulated. TRUE calculates the probabilty mass function, FALSE the cumulative distribution function. probabilty probability Thanks, fixed in master and 4-2 source, should be available after next Pootle update. Eike -- LibreOffice Calc developer. Number formatter stricken i18n transpositionizer. GPG key ID: 0x65632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A Support the FSFE, care about Free Software! https://fsfe.org/support/?erack -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Typo in Calc and one question related to Base/Writer
Hi Mateusz, On Monday, 2013-12-09 14:12:21 +0100, Mateusz Zasuwik wrote: Is it translatable? https://translations.documentfoundation.org/pl/libo_ui/officecfg/translate.html#unit=48540897 That Base: Database Form like all those other Base: ... are UI names, so yes, translatable. https://translations.documentfoundation.org/pl/libo_ui/sw/translate.html#unit=48540980 That's odd, they look like identifier labels, but apparently are not. I _think_ they are translatable, and originally maybe should had been named something like context width, tile X position, ... but I'm not sure, there might be some context I'm not aware of, maybe these are used as technical terms related to tile rendering. But it might also be lazyness of the original author ;-) Eike -- LibreOffice Calc developer. Number formatter stricken i18n transpositionizer. GPG key ID: 0x65632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A Support the FSFE, care about Free Software! https://fsfe.org/support/?erack -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Typo in Calc and one question related to Base/Writer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Em 12-12-2013 14:36, Eike Rathke escreveu: https://translations.documentfoundation.org/pl/libo_ui/sw/translate.html#unit=48540980 That's odd, they look like identifier labels, but apparently are not. I _think_ they are translatable, and originally maybe should had been named something like context width, tile X position, ... but I'm not sure, there might be some context I'm not aware of, maybe these are used as technical terms related to tile rendering. But it might also be lazyness of the original author ;-) Eike This one was marked translatable by mistake. Andras removed it from translation yesterday. - -- Olivier Hallot Founder, Board of Directors Member - The Document Foundation The Document Foundation, Kurfürstendamm 188, 10707 - Berlin, Germany Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts Legal details: http://www.documentfoundation.org/imprint LibreOffice translation leader for Brazilian Portuguese +55-21-8822-8812 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSqedeAAoJEJp3R7nH3vLx05wH/3hJ/G/4hhTRT/j1906e+wrN LEjnn7GmnLtZYUSVAj8xMczXf2nFC3YlNmjycmGu/eu6vysnYVDcf4S4vk7h+jk3 cdqKoUzIoIsec0itBAP1KDTX4Xgv8ZxoMHUujQSPMAjtRdsbAuG+ikq2wgSTzdpD JGqOWwNmVXA5l/PGdJQshoIcxY02ZqAG63gXGV3qWkY79aJ/e2J494cjtHf/PXin h+M2JDcFBnKN5mjVihsuPKdfD/Onyy4jvGwpBhzXFPfYRM6HYbWuV3RzgcTtRexf VzdWpO1KxKQXPDANp41FSq3eYdq6oV9ASdHmtNPh+cqX5RmydALUG0zHCK4EnZ4= =brdr -END PGP SIGNATURE- -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Typo in Calc and one question related to Base/Writer
Hi Eike, Sorry for postig unrelated issue here but can you have a look on this issuehttps://bugs.freedesktop.org/show_bug.cgi?id=67205 ? It´s Calc and OpenFormula related so I this you´re the one to contact. Regards 2013/12/12 Eike Rathke er...@redhat.com Hi Mateusz, On Monday, 2013-12-09 14:12:21 +0100, Mateusz Zasuwik wrote: Cumulated. TRUE calculates the probabilty mass function, FALSE the cumulative distribution function. probabilty probability Thanks, fixed in master and 4-2 source, should be available after next Pootle update. Eike -- LibreOffice Calc developer. Number formatter stricken i18n transpositionizer. GPG key ID: 0x65632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A Support the FSFE, care about Free Software! https://fsfe.org/support/?erack -- To unsubscribe e-mail to: l10n+unsubscr...@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 -- Sérgio Marques -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Typo in Calc and one question related to Base/Writer
Hi Sérgio, On Thursday, 2013-12-12 16:55:23 +, Sérgio Marques wrote: issuehttps://bugs.freedesktop.org/show_bug.cgi?id=67205 Done. Eike -- LibreOffice Calc developer. Number formatter stricken i18n transpositionizer. GPG key ID: 0x65632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A Support the FSFE, care about Free Software! https://fsfe.org/support/?erack -- To unsubscribe e-mail to: l10n+unsubscr...@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
[libreoffice-l10n] [ANN] LibreOffice 4.1.4 RC2 available
Dear Community, The Document Foundation is pleased to announce the second release candidate of LibreOffice 4.1.4. The upcoming 4.1.4 will be the fourth in a sequence of frequent bugfix releases for our feature-packed 4.1 line. Please be aware that LibreOffice 4.1.4 RC2 is not been flagged as ready for production use yet, you should continue to use LibreOffice 4.1.3 for that. The release is available for Windows, Linux and Mac OS X from our QA builds download page at http://www.libreoffice.org/download/pre-releases/ Should you find bugs, please report them to the FreeDesktop Bugzilla: https://bugs.libreoffice.org A good way to assess the release candidate quality is to run some specific manual tests on it, our TCM wiki page has more details: http://wiki.documentfoundation.org/QA/Testing/Regression_Tests#Full_Regression_Test For other ways to get involved with this exciting project - you can e.g. contribute code: http://www.libreoffice.org/get-involved/developers/ translate LibreOffice to your language: http://wiki.documentfoundation.org/LibreOffice_Localization_Guide or help with funding our operations: http://donate.libreoffice.org/ A list of known issues and fixed bugs with 4.1.4 RC2 is available from our wiki: http://wiki.documentfoundation.org/Releases/4.1.4/RC2 Let us close again with a BIG Thank You! to all of you having contributed to the LibreOffice project - this release would not have been possible without your help. On behalf of the Community, Christian -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Typo in Calc and one question related to Base/Writer
Hi Eike, Thanks for your commits. Regards 2013/12/12 Eike Rathke er...@redhat.com Hi Sérgio, On Thursday, 2013-12-12 16:55:23 +, Sérgio Marques wrote: issuehttps://bugs.freedesktop.org/show_bug.cgi?id=67205 Done. Eike -- LibreOffice Calc developer. Number formatter stricken i18n transpositionizer. GPG key ID: 0x65632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A Support the FSFE, care about Free Software! https://fsfe.org/support/?erack -- To unsubscribe e-mail to: l10n+unsubscr...@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 -- Sérgio Marques -- To unsubscribe e-mail to: l10n+unsubscr...@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
