Re: Slow and silent compilation

[Regis Perdreau]

Hi Mike,

I had 3.5.4; i have downgraded to 3.4.10, it works.

Tks

Régis Perdreau



Le dim. 22 sept. 2024 à 10:42, Mike Kaganski  a
écrit :

> On 22.09.2024 13:28, Regis Perdreau wrote:
> > With cygwin, Libreoffice takes ages, more than 6h to compile with no
> > indication on screen.. Compil time is usually less 2 hours with my
> > computer.
> > I have updated all.tools, visual studio, cygwin, libreoffice core.
>
> What version of cygwin do you have now? As far as I know, all 3.5.x
> versions have a problem, which I recall was fixed for 3.6, but that's
> not released yet. You need to downgrade to a 3.4.
>
>
> --
>
> Best regards,
>
> Mike Kaganski
>
>

Slow and silent compilation

[Regis Perdreau]

HI,

With cygwin, Libreoffice takes ages, more than 6h to compile with no
indication on screen.. Compil time is usually less 2 hours with my computer.
I have updated all.tools, visual studio, cygwin, libreoffice core.

I see :

[build DEP] LNK:Library/bootstraplo.dll.d
[build DEP] RC:smd/default
[build DEP] LNK:Library/smdlo.dll.d
[build DEP] RC:sm/default
[build DEP] LNK:Library/smlo.dll.d
[build DEP] RC:sot/default
[build DEP] LNK:Library/sotlo.dll.d
[build DEP] LNK:Executable/cpp.exe.d
[build DEP] LNK:Executable/g++-wrapper.exe.d
[build DEP] LNK:Executable/gcc-wrapper.exe.d
[build DEP] LNK:StaticLibrary/wrapper.lib.d
[build DEP] LNK:Executable/gbuildtojson.exe.d
[build DEP] LNK:Executable/concat-deps.exe.d
[build DEP] RC:smoketest/default
[build DEP] LNK:Library/smoketest.dll.d
[build DEP] RC:OGLTrans/default
[build DEP] LNK:Library/OGLTranslo.dll.d

And that's all.


What to do.?

Régis Perdreau

Windows build broken.

[Regis Perdreau]

Hi,

I follow carefully again windows build instruction wiki, but the windows
build does not work again. Could you we expect that it will work for
everybody not only on developper's computer ? (i know it's sometimes
difficult, but if we could have some news, it's better)

Regards,

Régis Perdreau

Re: build broken

[Regis Perdreau]

It works,
thanks a lot,

Régis Perdreau


Le ven. 9 févr. 2024 à 11:36, Regis Perdreau
 a écrit :
>
> Hi Stephan,
>
> you're right, i have #define HAVE_CPP_STRONG_ORDER 1
> I'm so happy to hear from you, and answer to a year mystery
> Only follow wiki procedure. Tks for advices, i will check this.
>
> Regards,
>
>
> Régis Perdreau
>
>
>
> Le ven. 9 févr. 2024 à 11:26, Stephan Bergmann 
>  a écrit :
>>
>> On 2/9/24 11:00, Regis Perdreau wrote:
>> > time to time, the master libreoffice build is broken
>>
>> What platform are you building on?  What compiler and what version of
>> that compiler are you using (Clang, GCC, ...)?  What standard library
>> and what version of that standard library are you using (LLVM's libc++,
>> GNU's libstdc++, ...)?  I assume your config_host/config_global.h has a line
>>
>> > #define HAVE_CPP_STRONG_ORDER 1
>>
>> with a "1" there and not a "0", right?
>>
>> (And next time, it would be helpful if you could copy any build output
>> into your email in a way that preserves line breaks; e.g. by using
>> non-HTML plain-text email and each line of the build output quoted with
>> "> " in front of it.)

Re: build broken

[Regis Perdreau]

Hi Stephan,

you're right, i have #define HAVE_CPP_STRONG_ORDER 1
I'm so happy to hear from you, and answer to a year mystery
Only follow wiki procedure. Tks for advices, i will check this.

Regards,


Régis Perdreau



Le ven. 9 févr. 2024 à 11:26, Stephan Bergmann <
stephan.bergm...@allotropia.de> a écrit :

> On 2/9/24 11:00, Regis Perdreau wrote:
> > time to time, the master libreoffice build is broken
>
> What platform are you building on?  What compiler and what version of
> that compiler are you using (Clang, GCC, ...)?  What standard library
> and what version of that standard library are you using (LLVM's libc++,
> GNU's libstdc++, ...)?  I assume your config_host/config_global.h has a
> line
>
> > #define HAVE_CPP_STRONG_ORDER 1
>
> with a "1" there and not a "0", right?
>
> (And next time, it would be helpful if you could copy any build output
> into your email in a way that preserves line breaks; e.g. by using
> non-HTML plain-text email and each line of the build output quoted with
> "> " in front of it.)
>

build broken

[Regis Perdreau]

Hi,

time to time, the master libreoffice build is broken
I suppose that when developers commit, they have tested their build, so
this should not happen :
Is there any explanation ?


/home/codeur/libo/libreoffice/chart2/source/view/main/VDataSeries.cxx: In
member function 'bool
chart::{anonymous}::lcl_LessXOfPoint::operator()(const
std::__debug::vector&, const std::__debug::vector&)':
/home/codeur/libo/libreoffice/chart2/source/view/main/VDataSeries.cxx:105:38:
error: no match for call to '(const std::__cmp_cust::_Strong_order) (const
value_type&, const value_type&)'
  105 | return o3tl::strong_order(first[0], second[0]) < 0;
  |~~^
In file included from /usr/include/c++/11/bits/stl_pair.h:65,
 from /usr/include/c++/11/bits/stl_algobase.h:64,
 from /usr/include/c++/11/memory:63,
 from
/home/codeur/libo/libreoffice/chart2/source/view/main/VDataSeries.cxx:21:
/usr/include/c++/11/compare:629:9: note: candidate: 'template  requires (__decayed_same_as<_Up, _Tp>) &&
(__strongly_ordered<_Tp, _Up>) constexpr std::strong_ordering
std::__cmp_cust::_Strong_order::operator()(_Tp&&, _Up&&) const'
  629 | operator()(_Tp&& __e, _Up&& __f) const
  | ^~~~
/usr/include/c++/11/compare:629:9: note:   template argument
deduction/substitution failed:
/usr/include/c++/11/compare:629:9: note: constraints not satisfied
/home/codeur/libo/libreoffice/chart2/source/view/main/VDataSeries.cxx: In
substitution of 'template  requires
(__decayed_same_as<_Up, _Tp>) && (__strongly_ordered<_Tp, _Up>) constexpr
std::strong_ordering std::__cmp_cust::_Strong_order::operator()(_Tp&&,
_Up&&) const [with _Tp = const double&; _Up = const double&]':
/home/codeur/libo/libreoffice/chart2/source/view/main/VDataSeries.cxx:105:38:
  required from here
/usr/include/c++/11/compare:598:15:   required for the satisfaction of
'__strongly_ordered<_Tp, _Up>' [with _Tp = const double&; _Up = const
double&]
/usr/include/c++/11/compare:601:11: note: no operand of the disjunction is
satisfied
  599 | = __adl_strong<_Tp, _Up>
  |   ~~
  600 |   // FIXME: || floating_point>
  |   
  601 |   || __cmp3way;
  |   ^~~
cc1plus: note: set '-fconcepts-diagnostics-depth=' to at least 2 for more
detail
make[1]: ***
[/home/codeur/libo/libreoffice/solenv/gbuild/LinkTarget.mk:340:
/home/codeur/libo/libreoffice/workdir/CxxObject/chart2/source/view/main/VDataSeries.o]
Error 1
make[1]: *** Waiting for unfinished jobs
make: *** [Makefile:290: build] Error 2



Régis Perdreau

Re: Embedded fonts

[Regis Perdreau]

Thanks, I'll check it out.

Regards,

Régis Perdreau



Le mer. 29 nov. 2023 à 10:37, Caolán McNamara 
a écrit :

> On Tue, 2023-11-28 at 17:08 +0100, Regis Perdreau wrote:
> > Hi,
> >
> > Is there any documentation anywhere about font embedding ?
> > It's not in the ODF standard
> > Is it a function that nobody use then nobody care ?
> > I think it's interesting to know why it was implemented.
>
> I don't remember too much about it at this distance in time but with
> some git log I get to an initial implementation in 2013 of
>
> https://cgit.freedesktop.org/libreoffice/core/commit/?id=989d0953a4d69bef3c8aba8e9dc7758194adcdc4
> referencing the 2011 bugzilla entry of
> https://bugs.documentfoundation.org/show_bug.cgi?id=42195
>
> Where the odf spec has: "Font face declarations support the font
> descriptor attributes and elements described in §20.8.3 of [SVG]."
> and svg allows: 
>
> In the UI you can get to this IIRC with file, properties, font and
> "Font Embedding". After the original commit I believe similar was
> implemented for OOXML support.
>

Embedded fonts

[Regis Perdreau]

Hi,

Is there any documentation anywhere about font embedding ?
It's not in the ODF standard
Is it a function that nobody use then nobody care ?
I think it's interesting to know why it was implemented.

Regards,

Régis Perdreau

Boost not included...

[Regis Perdreau]

Hi,

I have many difficulties to compile master :
I have tested on different version of GCC,  Clang and different
machines...there is always something broken, mainly some include are
missing...

i have this error message :
/home/codeur/libo/libreoffice/chart2/Library_chartcontroller.mk:21: ***
gb_LinkTarget_set_include: include paths
/home/codeur/libo/libreoffice/external/boost/include do not exist.  Stop.

I have another message that libcurl 4.8.0 is not included in the tarball...


How am I supposed to solve this ?
 the boost library is supposed to be downloaded and the directory created.
the right libcurl is supposed to be included

It's something strange to have this although contributors are supposed to
run tests and not commit something broken. I have tested on different
version of GCC and different machines..

Regards,

Régis Perdreau

Re: demande aide PHP mise à jour sur Windows

[Regis Perdreau]

Bonjour,

Je pense que vous vous êtes trompé de liste. Ici c'est les questions sur
LibreOffice.

Bien à vous,

Régis Perdreau



Le sam. 15 juil. 2023 à 18:55, cha degeil  a écrit :

> Bonjour
>
> J'ai installé wordpress (6.2.2) sur un serveur local . J'ai une alerte de
> sécurité sur WP qui me dit de mettre à jour la version PHP, 7.03 pour
> l'upgrader à 7.04. mais je ne sais pas comment faire. Quelqu'un peut
> m'expliquer  ? merci par avance
> Lucine
>

Re: Unsafe directory

[Regis Perdreau]

Hi Colomban,

I have set HOME to /tmp/mydir, it works.
Tks a lot.

Régis Perdreau



Le jeu. 13 juil. 2023 à 11:18, Colomban Wendling  a
écrit :

> Hello Régis,
>
> Le 13/07/2023 à 09:00, Regis Perdreau a écrit :
> > I'm trying to build master under Windows 11/cygwin.
> > Build failed with the message "autogen.sh: unsafe home directory:
> > `/home/Régis Perdreau"
>
> I'm not knowledgeable about Windows/CygWin, but I have two wild guesses:
> - the directory name contains non-ASCII characters ("é")
> - the directory name contains a space
>
> If it's anything like gnupg, it's likely the space (see the hardly
> readable check in https://github.com/gpg/gnupg/blob/master/autogen.sh#L127
> )
>
> You probably can work around this by either actually changing CygWin's
> homedir, or just adjust $HOME to point to some directory without those
> characters (e.g. HOME=/tmp/homedir, or anything less temporary yet still
> without spaces).
>
> HTH
> - Colomban
>

Unsafe directory

[Regis Perdreau]

Hi,


I'm trying to build master under Windows 11/cygwin.
Build failed with the message "autogen.sh: unsafe home directory:
`/home/Régis Perdreau"

and when compilation is stopped :

config.status: executing libtool commands

Libassuan v has been configured as follows:

Revision:   ()
Platform: x86_64-pc-mingw32

Making all in m4
Making all in src
mkheader.c
usage: mkheader host_os template.h version version_number
make[4]: *** [Makefile:1339: assuan.h] Error 1
make[3]: *** [Makefile:462: all-recursive] Error 1
make[2]: *** [Makefile:394: all] Error 2
make[1]: ***
[C:/sources/libo-core/external/libassuan/ExternalProject_libassuan.mk:26:
C:/sources/libo-core/workdir/ExternalProject/libassuan/build] Error 1
make[1]: *** Waiting for unfinished jobs

Any thoughts?

Thanks


Régis Perdreau

Re: Welcome Khaled Hosny, new Developer at TDF

[Regis Perdreau]

Great news, welcome, have fun !

Regards,
Régis Perdreau



Le mer. 31 mai 2023 à 07:05, Khaled Hosny  a écrit :

>
>
> > On 30 May 2023, at 10:36 AM, Mike Saunders <
> mike.saund...@documentfoundation.org> wrote:
> >
> > Hello everyone,
> >
> > Khaled Hosny has joined the team at The Document Foundation as a
> Developer focusing initially on RTL/CTL improvements:
> >
> >
> https://blog.documentfoundation.org/blog/2023/05/30/welcome-khaled-hosny-new-developer-at-tdf/
>
> Thanks everyone. I’m really happy to be able to work full time on
> LibreOffice.
>
> Regards,
> Khaled

Re: Compilation failed when linking

[Regis Perdreau]

Thanks,

I have added --with-system-icu, now it works.

regards,

Régis Perdreau



Le mar. 2 mai 2023 à 12:54, Eike Rathke  a écrit :

> Hi Regis,
>
> On Tuesday, 2023-05-02 07:50:31 +0200, Regis Perdreau wrote:
>
> > Compilation and linking failure with LibreOffice master (Linux)
> > clang version 10.0.0-4ubuntu1
> >
> >
> > ld.lld: error: undefined symbol:
> icu_72::UnicodeString::UnicodeString(char
> > const*)
> > >>> referenced by xmlparse.cxx:1069 (l10ntools/source/xmlparse.cxx:1069)
> >
> > What could be wrong?
>
> You probably somehow managed to compile against the internal ICU 72.1
> but link against the Ubuntu system ICU whatever.version.
>
> More context of the build log what it pulls in exactly where might be
> helpful.
>
>   Eike
>
> --
> GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918  630B 6A6C D5B7 6563
> 2D3A
>

Compilation failed when linking

[Regis Perdreau]

Hi,

Compilation and linking failure with LibreOffice master (Linux)
clang version 10.0.0-4ubuntu1


ld.lld: error: undefined symbol: icu_72::UnicodeString::UnicodeString(char
const*)
>>> referenced by xmlparse.cxx:1069 (l10ntools/source/xmlparse.cxx:1069)

What could be wrong?

Regards,

Régis Perdreau

Re: [libreoffice-marketing] Re: [libreoffice-design] Moving to LibreOffice 8?

[Regis Perdreau]

So, I agree with the proposal. L8 could be seen as a new start and not an
achievement... new developers mean new functionalities, evolving
organization. I think we can build something around that. Marketed as the
mix of different knowledge as distinguishing elements.

Regards,

Régis

Le ven. 7 avr. 2023 à 00:14, Italo Vignoli  a écrit :

> I have written that developers have a different mindset from marketing
> people. I have never said that developers are dumb people, and I have
> never even thought this.
>
> On 06/04/23 23:45, Regis Perdreau wrote:
> > Hi all,
> >
> > So if i understand correctly, developers are dumb people, talking only to
> > its computer, and marketer have the privilege to speak to real user...
> > Well, all the day, i speak to real user, and all say that marketers talk
> > non sense about Microsoft compatibility...
> > I wonder how to solve daily cognitive dissonnance
> > *
> > <
> https://context.reverso.net/traduction/anglais-francais/cognitive+dissonance
> >*
> > Just kidding
> >
> > Cheers,
> > Régis Perdreau
> >
> >
> >
> > Le jeu. 6 avr. 2023 à 23:00, Gustavo Buzzatti Pacheco <
> gbpach...@gmail.com>
> > a écrit :
> >
> >> Hi, Nigel, Ben, Eyal, all!
> >>
> >>   Let me add some comments. :)
> >>
> >>   For sure, the current approach is a requirement for our internal
> >> development organization, as Ben noted. Also, it was really important in
> >> the first years of LibreOffice/TDF, when we used it to demonstrate we
> were
> >> ahead of Apache OpenOffice for the users and the strong
> project/community
> >> we were building.
> >>
> >>   On the other hand, for the current moment of LibreOffice as a project
> and
> >> product, I think we can do more or different things. Nigel wrote
> >> exactly what I mean about 'boring' from the user perspective: most of
> the
> >> users don't care about minor changes.
> >>
> >>   So, I think, now, we should decide about releases with a Marketing
> >> perspective and the number 8 could be a first step to do it, even
> without
> >> big changes.
> >>
> >>   Could it mean we will do a marketing trick?
> >>
> >>   I think no, because we will be transparent with our users as we always
> >> have been. If the release won't have big improvements, we won't talk
> about
> >> big improvements.
> >>
> >>   Why release a version without big improvements?
> >>
> >>   That is the other point: I don't think we should focus only on big
> code
> >> improvements to use major version numbers (or even version names). We
> >> aren't only a product. We are a project and community. Indeed, the
> released
> >> product is our final work but a major version can also be used to spread
> >> (or celebrate) the maturity of the product/project/community. This is a
> >> different approach than paid software/non FLOSS. This is what I mean
> with
> >> consolidation.
> >>
> >>
> >> On Thu, Apr 6, 2023 at 8:22 AM Nigel Verity 
> >> wrote:
> >>
> >>> Hi Gustavo
> >>>
> >>> This is a very good point.
> >>>
> >>> If I see that some software I use regularly has gone from 7.5 to 7.6,
> >>> say, I wouldn't rush to upgrade unless I knew it fixed a problem that
> >>> affected me. I'm pretty sure that I would upgrade from 7.5 to to 8.0
> far
> >>> more quickly, if for no other reason that the psychological one of
> wanting
> >>> to be using what my head tells me must be an improvement over my
> current
> >>> version.
> >>>
> >>> Of course release notes are available to determine what really has
> >>> changed but I rather suspect that most users never read them.
> >>>
> >>> The discussion of the different motivators for development and
> marketing
> >>> people is very interesting. When I was a developer neither I nor
> anybody in
> >>> my teams was ever let anywhere near sales activities - and I think for
> very
> >>> good reasons.
> >>>
> >>> Cheers
> >>>
> >>> Nige
> >>>
> >>>
> >>> * LibreOffice - Free and open source office suite: LibreOffice Website
> >>> <https://www.libreoffice.org/> *
> >>> * Respects your privacy, and gives you back control over your data*
> >>&g

Re: [libreoffice-marketing] Re: [libreoffice-design] Moving to LibreOffice 8?

[Regis Perdreau]

Hi all,

So if i understand correctly, developers are dumb people, talking only to
its computer, and marketer have the privilege to speak to real user...
Well, all the day, i speak to real user, and all say that marketers talk
non sense about Microsoft compatibility...
I wonder how to solve daily cognitive dissonnance
*
*
Just kidding

Cheers,
Régis Perdreau



Le jeu. 6 avr. 2023 à 23:00, Gustavo Buzzatti Pacheco 
a écrit :

> Hi, Nigel, Ben, Eyal, all!
>
>  Let me add some comments. :)
>
>  For sure, the current approach is a requirement for our internal
> development organization, as Ben noted. Also, it was really important in
> the first years of LibreOffice/TDF, when we used it to demonstrate we were
> ahead of Apache OpenOffice for the users and the strong project/community
> we were building.
>
>  On the other hand, for the current moment of LibreOffice as a project and
> product, I think we can do more or different things. Nigel wrote
> exactly what I mean about 'boring' from the user perspective: most of the
> users don't care about minor changes.
>
>  So, I think, now, we should decide about releases with a Marketing
> perspective and the number 8 could be a first step to do it, even without
> big changes.
>
>  Could it mean we will do a marketing trick?
>
>  I think no, because we will be transparent with our users as we always
> have been. If the release won't have big improvements, we won't talk about
> big improvements.
>
>  Why release a version without big improvements?
>
>  That is the other point: I don't think we should focus only on big code
> improvements to use major version numbers (or even version names). We
> aren't only a product. We are a project and community. Indeed, the released
> product is our final work but a major version can also be used to spread
> (or celebrate) the maturity of the product/project/community. This is a
> different approach than paid software/non FLOSS. This is what I mean with
> consolidation.
>
>
> On Thu, Apr 6, 2023 at 8:22 AM Nigel Verity 
> wrote:
>
>> Hi Gustavo
>>
>> This is a very good point.
>>
>> If I see that some software I use regularly has gone from 7.5 to 7.6,
>> say, I wouldn't rush to upgrade unless I knew it fixed a problem that
>> affected me. I'm pretty sure that I would upgrade from 7.5 to to 8.0 far
>> more quickly, if for no other reason that the psychological one of wanting
>> to be using what my head tells me must be an improvement over my current
>> version.
>>
>> Of course release notes are available to determine what really has
>> changed but I rather suspect that most users never read them.
>>
>> The discussion of the different motivators for development and marketing
>> people is very interesting. When I was a developer neither I nor anybody in
>> my teams was ever let anywhere near sales activities - and I think for very
>> good reasons.
>>
>> Cheers
>>
>> Nige
>>
>>
>> * LibreOffice - Free and open source office suite: LibreOffice Website
>>  *
>> * Respects your privacy, and gives you back control over your data*
>> --
>> *From:* Gustavo Buzzatti Pacheco 
>> *Sent:* 05 April 2023 22:05
>> *To:* TDF Devs ; TDF Marketing <
>> market...@global.libreoffice.org>; TDF Design <
>> des...@global.libreoffice.org>
>> *Subject:* Re: [libreoffice-marketing] Re: [libreoffice-design] Moving
>> to LibreOffice 8?
>>
>> Hi Eyal, all!
>>
>>  I also respectfully disagree with you on some points. ;D
>>
>>  I like the idea to move to 8, even with no big technical innovation (if
>> we
>> have, for sure it will be better).
>>
>>  IMHO, long sequences of minor releases (7.6, in the current case) are
>> getting boring and not important for the users (for both enterprise and
>> individual profiles).
>>
>>  I'm not saying that we should embrace the Firefox approach, but thinking
>> about Italo's idea (8 <-> infinite), I guess the message of this version
>> could be consolidation, not exactly innovation.
>>
>> Best
>> Gustavo
>>
>>
>> On Tue, Mar 28, 2023 at 4:23 AM Eyal Rozenberg  wrote:
>>
>> > I respectfully disagree with Italo.
>> >
>> > First, about the "frame of reference". In my opinion, decisions such as
>> > major version number bumping are not, first and foremost, marketing
>> > decisions. That is a _consideration_, since the version number is
>> > declarative than technical. But - such an action should be "truthful"
>> > before being "marketable".
>> >
>> > It is more important, in my opinion, that users and potential users
>> > receive trustworthy signaling from the project - not just w.r.t. version
>> > numbers, but generally - than for the media to get a gimmick for
>> coverage.
>> >
>> > A second point is that bumping a version number without a major
>> > innovation moves you a few more steps into the category of, say, Firefox
>> > and such, where versions just increase automatically with no meaning
>

Bug 145666 - "Arial black" is not used for the "Text field" form when exporting as pdf.

[Regis Perdreau]

Hi

When exporting odt to pdf, text font are not the same in text box, radio
button.
Verdana font is exported as Arial 10.

Could i have any code pointers ?



Régis Perdreau

Re: ESC meeting agenda: 2022-03-31 16:00 Berlin time

[Regis Perdreau]

Hi,

I suggest that the members of the top ten are not taken into account
in the next period, in the goal to diversify and encourage people to
participate :)

All the bests.


Régis Perdreau



Le mer. 30 mars 2022 à 16:56, Miklos Vajna  a écrit :

> Hi,
>
> The prototype agenda is below. Extra items are appreciated either in
> this document or as a reply to this mail:
>
> https://pad.documentfoundation.org/p/esc
>
> You can join using Jitsi here:
>
> https://jitsi.documentfoundation.org/esc
>
> Regards,
>
> Miklos
>
> 
>
> * Present:
>  +
>
> * Completed Action Items:
>  + None
>
> * Pending Action Items:
>  + uninstall system boost on Linux Jenkins slaves (Cloph)
>[ only one box remaining ]
>
> * Release Engineering update (Cloph)
>  + 7.4 status:
>+ feature freeze in June
>  + 7.3 status: 7.3.2 rc1
>  + 7.2 status: 7.2.7 rc1
>  + Remotes: Android, iOS
>  + Android viewer
>
> * Documentation (Olivier)
>  + Bugzilla Documentation statistics
>  242(242) bugs open
>  + Updates:
>  BZ changes   1 week   1 month   3 months   12 months
> created 8(3) 38(2) 122(-3) 322(-5)
>   commented 2(-30)   69(-17)   382(-34)   1486(-47)
>resolved 2(0) 15(1)  57(-3) 202(-2)
>  + top 10 contributors:
>Olivier Hallot made 32 changes in 1 month, and 492 changes in 1
> year
>Seth Chaiklin made 19 changes in 1 month, and 54 changes in 1
> year
>Dieter made 10 changes in 1 month, and 101 changes in 1 year
>Heiko Tietze made 9 changes in 1 month, and 87 changes in 1 year
>Bielefeld, Rainer made 8 changes in 1 month, and 10 changes in
> 1 year
>Kaganski, Mike made 6 changes in 1 month, and 89 changes in 1
> year
>Alain Romedenne made 5 changes in 1 month, and 38 changes in 1
> year
>Ilmari Lauhakangas made 4 changes in 1 month, and 109 changes
> in 1 year
>steve -_- made 4 changes in 1 month, and 7 changes in 1 year
>Roman Kuznetsov made 3 changes in 1 month, and 30 changes in 1
> year
>
> * UX Update (Heiko)
>  + Bugzilla (topicUI) statistics
>  264(264) (topicUI) bugs open, 79(79) (needsUXEval) needs to be
> evaluated by the UXteam
>  + Updates:
>  BZ changes   1 week   1 month   3 months   12 months
>   added  4(-3) 8(-2)17(-2)  44(-3)
>   commented 45(-4)   228(-7)   630(14)2689(-30)
> removed  0(-2) 4(-1)13(0)   35(-1)
>resolved  3(-1)28(-4)   101(2)  400(-1)
>  + top 10 contributors:
>Heiko Tietze made 150 changes in 1 month, and 1909 changes in 1
> year
>Dieter made 28 changes in 1 month, and 227 changes in 1 year
>Eyal Rozenberg made 26 changes in 1 month, and 139 changes in 1
> year
>Timur made 20 changes in 1 month, and 120 changes in 1 year
>Ilmari Lauhakangas made 20 changes in 1 month, and 261 changes
> in 1 year
>Yeron 50201 made 17 changes in 1 month, and 17 changes in 1 year
>Di Hox made 16 changes in 1 month, and 16 changes in 1 year
>Robert Großkopf made 16 changes in 1 month, and 31 changes in 1
> year
>Juan C. Sanz made 13 changes in 1 month, and 13 changes in 1
> year
>Németh, László made 11 changes in 1 month, and 28 changes in 1
> year
>
> * Crash Testing (Caolan)
>  + 10(+0) import failure, 3(+0) export failures
>  + ??? coverity issues
>  + Google / ossfuzz: ?? fuzzers active now
>
> * Crash Reporting (Xisco)
>  + 7.2.6.21103(+634)
>  + 7.3.0.2131(+3)
>  + 7.3.0.324562(+1875)
>  + 7.3.1.38940(+3312)
>
> * Mentoring/EasyHack update (Hossein)
>committer...   1 week 1 month  3 months12 months
>open  66(6)  133(-45) 135(-46) 137(-46)
> reviews 476(116)   1502(-164)   3762(-50)   12692(-94)
>  merged 289(72)1401(-78)3997(-6)15711(-81)
>   abandoned  59(-51)190(24)  332(44)  864(44)
> own commits 205(43)1011(-66)3093(-16)   12512(-68)
>  review commits  49(-45)254(-37) 879(-54)3757(-72)
>  contributor...   1 week 1 month  3 months 12 months
>open  21(-1)  61(-103) 62(-103)
> 66(-103)
> reviews 966(-84)   3856(-98)9328(-20)34632(-88)
>  merged   9(-26) 79(-13) 226(-36) 1513(-25)
>   abandoned 106(91) 128(105) 171(98)   469(96)
> own commits   9(-53) 91(-29) 286(-68) 1524(-33)
>  review commits   0(0)0(0) 0(0)  0(0)
>  + easyHack statistics:
> needsDevEval 8(8)   needsUXEv

Re: Hi (Formats supported by LibreOffice).

[Regis Perdreau]

Hi,

Sorry, in Europe, we like to lose money, that's what our governments do
every day, top management always provides examples ;-)

>From your USA window, i think your vision is not as wide as you expect.
Some European states use it, french ministries, numerous big
cities...although they do not claim it at every street corner.


Régis Perdreau




Le mer. 23 mars 2022 à 08:43, A  a écrit :

>
> On Wed, 23 Mar 2022 at 13:06, Mike Kaganski 
> wrote:
>
>> On 23.03.2022 10:31, A wrote:
>> > Why is LO focussing on both MS formats and ODF?
>> >
>> > By focusing on both formats, it is not producing very good software in
>> > either of these.
>> >
>> > It should focus on only one format so that it can do a much better job.
>> >
>> > I am saying all this because LO is run by volunteers and it is not
>> > getting much resources and money from outside.
>> >
>> > So, whatever limited resources it has, it should use that optimally to
>> > produce one "very good" product.
>>
>> This implies that the volunteers (and contributors in general) all
>> should be *guided* in what they focus on. So the project should be
>> totally controlled from some central place, and everyone must either
>> work on what is "permitted", or not work at all.
>>
>> This is not how the project works. If (say) *I* need MS compatibility
>> improved (just imagining; I actually care about both), I will work on
>> that, and my work will be included in the software for the benefit of
>> others, regardless if others think that ODF is their priority. My work
>> doesn't prevent others to improve ODF support. But if others tell me "do
>> not work on OOXML compatibility, but focus on ODF", my manpower will not
>> be re-directed - I will just leave.
>>
>
>
> What LO people fail to realize is that LO is not very popular and it will
> not be and their efforts are going to waste.
>
> No big organizations/governments are using LO.
>
> I used to use LO and I sent a document which I wrote using LO but the
> recipient said that he could not open it.
>
> Then I bought MS Office and sent the document (which I wrote in MS Office)
> and he was able to open it.
>
> So, I ended up buying MS Office.
>
> In my opinion, LO is a wasted effort if it does not focus on only one
> thing.
>
> Some people will leave if LO focuses on only one thing but then other
> people will join.
>
> I will contribute to LO if LO focuses only on MS Office formats because I
> want people to save money.
>
> Amit
>
>

Re: Hi (Formats supported by LibreOffice).

[Regis Perdreau]

HI Amit,

OnlyOffice works in that way. It is supposed to provide Office
compatibility...
It's far from being perfect.
I really think the best way is to use a format designed for
interoperability, well documented, stable, all that OOXML is not.

ATB

Régis Perdreau



Le mer. 23 mars 2022 à 08:12, A  a écrit :

>
>
> On Wednesday, 23 March 2022, Jonathan Aquilina 
> wrote:
>
>> Amit,
>>
>> Why then dont you go barking to microsoft and tell them that they shoudl
>> focus on their formats only?
>>
>> Software will never be perfect there will always be room for improvement.
>>
>> What are you finding missing or that LO isnt doing well?
>>
>> Regards,
>> Jonathan
>> --
>>
>>
>
> You are again offending me by using the word "barking".
>
> Amit
>
>

Need code pointer for export bug TDF #145666

[Regis Perdreau]

Hi,

Could i have any code pointers about
https://bugs.documentfoundation.org/show_bug.cgi?id=145666 ?
It's a fonts problem in pdf when exporting Libreoffice controls. The font
in the exported text zone is not the same as the odt document (we have
Arial instead of Verdana)

Regards,

Régis Perdreau

Re: LibreOffice 7.2.0.4 : bug report

[Regis Perdreau]

Bonjour,

Je pense que vous feriez mieux de prendre la version 7.1.5 ici
https://fr.libreoffice.org/download/telecharger-libreoffice/?type=win-x86&version=7.2.0&lang=fr
version X64 probablement de nos jours ...
Vous avez pris une version qui peut etre qualifiée d'expérimentalr, des
plantages sont possibles...c'est clairement expliqué.

Par contre effectivement, vous aideriez la communauté en explicitant
comment vous avez réussi à obtenir le crash en question.
Les informations que vous avez récupèré ne permette pas directement
d'obtenir la cause...



Régis Perdreau



Le mar. 7 sept. 2021 à 23:05, Lydie TREBUCHON 
a écrit :

> Bonjour,
>
>
>
> Voici le bug que j’ai malheureusement sur mon ordinateur lorsque j’ouvre
> Calc, je saisis des chiffres dans une cellule et je fais Entrée.
>
> Rapport en pièce jointe.
>
> Ça fait peur pour un logiciel à peine installé et dont le code a soit
> disant était revu et dépoussiéré. C’est à vous dégoûter du libre.
>
> Microsoft a encore de beau jours devant lui !
>
>
>
> Cordialement,
>
> Pierre
>
>
>

Re: Weekly Progress of GSoC project

[Regis Perdreau]

Hi,

I'm trying to follow progress about this Gsoc and others, so it's nice to
have little thinkings about before.

We have error 500 when following the link above. (
https://summerofcode.withgoogle.com/dashboard/project/5869092168269824/details/
)

Cheers,

Régis Perdreau



Le dim. 6 juin 2021 à 08:40, Heiko Tietze <
heiko.tie...@documentfoundation.org> a écrit :

> Actually it was week zero - the real coding period begins tomorrow Jul/07
> and
> lasts until Aug/16. Google's idea of the current "bonding" is to make
> yourself
> familiar with code and community, which you did greatly.
>
> Cheers,
> Heiko
>
> On 05.06.21 21:07, anshu khare wrote:
> > Hi
> >
> > My GSoC project can be viewed here :
> >
> https://summerofcode.withgoogle.com/dashboard/project/5869092168269824/details/
> > <
> https://summerofcode.withgoogle.com/dashboard/project/5869092168269824/details/
> >
> >
> > In my first week, I made a good connection with my mentors. We came out
> with
> > different ways of communication. I really enjoyed talking to them and
> discussing
> > different ideas and approaches for the project.
> > In the technical aspect, I made a treeview and loaded Character Styles
> in that
> > treeview..
> >
> > My patch can be found here :
> https://gerrit.libreoffice.org/c/core/+/116340
> > 
> >
> > Looking forward to implement many more ideas in the next week :)
> >
> > Thanks
> > Regards
> > Anshu
> >
> >
> >
> >
> >
> >
> >
> > ___
> > LibreOffice mailing list
> > LibreOffice@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/libreoffice
> >
>
> --
> Dr. Heiko Tietze, UX-Designer and UX-Mentor
> Tel: +49 30 5557992-63 | Mail: heiko.tie...@documentfoundation.org
> The Document Foundation, Kurfürstendamm 188, 10707 Berlin, DE
> Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
> Legal details: https://www.documentfoundation.org/imprint
>
> ___
> 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

Re: autofilter in another line than line 2

[Regis Perdreau]

Tks for answer, but it's a dev/odf/interoperability question, an user can't
answer
I will make a bug report.


Régis Perdreau



Le mar. 10 nov. 2020 à 10:15, Mike Kaganski  a
écrit :

> Hi Régis Perdreau,
>
> On 10.11.2020 12:04, Regis Perdreau wrote:
> > Hi,
> >
> > I have a xlsx document from office suite with autofilter in line 2, do
> > we support autofilter in another line than line 1 ? Because when i try
> > to modify the document, the autofilter is automatically put into line
> > 1..it is not what i want.
> > A workaround is the insert column before autofilter which stays in line
> > 2 in this case.
>
> This is a user question, and should be posted to a user mailing list, or
> to another user help resource like https://ask.libreoffice.org.
>
> Answering the question, AutoFilters are applied either to the sheet, or
> to a database range (and in the latter case, you may define such
> range(s) in any place of a sheet using Data|Define Range); for ranges,
> several AutoFilters are possible on the same sheet.
>
> > I see in the bugzilla that numerous bugs stand about autofilter.
>
> It's unclear what bugs you refer to specifically, and what does it have
> with the first question.
>
> > Regards,
> >
> > Régis Perdreau
>
>
> --
> Best regards,
> Mike Kaganski
>
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

autofilter in another line than line 2

[Regis Perdreau]

Hi,

I have a xlsx document from office suite with autofilter in line 2, do we
support autofilter in another line than line 1 ? Because when i try to
modify the document, the autofilter is automatically put into line 1..it is
not what i want.
A workaround is the insert column before autofilter which stays in line 2
in this case.
I see in the bugzilla that numerous bugs stand about autofilter.

Regards,

Régis Perdreau
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Logerrit Error

[Regis Perdreau]

Hi,
it looks like the script has no idea where to go.

Well, have you something in your .ssh/config file?
in your home, do
cat .ssh/config

Something like this ?

 Host logerrit gerrit.libreoffice.org
   IdentityFile /path/to/your/private-key
   User YOUR_USERNAME_HERE
   Port 29418
   HostName gerrit.libreoffice.org



Regards,

Régis Perdreau



Le sam. 17 oct. 2020 à 01:35, Mariam Fahmy  a
écrit :

> Hey, I am Mariam, I am new in the open source community, I want to submit
> my patches in Gerrit for review.
> But here are some error:
> ./logerrit test
>
> There seems to be trouble. Please have the output of:
> ssh - logerrit
> at hand when looking for help.
>
> ssh -vvv logerrit
>
> OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017
> debug1: Reading configuration data /home/mariamfahmy2498/.ssh/config
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: /etc/ssh/ssh_config line 19: Applying options for *
> debug2: resolving "logerrit" port 22
> ssh: Could not resolve hostname logerrit: Name or service not known
>
> I am following
> https://wiki.documentfoundation.org/Development/gerrit/setup
> I have followed the easy way for setting up gerrit.
> I have also followed
> https://wiki.documentfoundation.org/Development/gerrit/SubmitPatch for
> submitting Patch but here is the errors:
> ./logerrit submit master
>
> ssh: Could not resolve hostname logerrit: Name or service not known
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
> Please guide me, thanks in advance
>
> ___
> 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

Re: How to add new source code file in directory

[Regis Perdreau]

forget, i have found why (problem is between chair and keyboard mainly)
tks for your attention.

Régis Perdreau



Le sam. 1 août 2020 à 20:24, Regis Perdreau  a
écrit :

> Hi,
>
> For example, i try to add new file in starmath source directory.
> I was unsuccessful to do it, the build system ignores it.
> (i have intentionally put garbage in it to stop compilation, make clean,
> but nothing better )
> I have not found practical notice to do this probably simple operation...
> A little clue makes me happy.
>
> (the next step is to add custom library, but it's the next step)
>
> Tks
>
> Régis Perdreau
>
>
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

How to add new source code file in directory

[Regis Perdreau]

Hi,

For example, i try to add new file in starmath source directory.
I was unsuccessful to do it, the build system ignores it.
(i have intentionally put garbage in it to stop compilation, make clean,
but nothing better )
I have not found practical notice to do this probably simple operation...
A little clue makes me happy.

(the next step is to add custom library, but it's the next step)

Tks

Régis Perdreau
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Easy Hacks

[Regis Perdreau]

Hi, thank you for joining us !


All commands are supposed to be entered in cygwin shell. (that's i do)
(but probably won't work out of the box, you need to set some environment
variables)

First : have you build a debug version of LibreOffice ?
as described here :
https://blog.documentfoundation.org/blog/2019/07/09/start-developing-libreoffice-download-the-source-code-and-build-on-windows/

Regards,

Régis Perdreau



Le ven. 24 juil. 2020 à 19:52, anshu khare  a
écrit :

> Hi
>
> I am new to this community.
>
> I was looking for some easy hacks on this page
>
>
> https://wiki.documentfoundation.org/Development/EasyHacks/by_Required_Skill/Skill_C%2B%2B#Skill_Level:_Beginner
>
>
> I was looking at the bug
>
> 42982 : improve UNO API error reporting
>
> Since I was completely unfamiliar with UNO, I directed to this page
>
> https://niocs.github.io/LOBook/extensions/part1.html#buildsec
>
> It says :
>
> The complete C++ program that creates a Desktop object and loads an empty
> calc document can be built and run as :
>
> $ git clone https://github.com/niocs/UNOCreateUseObject.git
> $ cd UNOCreateUseObject
> $ make
>
> $ make CreateUseObject.run
>
>
> Please let me know if I have to write these commands on Cygwin shell or on
> Git Bash.
>
> Also, am I heading in right direction to solve this particular bug?
>
>
> Thank you
>
> Regards
>
> Anshu
>
>
> ___
> 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

Re: Re[4]: Building LO from source

[Regis Perdreau]

HI Ismet,
I can confirm (IMHO) that you can't exclude easily some part from LO, it's
not designed in this way...For example, Impress depends from Draw. You need
Calc to embed sheets in Writer, etc...
Have you set an autogen.input file to exclude the doxygen documentation
(--without-doxygen) ?...It takes ages on my computer to be generated.
On my computer, a ridiculous core I3-6100 8Go nowadays, it takes around 2h
to compile LO from scratch under Linux.

Regards

Régis Perdreau



Le ven. 12 juin 2020 à 07:59, Ismet Bahadir  a
écrit :

> Thank you very much Tor,
>
> Yes, I didn't know the terminology, so I trusted that you would understand
> :)
>
> It takes over 5 hours to compile on my pc but I have a powerful machine
> with 64 cores and 128 GM ram. I think that will be faster.
>
> I'll try and get back to you. But I still do not know why the extension
> successfully installs on Ubuntu but fails on Debian.
>
> Regards
>
> -- Original Message --
> From: "Tor Lillqvist" 
> To: "Ismet Bahadir" 
> Cc: "Stephan Bergmann" ; "libreoffice-dev" <
> libreoffice@lists.freedesktop.org>
> Sent: 12-Jun-20 8:55:57 AM
> Subject: Re: Re[2]: Building LO from source
>
>
>
>> I think it's best to recompile the source from scratch with official DEB
>> packaging system.
>>
>
> IMHO, as an outsider, only Debian's own way to package LibreOffice can be
> said to be "official". It is *very* different from the way TDF packages
> LibreOffice in the .deb format.
>
> How can I exclude some of the apps such as "Draw"?
>
>
> Draw (and Writer, Calc, etc) are not "apps" as such IMHO but different
> kinds of documents that the one same app, LibreOffice, manages using the
> same soffice.bin process. But that is just terminology, we know what you
> mean.
>
>
>> Is it possible that
>> each app has its own DEB installation file so that I won't be installing
>> it if I skip its DEB file?
>
>
> That *is* exactly how the real Debian packages for LibreOffice are
> structured. See https://packages.debian.org/buster/libreoffice Also many
> (most?) other Linux distros, like Fedora for instance, split LibreOffice
> into multiple packages, like libreoffice-core, libreoffice-writer,
> libreoffice-calc, libreoffice-draw, etc.
>
> (As such, I don't think that it makes sense to split up LibreOffice like
> that, I find it fairly pointless, old-fashioned and needlessly complex, but
> then I am not a Linux zealot, I like macOS more. But just ignore me here.)
>
> --tml
>
> ___
> 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

Re: Doxygen

[Regis Perdreau]

Yes i confirm there are some lacks in doxygen. I'm not able to generate
myself documentation.  It will be interesting to generate uml diagram.
The doxygen process never ends on my computer.  I'm trying to test
Sourcetrails which is recently opensourced. It looks better for me. My goal
would be to able to recognize easily design pattern, inheritance and where
add méthods  without pain. For occasionnal self taught developper, it's
tricky to have global view of classes without a tool.

Regards,

Régis.








Le jeu. 30 avr. 2020 à 03:35, Olivier Hallot 
a écrit :

> Hi Michael
>
> Em 29/04/2020 13:39, Michael Stahl escreveu:
> > hi Olivier,
> >
> (snip)
>
> >
> > so you are unhappy with the current state? what in particular don't you
> > like about the API documentation?
>
> The way information is presented to the non-developer is sub-optimal.
> Pre-Doxygen sdk was much easier to navigate and get information as the
> ues cases below
>
> With installed sdk in his computer at
> file:///opt/libreoffice6.4/sdk/index.html
>
> Let's suppose I am a candidate to macro programming and want to
>
> Use case 1 : Search for ThisComponent -> no matches
>
> Use Case 2 : What are the methods/properties under getSheets() ?
> Answer : search for getSheets returns
>
> file:///opt/libreoffice6.4/sdk/docs/idl/ref/interfacecom_1_1sun_1_1star_1_1sheet_1_1XSpreadsheetDocument.html#a3ea7cfcc41c4d4690228e62ca4a6a55d
>
> where it says
> Public Member Functions
> com::sun::star::sheet::XSpreadsheetsgetSheets ()
> returns the collection of sheets in the document. More...
>
> NO mention to methods and properties of the collection object.
>
> just 2 examples on how hard it is to get information currently.
>
> I remind that if this sdk/documentation should be improved, we can look
> to get a resource funded by Google, provided we format into a tech doc
> project.
>
> Kind regards
> --
> Olivier Hallot
> LibreOffice Documentation Coordinator
> Comunidade LibreOffice
> Rio de Janeiro - Brasil - Local Time: UTC-03:00
> http://tdf.io/joinus
> ___
> 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

Re: Problems in building libre-office

[Regis Perdreau]

Hi,
Welcome in the long compilation process of LibreOffice. No pain, no gain.
Just kidding.

Don't know your OS, assuming it's linux. (quite similar on windows)

Check you have all commits in your local repository with "git pull -r"
Sometime the compilation failed because the repository is not fully updated.

Guess your CPU overheated probably.

You can try to reduce the number of cores used by the process with
./autogen.sh --with-parallelism=n (where n is your number of cores, try n-1)
(best put this parameter in a autogen.input file for further use).

You can try to build only the module where the compilation failed with
make 'modulename' (in my own experience, it's usually sc sw for hoverheat
trouble)
Check the trigram for the name of the module, something like [SC],[SW]  at
the beginning of the numerous lines displayed by the compilation process.
May be this link will help you :
https://wiki.documentfoundation.org/Development/BuildingOnLinux

I let core developers to add something.

Régis Perdreau



Le jeu. 30 janv. 2020 à 22:16, anshu khare  a
écrit :

> Hi everyone,
>
> There are some issues with my pc. It can run continually for only 2-3
> hours. After that it shuts down on its own.
>
> I was trying to build libre-office on my pc.
> It ran for 3 hours and then it switched off.
> At that time make 2>&1 command was running.
>
> The last lines before shutting off pc on cygwin were as follows :
> [build C] UnpackedTarball/expect/lib/xmlrole_x64.c
> c1 : command line warning D9025 : overriding '/D_X86_=1' with '/U_X86_'
>
> [build MOD] glm
> c1 : command line warning D9025 : overriding '/D_X86_=1' with '/U_X86_'
> [build MOD] mdds
>
> After the pc restarted I ran make 2>&1 command again.
> It gave the following error:
> make[1] = ***Waiting for unfinished jobs...
> make : *** [Makefile : 282 : build] Error 2
>
> I have spend a lot of time building libre-office upto this stage and am
> not willing to rerun the whole process again.
> Is there a way out?
>
> Anshu
>
> ___
> 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

StarBasic 64Ko Limit, where ?

[Regis Perdreau]

Hi,

I'm interested to know where is the starbasic module size limit definition
in the code ?
Some Help documents talk about a limit of 64 ko, but some users experiment
an error message "program too big" before this limit.


Régis Perdreau
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Survey: Relevance of Configuration Systems in Free and Open Source Software

[Regis Perdreau]

Hi,
Seems to be outdated ?

Régis Perdreau



Le jeu. 20 juin 2019 à 05:05, sunnysunny  a écrit :

> Your site has a lot of useful information for myself. I visit regularly.
> Hope
> to have more quality items.
> subway surfers 
>
>
>
> --
> Sent from:
> http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
> ___
> 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

Re: how to add .cxx file to be compiled and linked

[Regis Perdreau]

Ok, thanks.  It works...


Régis Perdreau



Le lun. 15 avr. 2019 à 16:39, Stephan Bergmann  a
écrit :

> On 15/04/2019 16:31, Regis Perdreau wrote:
> > I have added a file in, for example,  like
> > core/slideshow/engine/slide/test.cxx  with a method in it.
> > I have add with 'git add' to my work local branch repository
> > I expect that it will be compiled like the other files...but ... it
> > seems to be ignored
> > and  the linker fails because a method description is missing (include
> > test.hxx is ok)
> > Is there any something simple that i have forgotten ?
>
> You must add it to the gb_Library_add_exception_objects of some
> Library_*.mk, presumably slideshow/Library_slideshow.mk in your case.
>
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

how to add .cxx file to be compiled and linked

[Regis Perdreau]

Hi,

I have added a file in, for example,  like
core/slideshow/engine/slide/test.cxx  with a method in it.
I have add with 'git add' to my work local branch repository
I expect that it will be compiled like the other files...but ... it seems
to be ignored
and  the linker fails because a method description is missing (include
test.hxx is ok)
Is there any something simple that i have forgotten ?

I'm a bit stuck at this moment.

Régis Perdreau
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Open Badges for LibreOffice contributions

[Regis Perdreau]

To grow the thoughts,
May be we have to build a skill checklist or a  guidelines...

The problem is how to evaluate them with a computer...
Many badges are quantity evaluation in fact, not quality, "the most
numerous actions taken, the most numerous goals reached...etc" because it's
easy to count.

So classify them in what is easy to check, and not easy to check

In some french education , sometimes we can see this simple classification
(from Bloom):

level 1: what is pure information (I know that Libreoffice is a word
processor, so we need to list what you have to know about LibreOffice and
its organization)
level 2: what i can explain, knowledges i can share (i'm able to explain
how Libreoffice work, i know the vocabulary, i know some basics of the LO
organisation and i can talk about it)
level 3: what you have understand and you can use directly to solve a
probleme (i know what a style is and i can use one, modify one in the goal
to write a document,use simple script)
level 4: I can now create complex document and solve complex task (create a
new template, a new starbasic script with not already provided function or
tool)

Régis Perdreau



Le mar. 19 févr. 2019 à 11:36, sophi  a écrit :

> Hi all,
>
> I'm working with Mike Saunders on implementing the Open Badges system
> in our community: https://openbadges.org
>
> Mike is working with the Design project to get some badges with
> LibreOffice identity. Guilhem is working on the infra side to see how to
> automate the process.
>
> In the meantime, I would like to ask you what would be the basis in your
> opinion to get badges. If you read what OpenBadges is, it's not only
> about contributions but also awarding skills. Those badges get more and
> more recognized by companies and universities, so it's also an
> opportunity for contributors to add to their experience.
>
> In that regard, what realizations/targets would you propose to get awarded?
> 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
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: vallgrind from sdk

[Regis Perdreau]

it seems to work now !

Régis Perdreau



Le dim. 10 févr. 2019 à 16:47, Regis Perdreau  a
écrit :

> Hi,
>
> Could we launch valgrind from a sdk application ?. I want to
> valgrind/callgrind soffice executable launched with the bootstrap link from
> a program written with the sdk, but 'm not succeed at this moment. Any clue
> or pointer to do that ?
>
> Régis Perdreau
>
>
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

vallgrind from sdk

[Regis Perdreau]

Hi,

Could we launch valgrind from a sdk application ?. I want to
valgrind/callgrind soffice executable launched with the bootstrap link from
a program written with the sdk, but 'm not succeed at this moment. Any clue
or pointer to do that ?

Régis Perdreau
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Build fails in UnitTest

[Regis Perdreau]

Forget the noise, Lo accept to launch itself at the second try :)

Régis Perdreau


Le lun. 29 oct. 2018 à 21:18, Regis Perdreau
 a écrit :
>
> Hi,
>
> I have this error when i try to launch debug version of libreoffice in GDB.
>
>
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> warning: Corrupted shared library list: 0x55850240 != 0x77f97cc0
>
> Some clues to solve this problem ?
>
> Régis Perdreau
> 07 68 88 26 07
>
> Le mar. 16 oct. 2018 à 19:36, kalriel  a écrit :
> >
> > Hello.
> > I get the following error when building the master
> >
> > Error: a unit test failed, please do one of:
> > make CppunitTest_sc_subsequent_filters_test CPPUNITTRACE="lldb --"   #
> > for interactive debugging on OS X
> > make CppunitTest_sc_subsequent_filters_test VALGRIND=memcheck#
> > for memory checking
> >
> > You can limit the execution to just one particular test by:
> >
> > make CppunitTest_sc_subsequent_filters_test CPPUNIT_TEST_NAME="testXYZ"
> > ...above mentioned params...
> >
> > /[...]/LibreOffice_Source/lode/dev/core/solenv/gbuild/CppunitTest.mk:120:
> > recipe for target
> > '/[...]/LibreOffice_Source/lode/dev/core/workdir/CppunitTest/sc_subsequent_filters_test.test'
> > failed
> > make[1]: ***
> > [/[...]/LibreOffice_Source/lode/dev/core/workdir/CppunitTest/sc_subsequent_filters_test.test]
> > Error 1
> > Makefile:167: recipe for target 'CppunitTest_sc_subsequent_filters_test'
> > failed
> > make: *** [CppunitTest_sc_subsequent_filters_test] Error 2
> >
> > Best regards.
> > Kalriel
> >
> >
> >
> > --
> > Sent from: 
> > http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
> > ___
> > 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

Re: Build fails in UnitTest

[Regis Perdreau]

Hi,

I have this error when i try to launch debug version of libreoffice in GDB.


Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
warning: Corrupted shared library list: 0x55850240 != 0x77f97cc0

Some clues to solve this problem ?

Régis Perdreau
07 68 88 26 07

Le mar. 16 oct. 2018 à 19:36, kalriel  a écrit :
>
> Hello.
> I get the following error when building the master
>
> Error: a unit test failed, please do one of:
> make CppunitTest_sc_subsequent_filters_test CPPUNITTRACE="lldb --"   #
> for interactive debugging on OS X
> make CppunitTest_sc_subsequent_filters_test VALGRIND=memcheck#
> for memory checking
>
> You can limit the execution to just one particular test by:
>
> make CppunitTest_sc_subsequent_filters_test CPPUNIT_TEST_NAME="testXYZ"
> ...above mentioned params...
>
> /[...]/LibreOffice_Source/lode/dev/core/solenv/gbuild/CppunitTest.mk:120:
> recipe for target
> '/[...]/LibreOffice_Source/lode/dev/core/workdir/CppunitTest/sc_subsequent_filters_test.test'
> failed
> make[1]: ***
> [/[...]/LibreOffice_Source/lode/dev/core/workdir/CppunitTest/sc_subsequent_filters_test.test]
> Error 1
> Makefile:167: recipe for target 'CppunitTest_sc_subsequent_filters_test'
> failed
> make: *** [CppunitTest_sc_subsequent_filters_test] Error 2
>
> Best regards.
> Kalriel
>
>
>
> --
> Sent from: 
> http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
> ___
> 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

Re: Could not determine MSC version.

[Regis Perdreau]

Have your windows have english langage installed and defined as
default langage ...I have this error when i use french langage because
the string of the prompt of cl.exe when version is requested is
différent in some case and is not correctly interpreted when some
librairies are compiled (nss in my memory)



Régis Perdreau
07 61 51 90 35


Le 28 juillet 2017 à 15:39, GUILBERT Sarah
 a écrit :
> Hello,
>
>
>
> I want compile libreoffice to develop on visual studio.
>
> I have visual studio 2017 and y try compile libreoffice from this link
>
>
>
> git clone http://anongit.freedesktop.org/git/libreoffice/core
>
>
>
> and i try this tutorial :
>
> https://wiki.documentfoundation.org/Development/BuildingOnWindows
>
>
>
> that work but at command
>
> /opt/lo/bin/make gb_COLOR=1
>
>
>
> I have this error : checking for cl...
> C:/PROGRA~2/MICROS~4/2017/COMMUN~1/VC/Tools/MSVC/1410~1.250/bin/HostX86/x86/cl.exe
> -arch:SSE
>
> configure: error: Could not determine MSC version.
>
>
>
> I use W10,
>
>
>
> Why it’s don’t work ?
>
>
>
> Thank you and excuse me for my bad english.
>
>
>
> Sakama.
>
>
> 
> Ce message et ses éventuelles pièces jointes sont adressés exclusivement à
> l'usage de leur(s) destinataire(s), et leur contenu est strictement
> confidentiel. Toute copie, retransmission, diffusion ou autre usage en tout
> ou partie, ainsi que toute utilisation par toute personne ou entité légale
> sont formellement interdits. Si vous recevez ce message par erreur, nous
> vous remercions de le détruire et d'en aviser immédiatement l'expéditeur.
> Les précautions raisonnables ont été prises pour éviter que les virus ne
> soient transmis par ce message mais il vous appartient de mettre en place
> des mesures de sécurité destinées à détecter et éradiquer la présence d'un
> éventuel virus. Nous refusons toute responsabilité pour tout dommage causé
> par la transmission d'un virus et/ou la contamination de votre système
> informatique. Le réseau Internet ne permettant pas d'assurer l'intégrité de
> ce message, l'expéditeur décline toute responsabilité au cas où il aurait
> été intercepté ou modifié par quiconque.
>
> ___
> 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

vs2015 include path problem

[Regis Perdreau]

Hi

I have checked again and find a bug report about my issue
https://bugs.documentfoundation.org/show_bug.cgi?id=99055

Sorry for the noise.

Régis


--
Hi

I haveVS2015 update 3  and now i have an issue with autogen.sh script...

This command line generated by autogen.sh script doesn't work
(contest.c is a copy of the conftest.c file used by autogen.sh script)

Even if i enter this in a cmd terminal, the result is the same (as i expect)

C:/PROGRA~2/MICROS~1.0/VC/bin/cl.exe -arch:SSE -c
-IC:/PROGRA~2/WI3CF2~1/10/Include/10.0.14393/ucrt
c:\sources\lode\dev\conftest.c

c:\sources\lode\dev\conftest.c(43): fatal error C1083: Cannot open
include file: 'assert.h': No such file or directory

 (snip)
Best Regards

Régis Perdreau
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: vs2013-ide-integration: sfx2 include path incomplete

[Regis Perdreau]

Hi

I haveVS2015 update 3  and now i have an issue with autogen.sh script...

This command line generated by autogen.sh script doesn't work
(contest.c is a copy of the conftest.c file used by autogen.sh script)

Even if i enter this in a cmd terminal, the result is the same (as i expect)

C:/PROGRA~2/MICROS~1.0/VC/bin/cl.exe -arch:SSE -c
-IC:/PROGRA~2/WI3CF2~1/10/Include/10.0.14393/ucrt
c:\sources\lode\dev\conftest.c

c:\sources\lode\dev\conftest.c(43): fatal error C1083: Cannot open
include file: 'assert.h': No such file or directory


to troubleshoot this issue, i use windows path format  and  it works !

C:\Users\regis>C:/PROGRA~2/MICROS~1.0/VC/bin/cl.exe -arch:SSE -c
-IC:"\Program Files (x86)\Windows Kits\10\Include\10.0.14393.0\ucrt"
-IC:"\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include"
c:\sources\lode\dev\conftest.c

(i have added the VC\include directory because cl.exe complains the
vcruntime.h is missing)

it seems to be a PATH issue with 8.3 format filename...A clue to know
what to do ?

Best Regards

Régis Perdreau
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Regis Perdreau licence statement

[Regis Perdreau]

All of my past & future contributions to LibreOffice may be
licensed under the MPLv2/LGPLv3+ dual license.


Regards,

Régis Perdreau
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Alexis PAQUIN license statement

[Regis Perdreau]

All of my past & future contributions to LibreOffice may be
   licensed under the MPLv2/LGPLv3+ dual license.


rgds

Régis Perdreau
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice