Program Committee of the LibreOffice Conference 2019
Hi all, Like each year, we need a program committee to frame the tracks and vote on the papers for the LibreOffice conference. The committee will have to decide on the main topics of the conference, then read and decide on the talk proposals and set the program for the three days of conference together with the local team. This will be done during July and August. If you want to be part of the committee just answer here or send me a mail, be aware however that a high availability will be requested *during July and August*. We will need no more than 5 persons. Thanks in advance, Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: String "Document signed but not all files" in LO online
Hi Miklos, Le 21/12/2018 à 17:02, Miklos Vajna a écrit : > Hi Sophie, > > On Fri, Dec 21, 2018 at 11:21:48AM +0100, sophi wrote: >> Could you give us (l10n team) some context about this string ""Document >> signed but not all files are signed." Which files of the document is it? > > This is user interface for the same "partial signature" functionality, > which is available in core for a long time. include/sfx2/strings.hrc, > STR_SIGNATURE_PARTIAL_OK calls this "The signature is OK, but the > document is only partially signed". (I.e. "not all files signed" and > "document is partially signed" meant to refer to the same situation.) > > Tomaz, would it make sense to use the same strings in online and core > for this? Both just describe enumerators of SignatureState. Thanks a lot for your answer Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Reminder: CFP for LibOCon
Hi all, This is a reminder that the call for papers for the LibreOffice conference is still open until end of June. All information available from here: https://blog.documentfoundation.org/blog/2018/04/21/libreoffice-conference-call-for-paper/ Conference website will be soon turned on for information on the conference location, venue and practical info. In the meantime, if you have questions, don't hesitate to ping me. Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Program Committee for LibreOffice conference 2018
Hi all, Like each year, we need a program committee to frame the tracks and vote on the papers for the LibreOffice conference. The committee will have to decide on the main topics of the conference, then read and decide on the talk proposals and set the program for the three days of conference together with the local team. This will be done during July and August. If you want to be part of the committee just answer here or send me a mail, be aware however that a high availability will be requested *during July and August*. We will need no more than 5 persons. Thanks in advance, Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Moztrap question
Hi Pau, Le 29/11/2017 à 08:57, Muhammet Kara a écrit : > Hi Pau, > > As far as I know, Mozilla no longer uses Moztrap for testing their > products. They use Testrail instead: > https://wiki.mozilla.org/TestEngineering/Testrail And as a complement of Muhammet answer, we (LibreOffice) now use TestLink for manual testing. Kind regards Sophie > > Best, > Muhammet > > On 11/28/2017 12:40 PM, Campaña Soler Pau wrote: >> >> Hello. >> We are students of Aalto University, and we have to make an study of >> Thunderbird. We have seen that for the tests cases they use moztrap, >> but all the links of that webite are not working. We have also found in: >> >> https://wiki.documentfoundation.org/MozTrap/User_Guide >> >> that they also use manual test libreoffice, but we do not know how to >> register (https://manual-test.libreoffice.org/login.php?viewer=). Can >> you provide us a link to register or a username and passwoord just to >> see how it inside (we will not make any modification). >> >> If it is not posible, can you tell us if it is used by Thunderbird? >> >> Thanks, Pau. >> >> >> >> ___ >> LibreOffice mailing list >> LibreOffice@lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/libreoffice > > > > > ___ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/libreoffice > -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: A proposal for separate English localization
Le 16/10/2017 à 14:22, Kaganski Mike a écrit : > On 10/16/2017 3:16 PM, Sophie wrote: >> Hi Mike, >> >> Le 13/10/2017 à 23:31, Kaganski Mike a écrit : >>> Hello! >>> >>> Recently I was approached by members of our local community who manage >>> the translation of LibreOffice UI to Russian. I was told that they have >>> a regularly recurring problem, that each time a developer changes an >>> English string in LibreOffice UI, they have that string untranslated in >>> pootle, and need to repeat same actions again to re-translate it. What's >>> worse, the translation that pootle suggest in that case is oftentimes wrong. >> >> Please read the l10n list archives, this has already been discussed >> numerous times and the reason why it's not possible are clearly >> explained here. Same for the problems when typos are fixed in the >> source, and the current problem of scripting the changes. See my last >> mail with topic 'Please read'. Thanks >> Cheers >> Sophie >> > > Sorry Sophie, I cannot see how that mail is relevant here (I stressed > that it's not related to the gettext work), and how it explains the > impossibility of solution direction suggested. Would be most thankful if > you post a direct link to the mail you refer to (I looked at > https://listarchives.libreoffice.org/global/l10n/msg11231.html). This is not the oldest, there were previous discussions already: http://nabble.documentfoundation.org/Workflow-between-dev-UX-and-l10n-teams-td4136598.html Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: A proposal for separate English localization
Hi Mike, Le 13/10/2017 à 23:31, Kaganski Mike a écrit : > Hello! > > Recently I was approached by members of our local community who manage > the translation of LibreOffice UI to Russian. I was told that they have > a regularly recurring problem, that each time a developer changes an > English string in LibreOffice UI, they have that string untranslated in > pootle, and need to repeat same actions again to re-translate it. What's > worse, the translation that pootle suggest in that case is oftentimes wrong. Please read the l10n list archives, this has already been discussed numerous times and the reason why it's not possible are clearly explained here. Same for the problems when typos are fixed in the source, and the current problem of scripting the changes. See my last mail with topic 'Please read'. Thanks Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Awami Nastaliq and LibreOffice for Pakistan
Hi, Le 21/07/2017 à 10:32, Martin Hosken a écrit : > Dear All, > > I realise this is a bit of a sales pitch, but it's a mutual benefit pitch. > > SIL's Awami Nastaliq font has just been released > http://software.sil.org/awami/release-1-000. This is a nastaliq Arabic font > that, in combination with LibreOffice (since it's Graphite only) makes > LibreOffice the most powerful accessible word processing system for not just > Urdu but all the languages of Pakistan that use nastaliq. > > So if you are of know of users in that region, please let them know that they > now have the capability to produce nice looking text for free! > > BTW the font also works in FireFox. So you can put up webpages with it too. Thanks a lot for the information, I'm copying your mail to l10N list and other relevant lists. Kind regards Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Protect Ask against spam
Le 13/07/2017 à 10:23, Florian Effenberger a écrit : > Hello, > > Sophie wrote on 2017-07-13 at 10:13: >> Part is done already, user and IP are blocked and posts deleted. There > > thanks! > >> is no possibility regarding the posts withing a short time. > > Does AskBot support user blocking after x posts have been deleted, as > Regina suggests? Or is blocking always manually? Once a moderator decided it's a spammer, it's possible to block it automatically, the same for IPs. Cheers Sophie signature.asc Description: OpenPGP digital signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Protect Ask against spam
Le 13/07/2017 à 10:10, Florian Effenberger a écrit : > Hello, > > Thorsten Behrens wrote on 2017-07-11 at 15:49: >>> My personal favorites would be to block a user automatically after >>> two of his posts have been deleted, or to block a user, after he had >>> made two posts within a short time (2 min e.g.). >>> >> Was that discussed at the ESC in the end? But it sounds like an easy >> enough solution, to rate-limit spammers. > > is this configurable in AskBot already (cc'ing Sophie on this, she knows > quite some details about Ask) - if not, we need to fund implementation > and I can check with Evgeny about the costs. Let me know, Sophie. :-) Part is done already, user and IP are blocked and posts deleted. There is no possibility regarding the posts withing a short time. > > Given the reports about spam I hear, it seems to make a lot of sense > indeed. Cheers Sophie signature.asc Description: OpenPGP digital signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Protect Ask against spam
Le 11/07/2017 à 15:58, Michael Stahl a écrit : > On 11.07.2017 15:49, Thorsten Behrens wrote: >> Regina Henschel wrote: >>> My personal favorites would be to block a user automatically after >>> two of his posts have been deleted, or to block a user, after he had >>> made two posts within a short time (2 min e.g.). >>> >> Was that discussed at the ESC in the end? But it sounds like an easy >> enough solution, to rate-limit spammers. > > it was not, but i don't see what the ESC could do about that anyway; i > guess there's some TDF Infra meeting somewhere where this could be > discussed? I handled it with Evgeny Fadeev (Ask maintainer) already, problem was to find patterns in Korean, but with the help of the Korean team he should solve that soon. I'm currently moderating the instance every 2 hours or so. Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Protect Ask against spam
Hi Regina, Le 03/07/2017 à 12:33, Regina Henschel a écrit : > Hi all, > > can the ESC please discuss methods to protect Ask against spam? [And of > cause establish a solution, or suggest a solution to the board.] > > Read e.g. > https://ask.libreoffice.org/en/question/106719/spam-why-doesnt-someone-from-tdf-post-their-view/ > > https://ask.libreoffice.org/en/question/103981/anti-spam-measures/ I'm in charge of removing the spam and does it daily but not over the week-end. Evgeny Fadeev has been informed of the spam attack of these last days. Unfortunately, it's not easy to find a pattern when it's in Korean and I put him in contact with Korean speakers to help. > > My personal favorites would be to block a user automatically after two > of his posts have been deleted, or to block a user, after he had made > two posts within a short time (2 min e.g.). I block them and their IP, but the bot is faster than me. Sorry for the inconvenience. Kind regards Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Call for papers for LibOCon Roma
Hi all, For information, the call for papers for LibreOffice Conference in Roma has been published, you'll find it either on the blog or on the conference site: http://conference.libreoffice.org/2017/call-for-papers-3/ Let me know if you have any question. Kind regards Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Conference Program Committee
Hi all, The program committee is currently composed with Marina, Thorsten and Italo, does one of you with technical skills would be willing to be part of it? Note that you should be available during July and August where the votes will take place. Thanks a lot in advance, Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Localization issues related to telling users to update after submitting a crash report
Le 17/04/2017 à 00:47, Markus Mohrhard a écrit : > Hey, > > so I have been looking into the crashreporter and we are still seeing a lot > of crash reports for old versions. As we need to be able to deprecate the > support for older builds at some point we need a way to notify users that > reports for these versions are ignored and that they should use a newer > version. > > An example for this would be reports for all 5.2.x with x < 6 that are > still responsible for a huge part of the reports with 5.2.4 still around > 50% of the reports. > > Doing this is theoretical trivial and I already have some patches that > support this feature in future versions (sadly the 5.2.x versions have no > way to show the string from the server). My problem is now whether we need > to provide a localized version of this string. The string would come from > the server which currently has no translation support. In theory we know > the localization of the soffice instance that has submitted the crash > report but I'd like avoid adding many localized strings to the crash > reporter. > > Are there any objections against showing the generic update request instead > of a localized one when someone uses an old version? If there are no > objections I would implement this and try to get the necessary changes in > 5.4 and 5.3.3. I'm afraid it would be useless to show untranslated message, people won't be able to understand that they need to upgrade. Mike proposal would be a solution. Cheers Sophie -- Sophie Gautier, administrative assistant Tel: +33 683901545 | IRC: sophi on Freenode The Document Foundation, Kurfürstendamm 188, 10707 Berlin, DE Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts Legal details: http://www.documentfoundation.org/imprint ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: LibreOffice Conference 2017
Hi Shimon, Le 28/03/2017 à 16:23, Shimon Shore a écrit : > Hello, > > Are there any details available about the LibreOffice conference in Rome > September? > > I wanted to know: > > * The program The program will be set later, it should be available around July > > * Is there something planned for Tuesday September 26th (similar to > the conference in 2016)? Generally, we call it community day, there are workshops for l10n and NLPs, and sometimes other teams gather, it's not yet defined > > * Is there a charge for attending the conference? No, all the conferences are at no charge > > * Where exactly in Rome is the conference located? That should be very soon added to the conference site, the local team will add information about travel, accommodation and the venue on http://conference.libreoffice.org Kind regards Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Android app translation
Le 05/01/2017 à 16:05, jan iversen a écrit : > > >> ¡ >> It would be nice to use LO Android app in our language. Could we use >> Document Foundation's pootle server for translations? > > Already being used, have a look at > https://translations.documentfoundation.org/projects/android/ Necdet is the translator for those apps, so I think he was talking about LibreOffice itself and not the remote apps. Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Pootle upgrade and migration
Hi all, Pootle will be upgraded tomorrow at 11:00 Berlin time and the migration will last for about 24h. Please monitor status on http://status.documentfoundation.org/ I'll keep you informed on how it goes. Thanks for your patience and sorry for the inconvenience Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Wiki page for FOSDEM17 hackfest
Hello all, Fosdem17 hackfest page created, please add your name and what you'll work on, thanks! https://wiki.documentfoundation.org/Hackfest/FOSDEM2017 Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Content for the next Annual Report
Hi all, The next annual report will be soon at the door again, we need to feed it and believe me, it is greedy :-) So please fill the pad with your activities since the beginning of the year, it is really a great help for us in order to build a shiny and exhaustive report that represents all the parts of the community and the project achievements. Thanks a lot in advance for your help and your time :) Pad: http://pad.documentfoundation.org/p/annualreport Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-commits] core.git: sw/source
sw/source/core/undo/docundo.cxx | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
New commits:
commit 5059efab2f982daf041701165d15587794ffbfc7
Author: Sophie Su
Date: Sat Aug 27 10:59:53 2016 +0800
tdf#43157 clean up OSL_ASSERT in /core/sw/source/core/undo/docundo.cxx
Change-Id: I866ba17ffe82294758fd54c525c030eda1e0761a
Reviewed-on: https://gerrit.libreoffice.org/28418
Reviewed-by: Michael Stahl
Tested-by: Michael Stahl
diff --git a/sw/source/core/undo/docundo.cxx b/sw/source/core/undo/docundo.cxx
index dcab9bb..06a53f7 100644
--- a/sw/source/core/undo/docundo.cxx
+++ b/sw/source/core/undo/docundo.cxx
@@ -40,6 +40,7 @@
#include
#include
#include
+#include
using namespace ::com::sun::star;
@@ -64,7 +65,7 @@ UndoManager::UndoManager(std::shared_ptr const &
xUndoNodes,
, m_pDocShell(nullptr)
, m_pView(nullptr)
{
-OSL_ASSERT(m_xUndoNodes.get());
+assert(m_xUndoNodes.get());
// writer expects it to be disabled initially
// Undo is enabled by SwEditShell constructor
SdrUndoManager::EnableUndo(false);
@@ -271,13 +272,13 @@ UndoManager::StartUndo(SwUndoId const i_eUndoId,
SwUndoId const eUndoId( (i_eUndoId == UNDO_EMPTY) ? UNDO_START : i_eUndoId
);
-OSL_ASSERT(UNDO_END != eUndoId);
+assert(UNDO_END != eUndoId);
OUString comment( (UNDO_START == eUndoId)
? OUString("??")
: OUString(SW_RES(UNDO_BASE + eUndoId)) );
if (pRewriter)
{
-OSL_ASSERT(UNDO_START != eUndoId);
+assert(UNDO_START != eUndoId);
comment = pRewriter->Apply(comment);
}
@@ -313,12 +314,12 @@ UndoManager::EndUndo(SwUndoId const i_eUndoId, SwRewriter
const*const pRewriter)
if (nCount) // otherwise: empty list action not inserted!
{
-OSL_ASSERT(pLastUndo);
-OSL_ASSERT(UNDO_START != eUndoId);
+assert(pLastUndo);
+assert(UNDO_START != eUndoId);
SfxUndoAction *const pUndoAction(SdrUndoManager::GetUndoAction());
SfxListUndoAction *const pListAction(
dynamic_cast(pUndoAction));
-OSL_ASSERT(pListAction);
+assert(pListAction);
if (pListAction)
{
if (UNDO_END != eUndoId)
@@ -644,7 +645,7 @@ bool UndoManager::Repeat(::sw::RepeatContext & rContext,
return false;
}
SfxUndoAction *const pRepeatAction(GetUndoAction());
-OSL_ASSERT(pRepeatAction);
+assert(pRepeatAction);
if (!pRepeatAction || !pRepeatAction->CanRepeat(rContext))
{
return false;
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: cui/source
cui/source/tabpages/autocdlg.cxx |2 ++ 1 file changed, 2 insertions(+) New commits: commit 48e1f5028c5e507f1343bc695ec7e1079fd177cf Author: Sophie Su Date: Sun Aug 28 18:37:49 2016 +0800 tdf#9 in AutoCorrectDialog list also CJK languages if enabled Change-Id: If203511e6645848544895d2f0813f3f362a8e336 Reviewed-on: https://gerrit.libreoffice.org/28437 Reviewed-by: Eike Rathke Tested-by: Eike Rathke diff --git a/cui/source/tabpages/autocdlg.cxx b/cui/source/tabpages/autocdlg.cxx index 489ef2a..00363a5 100644 --- a/cui/source/tabpages/autocdlg.cxx +++ b/cui/source/tabpages/autocdlg.cxx @@ -114,6 +114,8 @@ OfaAutoCorrDlg::OfaAutoCorrDlg(vcl::Window* pParent, const SfxItemSet* _pSet ) if( SvtLanguageOptions().IsCTLFontEnabled() ) nLangList |= SvxLanguageListFlags::CTL; +if( SvtLanguageOptions().IsCJKFontEnabled() ) +nLangList |= SvxLanguageListFlags::CJK; m_pLanguageLB->SetLanguageList( nLangList, true, true ); m_pLanguageLB->SelectLanguage( LANGUAGE_NONE ); sal_Int32 nPos = m_pLanguageLB->GetSelectEntryPos(); ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
Sophie license statement
All of my past & future contributions to LibreOffice may be licensed under the MPLv2/LGPLv3+ dual license. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
蘇芃之 licence statement
All of my past & future contributions to LibreOffice may be licensed under the MPLv2/LGPLv3+ dual license. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: help about MozTrap
Hi Beyza, all Le 09/05/2016 23:49, Beyza Nur Esen a écrit : > hi, I'm Beyza nur. I'm first class at computer engineering and I'm > interested in libreoffice and I want to do something about it. As a > starter, I thought writing manuel test may improve me. I've been already > writing for a while and I'd like to pass it on MozTrap. If you could give > me access for MozTrap I can be an user and I may be useful. I talked about > it with Sophie before but I couldn't get a respond so I'm waiting for > reply, Thank you. Sorry for the delay and thank you very much for your implication. I'm following-up with you off list for the details on your test samples. Thanks again :) Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
LibOCon CFP published
Hi all, For information LibOCon CFP has been published: https://blog.documentfoundation.org/blog/2016/04/08/libreoffice-brno-conference-call-for-paper/ You have until the 15th of July to send it, but please don't wait until the last hour ;-) Thanks a lot in advance for your contributions! Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Cosmetic changes in help files
Hi Christian, Le 22/03/2016 12:13, Christian Lohmaier a écrit : > Hi Sophie, *, > > On Tue, Mar 22, 2016 at 11:44 AM, Sophie wrote: >> Dear developers, >> >> A reminder about dealing with help files and cosmetic changes: > > Despite what translators think and how they voice their opinion, > fixing syntax errors is not doing cosmetic changes. Well, you're right, sorry for the wrong word, but it has been there for so many years... > > Validation errors have been ignored for too long, time to weed that > out, whether translators like it or not. > We have validation checks in pootle for a reason. While some are less > useful than others, at least the xml-validility ones should be > respected. And if people don't know why a error is triggered, they > should use feedback functionality/ask on the list. > >> attributes removal such as oldref > > and this has been discussed already. (that's the cause for msg-context > changes and will be auto-fixed) > > Adding up already-told-to-be-autofixed with other occurences of fuzzy > strings won't make that double the amount of strings to fix. The request is to not have all at the same time, and at least have the l10n team informed about how that will impact them. If it has been there for years, then the changes could be spanned over several versions. The same way, we don't organize our time the same if we know that we will have a large amount of strings to review. If you tell us "ignore this file", we won't spend time to work on it. It's just about communication among groups, not to reproach anybody the work he has done and how legitimate it is, on the contrary each enhancement is welcome, but evaluating and leverage the impact on others work is also part of it. Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Cosmetic changes in help files
Dear developers, A reminder about dealing with help files and cosmetic changes: the l10n team is again impacted with thousands of changes (57k fuzzy strings that needs to be checked one by one) that doesn't concern them. Examples: has been changed to . or attributes removal such as oldref etc. Please, please before doing such changes, have a thought about the balance between the work you ask to the l10n team and the value of the change. If it's really necessary (I can understand cleaning of oldref, yes), write a script or ask for it and don't commit until you get it. In any case, drop a line to the l10n list so we can help without being under the impression that nobody cares :) Thanks in advance for your understanding, Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Can no longer login to ask.libreoffice.org
Hi Regina, I'm adding the website list on copy, I get the same issue and can't do the moderation, I don't know what is happening. Cheers Sophie Le 03/02/2016 15:53, Regina Henschel a écrit : > Hi, > > I try to login with my AskLibO user name and password. Neither the user > name regina nor the email rb.hensc...@t-online.de works. > > When I do "Recover account" I get an email with a link. I click the link > and I reach my account to enter a new password. I can enter the password > and then login is done. I can see my account informations. But when I > then logout and try to login again, the same happens. No login possible. > > I have tried it with different browsers and different PCs. > > I need help for login. Who is responsible for ask.libreoffice.org and > can look what is wrong with my account? > > Kind regards > Regina > ___ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Program Committee for LibOCon
Hi all, As each year, it's time to form the Program Committee. We need at least 3 or 4 persons available to review the talks proposed by the community, sort and organize them and then manage the conference program. *Important note*: you need to be available during July and August as these are the months during which we set the program. Thanks in advance to those volunteering Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: web site
Hi Alfieri, Le 21/01/2016 03:57, alfieri morillo a écrit : > Hello good evening, I am responsible for libreoffice Venezuela and its web, I > wonder if the theme used on its official website available for the use of > the web that we work through our websites occurs to me that we can all > use a single > subject as the default, I hope not bother, thank you very much! Reference I > leave the place I've been Thanks for supporting LibreOffice! You're posting on the developer list, best is to resent your message to the website list where the team will be able to help you with your request. Here is how to proceed to join the list: http://www.libreoffice.org/get-help/mailing-lists/ go to the webs...@global.libreoffice.org Kind regards Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Annual report reminder, participate now!
Hi all, This is a reminder that we will very soon begin to work on the annual report. If you have not done so yet, please fill the pad with any information that is relevant to the report and the community activities. Last year we had a very nice and interesting one, it was all due to your help in writing it, we hope to have even more to compile this year :) Thanks a lot in advance for your help! http://pad.documentfoundation.org/p/annualreport Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Google Mentor Summit report
Hi Cedric, Thanks a lot for your report, I've added it to the pad for our annual report here: http://pad.documentfoundation.org/p/annualreport Cheers Sophie Le 20/11/2015 17:26, Cedric Bosdonnat a écrit : > Hi all, > > I have attended the Google Mentor Summit on Nov. 6th - 8th. Here is a > short summary of what it has been for me. > > * As usual it has been a nice occasion to meet people from projects we > would never have met > * Had an interesting discussion on coala (http://coala-analyzer.org/) > * Discovered twitter search tool loklak (http://loklak.org/). I'm not > using twitter, but I'm sure this could be useful for someone ;) > * Interesting chat with openkeychain guys > * Good to meet Marcus and libvirt/qemu guys once again > * Had a session on virtualization/containers usage in opensource > projects. Our pre-built sources VM for hackfest has interested mariadb > people. Nothing really new on the topic other than that. > * Like every year, the chocolate and tea rooms where exceptional > * This year, Google hosted us in the TechCorner, that was at a walking > distance from the hotel: a really good point. > * Attended the lightning talks sessions: there are always crazy > projects during gsoc. > > -- > Cedric > ___ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice > -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: QA Meeting Minutes - 2015-10-21
Le 27/10/2015 16:28, Robinson Tryon a écrit : > On Tue, Oct 27, 2015 at 9:30 AM, Sophie wrote: >> Hi Robinson, >> Le 24/10/2015 09:37, Robinson Tryon a écrit : >>> Hi all, >>> >>> Thanks for the great QA Meeting on Wednesday! >>> >>> Minutes are here: >>> https://wiki.documentfoundation.org/QA/Meetings/2015/October_21 >>> >>> Our next meeting will be on the 28th, just a couple of days before the >>> BugHunting Session for LibreOffice 5.1. We'll go over any last-minute >>> updates for the weekend at that point: >>> https://wiki.documentfoundation.org/QA/Meetings/2015/October_28 >> >> I just saw in the log that the meeting was on 18:00 UTC, could you >> announce it next time, on the wiki it was still 13:00 UTC and I didn't >> read anything on the list about it. Thanks! > > Hi Sophie, > Sorry for the kerfuffle last week. The meeting this week will be the > usual: Wednesday, 13:00 UTC, in #libreoffice-qa: > https://wiki.documentfoundation.org/QA/Meetings/2015/October_28 Great, thanks :) Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: QA Meeting Minutes - 2015-10-21
Hi Robinson, Le 24/10/2015 09:37, Robinson Tryon a écrit : > Hi all, > > Thanks for the great QA Meeting on Wednesday! > > Minutes are here: > https://wiki.documentfoundation.org/QA/Meetings/2015/October_21 > > Our next meeting will be on the 28th, just a couple of days before the > BugHunting Session for LibreOffice 5.1. We'll go over any last-minute > updates for the weekend at that point: > https://wiki.documentfoundation.org/QA/Meetings/2015/October_28 I just saw in the log that the meeting was on 18:00 UTC, could you announce it next time, on the wiki it was still 13:00 UTC and I didn't read anything on the list about it. Thanks! Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: QA Meeting Minutes - 2015-10-21
Hi Robinson, Le 24/10/2015 09:37, Robinson Tryon a écrit : > Hi all, > > Thanks for the great QA Meeting on Wednesday! > > Minutes are here: > https://wiki.documentfoundation.org/QA/Meetings/2015/October_21 > > Our next meeting will be on the 28th, just a couple of days before the > BugHunting Session for LibreOffice 5.1. We'll go over any last-minute > updates for the weekend at that point: > https://wiki.documentfoundation.org/QA/Meetings/2015/October_28 Has the meeting changed its time or place? I was online at 13 UTC but didn't see anything on irc? Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
The annual report needs you!
Hi all, This is this time of the year where we need to complete the annual report. Please, take the time to write some lines about your own achievements, project and/or those of your project, community. We need to have an impressive annual report again and it's only because of you that it will reflect our vibrant community :) So, stop everything else and start writing here: http://pad.documentfoundation.org/p/annualreport You can add parts, subtitle, projects, anything you see that will be important for this report. Big thank you in advance! Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: - Extended tips in Helpcontent & VCL + Glade
Hi all, Thanks a lot for your work and explanations, I jump to the end: Le 26/08/2015 18:35, Markus Mohrhard a écrit : > Hey Olivier, [...] > > At least my patches to move the tooltips extracts them to simple java like > property files. You can easily process them from there. That format at > least easily allows us to keep all the existing translations and handle all > the corner cases that are currently not covered by ui files. Additionally > the agreement with the translators asks us to make sure that the extended > tooltips can be extracted into an own pootle project to keep them > independent of the normal UI translations. > > > I hope my points explain why all this is less of an technical problem and > more a social one where before you can do any work you need to convince the > people affected by your change to come to a common understanding. At least > your current proposal goes against the current agreement betwee Kendy, > Sophi, me and the translators. (It already took a long time to get that > far). I think we could go further now if we plan the changes largely in advance and if it would be possible to make the changes in 3 or 4 steps instead of a big one. Knowing it in advance will allow translators to organize their work between the different open source projects they contribute to. Olivier, we will discuss the help topic during the l10n workshop at LibOCon, would it be possible that you explain the process to the group during Tuesday afternoon? Then I'll discuss with the team to push the project further. Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Ease maintenance of build-in help
Hi Regina, Le 02/08/2015 19:06, Regina Henschel a écrit : > Hi all, > > I have started a new thread so that the problem is not hidden inside > other threads or in private mails. Thanks a lot for that > > First, is there consensus, that the current build-in help will be retained? Yes, it's the only documentation available for the different languages we offer to our users and in some countries, you are not allowed to deliver a software without translated build-in help. > > If not, then the following ideas are useless and starting would be waste > of time. In such case, please stop me immediately. > > I collect here some ideas from some threads and mails: > > A > Authors of help texts are allowed to start in ODF to discuss and > finalize the content and appearance of the intended help texts. There > should be a place in the repository to store such files. This way > authors did not need deep knowledge of the technical structure of > helpcontent2. The person who integrates the help texts into the build-in > help need not be the content author. > > B > Improve the extension "HelpAuthoring" and fix its bugs. The extension > might be principally not suitable to generate the final version of a > help file, but it is useful as start, because it sets a lot of the > needed XML-elements and attributes automatically. The result might still > needs additions and corrections, but that is less work, than writing all > from scratch. Even if someone do not know all details about the help, he > can start and deliver a file, which other then can improve and integrate. > > C > Provide a development section about the build-in help to the Wiki. It > should not only contain a tutorial about help authoring but in addition > a description how the current help works at all from a developer view, > and how it is actually structured. > We can start with the document "OOo2HelpAuthoring.pdf". The content has > to be revised and adapted and extended. For example the .mk files are > different than described in that document and the document describes the > possibilities of the help format, but not all details of the actual > realization. > Having it in the Wiki keeps such knowledge available, when a help expert > leaves the community. It can be adapted to future developments. Experts > of different areas can better work together to collect help knowledge in > one place, for example experts for "Help to Wiki" and experts for > "translating help". > > D > It would ease work, when there would be a tool, that shows a .xhp file > the same way as it it shown in the help viewer, so that it is not needed > to build helpcontent2 every time when you test some changes in your way > to the final version. And authors who use "HelpAuthoring" need not be > able to build LibreOffice. Again thanks for the details. I do not have time to participate much at the moment, but when the 5.0 will be out and the LibOCon organization more advanced, I would very much like to help where I can. Kind regards Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
If you attend LiboCon in Aarhus, please register now!
Hi all, If you plan to attend the conference, please register on the site here: http://conference.libreoffice.org/2015/registration/ We need it for security reasons, but also that will help a lot the local organization of the different days and events. You will then be subscribed to the conference@ mailing list and won't miss any important information hat we will publish there. Thanks a lot in advance :) Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: HelpAuthoring.oxt: An easy way to edit help files
Hi Kendy Le 3 juil. 2015 20:16, "Jan Holesovsky" a écrit : > > Hi Sophie, > > Sophie Gautier píše v Pá 03. 07. 2015 v 18:57 +0200: > > > > > Maybe we should merge the page you asked me to write some times ago > > https://wiki.documentfoundation.org/HelpContent So what should I do with that page? Delete or merge? > > > > I've begin to write a simplified guide more complete than what I wrote > > on the wiki > > Ah great - thanks! :-) I'll work on it in August if there is some interest > > > There is also the two extra files that will help to locate the help > > files to modify that we should decide where to put. > > No idea what they are for, can you explain? The extension seems to work > for me even without them, but I probably don't understand correctly how > exactly are they supposed to be used. The extensions doesn't need them. They were used by the help authors anb have been available for l10n purpose. As written in the wiki, one adds an index of the help files named as they appear in the sources. The second one add the tag IDs of the strings. These two files allow you to quickly locate the files you want to work on as the help page displays the full path of the file. The ID let you know if it's an embedded paragraph, a link or a full text and its type (section, text, title...), so the tag and the style you have to use when writing with the .oxt/template > > > Also is the modified template on git? > > There is some template in the .oxt itself that Olivier modified I think, > but best if you talk the details with him, he's done all the heavy > lifting there :-) Ok, the template I use works too, but I'll check with him. Cheers Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: HelpAuthoring.oxt: An easy way to edit help files
Hi Kendy, On Fri, Jul 3, 2015 at 5:39 PM, Jan Holesovsky wrote: > Hi, > > Olivier recently resurrected the HelpAuthoring.oxt extension that makes > it much easier to edit help files, and I've pushed that to git now: > > > http://cgit.freedesktop.org/libreoffice/contrib/dev-tools/tree/helpauthoring > > I don't want to announce it too widely yet, tough; it has a bug that > from some reason, the new edits appear in bold when saved (they appear > enclosed in / ). > Maybe I can have a look during the week-end. > > Olivier, anybody - can you please have a look why that happens? Cannot > do myself ATM :-( > > Once this is fixed, I hope the editing of Help will get much easier, and > we'll be able to get better coverage / higher quality Help even before > we convert to some better editable format. Some instructions how to use > it: > > https://wiki.documentfoundation.org/Documentation/Help > Maybe we should merge the page you asked me to write some times ago https://wiki.documentfoundation.org/HelpContent I've begin to write a simplified guide more complete than what I wrote on the wiki There is also the two extra files that will help to locate the help files to modify that we should decide where to put. Also is the modified template on git? > > Olivier - if you can make it to the next ESC, that would be great :-) > Thanks so much for making this happen! > Cheers Sophie > > -- Sophie Gautier GSM:+33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Registration for the conference is open!
Hi all, Registration for the conference is now open! Please do register if you plan to attend, it will help a lot the organization team. Registration page: http://conference.libreoffice.org/2015/registration/ General announcement: http://blog.documentfoundation.org/2015/07/02/registration-for-the-libreoffice-conference-is-now-open/ Thanks in advance :) Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Fwd: Call for papers: send your proposals!
Message transféré Sujet : Call for papers: send your proposals! Date : Tue, 16 Jun 2015 11:16:49 +0200 De : Sophie Pour : proje...@global.libreoffice.org , LibreOffice-l10n , des...@global.libreoffice.org , libo-marketing-p...@lists.documentfoundation.org Hi all, This is a reminder that the call for papers is still running. Please share your knowledge, achievements, ideas with the community, we are very interested to hear you! You have the choice between a presentation of 45 mn or one of 20 mn including questions and answers. You'll find all the details here: http://conference.libreoffice.org/2015/call-for-papers/ Don't hesitate to come back to me if you have any question or need help with your travel and accommodations. Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Fountain pen on front page of site
Hi Alexander, Le 26/05/2015 18:30, Alexander a écrit : > Hi, > > I want give idea about change "symbol" of LibreOffice from fountain pen to > actual, > modern or classic just and practical writing tool without any calligraphy. Thanks for your feedback, I'm forwarding your mail to the website list, the developer list being focused on product development. Kind regards Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Reviewers committee for the LibreOffice conference talks.
HI all, In order to prepare the CFP agenda and content, we need to have the reviewers committee in place now. Who would like to participate this year on reviewing the papers? Ideally we need someone for the Community track, someone for the Developers track and someone for the Marketing/Migration track The main tracks we usually have are here: http://conference.libreoffice.org/2014/talks/ *Note*: reviewers need to be available during the July and August. Thanks in advance Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Help me pls
Hi, Le 19/02/2015 17:50, Bjoern Michaelsen a écrit : > Hi, > > On Thu, Feb 19, 2015 at 10:57:42AM +0300, Kismabo adwa wrote: >> 1. I have downloaded the source code then how could i edit it( wht >> environment do i need to set up for building)? > > http://www.libreoffice.org/about-us/source-code/ > https://wiki.documentfoundation.org/Development/How_to_build > https://www.youtube.com/watch?v=2gIqOOajdYQ&hd=1 > > Should be a starting point. > >> 2. wht are the main tasks that i should to know about the localization? >> 3. we are working on pootle ,how does those gettext po files come out >> from the source? If you have a translation project, best is to join the l10n list http://www.libreoffice.org/community/localization/ We have a Pootle instance that serves either as a repository or a translation tool depending on what you prefer. We make .pot available too. But best is to continue on the l10n list, it's more appropriate. Kind regards Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org GSM: +33683901545 IRC: sophi Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Workflow between dev, UX and l10n teams
Hi, Le 30 janv. 2015 12:25, "Lionel Elie Mamane" a écrit : > > On Fri, Jan 30, 2015 at 12:14:04PM +0100, Bjoern Michaelsen wrote: > > On Fri, Jan 30, 2015 at 10:06:36AM +0100, Lionel Elie Mamane wrote: > > >> Interestingly, doing a web search for "pootle git synchronisation" > >> leads me to http://weblate.org/en/features/ >:-) > > > Well, once we dont require to be self-hosted anymore, > > https://translations.launchpad.net/ certainly would be an option too. However, > > IMHO there are very good reasons to be self-hosted with > > translations. > > From glancing at the webpage, Weblate is a software that we can host > ourselves. This is something the l10n team has already in his radar. But please, before changing our tool and our workflow, let's discuss at Fosdem with Dwayne from the Pootle team what we can achieve. Cheers Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: where do the canonical translations live, git or pootle
Le 29/01/2015 15:24, Christian Lohmaier a écrit : > Hi Caolán, *, > > On Thu, Jan 29, 2015 at 3:10 PM, Caolán McNamara wrote: >> On Wed, 2015-01-28 at 10:20 +0100, Stephan Bergmann wrote: >>> On 01/19/2015 11:03 AM, Sophie wrote: >> >> e.g. in the past changing the "Letter" size translation in Spanish to >> "Oficio" instead of the literal translation was a pain. And right now I >> want to fix a gadzillion Indic translations short-cuts to ascii chars >> and not characters that only available via IM. What I want to do is to >> commit to the translations git repo and forget about it. Does that >> work ? > > Nope, as on the next export from pootle those changes will be overridden > again. > > The changes need to be done in pootle. (not necessarily via web-UI, > that would be tedious, but the change needs to be reflected in pootle > to "stick"). Maybe this is something that I should document on the wiki, what happen betweeng git/pootle and source/targets. > > But as some languages use offline translation, even doing the change > in pootle might be undone when teams just upload their local copy > again without bothering to check for updates that were done in pootle. Well, when you're used to be alone to work on your language, you usually don't need to check for updates ;-) Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org Tel:+33683901545 Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Workflow between dev, UX and l10n teams
Le 28/01/2015 10:20, Stephan Bergmann a écrit : > On 01/19/2015 11:03 AM, Sophie wrote: >> - if there is a way to script changes, script them otherwise wait until >> there is a script available to commit them > > I am not sure I understand you here (to me, the "otherwise" part reads: > "if there is no way to script changes, wait until there is a script > available," which would not make sense). Sorry for being unclear, I mean if scripting is possible but the commiter don't know how to write the script, or have no time for it, wait until somebody else write it. Of course, if it's no scriptable, then no need to wait for a script :) > > When talking about (developer-side) scripting, is it actually OK to > commit modifications to the translations in the translations git > sub-repo? My understanding was that such modifications would be > overwritten by the next "import commit" (as typically done by Andras, > AFAIU from some Pootle database). I don't know, maybe Andras or Rimas will. Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org Tel:+33683901545 Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [libreoffice-l10n] Re: Workflow between dev, UX and l10n teams
Hi Rimas, all
Le 27 janv. 2015 19:32, "Rimas Kudelis" a écrit :
>
> Hi Jan,
>
>
> 2015.01.26 16:43, Jan Holesovsky rašė:
> > Mihovil Stanić píše v Po 26. 01. 2015 v 10:25 +0100:
> >
> >> Cosmetic changes (~ to _ or "Status" to "Status:" or ... to … or those
> >> different quote styles I don't even have on my keyboard) and anything
> >> similliar - NOT OK if you don't script it for all languages
> >> Cosmetic changes ("Big brown fox" -> "Big Brown Fox") - NOT OK at all,
> >> change just for en_us, don't change my strings and don't even notify me
> >> you did it in en_us
> > I see 2 problems here:
> >
> > 1) There is no tool that would detect these trivial changes, and would
> >act accordingly.
> >
> >
> > Regarding 1) - I thought that Pootle is detecting the trivial changes
> > some way, and offering the original translation. Is it not? What can
> > be done to improve that, so that for translators it is just a matter of
> > checking; not a matter of translating? [Or even what you suggest - that
> > it would just update the source strings without touching the
> > translations?]
>
> Pootle does offer the original translation, but the localizer still has
> to approve it.
>
> Furthermore, Pootle does not apply any automatic changes. If you had
> e.g. "Some ~string", and you change it to "Some _string", Pootle will
> show the original translation as a hint, but the user will still have to
> port this trivial change to the translation manually.
>
> Needless to say, sometimes these minor differences avoid being noticed
> by the localizers, which results in errors in the locale (I've seen
> incorrect access key identifiers in the menus at least once).
>
> However, while you are correct that there is no tool to detect these
> changes, I don't think there has to be. The person who implements the
> change knows better than anyone whether or not it can be automated,
> perhaps they even automated it themselves. For example, I seriously
> doubt that somebody went over all L10n files and changed triple dots to
> ellipses manually, this was most likely a scripted change. Same, or very
> similar, script would have probably worked with all other locales, but I
> guess that person simply didn't think about it.
>
> Similarly, changes in used quote characters most likely could have been
> isolated and transplanted to locales.
>
> Adding colons to certain strings only would probably have been slightly
> more difficult, but still scriptable.
>
> And none of that requires any "tool to detect trivial changes"... ;)
That's the point of this discussion, thanks Rimas to make it :-)
L10n team can always react, and earlier now, but making the scripting part
of the commit or part of the 'one making the change' is more natural in the
workflow. In other words, our product is not en_US only.
>
>
> > 2) The texts for translations are updated in big 'code' drops, without
> >possibility for translators to affect the process in any way - for
> >them it is too late.
> >
> >
> > Regarding 2) - I'm glad that you say that the strings will be now
> > getting to Pootle immediately after the code / string changes in master.
> > I think it is important that the translators will be able to deal with
> > the changes immediately, not several months later, so that they can
> > cooperate, and not only react.
> >
> > In general, I don't think that setting extremely strict rules works,
> > unless you have means how to enforce them - like via a commit hook or so
> > (and it is extremely unpopular way to do things).
> >
> > It is always much better to communicate - if you see a developer who
> > commits a change that causes you grief, please _do_ tell _him/her_
> > immediately, and - if possible - in a friendly way. I'm sure he/she
> > will do much better the next time.
> >
> > Unfortunately I did not see any signs of notice that this or that change
> > was problematic for localization on the development mailing list - were
> > there such warnings there? Like "commit XY caused AB - please don't do
> > such things, unless we agree how to do that effectively / without pain"?
> > Or was it impossible so far because the strings in Pootle were not
> > synced with master?
>
> I fully agree with you here, and yes, so far communicating these issues
> was really difficult because these massive changes appeared in front of
> the localizers' eyes way too late in the process.
What we should take care though is to not over complicate the work of l10n
team by relying on this fact. So as I already said, it should be a shared
work and vigilance by the concerned teams.
Cheers
Sophie
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Workflow between dev, UX and l10n teams
Hi Kendy, Le 26/01/2015 16:40, Jan Holesovsky a écrit : > Hi Sophie, > > Sophie píše v Po 26. 01. 2015 v 16:19 +0100: > >> Pootle will show you a modified string, even if it doesn't affect your >> translation you will have to validate the string again to have it on a >> translated state. Also we don't all work on Pootle, several of us are >> working off line and Pootle is only a repository for our files. > > But the offline files are taken from Pootle too - right? So if fixes > are done at the time of uploading to Pootle, everybody gets them - > correct? yes, I'll have a meeting with Dwayne (Pootle developer) during Fosdem and will discuss with him about that. > >> That's why we were thinking of a en_US version as a real language and >> different from the sources and > > But at some stage this will have to apply to the sources - and at that > time, it will be even worse than now :-( I'm afraid having en_US as a > separate language will make the situation worse, not better. Yes, I'm not sure either > >> also about scripting changes when >> possible (like the substitution of ~ by _) > > Sure - so I think this was something that could have been automatized > with a trivial script; when this was noticed for the first time, please? > Pity that it was not brought to the ESC as a problem... It was brought on the dev list, but when the l10n team discovered it, it was too late. Cloph has already scripted several changes, but he can't do it all. > >> Translators are for most of them non technical people and will not see a >> commit, but only the result on Pootle, sometimes months later. > > The "months later" is the problem, not the non-technicality :-) It is > enough to send "something happened yesterday - please check what's up"; > similarly to how people are checking the daily builds. that will be possible now that some of us are translating on master > >>> Also - should we have a 'Localization' recurring topic in the ESC? Who >>> would be the right representative there, please? >> >> Maybe not as a recurring topic, but something that should be in mind of >> UX team and developers when they commit or check for commits that have a >> huge impact on l10n. > > Well - if it's not recurring, it's easy to forget ;-) Also I think it > will be more effective to discuss this there - are you able to join this > Thursday? Thanks for the invitation and yes, let me know the time and I'll join. Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org Tel:+33683901545 Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Workflow between dev, UX and l10n teams
Hi Kendy,
Le 26/01/2015 15:43, Jan Holesovsky a écrit :
> Hi Sophie, Mihovil,
>
> Mihovil Stanić píše v Po 26. 01. 2015 v 10:25 +0100:
>
>> Cosmetic changes (~ to _ or "Status" to "Status:" or ... to … or those
>> different quote styles I don't even have on my keyboard) and anything
>> similliar - NOT OK if you don't script it for all languages
>> Cosmetic changes ("Big brown fox" -> "Big Brown Fox") - NOT OK at all,
>> change just for en_us, don't change my strings and don't even notify me
>> you did it in en_us
>
> I see 2 problems here:
>
> 1) There is no tool that would detect these trivial changes, and would
>act accordingly.
>
> 2) The texts for translations are updated in big 'code' drops, without
>possibility for translators to affect the process in any way - for
>them it is too late.
>
> Regarding 1) - I thought that Pootle is detecting the trivial changes
> some way, and offering the original translation. Is it not? What can
> be done to improve that, so that for translators it is just a matter of
> checking; not a matter of translating? [Or even what you suggest - that
> it would just update the source strings without touching the
> translations?]
Pootle will show you a modified string, even if it doesn't affect your
translation you will have to validate the string again to have it on a
translated state. Also we don't all work on Pootle, several of us are
working off line and Pootle is only a repository for our files.
That's why we were thinking of a en_US version as a real language and
different from the sources and also about scripting changes when
possible (like the substitution of ~ by _)
>
> Regarding 2) - I'm glad that you say that the strings will be now
> getting to Pootle immediately after the code / string changes in master.
> I think it is important that the translators will be able to deal with
> the changes immediately, not several months later, so that they can
> cooperate, and not only react.
yes, that's much better, even if we have to be cautious about the workflow.
>
> In general, I don't think that setting extremely strict rules works,
> unless you have means how to enforce them - like via a commit hook or so
> (and it is extremely unpopular way to do things).
>
> It is always much better to communicate - if you see a developer who
> commits a change that causes you grief, please _do_ tell _him/her_
> immediately, and - if possible - in a friendly way. I'm sure he/she
> will do much better the next time.
Translators are for most of them non technical people and will not see a
commit, but only the result on Pootle, sometimes months later. In the
same way the developer who is doing tons of changes for en_US is invited
to discuss them with the l10n team :)
>
> Unfortunately I did not see any signs of notice that this or that change
> was problematic for localization on the development mailing list - were
> there such warnings there? Like "commit XY caused AB - please don't do
> such things, unless we agree how to do that effectively / without pain"?
> Or was it impossible so far because the strings in Pootle were not
> synced with master?
Yes, I think it was too late and when the l10n team is at work, it's the
rush i.e RC time for developers, so not the best period to discuss hot
topics ;) That's why I've waited to open this discussion.
Also, even if I've discussed as much as possible about l10n on issues
concerning UI changes, it's a lot of work to follow each commit that
could have an effect. Sharing the effort between developers/UX/l10n
teams should be possible. As we follow Gnome HIG, adding it as
pre-requisite for UI changes/adds may prevent to have to rewrite dialogs
for example.
>
> Also - should we have a 'Localization' recurring topic in the ESC? Who
> would be the right representative there, please?
Maybe not as a recurring topic, but something that should be in mind of
UX team and developers when they commit or check for commits that have a
huge impact on l10n.
Cheers
Sophie
--
Sophie Gautier sophie.gaut...@documentfoundation.org
Tel:+33683901545
Co-founder - Release coordinator
The Document Foundation
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Workflow between dev, UX and l10n teams
Hi, Resending as there was no answer to the proposals :) Cheers Sophie Le 19/01/2015 11:03, Sophie a écrit : > Hi all, > > [Please follow-up the discussion on projects@ list to keep the history > of the thread there and ease the discussion, thanks :-)] > > I would like to open a discussion about the way developers team, UX team > and l10n team should interact and work together. > > There has been a heavy discussion [see this thread 1] during this round > of translation. The l10n team was a bit frustrated that there were again > so many changes in the en_US version that does not concern the l10n > versions (like adding colon at the end or capitals in the middle of the > strings). > > Each time, it seems part of this could be automated or a reflection > on how to avoid messing the l10n work should have been introduced before > those changes are committed. For example, if I decide to change FR > localization to have sentence capitalization in the menu entries, none > of the 100 other localizations won't and shouldn't be affected. It > should be the same for en_US version or if really impossible, try to > find a solution that lower the impact on all localizations. > > None of the l10n teams is against changing or correcting the UI of the > en_US version and none is against the natural evolution of the suite. > What is not bearable is when you have 100 000 changes in en_US and only > a 1/3 concerns all the other languages and it is repeated over the > branches. > > We are trying to change our workflow to work on master instead of > branches. That will allow us to review the strings earlier (to leverage > heavy unneeded changes if possible) and have more time to localize. But > that will work only if each taking part of the changes take care of the > others. > > To conclude, what l10n team would like to see is: > - a review process of the strings before they are committed and make > sure they respect the en_US standards (capitals, grammar, punctuation, > typography). Maybe adding the Gnome HIG book to our pages [like 2] if > not already. > > - if there is a way to script changes, script them otherwise wait until > there is a script available to commit them > > - any time there are heavy changes that pop up in someone's mind (like > changing ... for …) discuss it with the l10n team before committing > those changes. > > I know it may lower the enthusiasm of some contributors, but it will > regain the one of our l10n teams for sure :) > > > [1] > http://nabble.documentfoundation.org/libreoffice-l10n-Workflow-based-on-master-tt4131453.html#a4132459 > [2] https://developer.gnome.org/hig-book/3.12/design-text-labels.html.en > > Cheers > Sophie > -- Sophie Gautier sophie.gaut...@documentfoundation.org Tel:+33683901545 Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Workflow between dev, UX and l10n teams
Hi all, [Please follow-up the discussion on projects@ list to keep the history of the thread there and ease the discussion, thanks :-)] I would like to open a discussion about the way developers team, UX team and l10n team should interact and work together. There has been a heavy discussion [see this thread 1] during this round of translation. The l10n team was a bit frustrated that there were again so many changes in the en_US version that does not concern the l10n versions (like adding colon at the end or capitals in the middle of the strings). Each time, it seems part of this could be automated or a reflection on how to avoid messing the l10n work should have been introduced before those changes are committed. For example, if I decide to change FR localization to have sentence capitalization in the menu entries, none of the 100 other localizations won't and shouldn't be affected. It should be the same for en_US version or if really impossible, try to find a solution that lower the impact on all localizations. None of the l10n teams is against changing or correcting the UI of the en_US version and none is against the natural evolution of the suite. What is not bearable is when you have 100 000 changes in en_US and only a 1/3 concerns all the other languages and it is repeated over the branches. We are trying to change our workflow to work on master instead of branches. That will allow us to review the strings earlier (to leverage heavy unneeded changes if possible) and have more time to localize. But that will work only if each taking part of the changes take care of the others. To conclude, what l10n team would like to see is: - a review process of the strings before they are committed and make sure they respect the en_US standards (capitals, grammar, punctuation, typography). Maybe adding the Gnome HIG book to our pages [like 2] if not already. - if there is a way to script changes, script them otherwise wait until there is a script available to commit them - any time there are heavy changes that pop up in someone's mind (like changing ... for …) discuss it with the l10n team before committing those changes. I know it may lower the enthusiasm of some contributors, but it will regain the one of our l10n teams for sure :) [1] http://nabble.documentfoundation.org/libreoffice-l10n-Workflow-based-on-master-tt4131453.html#a4132459 [2] https://developer.gnome.org/hig-book/3.12/design-text-labels.html.en Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org Tel:+33683901545 Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [libo-marketing-priv] Announcing Pebble Smartwatch Application for LibreOffice Impress
Hi, Le 5 janv. 2015 20:47, "Gülşah Köse" a écrit : >> >> Hi Gulsah, > > > Hi Michael > >> >> >> We'd really prefer to use the MPLv2 (Mozilla Public License) - which is >> a quad-license with the GPL/LGPL/AGPL - that just helps us avoid having >> too many different license combinations around. >> if you're ok with that :-) > > > MPLv2 licence is ok for me. I changed the license of the project.--> https://github.com/COMU/pebble-remote/blob/master/LICENCE > > I added i18n and l10n support project recently. Italian and Turkish languages have been added. > Great, thanks a lot :-) > >> >> >> Are you interested in folding your work in up-stream & joining the >> LibreOffice development team ? =) I hope so. > > > I would be very pleased to join in the LibreOffice development team :) > >> And poke me / the list / Christian with your account name =) > > > This is my account name : gulsahkose > Cloph once done, could we have the project on Pootle so the L10n team take care of it? Thanks in advance! Cheers Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Annual Report: last chance to complete it!
Hi all, A gentle reminder that the pad for the annual report will be closed soon in order to give Flo enough time to write the report for the Berlin authorities. So please, add now what your team has done these last months! If you have links to blogs in English, don't hesitate to add them too. http://pad.documentfoundation.org/p/annualreport An English version will be extracted from the report, it will be then available for NLPs and the marketing team. Thanks a lot in advance for your help to report on our project activities :) Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org Tel:+33683901545 Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Change in the l10n workflow
Hi all, The l10n team is modifying his workflow. Currently the work is based on branches with a huge workload between beta2 and RC2. In order to extend the l10n period of work and lower the load, Cloph will create a project based on master in Pootle and will update the template once a month to retrieve the new/modified strings. So be aware that reverting a string change on master will affect also the workflow of the l10n team :) Kind regards Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org Tel:+33683901545 Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice-qa] 4.4 refactorings and BHS (was: minutes of ESC call ...)
Hi Bjoern, On Fri, Nov 14, 2014 at 5:37 PM, Bjoern Michaelsen < bjoern.michael...@canonical.com> wrote: > On Fri, Nov 14, 2014 at 03:42:16PM +0100, Sophie Gautier wrote: > > Maybe it would be easier if I add the test cases to MozTrap? there could > be > > also a follow-up through the beta/rc/final. > > Thank you, that would be great! I was suggesting to "just edit the wiki" as > telling hackers to enter stuff in MozTrap likely earns us just a few groans > mumbling "yet another login/account". > yes, no problem, I write the tests and upload them. > > Speaking of that: If people come forward during the ESC call with stuff > done > for 4.4 we should just put that in the minutes -- we can copy it over to > the > Wiki/MozTrap later. > Just let the stuff in the minutes, I read them anyway and will ping the developer when I don't understand. Cheers Sophie -- Sophie Gautier Tel:+33683901545 Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice-qa] 4.4 refactorings and BHS (was: minutes of ESC call ...)
Hi Bjoern, all On Fri, Nov 14, 2014 at 1:55 PM, Bjoern Michaelsen < bjoern.michael...@canonical.com> wrote: > Hi, > > On Thu, Nov 13, 2014 at 04:13:33PM +, Michael Meeks wrote: > > * QA (Robinson) > > There is a Bug Hunting Session for 4.4 coming up next week. If you did any > bigger refactoring or other work that primarily can be assumed to affect a > specific area of usecases, please add this to: > > > https://wiki.documentfoundation.org/BugHunting_Session_4.4.0.0#What_to_test > Maybe it would be easier if I add the test cases to MozTrap? there could be also a follow-up through the beta/rc/final. Cheers Sophie -- Sophie Gautier Tel:+33683901545 Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: ESC call Thursday 16:00 central European time ...
Hi all, Le 08/10/2014 10:44, Michael Meeks a écrit : > Hi Jean-Baptiste, > > On Wed, 2014-10-08 at 07:28 +0200, Jean-Baptiste Faure wrote: >> I do not know where to write in the agenda, so I do my suggestion here: > > Ah - in general anywhere in the middle is fine - the action items we > try to do while people turn up - to keep the call short. Just for information, I've added the link to Jean-Baptiste message on the QA part of the pad, so you have it at hand if Jean-Baptiste can't attend. Cheers Sophioe -- Sophie Gautier sophie.gaut...@documentfoundation.org Tel:+33683901545 Co-founder - Release coordinator The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: LibreOffice Weekly News #5 waiting for reviews
Hi, Le 13/09/2014 10:07, Norbert Thiebaud a écrit : [...] > > "Yet 7 new contributors to the LibreOffice project! Welcome to them!" > -> > "We welcomed 7 new contributors to the LibreOffice project:" And I would say ...7 new contributors to the development team, there are new contributors to the project not cited here. Kind regards Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org Tel:+33683901545 Co-founder - Release coordinator Certification Committee Member The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Helpcontent2
Hi Olivier, Le 17/08/2014 02:04, Olivier Hallot a écrit : > Hello guys... > > AFAIK we have no tool to edit the help pages for LibreOffice. The tools > scattered here and there that I tested are broken and I end up having to > edit the XML text file with great pain, limiting the possibilities to > add/improve content. > > A feature with no help page is a hidden feature/secret for most users. > > OTOH, discussions on a new help system are stalled, some hickups once a > while, since LO birth. It's not stalled, but there is technical decisions to make (extended tooltips for example), see our last discussion on the l10n list. > > The extension I am told to investigate is HelpAuthoring.oxt, + a SUN > Help2 Reference Guide in PDF available in the net. The extenstion is > broken and debate will rise to fix it or design a new help system with > no foreseable future. > > So, is there *anywhere* a version of OpenOffice.org + Helpauthoring.oxt > known to work in Linux/windows(*) that I can install and edit > LibreOffice Help pages? I sent you one some times ago, and I've it installed on my Debian working with the last LibreOffice version. But using it is a nightmare, you have a lot to learn with the styles used, the syntax and the structure before being able to create an article. I would like to have a follow up in Bern with Moggi and Kendy on our last discussion because this is something I'm concerned to push too. Cheers Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: is fdo#81113 a release blocker for 4.3.0?
Hi, Le 16/07/2014 16:55, Joren DC a écrit : > Hi David, > > Thanks for bringing this to the mailinglists. +1 > > op 16-07-14 16:01, David Tardon schreef: >> Hi all, >> >> Any opinions on $SUBJECT? The bug has got importance highest/critical; >> unfortunately it was triaged a day too late... Note that this is just >> one possible manifestation of the problem: the same misdetection (and >> failure to open the file) can happen whenever a remote file is opened. >> It depends on whether the file is detected before the Keynote filter is >> tried. > I had a little chat with David in the IRC: > > (16:46:17) jorendc: dtardon: what file formats are affected do you think? > (16:46:29) jorendc: dtardon: depending on that it might be a blocker or > not (IMHO) > (16:47:00) dtardon: jorendc, i have no idea. any that would come after > keynote during the detection > (16:47:28) jorendc: dtardon: is there a chronological list where I can > see what comes after keynote detection? > (16:48:27) dtardon: jorendc, no, there isn't > (16:49:29) jorendc: dtardon: okay, I see. But I assume all ODF and other > common file formats (OOXML,...) are non affected? I'm struggling about > how many users'd be affected. > (16:49:46) jorendc: And the fact we still advice to use 4.3.0 version > for testing purpose > (16:49:55) jorendc: (very) early adopters > (16:50:05) dtardon: jorendc, these should be well before that > > Little summary: > * As far I understand _most common_ file formats are not affected > * We clearly state that point .0 versions are for testing/(very) early > adopters only. > > As far I'm concerned: don't block the release of 4.3.0 but make sure it > is in 4.3.1. +1 :) Cheers Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Mise à jour et installation LibreOffice - erreur interne 2503
Bonjour, Vous avez posé votre question sur la liste de développement de LibreOffice qui n'est pas une liste d'aide aux utilisateurs. Pour poser votre question sur la bonne liste et en français, veuillez consulter cette page: http://fr.libreoffice.org/get-help/community-support/ Merci par avance Cordialement Sophie Le 07/07/2014 11:10, VRAC Jean-Claude a écrit : > Bonjour, > > Sous windows 8.1, j'ai voulu installer la nouvelle version > LibreOffice_4.2.5_Win_x86.msi. > > L'installation s'est bloquée avec message ''erreur interne 2503". > > J'ai désinstallé la précédente version de LibreOffice et réinstallé la > nouvelle : même problème. > > idem comme administrateur ou avec résoudre le problème de compatibilité. > > J'ai vérifié, il n'y a plus de traces de fichiers de LibreOffice sur le > disque dur et regedit. > > A priori, je n'ai pas de problème d'installation avec d'autres logiciels. > > Je ne peux donc plus utiliser LibreOffice (sauf en version portable). > > Que faire ? > > Cela vient-il de Microsoft installer ? > > Merci de vos réponses pour toutes solutions positives > > --- > Ce courrier électronique ne contient aucun virus ou logiciel malveillant > parce que la protection avast! Antivirus est active. > http://www.avast.com > > _______ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice -- Sophie Gautier Tel:+33683901545 Membership & Certification Committee Member - Co-founder The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
LibOCon Bern: book your hotel :)
Hi all, For those who are going to Bern for LibOCon, please book your hotel asap! Here is a list where you'll find prices and distance from the venue: http://conference.libreoffice.org/2014/accommodation/ Let us know if you have any question. Cheers Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Register to the LibreOffice conference
Hi all, If you plan to attend the LibreOffice conference in Bern, please don't forget to register, this will help the organization team a lot :) To do so, follow this link: http://conference.libreoffice.org/2014/registration/ Thanks! Cheers Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
LibOCon Registration and Visa
Hi all, The registration for the LibreOffice Conference in Bern is open and will end mid-July. Registering will greatly help our organization team to get an idea of how many of you guys are going to attend the conference. *If you need a visa*, you can contact Ronny Standtke for any help, you will find all the detailed information on this page http://conference.libreoffice.org/2014/visa/ If you want to attend the conference, we ask you to register within the deadline at http://conference.libreoffice.org/2014/registration/ If you check here the need for a visa, Ronny will contact you back to help you. In case you do not want to attend the conference yet, I’d like to advertise a bit more. :) Our program committee is investing lots of time to make this conference an unforgettable, noteworthy event, and we are proud to give a program with a vivid mixture of development, community, marketing, infrastructure and many other working areas of the LibreOffice project. The program will be provided asap on the Conference website. Last but not least, this is your chance to meet the faces behind the LibreOffice community: developers, marketeers, admins, localizers, documentation writers, designers and many, many more. We’ll all have a great time in Bern, and want you to be a part of it! If you have any question or problem regarding registration, don't hesitate to send a mail to confere...@libreoffice.org Looking forward to meeting you in Bern! Kind regards Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Need info on sd/source/ui/accessibility.po for l10n
Hi Caolán Le 13/05/2014 15:31, Marina Latini a écrit : [...] >> Da: "Caolán McNamara" >> A: "Sophie" >> Cc: "libreoffice-dev" , >> "LibreOffice-l10n" >> Inviato: Martedì, 13 maggio 2014 14:58:37 >> Oggetto: Re: Need info on sd/source/ui/accessibility.po for l10n >> >> Looking at where they get used, they are the accessibility descriptions >> for the things they describe, presentation pages and notes and so on. So >> you'd need an accessibility tool to hear them read out as you select >> them in the UI. Anyway, it looks completely safe to separate them with >> spaces and remove the capitals etc, and just format them as natural for >> your language. We should probably separate them in the English version >> too. Thanks a lot for your feedback and clear explanation :) Cheers Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Need info on sd/source/ui/accessibility.po for l10n
Hi all, We (l10n team) need some information for localization purpose. In libo43_ui/sd/source/ui/accessibility.po, some strings in the form of PresentationOutlinerShape UnknownAccessiblePresentationShape Few of our languages support this sort of notation where there is a mix of capitals in one attached word. How should we translate that, are we allowed to separate the words (add spaces or underscores) and remove the capitals? Where does it appears in the UI? Thanks in advance Kind regards Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Reminder: Call for papers LiboCon Bern 2014
Hi all, This is a reminder that you have until *May, 15* to submit your talk proposals for the LibreOffice Conference in Bern. See the original announcement here http://nabble.documentfoundation.org/LibreOffice-Conference-2014-Call-for-Paper-td4100170.html Submit your proposal on the conference at libreoffice.org list. Thanks :) Kind regards Sophie -- Sophie Gautier Tel:+33683901545 Membership & Certification Committee Member - Co-founder The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Reminder call for papers for LibreOffice conference in Bern
Hi all, This is a reminder that the call for papers is still open for our next conference in Bern in September. Find the original announcement here: http://blog.documentfoundation.org/2014/03/05/libreoffice-conference-2014-call-for-paper/ More information and material are also on the wiki: https://wiki.documentfoundation.org/Events/2014/LibreOffice_Annual_Conference Let us know if you have any question Kind regards Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Call for paper LibreOffice conference reminder
Hi all, This is a reminder that the Call for Paper for the next LibreOffice Conference in Bern is still running until May 15. Please follow this link for further indications: http://blog.documentfoundation.org/2014/03/05/libreoffice-conference-2014-call-for-paper/ Thanks for your participation :) Kind regards Sophie -- Sophie Gautier Tel:+33683901545 Membership & Certification Committee Member - Co-founder The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: MSI Editing / Documentation for the Community
Hi Adrian, Le 05/03/2014 05:15, AJ a écrit : > Hello, > > I am trying to coordinate documentation on editing the MSI file using ORCA > or other MSI editor in order to create a custom installer package(s). > Since there is not any official documentation for this I was hoping that > those with expertise in this area would be willing to work with me in > defining fields and options and I will work to create the > information/documentation in an easy to use format. This is a pretty > regularly requested item from what I can see and I am looking to help > myself while giving back to the community. Please let me know if you can > help. Thanks for your proposal, may be you could enhance the documentation on the wiki here https://wiki.documentfoundation.org/Deployment_and_Migration Kind regards Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Fwd: FOSDEM travel and hotel refund
Hi all, Please send your travel and hotel refund as explained bellow, we would like to group the requests. Thanks! Cheers Sophie Message original Sujet: FOSDEM travel and hotel refund Date : Fri, 07 Feb 2014 11:44:18 +0100 De : Sophie Pour : proje...@global.libreoffice.org, libreoffice-dev , libreoffice-ux-adv...@lists.freedesktop.org Hi all, To all FOSDEM participants, please send you travel and hotel refund requests during next week so we can start refundings and group them. You need to send : - your hotel invoice - your travel invoice - the SPI form available here https://wiki.documentfoundation.org/TDF/Policies/Refunding Send all this to treasu...@documentfoundation.org The link above will also give you the detailed rules. Thanks in advance! Kind regards Sophie -- Sophie Gautier Tel:+33683901545 Membership & Certification Committee Member - Co-founder The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
FOSDEM travel and hotel refund
Hi all, To all FOSDEM participants, please send you travel and hotel refund requests during next week so we can start refundings and group them. You need to send : - your hotel invoice - your travel invoice - the SPI form available here https://wiki.documentfoundation.org/TDF/Policies/Refunding Send all this to treasu...@documentfoundation.org The link above will also give you the detailed rules. Thanks in advance! Kind regards Sophie -- Sophie Gautier Tel:+33683901545 Membership & Certification Committee Member - Co-founder The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: IRC going crazy ?
Le 03/02/2014 19:09, Jonathan Aquilina a écrit : > Freenode is being DoSed you are best using a european based server as US, > australian and asian servers are being attacked. It seems European too, I've been unable to connect this afternoon... Cheers Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Thanks to have filled the pad!
Hi all, I would like to thank everybody who has filled the pad for the annual report. Really, thanks a lot :) If you still have to add something, you have until the end of the month and it's here: http://pad.documentfoundation.org/p/annualreport Cheers Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: MABs and priority
Hi Bjoern, all, Le 17/01/2014 12:01, Bjoern Michaelsen a écrit : > Hi, > > On Thu, Jan 16, 2014 at 06:21:48PM +, Michael Meeks wrote: >> + All Most Annoying Bugs -> priority Highest (Bjoern) > > This is done now too, so right now, all NEW bugs(*) with priority highest > should > also block a MAB and all NEW bugs blocking a MAB should be priority highest. > > I updated the MAB instructions to include setting "priority: highest" when > adding a bug to MAB. > > for QA, this means two things, one short term, one long term. > > == short term == > > To keep the highest=MAB equivalence clean, some regular (weekly?) checking for > bugs that are priority:highest and not a MAB would be needed. Such bugs could > be seen as "proposed MABs" and either be: > - promoted to a MAB with the usual procedure (rationale etc.) > - or respectfully rejected and bumped to priority:high > > Someone volunteering for this task? > > If so, it would be interesting: > - how many such bugs there are each week > - what is their quality (as in: how many are good MABs? how many are well > triaged?) > For information, I've forwarded and translated your mail to our qa list. I'll have a look today to those bugs having priority:highest and not in the Mab yet. Cheers Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: data streams in 4.2
Le 13/01/2014 15:05, Kohei Yoshida a écrit : > On Sun, 2014-01-12 at 21:53 -0500, Neeraj Rai wrote: >> sorry, that was accidental partial send: >> Hi, >> >> >> https://wiki.documentfoundation.org/ReleaseNotes/4.2 >> 1. I tried to use Data Streams in the latest release. >> a) I enabled Data stream >> b) entered URL : http://finance.yahoo.com/q?s=JPM&ql=0 >> c) value1,value2...: A2:A12 d) limit to : 10 >> the OK button is not enabled >> 2. Once I get this working, I am hoping to get some pointers so I can >> plug in an extension to feed data to it. > > You can't just yet. This feature is still experimental for a reason, as > it's not yet ready for main stream use. So, I'll move it to the experimental features part in the release notes. Cheers Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: LO 4.2.0RC2 -- serious dependency problems DEB 64 bits version
Hi Raymon, Le 08/01/2014 20:54, r_ouellette a écrit : > On 2014-01-08 LO 4.2.0RC2 can be upload for testing purposes. > > I downloaded these 3 files and install them as I always did. Almost every > package has an install error and, in the end, 57 packages were declared > broken. Surprisingly, LO 4.2 works without problem. But the deb database is > now full of broken packages and it can't be left like that! Thanks for the feedback, this is the purpose of the announcement made on the QA list to check for this sort of issue before a more general availability of the release. Please next time, report the problems you meet on the QA list, the dev list doesn't deal with this. Kind regards Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: New Feedback Page
Hi Joel, all, Le 09/01/2014 18:36, Joel Madero a écrit : > Hi All, > > Robinson and Christian did some great work here. We have our new > feedback page live and linked. If you go to Send Feedback from within > LibreOffice you will see the new page with nifty options and clean "get > involved" links. > > Thanks to Robinson and Christian for getting this done :) Thanks a lot :) > > I'm not sure if we want this to be translated or not since we want all > bug reports filed in English and the BSA (previously linked from send > feedback) was exclusively English until very recently. > > Sophie, thoughts here? I think we discuss this in a QA call and it will be translated but the wording will explicitly be that bugs or enhancements are in English while the happy/not happy will be in the user language (I don't know if this part is still available, but we should then also decide who will take care of this feedback). If we all agree on that, I'll send a mail on l10n and website lists tomorrow to ask for participation. Cheers Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Wiki editing page
Hi, Le 21/12/2013 05:02, Tae Wong a écrit : > Since the wiki.documentfoundation.org site is slow to load, you'll > need to fix the slow loading problems for this site. If you have a problem with the wiki, please, fill a bug. This is the developer list, so unless you have a patch or you want to help with the LibreOffice product development, your post could be seen as spam here :) > > The LibreOffice mailing list is spammed so you want to get past > filters to remove spam messages. Posting to non-subscribers is still > possible. No moderator approval is needed! Yes, if you want to read the list without spam, you can do it from here http://nabble.documentfoundation.org/Dev-f1639786.html, or subscribe to the list and let your spam filter work. Kind regards Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: l10n process, en_US version, Help files
Hi Caolán, Le 18/12/2013 11:19, Caolán McNamara a écrit : [...] > >> * About the help files >> - I always wonder why there is a Help button on a new dialog when no >> help file is appended ;) > > One thing that we could with the new .ui file format is to confirm if > each dialog actually has a help entry for it. There is an easy hack at > https://bugs.freedesktop.org/show_bug.cgi?id=67350 to extract out the > new-format helpids from the help and determine if they actually exist. > That would weed out typos where the help gets detached from the thing it > documents. > > Similarly someone could script if each new-format dialog has a help > entry and make a list of stuff that is missing help and turn those into > a list of tasks to document those things. > > Another thing that could be automated is to generate a skeleton help > page from a new-format dialog. i.e. generate the help ids bookmarks for > the interactive widgets, buttons, checkboxes, etc. and have fill-me-in > headings and bodytext. Thank you very much for your suggestions. Would your two last suggestions fall also under easyhacks or is it something more complicated to code? Kind regards Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: l10n process, en_US version, Help files
Hi Mat, Le 12/12/2013 22:56, Mat M a écrit : > Hi all > > My grain of salt there. I strongly believe we need to cross-talk, so I > go on cross-posting. Thanks a lot for your input, jumping to my question: [...] > > * And... fixing ! > Easy hacks or l10n sessions to fix that are both valid choices. We may > want to automate finding occurrences of text in the code. We began with > fdo#39439, but further steps are required. did you submit your work, is it now integrated? Kind regards Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
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 ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
l10n process, en_US version, Help files
Hi all, This mail is posted to the dev list and the l10n list, please follow up on the l10n list. I would like to open a discussion on the l10n workflow, the quality of the en_US version and the Help files. All is linked and I would like to discuss how we can improve the process here. I'm sure that having a better understanding between the l10n process and the dev process should help us to improve things :) So here is a proposal, it's a bit long, sorry for that. *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. *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 *After RC1 and l10n integration - we need to know when integration is made after our fixes, there is currently no communication on this ==> 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. *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. - 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) - 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 * 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. Thanks for reading :) Cheers Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Annual report on activities
Hi all, This is the time to prepare our annual report about the so various activities we have achieved during this year. Florian will then translate and adapt it to serve as the official report for the Berlin authorities. I've prepared a pad here: http://pad.documentfoundation.org/p/annualreport So please, fill in the activities you've lead during the year, do not give to many details (it's a report :) but draw the main lines of what your project has achieved. Thank you very much in advance for your participation, it's an important task for our project. Aside the official report, we can use it also to present our project to the various publics we meet. If you have question, please follow up on the projects list. Kind regards Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: LibO 4.2.0.0beta2 can't launch internal help
Hi Raymond, Le 05/12/2013 04:45, r_ouellette a écrit : > I had the same behavior with 4.2.0.0 beta1. Right now I'm using: > Version: 4.2.0.0.beta2 > Build ID: 1a27be92e320f97c20d581a69ef1c8b99ea9885d You're mail would have more answers on a users list or the qa list. > > 64 bits, Ubuntu-Linux 13.10. I installed also the two french tar.gz packages > for localisation and for help. A few strings don't appear in french (mostly > in the Options Menu for settings). But my main concern is the fact that I > can't launch the internal help, only the web version opens. The french help > is correctly installed and visible in /opt/libreoffice4.2/help/fr. I double > checked with a LibO 4.1 working installation and the 4.2 installation seems > similar... The French localization is not over, so not integrated yet. If you want to test the 4.2.0 beta versions, I recommend you don't install the languages pack as they can show errors. > > The internal help is very useful, very complete and, most of all, can be > accessed without an Internet connection. > > I tried to find in different settings files to correct this behavior :-( but > no success... > > Someone has a hint? This is a bug that was discussed on the qa list. Kind regards Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: gru (MozTrap, Jenkins) currently down
Le 27/11/2013 14:07, Florian Effenberger a écrit : > Hello, > > Florian Effenberger wrote on 2013-11-27 13:25: >> I am sorry to say that gru (hosting MozTrap and Jenkins) is currently >> down. It looks like a hardware problem given that not even a hardware >> reset with forced boot into the rescue system work. >> >> Our ISP has been informed and I hope will act soon. > > the machine is now up again. It was stalled at the BIOS during hard disk > detection (which makes me hope it's not a hardware issue, because it > crashed before we did a reboot). > > I am now working on restoring the services. ok, thanks a lot! Cheers Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
General release organization meeting
Hi all, In order to try to have the best organization for the release of 4.2.0 that will happen in February, I would like to organize a meeting between all the projects concerned to make sure we don't forget anything or miss some deadlines and coordinate well together. It would be good to have this meeting during RC1 period (16 to 22 of December) so we have still some time left before the final release. I've set a Doodle here : http://doodle.com/sqkyaaeb5aaigarq We will use the marketing channel on IRC and it would be really great if we could have people representative from : - design team - marketing team - QA team - localization team - native language team and members who administrate website in their language - developer team - documentation team, I'm not sure this team is really concerned but feel free to join :) If I miss somebody don't hesitate to tell me :) And please follow up the discussion on the *marketing list*. I will provide an agenda of the meeting on the wiki next week, where you'll be able to add the points you want us to discuss. I would like to keep it short for all teams and we will do another meeting if one team feels it's necessary. Thanks all in advance for your participation! Kind regards Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Manual tests on regression for 4.2.x version
Dear developers, I'm currently working on updating manual tests for the 4.2.x version. Tests for new features will be written as well. Do you have any regressions in mind that we should particularly monitor during the test series we will run on this version? If yes, please give me the bug number and I'll add a test for it. Thanks in advance Kind regards Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Your videos on LibreOffice TDF chanel
Dear developers, We now have an official YouTube channel that I try to populate with useful material for our project: http://www.youtube.com/channel/UCQAClQkZEm2rkWvU5bvCAXQ If you have any videos (related to LibreOffice ;-) that you want to see added here, please send me the link directly. I don't have set a Talk playlist yet, but that will come soon and if you want another playlist, just tell me. Thanks in advance Kind regards Sophie PS: I hope to come soon with an easier link and some visual too. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [libreoffice-l10n] Re: LibreOffice Help
Hi Martin, Hey, hey :-) this is not the case for the moment. Rob is currently working on exporting the wiki help content to the sources (if I understand well). My mail was to make sure that all the aspects of maintaining the help on the wiki are taken into account. But if the help is better enhanced on the wiki, it's not a problem on the contrary, the l10n process should not be changed however. Kind regards Sophie GSM Le 8 oct. 2013 22:24, "Martin Srebotnjak" a écrit : > Hi, > > maintaining and translating LO help via wiki is a no-go for localization > (teams). > > If someone wants to play with that, he/she can do it as one's own pet > project, maybe by creating a fork of LO. But LO should officially stay away > from it. Or it will, quite soon, become an English-only office suite. If > that will be the case, the localization teams should think about forking LO > :-) > > Lp, m. > > > 2013/10/8 Sophie > >> Hi Rob, >> >> I'm adding the l10n list in copy because they are concerned >> Le 08/10/2013 11:16, libreoffice-ertai.nl a écrit : >> > Hi Sophie, >> > >> > As I understood the offline help is now hard to maintain. >> >> Yes, this is something complicated for developers >> This should >> > change that so that the help-wiki will be exported for each release's >> > offline help. So It should make changing/translating the help easier. >> >> I don't doubt that the wiki would be easier than filling the help .ott >> and using the basic macros that was used in the past, I've used it and >> it's really complicated. >> What is important for us (l10n team) is the possibility to use Pootle to >> maintain our translation, because the wiki is not a translation tool (no >> glossary, no TM, no way to track changes, no way to mark incorrect/fuzzy >> strings, no way to share the files, no xml checks, etc...) and is >> impossible to search currently (we need a i18n wiki for that). >> That means also that the wiki edition is restrained to the necessary >> changes and enhancements that are needed and only those and that changes >> are only made in the en_US sources. >> I understand that you are currently only working on the process to >> export the wiki, but I think that the l10n team may have some input too. >> Again (because already expressed to Kendy), my concerns are not about >> the changes in the process, I really understand that, but about to make >> sure that the l10n team is made aware of the changes in their work if >> any, and that the way they are working currently to localize those >> important and huge files is taken into account in the process. >> >> Kind regards >> Sophie >> > >> > -- >> > Greetings, >> > Rob Snelders >> > >> > Sophie schreef op 08-10-2013 09:20: >> >> Hi Markus, Rob, >> >> Le 08/10/2013 01:52, Markus Mohrhard a écrit : >> >>> Hey Rob, >> >>> >> >>> >> >>> 2013/10/7 Rob Snelders >> >>> >> >>>> Hi Markus, >> >>>> >> >>>> We have spoken about exporting the help-system from the help-wiki. >> >>>> We will >> >>>> need a html/javascript framework for that. I don't think a basic >> >>>> framework >> >>>> will need more time then a month or 2 for me. But I think we will >> >>>> also need >> >>>> to look at how we export the pages from the wiki because how the >> >>>> pages are >> >>>> exported is important. >> >>>> >> >>> >> >>> >> >>> >> >>>> >> >>>> Can you tell me what plugin for mediawiki you had in mind to do the >> >>>> export? >> >>>> >> >>> >> >>> I found DumpHTML at the mediawiki page. I wanted to try this first >> >>> before >> >>> looking for other scripts. >> >>> >> >>> >> >>> >> >>>> Is there a test-wiki to try it on to see what it does, maybe we'll >> >>>> need to >> >>>> change the plugin to fit our needs. >> >>>> >> >>> >> >>> We will get a VM from the infrastructure team soon. We will test all >> the >> >>> steps there. I'll tell you more as soon as we get the VM and have it >> >>> correctly set up with a wikihelp instance. >> >> >> >> If the l10n team is impacted by your project, please tell me, as this >> is >> >> their (huge) work, I would like to keep them in the loop. >> >> Thanks in advance >> >> Kind regards >> >> 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 mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: LibreOffice Help
Hi Rob, I'm adding the l10n list in copy because they are concerned Le 08/10/2013 11:16, libreoffice-ertai.nl a écrit : > Hi Sophie, > > As I understood the offline help is now hard to maintain. Yes, this is something complicated for developers This should > change that so that the help-wiki will be exported for each release's > offline help. So It should make changing/translating the help easier. I don't doubt that the wiki would be easier than filling the help .ott and using the basic macros that was used in the past, I've used it and it's really complicated. What is important for us (l10n team) is the possibility to use Pootle to maintain our translation, because the wiki is not a translation tool (no glossary, no TM, no way to track changes, no way to mark incorrect/fuzzy strings, no way to share the files, no xml checks, etc...) and is impossible to search currently (we need a i18n wiki for that). That means also that the wiki edition is restrained to the necessary changes and enhancements that are needed and only those and that changes are only made in the en_US sources. I understand that you are currently only working on the process to export the wiki, but I think that the l10n team may have some input too. Again (because already expressed to Kendy), my concerns are not about the changes in the process, I really understand that, but about to make sure that the l10n team is made aware of the changes in their work if any, and that the way they are working currently to localize those important and huge files is taken into account in the process. Kind regards Sophie > > -- > Greetings, > Rob Snelders > > Sophie schreef op 08-10-2013 09:20: >> Hi Markus, Rob, >> Le 08/10/2013 01:52, Markus Mohrhard a écrit : >>> Hey Rob, >>> >>> >>> 2013/10/7 Rob Snelders >>> >>>> Hi Markus, >>>> >>>> We have spoken about exporting the help-system from the help-wiki. >>>> We will >>>> need a html/javascript framework for that. I don't think a basic >>>> framework >>>> will need more time then a month or 2 for me. But I think we will >>>> also need >>>> to look at how we export the pages from the wiki because how the >>>> pages are >>>> exported is important. >>>> >>> >>> >>> >>>> >>>> Can you tell me what plugin for mediawiki you had in mind to do the >>>> export? >>>> >>> >>> I found DumpHTML at the mediawiki page. I wanted to try this first >>> before >>> looking for other scripts. >>> >>> >>> >>>> Is there a test-wiki to try it on to see what it does, maybe we'll >>>> need to >>>> change the plugin to fit our needs. >>>> >>> >>> We will get a VM from the infrastructure team soon. We will test all the >>> steps there. I'll tell you more as soon as we get the VM and have it >>> correctly set up with a wikihelp instance. >> >> If the l10n team is impacted by your project, please tell me, as this is >> their (huge) work, I would like to keep them in the loop. >> Thanks in advance >> Kind regards >> Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: LibreOffice Help
Hi Markus, Rob, Le 08/10/2013 01:52, Markus Mohrhard a écrit : > Hey Rob, > > > 2013/10/7 Rob Snelders > >> Hi Markus, >> >> We have spoken about exporting the help-system from the help-wiki. We will >> need a html/javascript framework for that. I don't think a basic framework >> will need more time then a month or 2 for me. But I think we will also need >> to look at how we export the pages from the wiki because how the pages are >> exported is important. >> > > > >> >> Can you tell me what plugin for mediawiki you had in mind to do the export? >> > > I found DumpHTML at the mediawiki page. I wanted to try this first before > looking for other scripts. > > > >> Is there a test-wiki to try it on to see what it does, maybe we'll need to >> change the plugin to fit our needs. >> > > We will get a VM from the infrastructure team soon. We will test all the > steps there. I'll tell you more as soon as we get the VM and have it > correctly set up with a wikihelp instance. If the l10n team is impacted by your project, please tell me, as this is their (huge) work, I would like to keep them in the loop. Thanks in advance Kind regards Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [PATCH][PUSHED] fdo#31714 Help: Improve Show rows/column help
Hi all, Le 19/09/2013 17:01, Jan Holesovsky a écrit : > Hi Laurent, > > Caolán McNamara píše v Čt 19. 09. 2013 v 14:48 +0100: > >>> I did not add id for added paragraph because I don't know how to do it. >> >> I believe you just "make one up" that isn't already in use in that file. >> i.e. its just got to be unique in that file. >> >> I think there is some sort of help editor/macro/extension in existence, >> but I'm very hazy on that. kendy probably knows. > > I am not sure if / where the help editing extension lives today, but at > least the docu: > > http://www.openoffice.org/documentation/online_help/OOo2HelpAuthoring.pdf > > explains a bit; like that the paragraph id is mandatory, but no rules > how it should look like - just "The ID must be unique within a help file > so that referencing across files and relocating sections and paragraphs > across files is possible." :-) If needed, I've the extension and the template to write help articles within LO, I retrieve them some months ago from svn. Cheers Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Gerrit news sent to fr-qa list
Hi Bjoern, On 24/06/2013 11:47, Bjoern Michaelsen wrote: > Hi Sophie, > > On Sat, Jun 22, 2013 at 09:15:59AM +0200, Sophie Gautier wrote: >> Would it be possible to also send the daily gerrit news mail to >> the fr-qa list? > > Here is a trivial proposal for that: > > https://gerrit.libreoffice.org/#/c/4471/ Thanks a lot! > > It would be great for someone from the french community taking it on > from there (that is: reviewing and pushing it), so that there is no > single point of failure (me) and the local community can update and > adjust to their needs. I'm not sure that we are able to do that, but will have look tomorrow. > > If reviewed, Ill will deploy it (although I might do so after the > gerrit update/outtime on Thursday). Note also you might need to > whitelist/unblock ger...@libreoffice.org for the french QA list for > the messages to come through then. ok, thanks :) Cheers Sophie ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Gerrit news sent to fr-qa list
Hi all, Would it be possible to also send the daily gerrit news mail to the fr-qa list? if not, that's not an issue, I'll forward it like I do today, but it would be great to have it automated :) Thanks in advance Kind regards Sophie -- Sophie Gautier Tel:+33683901545 Membership & Certification Committee Member - Co-founder The Document Foundation ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-commits] core.git: sw/source
sw/source/ui/app/app.src |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 1cf6f36306eb4d11279118c547e87a2c4b2551d4
Author: Sophie Gautier
Date: Sat Jun 1 18:01:07 2013 +0300
Fix typo: connections -> connection
Change-Id: Ica73de8975de0c3565e3eaad82e6dbb677bec33d
diff --git a/sw/source/ui/app/app.src b/sw/source/ui/app/app.src
index 8dbc309..134da77 100644
--- a/sw/source/ui/app/app.src
+++ b/sw/source/ui/app/app.src
@@ -541,7 +541,7 @@ ModalDialog DLG_MERGE_SOURCE_UNAVAILABLE
Pos = MAP_APPFONT ( 12 , 6 ) ;
Size = MAP_APPFONT ( 178 , 40 ) ;
WordBreak = TRUE;
-Text [ en-US ] = "The data source '%1' was not found. Thus the
connection to the data source could not be established.\n\nPlease check the
connections settings.";
+Text [ en-US ] = "The data source '%1' was not found. Thus the
connection to the data source could not be established.\n\nPlease check the
connection settings.";
};
OKButton PB_MERGE_OK
{
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
