Estimated read time: 1 minutes

I just got the mail about my LibreOffice proposal got accepted to Google Summer of Code 2011. I’m looking forward to an exciting summer. :)
Estimated read time: 1 minutes
I just got the mail about my LibreOffice proposal got accepted to Google Summer of Code 2011. I’m looking forward to an exciting summer. :)
Estimated read time: 1 minutes
LibreOffice 3.4 will have a new feature, if you edit styles in Writer, then you can test your style changes without manually closing and opening the style edit dialog again.
Do you like this feature? There are still similar remaining dialogs to improve like this, send in a patch!
Estimated read time: 1 minutes
We recently merged KDE 4.6 in Frugalware -current and since now it uses
upower
, it catches the sleep button of my netbook. The problem is that
it tried to suspend instead of hibernation - what I wanted.
The trick is easy, but not really obvious. First, I disabled
suspend/hibernate in
/usr/share/polkit-1/actions/org.freedesktop.upower.policy
so that I
can play with this without actually hibernating/suspending the system.
Second, I went to System Settings → Input actions → Global, selected "KDE services" and there you can see Suspend and Hibernate as well. Go to Hibernate, and set a custom shortcut: it will ask if you want to remove the sleep button from Suspend - the answer is obviously yes.
Done!
Estimated read time: 1 minutes
I got a report about two problems which got fixed in master now.
The first error is triggered, if you have special (in RTF terms, so for
example {
or }
) characters in style names. The result was not so
friendly when you opened such a document:
After applying the first fix, the document was imported but the original Тест text was replaced by something non-unicode:
The second fix addresses this, and now the result is the expected one:
Estimated read time: 1 minutes
There was a thread about this topic already, but just refusing to commit new files without documentation sounded too aggressive. So the current code just prints a warning.
It was also requested to show some good/bad examples. Lubos volunteered to add detailed instructions in the wiki, so I’m just describing in short what did I test so far.
A good example:
/// Handles export of foos using RTF markup class RtfFoo { };
A bad example:
class RtfBarBuggy { };
Example output when a warning is emitted:
~/git/libreoffice/master/sw$ git commit -a -m foo
sw/source/filter/ww8/bar.hxx:30: warning: Compound RtfBarBuggy is not documented.
[master 1b11571] foo
3 files changed, 68 insertions(+), 0 deletions(-)
create mode 100644 sw/source/filter/ww8/bar.hxx
create mode 100644 sw/source/filter/ww8/foo.hxx
Estimated read time: 1 minutes
Estimated read time: 1 minutes
Just a FYI:
$ ./chkacc --verbose
Accepting active developer 'vmiklos' [hu]
Accepting active developer 'iron' [hu]
Accepting active developer 'voroskoi' [hu]
Accepting active developer 'boobaa' [hu]
Accepting active developer 'crazy' [ro]
Accepting active developer 'priyank' [in]
Accepting active developer 'hermier' [fr]
Accepting active developer 'devil505' [fr]
Accepting active developer 'bouleetbil' [fr]
Accepting active developer 'ryuo' [us]
Accepting active developer 'gholafox' [fr]
Accepting active developer 'phayz' [au]
Accepting active developer 'elentir' [fr]
Accepting active developer 'cedynamix' [fr]
Accepting active developer 'jercel' [fr]
Accepting active developer 'exceed' [fr]
Accepting active developer 'dex' [de]
Accepting active developer 'kooda' [fr]
Accepting active developer 'centuri0' [fr]
Accepting active developer 'kikadf' [hu]
Accepting active developer 'pingax' [fr]
Estimated read time: 1 minutes
I’ve got a report which turned out to be two separate issues. One is a regression from Go-OO 3.2.x, this post is about this part. The other part is about the improvement of both the import/export RTF filter, the bug has some detail on that part as well.
So the problem was that wrapped images (when the image is a frame and not a character) had some extremely small height. I did not notice this bug in LO as an LO-specific extension hides that value, but in Word you can see it:
The fix is to use the height of the containing frame instead of the height of the picture itself, then it’ll look fine:
Estimated read time: 1 minutes
Yesterday I bought a HP LaserJet Pro P1566 printer. The device itself is nice, supported by foo2zjs, though of course that support is unofficial. I was curious what do they offer a "Linux support" on their website, since the case of the printer mentions Linux support. And I had to use the above picture to select my country.
It’s Magyarország, not Magyarorság.
The map of the country isn’t even close to reality, what are they smoking? ;)
Estimated read time: 1 minutes
About four days ago it has been asked on #libreoffice
if it’s possible
to bind functions to F13..F16 in Calc. The short answer is no, but it
turned out it’s pretty trivial to allow that (and of course not only in
Calc).
Cedric’s great post is helpful here to find the relevant code. It also truned out that VCL already supports those keys, so only the user interface has to be improvied to export that feature.
The patch is here.