License for my contributions

2012-02-29 Thread André Schnabel 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

although I stated this for my (minimal) contributions to LibO already,
one contribtuion submitted in the past to go-oo did not have an
explicit license statement. So here we go again:

All of my past & future contributions to LibreOffice may be licensed
under the MPL/LGPLv3+ dual license, including previous contributions
to the go-oo code.

best regards,

André
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPTxIMAAoJED/K41EyZ3hDGtwIAL/zPXW9wiDo1WgtSWIuYVO8
PbGliErKFxgbIl+OBsu7gO5AFU9ZtmJsAfie+cyamXoA6/NGUcFwnlyXd/uVMPfn
sUYj429CptaAa6jUd1fTgFsPkZ702FjPtfFCmDKdGGACOnJHSxOed8C30OokiGhl
mDiJUdo+b8cvbqiQ3ySqr/uUCmfSFHDJ6aTIMA2otgrxlhG+k5Zmui1gMRNmSbCq
+IQh2DCP5xmVDWgWPOsg93BvxhcEbdaE4ETFXKKGhthEYWP2EhyhHEb4ud3HfYPP
IiZcjym+3P91dXe/Sn9P+xVEA8SV9pnmy3a+FAbHoCryYKl8OgA1dVeRJ+rPU/4=
=qHiF
-END PGP SIGNATURE-
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] Are we back to having this spec process again!?

2011-07-11 Thread André Schnabel 

Hi Kohei, *


Am 11.07.2011 15:46, schrieb Kohei Yoshida:

On Sun, 2011-07-10 at 11:57 +0200, André Schnabel wrote:

All that said: if you can suggest some other word for "spec" I'd be
quite happy.

Dennis suggested "design notes".  I normally call it either feature
documentation, feature description, feature page, or simply just a wiki
page for feature XYZ.


Ok, among those I'd prefere "design notes".


To me, the word "specification" implies much more than just a collection
of information; it implies formality and final, approved decision that
cannot be changed without paperwork, votes, or whatever is the formal
way of proposing changes.


Oh - we are on the same side here :) I never ever again want to see a 
bugreport rejected, just because an obvious bug works "as defined in the 
spec and we cannot change the spec".


I want those design notes for mainly two reasons:

- before / during / right after implementation we know that a small team 
did some elaboration how a certain feature should be implemented and 
found consensus on how to implement. The implementation should be based 
on this consensus and not be changed by a single party. (But please: no 
formalism, no big administration .. if there is a team that's all you 
need .. if there is no team, then don't stop working)


- some time after implementation the notes could be used as input for 
further implementation /changes, documentation, testing ... So it's a 
(hopefully helpfull) input for future tasks - nothing that schould 
hinder future work.




But I think Michael's explanation is pretty
much in line with how I perceive this term, and why I think it's a
mis-used term for this purpose.


So please let's not stick to the term :)

I agree to many of Michael's points as well as to Bjoern's. E.g. no 
bugfix (that improves the situation and does not just move from one 
awkward situation to another) should be delayed, just for the "sake of 
having a spec". No one should be put in charge of doing some work 
without being asked beforehand etc.


I'd like to have all this as help for developers. E.g. I don't want to 
write the help texts (there are lot's of people who have much better 
skill in technical writing) - I don't want to do an in-deep analysis of 
competitor's software features - I don't like to elaborate migration 
szenarios. But I want people to make people that many of such things 
need to be done - and my experience from the last few weeks is, that 
hardly anybody outside the dev-list is aware of this :(


regards,

André

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] Are we back to having this spec process again!?

2011-07-10 Thread André Schnabel 

Hi Kohei,


Am 09.07.2011 19:39, schrieb Kohei Yoshida:

Regarding this bug

https://bugs.freedesktop.org/show_bug.cgi?id=39068

Rainer started the specification process for this.


I'd rather say he started to collect information in a structured way to 
help all the people involved in a new feature implementation. And to 
make more people aware that their help is needed.



I thought one thing we decided to do was not to re-introduce this
over-engineered, time-wasting specification process.  Is this a new
development in the LibreOffice space?

It's not about a mandatory over-engineered process.

I started something similar for the gridline display. I (and others) 
found this quit helpfull - but I would not do it again in that detail 
for quite simple patches. It was more to see, what might work and what not.


Anyway - what I really dislike from your further communication (your 
answer to Christoph) is the way you speak about "us" developers and 
"you" UX, QA and documentation guys. It's after all "we" who create and 
develop LibreOffice.


All that said: if you can suggest some other word for "spec" I'd be 
quite happy. For me it is more or less a notes collection for an 
implementation - and not the thing that was used at OOo. What Rainer and 
me currently do with those spects is really only a first step and maybe 
a step to far. Again - we are currently trying to see what works and 
what not.


André
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] [GSOC] Report #5. Wizards

2011-07-08 Thread André Schnabel 

Hi Peter,

sorry for randomly jumping in with just some side-notes ...

Am 06.07.2011 22:10, schrieb Peter Jentsch:

I'm unsure about where to put the xliff files, because I'm completely
ignorant of the translation workflow and the different places where
translatable items are put in order to get easily picked up by translators.


If we want to go that way, Andras Timar might have an idea about where 
to store this stuff.



Plus, I found xliff allows for a lot of things, and the Xslt script will
make a few assumptions on how (simple) the xliff file is structured, so
the process might break easily if the translation tools want to do nasty
things with the xliff file (that a fully working xliff toolchain would
be required to understand). But maybe that's not happening anyway, and
in practice it's less complex than it looks on first sight.


Afaik there is hardly any "fully working FOSS-based xliff toolchain" 
that includes translation editors and complext xliff files.


Translate toolkit has a quite good support for XLIFF <-> po conversion 
(as long as you do not use advanced xliff features). If we want to go 
that way, I could test the conversion and how this works for a translator.


regards,

André
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] [PATCH] fix for fdo#30800: Option to display calc gridlines on colored cells

2011-07-04 Thread André Schnabel 
Hi,

Am 04.07.2011 15:32, schrieb Katarina Machalkova:
>
> Well done! Attached is a small modification to the code (and the function) 
> I've made. I.e. it makes sense to allow user to define grid colour (and thus 
> enable fixed text & related listbox) in both cases when the grid is enabled 
> -- 
> in both "show" and "show on colored cells" case.

Yes, please apply with the modifications.

While

-if ( bGrid )
+if ( bGrid || bGridOnTop )


just makes more obvious, what happens - the other one

-aColorFT.Enable(bGridOnTop);
-aColorLB.Enable(bGridOnTop);
+aColorFT.Enable(bGrid);
+aColorLB.Enable(bGrid);

is a real error :(

> Also, before I really push the patch -- may I suggest some change to the 
> wording being used? 
> "Show on colored cells" sounds slghtly misleading to me, as the grid is 
> shown everywhere (all over the sheet), not only over the cells filled by some 
> colour. Something along "Show always on top" or "Show in the foreground" line 
> would imao describe its function much better ... Consequently, the option 
> name 
> would become GridOnTop, or GridInForeground, but that's just nitpicking ...


This had been discussed at some point (actually I did prefer "on top" as
you see in the implementation). But comments showed that "on top" or "in
foreground" is not a much better description. The grid is not really on
top, as it is still behind drawing elements, notes ... So I'd rather
stay with the current strings.


thanks and regards,

André



___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] extra testing needed for 3.4.2 Linux fullscreen slideshow

2011-07-03 Thread André Schnabel 
Hi Thorsten, *

Am 29.06.2011 10:49, schrieb Thorsten Behrens:
>
> Hm, so we need to pay special attention here. Andre, Sophie, do we
> have a place where to collect those "special QA" requests already?

Rainer started to collect ideas and people for monthly QA sessions, see
 
http://wiki.documentfoundation.org/QA-Projects-Incubator#Monthly_Bug_Hunting_Sessions

Although these are meant to be for bug triage, we could also use these
sessions to test new implementation.

I'd suggest, that developers interested in special testing add some
info, what needs to be tested - and provide a build for testing short
before the qa session.

Regards,

André
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

[Libreoffice] [PATCH] help for fdo#30800: Help for changed grid line option

2011-07-03 Thread André Schnabel 
Hi,

this would add the correct help strings for the patch I sent recently.

So if you apply the source code patch, please also apply this one to
change the help accordingly.

btw: I could also commit the help changes if this would make it easier.


Patch is contributed under LGPLv3+/MPL.

Thanks and regards,

André



>From 043c6ce63eef4b60a3e30ee7dac2bb14b06eb8a5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Schnabel?= 
Date: Sun, 3 Jul 2011 22:18:11 +0200
Subject: [PATCH] help for fdo#30800: help for changed grid line option

Changed help and tool tip strings for the new grid line option
(using tri-state drop-down instead of checkbox)
---
 .../source/text/scalc/guide/table_view.xhp |3 +--
 .../source/text/shared/optionen/01060100.xhp   |5 ++---
 2 files changed, 3 insertions(+), 5 deletions(-)

diff --git a/helpcontent2/source/text/scalc/guide/table_view.xhp b/helpcontent2/source/text/scalc/guide/table_view.xhp
index 8413a26..1af9c74 100644
--- a/helpcontent2/source/text/scalc/guide/table_view.xhp
+++ b/helpcontent2/source/text/scalc/guide/table_view.xhp
@@ -59,8 +59,7 @@
 To hide grid lines:
 
 
-Under the menu item %PRODUCTNAME - PreferencesTools - Options - %PRODUCTNAME Calc
-, go to the View tab page. Unmark Grid lines. Confirm with OK.
+Under the menu item %PRODUCTNAME - PreferencesTools - Options - %PRODUCTNAME Calc, go to the View tab page. Choose to hide Grid lines from the drop-down. Confirm with OK.
 
 
 
diff --git a/helpcontent2/source/text/shared/optionen/01060100.xhp b/helpcontent2/source/text/shared/optionen/01060100.xhp
index 7c5b936..7976bb4 100644
--- a/helpcontent2/source/text/shared/optionen/01060100.xhp
+++ b/helpcontent2/source/text/shared/optionen/01060100.xhp
@@ -76,11 +76,10 @@
   Visual aids
   Specifies which lines are displayed.
-
+
 Grid lines
-  Specifies whether to display grid lines between the cells.For printing, choose Format - Page - Sheet and mark the Grid check box.
-
+  Specifies when grid lines will be displayed. Default is to display grid lines only on cells that do not have a background color. You can choose to also display grid lines on cells with background color, or to hide them. For printing, choose Format - Page - Sheet and mark the Grid check box.
 
 Color
 Specifies a color for the grid lines in the current document. To see the grid line color that was saved with the document, go to %PRODUCTNAME - PreferencesTools - Options - %PRODUCTNAME - Appearance, under Scheme find the entry Spreadsheet - Grid lines and set the color to "Automatic".
-- 
1.7.3.4

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

[Libreoffice] [PATCH] fix for fdo#30800: Option to display calc gridlines on colored cells

2011-06-29 Thread André Schnabel 
Hi,

this is a patch to fix fdo#30800.

A tiny specification, what has been implemented is at the wiki:
http://wiki.documentfoundation.org/User:Andreschnabel/Spec_Calc_grid_lines_on_colored_background

Comments and questions are welcome, as this is the first time that I
actually *add* some code.

Patch is contributed under LGPLv3+/MPL.

Thanks and regards,

André



>From 619e34e7c3a594804cca9c6f6a070b534a2d074c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Schnabel?= 
Date: Wed, 29 Jun 2011 20:02:47 +0200
Subject: [PATCH] fix for fdo#30800: Option to display calc gridlines on colored cells

* change UI option for grid line display to tri-state drop down
* view option VOPT_GRID will take the information wheter to "Show"
  or "Hide" grid lines. New view option VOPT_GRID_ONTOP will take
  the information wheter to display grid lines on top of colored
  cells or not
* depending on VOPT_GRID_ONTOP grid lines will be drawn before or
  after drawing cell background in ScGridWindow::Draw
* store option as boolean property "GridOnColoredCells" (path:
  "/org.openoffice.Office.Calc/Layout/Line") in user config
* see
  http://wiki.documentfoundation.org/User:Andreschnabel/Spec_Calc_grid_lines_on_colored_background#UI_definitions
  for spec
---
 sc/inc/viewopti.hxx  |1 +
 sc/source/core/tool/viewopti.cxx |   11 +++-
 sc/source/ui/inc/optdlg.hrc  |3 +-
 sc/source/ui/inc/tpview.hxx  |5 ++-
 sc/source/ui/optdlg/tpview.cxx   |   50 +-
 sc/source/ui/src/optdlg.src  |   21 +--
 sc/source/ui/view/gridwin4.cxx   |2 +-
 7 files changed, 68 insertions(+), 25 deletions(-)

diff --git a/sc/inc/viewopti.hxx b/sc/inc/viewopti.hxx
index ad4641e..6ad4814 100644
--- a/sc/inc/viewopti.hxx
+++ b/sc/inc/viewopti.hxx
@@ -52,6 +52,7 @@ enum ScViewOption
 VOPT_OUTLINER,
 VOPT_HEADER,
 VOPT_GRID,
+VOPT_GRID_ONTOP,
 VOPT_HELPLINES,
 VOPT_ANCHOR,
 VOPT_PAGEBREAKS,
diff --git a/sc/source/core/tool/viewopti.cxx b/sc/source/core/tool/viewopti.cxx
index 97139c6..85e6b0d 100644
--- a/sc/source/core/tool/viewopti.cxx
+++ b/sc/source/core/tool/viewopti.cxx
@@ -153,6 +153,7 @@ void ScViewOptions::SetDefaults()
 aOptArr[ VOPT_FORMULAS	  ] =
 aOptArr[ VOPT_SYNTAX	  ] =
 aOptArr[ VOPT_HELPLINES   ] =
+aOptArr[ VOPT_GRID_ONTOP  ] =
 aOptArr[ VOPT_BIGHANDLES  ] = false;
 aOptArr[ VOPT_NOTES		  ] =
 aOptArr[ VOPT_NULLVALS	  ] =
@@ -308,7 +309,8 @@ SfxPoolItem* ScTpViewItem::Clone( SfxItemPool * ) const
 #define SCLAYOUTOPT_VERTSCROLL		8
 #define SCLAYOUTOPT_SHEETTAB		9
 #define SCLAYOUTOPT_OUTLINE			10
-#define SCLAYOUTOPT_COUNT			11
+#define SCLAYOUTOPT_GRID_ONCOLOR11
+#define SCLAYOUTOPT_COUNT			12
 
 #define CFGPATH_DISPLAY		"Office.Calc/Content/Display"
 
@@ -343,6 +345,7 @@ Sequence ScViewCfg::GetLayoutPropertyNames()
 static const char* aPropNames[] =
 {
 "Line/GridLine",			// SCLAYOUTOPT_GRIDLINES
+"Line/GridOnColoredCells",  // SCLAYOUTOPT_GRID_ONCOLOR
 "Line/GridLineColor",		// SCLAYOUTOPT_GRIDCOLOR
 "Line/PageBreak",			// SCLAYOUTOPT_PAGEBREAK
 "Line/Guide",// SCLAYOUTOPT_GUIDE
@@ -445,6 +448,9 @@ ScViewCfg::ScViewCfg() :
 case SCLAYOUTOPT_GRIDLINES:
 SetOption( VOPT_GRID, ScUnoHelpFunctions::GetBoolFromAny( pValues[nProp] ) );
 break;
+case SCLAYOUTOPT_GRID_ONCOLOR:
+SetOption( VOPT_GRID_ONTOP, ScUnoHelpFunctions::GetBoolFromAny( pValues[nProp] ) );
+break;
 case SCLAYOUTOPT_PAGEBREAK:
 SetOption( VOPT_PAGEBREAKS, ScUnoHelpFunctions::GetBoolFromAny( pValues[nProp] ) );
 break;
@@ -613,6 +619,9 @@ IMPL_LINK( ScViewCfg, LayoutCommitHdl, void *, EMPTYARG )
 case SCLAYOUTOPT_GRIDLINES:
 ScUnoHelpFunctions::SetBoolInAny( pValues[nProp], GetOption( VOPT_GRID ) );
 break;
+case SCLAYOUTOPT_GRID_ONCOLOR:
+ScUnoHelpFunctions::SetBoolInAny( pValues[nProp], GetOption( VOPT_GRID_ONTOP ) );
+break;
 case SCLAYOUTOPT_PAGEBREAK:
 ScUnoHelpFunctions::SetBoolInAny( pValues[nProp], GetOption( VOPT_PAGEBREAKS ) );
 break;
diff --git a/sc/source/ui/inc/optdlg.hrc b/sc/source/ui/inc/optdlg.hrc
index 4cdb0a5..90c0db7 100644
--- a/sc/source/ui/inc/optdlg.hrc
+++ b/sc/source/ui/inc/optdlg.hrc
@@ -145,7 +145,6 @@
 #define CB_TBLREG		54
 #define CB_OUTLINE		55
 #define GB_LINES		56
-#define CB_GRID			57
 #define FT_COLOR		58
 #define LB_COLOR		59
 #define CB_GUIDELINE	60
@@ -162,6 +161,8 @@
 #define FL_SEPARATOR1   71
 #define FL_SEPARATOR2   72
 #define FL_SEPARATOR73
+#define FT_GRID 74
+#define LB_GRID 75
 
 // TP_INPUT
 #define GB_OPTIONS		70
diff --git a/sc/source/ui/inc/tpview.hxx b/sc/source/ui/inc/tpview.h

Re: [Libreoffice] [PATCH] fix for fdo#32421: set indent for footnotes / endnotes to 0.6cm

2011-06-21 Thread André Schnabel 

Hi Tor,


Am 22.06.2011 07:00, schrieb Tor Lillqvist:

Patch is attached. It is just setting the indent for Footnote / Endnote
styles to 0.6cm (previously 0.5cm). It has not big effect to footnotes
<=99 but makes them prettier for numbers>=100.

I guess actually fixing it so that the (automatic?) indentation depends on the 
number of footnotes is hard?


This would have to be done at another place - not in the style but for 
the paragraph, when the footnote gets inserted (check number width, 
calculate widht, apply attributes per Paragraph).


This would be higher efford and the outcome would not be desirable, as 
thenthe  user would have inconistent display of footnotes.



This indentation can be modified manually afterwards, right?


yes. That's the workaround, already mentioned in the bug report.


How many footnotes to "typical" documents have (yeah, I know zero...). I mean, how many 
footnotes do "typical" documents that have footnotes at all have?


I'd assume scientific or legal documents to have something like 100..300 
footnotes / endnotes.  But I'm not an expert in this. I can as 
Jacqueline (who pointed me to the bugreport - she is our "german writer 
expert").


André
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

[Libreoffice] [PATCH] fix for fdo#32421: set indent for footnotes / endnotes to 0.6cm

2011-06-21 Thread André Schnabel 
Hi,

as I was trying to get an idea how (and where)  the "internal" writer
styles are implemented. So I found fdo#32421 a really easy hack :)

Patch is attached. It is just setting the indent for Footnote / Endnote
styles to 0.6cm (previously 0.5cm). It has not big effect to footnotes
<=99 but makes them prettier for numbers >=100.

The modification does only have local effect and will only be seen for
new writer files (imo no need to migrate any files or care about
document fidelity for existing files).

Patch is contributed under LGPLv3+/MPL.

regards,

André
>From 1feeb60b76dbf3b97029bcc003481ac3520da8e5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Schnabel?= 
Date: Tue, 21 Jun 2011 16:55:41 +0200
Subject: [PATCH] fix for fdo#32421: set indent for footnotes / endnotes to 0.6cm

with this footnotes with number >99 will look much better
---
 sw/source/core/doc/poolfmt.cxx |8 
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/sw/source/core/doc/poolfmt.cxx b/sw/source/core/doc/poolfmt.cxx
index 54e9a93..e97b56b 100644
--- a/sw/source/core/doc/poolfmt.cxx
+++ b/sw/source/core/doc/poolfmt.cxx
@@ -575,12 +575,12 @@ SwTxtFmtColl* SwDoc::GetTxtCollFromPool( sal_uInt16 nId, bool bRegardLanguage )
 }
 break;
 
-case RES_POOLCOLL_FOOTNOTE:// Fussnote
-case RES_POOLCOLL_ENDNOTE:
+case RES_POOLCOLL_FOOTNOTE: // paragraph style Footnote
+case RES_POOLCOLL_ENDNOTE:  // paragraph style Endnote
 {
 SvxLRSpaceItem aLR( RES_LR_SPACE );
-aLR.SetTxtFirstLineOfst( -(short)GetMetricVal( CM_05 ));
-aLR.SetTxtLeft( GetMetricVal( CM_05 ));
+aLR.SetTxtFirstLineOfst( -(short)( GetMetricVal( CM_05 ) + GetMetricVal( CM_01 ) ) );
+aLR.SetTxtLeft( GetMetricVal( CM_05 ) + GetMetricVal( CM_01 ) );
 SetAllScriptItem( aSet, SvxFontHeightItem( PT_10, 100, RES_CHRATR_FONTSIZE ) );
 aSet.Put( aLR );
 SwFmtLineNumber aLN; aLN.SetCountLines( sal_False );
-- 
1.7.3.4

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

[Libreoffice] [PATCH] fix for fdo#37761: Keyboard navigation broken in tools - options

2011-05-31 Thread André Schnabel 

Hi,

we came across a minor accessability issue at the German discuss list. 
But the fix is so easy that even I could do it.


It's just to remove one line that breaks the keyboard navigation in the 
options dialog and has no sense at all. Christoph Noack confirmed tha 
change for UX at bugzilla.


Patch is contributed under LGPLv3+/MPL.

regards,

André
>From 9e94864caaad5784e79da12c1f67d10994017640 Mon Sep 17 00:00:00 2001
From: Andre Schnabel 
Date: Tue May 31 18:56:12 CEST 2011
Subject: [PATCH] fix for fdo#37761:  Keyboard navigation broken in tools - 
options

prevent that aAutoSaveEdit will grab the focus in options dialog
---
 cui/source/options/optsave.cxx |1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/cui/source/options/optsave.cxx b/cui/source/options/optsave.cxx
index c0719b4..4e98d90 100644
--- a/cui/source/options/optsave.cxx
+++ b/cui/source/options/optsave.cxx
@@ -544,7 +544,6 @@ IMPL_LINK( SfxSaveTabPage, AutoClickHdl_Impl, CheckBox *, 
pBox )
 {
 aAutoSaveEdit.Enable();
 aMinuteFT.Enable();
-aAutoSaveEdit.GrabFocus();
 }
 else
 {
-- 
1.7.3.4

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] [libreoffice-l10n] Beta 4, untranslated strings

2011-05-07 Thread André Schnabel 

Hi,

Am 07.05.2011 01:35, schrieb Olivier Hallot:

Hi Andras

I found many, many strings in the UI that were left in english in the 
Beta4 in the pt-br build for windows.


Same for German.

Thank god or homever we didn't name this once again broken build "RC". :(

For German the stylenames, object names in Navigator are untranslated. 
Complete frame / object properties dialog and formatting dialoges are a 
mess (one page is translated others are not).


André

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] [libreoffice-l10n] Names of Impress backgrounds not localized

2011-01-07 Thread André Schnabel 

Hi,


Am 07.01.2011 17:36, schrieb Michael Meeks:


https://bugs.freedesktop.org/show_bug.cgi?id=32897

This fixes the problem (we think) (Thanks Caolan) - so for now, we can
run it on the template docs, and check them in - though it'd be great to
test that on your Linux machine in your language. In future we should do
that during the build I think.

Testing much appreciated,


Not tested but tried to find my own solution (without reading the mails 
first) and came to exactly the same way to fix it (not yet automated).


So - the way to clean up the language info is correct (gives 
presentation with de-DE locale created from the cleaned template).
The demoscript looks also correct to me (not tested,  but see no problem 
in it).


Thanks! (means - I'm happy :) )

André
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] Minutes technical group call

2010-11-11 Thread André Schnabel 

Hi,

short update ...

Am 11.11.2010 15:01, schrieb Michael Meeks:

* L10n
+ additional libreoffice strings, waiting for string freeze, get PO
  files, then you translate this. need a date.


We will hopefully have "tomorrow" as date (l10n list has already been 
notified).



+ some teams have asked to update the sdf files - in theory Andre
  has commit access, but at the moment not able to build sdf files,
  such that they are similar to the ones in the repo. Andre is
  referring to the big ones inside l10n module. don't know what
  templates have been used there - cannot build an sdf file that's
  similar to the ones from OOo
+ need to grok existing tooling (Fridrich / Petr)


Petr did provide some tooling, and ..


+ 4 south african langs, by friedel wolf and dwaine - five langs.


I processed those languages (with Petr's help). So in case there are 
more requests, either me or Petr can handle these requests (but it's 
manual work at the moment). It's not to complicated, so other people can 
help as well.


regards,

André


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] LibreOffice config migration

2010-10-15 Thread André Schnabel 

Hi,

Am 15.10.2010 17:21, schrieb Michael Meeks:


So - here is my suggestion ;-) hopefully it annoys everybody, and it is
two-fold.



(no question on 1. - harden the code for migration)
...

2. we continue to do automatic config migration since this is
   a commonly desired use-case
*but*
   as we migrate the settings the first time, we write into the
   (original - ie. the old version)'s directory a stamp file
   that says "these have been imported"
*and*
   if the same version is run again with the new settings
   directory removed (ie. someting went wrong); we prompt the
   user on the second time:
"do you want to (re-)import settings from ABC install"



Sounds like a reasonable compromise to me. Mechtilde?

regards,

André
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] LibreOffice config migration

2010-10-13 Thread André Schnabel 

Hi,

Am 14.10.2010 07:51, schrieb Mechtilde:

please don't take any user information from older version without any
agreemaent of the user


I second this.



If you do so you haven't the possibilityy to start *office with a new
user directory e.g in case you destroy something yourself.


Correct. Config migration is not sometimes not very reliable and you may 
end up with a broken config. Best way to get around this is to remove 
config dir. But normally the people who give support only know about the 
*current* config dir - so if there are some legacy directories, these 
will not be removed and break the config at the next start.


André
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] [testscripts] Guidance and project management

2010-10-12 Thread André Schnabel 

Hi,


Am 09.10.2010 23:02, schrieb some...@boldandbusted.com:

Howdy. I was asked to post a message here to kick off a discussion of
test script coordination. I'm volunteering to help with them because a)
it's simple, and b) I'm simple.


:) you are simply welcome.



I know shell, as you can see from the add-modelines script I just
submitted, and I'm told that StarBASIC is "as easy", and that's what
(some? all?) of the test scripts are written in. So add me to the list
of folks on the "testscripts" team, please.


Well - we are just starting, so we need to establish the team first. But 
meanwhile you can start working.





What I'd like to see is some way to coordinate work surrounding the test
scripts:

* A wiki page with best practices, local custom, etc.


I just created a very simple page at the wiki to give people a start.
http://wiki.documentfoundation.org/Qa/testing/Using_Testtool

Could you please go through the page, try if it works and enhance it?

In genereal I would suggest to:
* learn how to run one manual test and analyze the results
* learn how to run a set of tests and analyze the results
* define a small set of testscripts that need to be stabel
* start improving those scripts (we will face many errors, just because 
LibO has additional or changed functionality compared to OOo)



* A status board (what is failing where, and what test scripts are born
bad and need some discipline)
* Pretty graphs and charts. Freenode IRC bot for queries?
* Some statistics. (Maybe use R?)


Yes, but this needs more people who have knowledge about the testtool 
and the time to set all this up. Everyone is welcome to work on this.


To run scripts in batch and analyze the results, we have some scripts in
testautomation/tools. The scripts are quite simple.


* A list of info about the team of folks on the "test scripts" team (is
this QA?), who is active and who is inactive.


I think, we can use the wiki for this.


* A section of bugzilla (or whatever bug tracker we're using) for
[testscript]-ers.



Hmm .. yes. But maybe not for the start.


best regards,

André
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice