Bug 31557 – Manual layout improvements

Bug 31557 - Manual layout improvements


Summary:	Manual layout improvements

Status:	RESOLVED WONTFIX

Product:	UCS@school
Classification:	Unclassified
Component:	Documentation
Version:	UCS@school 3.1
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	---
Assigned To:	UCS@school maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-05-28 19:58 CEST by Alexander Kläser
Modified:	2019-02-05 21:49 CET (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Design
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Alexander Kläser

2013-05-28 19:58:09 CEST

This applies to the UCS@school manual, as well.

+++ This bug was initially created as a clone of Bug #30334 +++

The following points have caught my eyes when working with the documentation:
* It would be nice to have a sans serif font in general (as in the old doc)
* The links to the sections are not colored (as in the old doc)
* The size of the chapter and section headlines seem to be a bit too large
relatively to the font size of the standard text

Comment 1 Sönke Schwardt-Krummrich

2019-02-05 21:49:30 CET

This issue has been filled against UCS@school 3. The maintenance with
bug and security fixes for the last UCS@school version for UCS 3.x 
(→ UCS@school 3.2) has ended on Dec 31, 2016.

Customers still on UCS 3.x are encouraged to update to UCS 4.3 (or later). 
Please contact your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug"
or simply reopen the issue. In this case please provide detailed information on
how this issue is affecting you.