> No, my idea was to put the above text in the about box, to replace our
> current 4f11d0a-adcf6d5-... string.
Oh, I see! But then it would be easier to use the "pretty printing
date" instead of having 2 strings to compare for each repository. That
would be a nice improvement.
What I was proposin
On Thu, Dec 01, 2011 at 07:11:04PM -0800, Mike Whiteley wrote:
> From 3fb61e525f5a15fab65c6ab494d5c4d0135a2471 Mon Sep 17 00:00:00 2001
> From: mikew
> Date: Thu, 1 Dec 2011 19:13:20 -0800
> Subject: [PATCH] translated some comments from German to English
Thanks. A few remarks, though. Please do
On Sat, Dec 03, 2011 at 11:40:01PM +, Pedro Lino wrote:
>> Git commit IDs as identifiers have the huge problem that they are not
>> comparable (one cannot say which one is "greater") without referring
>> to the repository. How about we also put the *commit* (not author)
>> timestamp (in UTC) o
Hi Markus,
On Sat, Dec 3, 2011 at 5:30 PM, Markus Mohrhard
wrote:
> Do you have any ideas?
You are almost there. IIRC there is some quirk with setting a
background color with the Edit control; you need to set fore ground
color before setting the background color in order to change the
backgrou
Hi Lionel
> Git commit IDs as identifiers have the huge problem that they are not
> comparable (one cannot say which one is "greater") without referring
> to the repository. How about we also put the *commit* (not author)
> timestamp (in UTC) of the top node (commit), and maybe the branch?
That w
Hi,
As said in this post :
http://lists.freedesktop.org/archives/libreoffice-qa/2011-December/000550.html
the button Close of the dialog Insert -> Fields -> Other... in Writer
does not work anymore, it does nothing.
After investigating with the help of Arnaud and Norbert, it seems that
the commit
Hey,
I'm trying to set the background color of an Edit in the code but I
failed with Window::SetControlBackground, Window::SetControlForeground
and throught the OutputDevice::SetBackground,
OutputDevice::SetFillColor methods.
Do you have any ideas?
Regards,
Markus
___
On Tue, Nov 29, 2011 at 09:36:31AM -0500, Terrence Enger wrote:
>
> This is one more time when it would be nice for the
> project to have a database server to play with. (Now,
> will somebody please bring some chheeze, so that we can
> have a party?)
>
Yes and no, because Murphy's law w
On Sat, Dec 03, 2011 at 01:06:18PM +0100, Andras Timar wrote:
> 2011/12/3 Pedro Lino :
>> Another situation: I download a master build from a tinderbox. How do
>> I know the build included? How do I know if the source it was
>> generated from is newer or older than the one I already have? Easy.
>>
https://bugs.freedesktop.org/show_bug.cgi?id=37361
clio changed:
What|Removed |Added
Depends on||43462
--- Comment #36 from clio 2011-12-03 12:41
On Sat, Dec 3, 2011 at 10:20 PM, Andras Timar wrote:
> Hi Kaplan,
>
> 2011/12/3 Lior Kaplan :
> > Hi,
> >
> > I'm not sure if this is a valid use of the menuitem tag, as the other use
> > cases link to a deeper item in the hierarchy. If no the text can be
> > re-phrased to use the tag as on the o
Hi Kaplan,
2011/12/3 Lior Kaplan :
> Hi,
>
> I'm not sure if this is a valid use of the menuitem tag, as the other use
> cases link to a deeper item in the hierarchy. If no the text can be
> re-phrased to use the tag as on the other strings in the file.
>
It is valid. tag will be transformed int
Hi,
I'm not sure if this is a valid use of the menuitem tag, as the other use
cases link to a deeper item in the hierarchy. If no the text can be
re-phrased to use the tag as on the other strings in the file.
Kaplan
0001-Add-link-to-tools-options-dialog.patch
Description: Binary data
__
https://bugs.freedesktop.org/show_bug.cgi?id=37361
--- Comment #35 from manj_k 2011-12-03
11:12:57 PST ---
Nominate 'Bug 43422 - Spell check: Crash "Runtime Error" with AutoSpellcheck';
not acceptable for a release.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
---
https://bugs.freedesktop.org/show_bug.cgi?id=37361
manj_k changed:
What|Removed |Added
Depends on||43422
--
Configure bugmail: https://bugs.freed
Hi,
currently I have much trouble using existing user profiles with Master
or 3.5.0 Beta. The trouble vanishes when I switch to a blank new user
profile for.
I believe that might cause heavy trouble when users update from 3.4 8or
3.3), but on the other hand my suspect might be complete nonse
On 12/3/11 6:27 PM, Cor Nouws wrote:
> Will be something that marketing is going to praise us for, isn't it?
If the change of code name is not a problem, it would make thing easier
for everyone.
--
Italo Vignoli - italo.vign...@gmail.com
mob +39.348.5653829 - VoIP 5316...@messagenet.it
skype it
Michael Meeks wrote (03-12-11 15:49)
Well - we've fixed a number of the most obvious packaging bugs,
parallel installability etc. etc. in master - so (without further new
problems - of which we expect some up to the freeze) Beta1 will be
rather better.
It's more realistic to expect tha
Michael Meeks wrote (03-12-11 15:50)
Yes ! we have not branched yet; master will branch at the
feature-freeze before B1 so we have:
master Beta0 ---\--- crazy stuff ...
\
\- Beta1 --- stabilisation -
Pedro Lino wrote (03-12-11 11:23)
I hope that _at least_ they make DAMN sure that Beta1 doesn't
overwrite the stable build...
To be honest: I have no idea. I just install zillions (well, little less
;-) ) without system integration.
But your question is relevant indeed.
Anyone else?
Thanks,
> No need to know. It is just a random (or not so random) sequence of
> hex digits. If nothing documents it to have some significance, don't
> assume it to have any significance.
Thank you for the clarification. It does have some significance.
>> Anyway, even if this was a combination of the GIT
> I thought Andras was referring to the single 8 letter/number code
> added to the Windows install folder name.
> Where does that come from?
No need to know. It is just a random (or not so random) sequence of
hex digits. If nothing documents it to have some significance, don't
assume it to have an
Hi Rainer,
On Sat, 2011-12-03 at 08:42 +0100, Rainer Bielefeld wrote:
> it's a disaster, completely unusable ! Quality of Beta0 is far behind
> quality of Master during the last weeks, it seems that we were not lucky
> with the time where the tag has been created
Quite quite :-) so Beta
Hi Korrawit
> That is, if your 4f11d0a is the first group of IDs in About box, it's
> the core repository's commit ID.
Yes, obviously. Sorry for the confusion.
I thought Andras was referring to the single 8 letter/number code
added to the Windows install folder name.
Where does that come from?
E
Hello Pedro, Andras, *
On Sat, Dec 3, 2011 at 20:16, Pedro Lino wrote:
> So, 4f11d0a is a global commit ID calculated from the partial 5 git
> commit IDs?
No, it isn't. It's like what you've explained:
> So the About box says a286353-090bcba-3bf3b94
> which I just realized are the 7 first lette
Hi again Andras
> We have 5 repositories now: core, binfilter, dictionaries, help, and
> translations. Therefore there are 5 git commit IDs in the About box
> separated by dashes. These are good identifiers of the build, at least
> these uniquely identify the source code that the build was made fr
Hi Pedro
2011/12/3 Pedro Lino :
> Hi Andras
>
> Thank you for your quick and enlightening reply!
>
>> LibreOffice 3.5 will not unpack anything to desktop. But we can't
>> change the past... :)
>
> Fair enough :)
>
>> You can check what's included and what's not, when you visit
>> for example
>> h
Hi Andras
Thank you for your quick and enlightening reply!
> LibreOffice 3.5 will not unpack anything to desktop. But we can't
> change the past... :)
Fair enough :)
> You can check what's included and what's not, when you visit
> for example
> http://cgit.freedesktop.org/libreoffice/core/log/
Hi Pedro,
2011/12/3 Pedro Lino :
> Hi all
>
> This is my final request about this subject.
>
> Can you please make some sense out of the version naming convention?
>
> I was about to reinstall version 3.4.4 (after it was overwritten by
> 3.5.0 Beta0) and I already had an unpacked install folder on
Hi all
This is my final request about this subject.
Can you please make some sense out of the version naming convention?
I was about to reinstall version 3.4.4 (after it was overwritten by
3.5.0 Beta0) and I already had an unpacked install folder on my
desktop. The only way I could verify that i
> Kendy (this time CC'd), please don't commit this stuff. It breaks
> incremental build on Windows, making debugging Windows impossible.
Hear, hear. If we want beta1 to be better than beta0, we can't require
people having to make clean after each edit, and rebuild from scratch
(effectively making
Hi Rainer,
Rainer Bielefeld wrote (03-12-11 08:42)
Shit happens, now the question is how we will go on.
As posted already yesterday, it is not unlikely that beta1 will have
about the same troubles. If so, those will be fixed before beta2, which
will make that version fine for larger testing
A patch has been attached in the bug, can someone please review?
Thx
Rainer
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
33 matches
Mail list logo
