Bug 233096 - Words are truncated when printing using print week radio button
Summary: Words are truncated when printing using print week radio button
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: LO normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-02 19:14 UTC by Sabine Faure
Modified: 2017-01-07 22:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sabine Faure 2010-04-02 19:14:03 UTC
Version:            (using Devel)
Compiler:          gcc 4.3.2 
OS:                Linux
Installed from:    Compiled sources

- Launch Korg
- Create an event for Monday including a long title, a location, a start and end time and a long description
- Go to File menu/Print Preview...
- In the Print Style section (left hand side) select the 'print week' radio button
- Leave all the other options as set per default
- Click on Preview

Each day is represented by a column and the event you've created should be displayed on Monday on the correct time.
However, the title, the location and the description are truncated in the middle of words whereas it would be a lot more readable if the text was cut in between words.

It would be even better if the different sets of information were displayed on different lines:
time 
title
location
description

Trunk, Svn Rev 1110236
Comment 1 Denis Kurz 2016-09-24 18:43:38 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:38:35 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.