serverguide-pdf: ubuntu font instead of serif/monospace/symbol

Bug #922251 reported by Savvas Radevic
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Ubuntu Server Guide
Won't Fix
Undecided
Unassigned
ubuntu-ru-docs
Triaged
Critical
Unassigned

Bug Description

I have created a bzr patch to create the serverguide pdf using the Ubuntu font.
Using the Greek translation I get "#" characters with the current makefile.

Here's how I use the patch for the greek (el) translation:

sudo apt-get install bzr bzrtools fop xsltproc docbook-xsl gnome-doc-utils yelp-tools

bzr branch lp:serverguide
cd serverguide
mkdir po

https://translations.launchpad.net/serverguide/trusty/+pots/serverguide/el/+export
Request the .po fuke (PO format). Θα σταλεί στο email.

Rename the po file as "el.po" and place it in po/ folder.

Patch the bzr tree:
wget http://people.ubuntu.com/~medigeek/serverguide_el/bzrpatch.diff -O bzrpatch.diff
bzr patch bzrpatch.diff

For html: make serverguide-html LN=el

For pdf: make serverguide-pdf LN=el

Revision history for this message
Savvas Radevic (medigeek) wrote :
tags: added: patch
Changed in serverguide:
status: New → Confirmed
Revision history for this message
Savvas Radevic (medigeek) wrote :

Ping! Refreshed patch.

Revision history for this message
Anton Patsev (patsev-anton) wrote :

Savvas Radevic (medigeek) help please

bzr patch bzrpatch2.diff
bzr: ERROR: unknown command "patch"

Revision history for this message
Savvas Radevic (medigeek) wrote :

you need the bzrtools package:
sudo apt-get install bzrtools

description: updated
Revision history for this message
Vadim Nevorotin (malamut) wrote :

Please, fix this bug in main branch. Without it it's impossible to build translated PDF's for most langauges.

Changed in ubuntu-ru-docs:
status: New → Triaged
importance: Undecided → Critical
Revision history for this message
Doug Smythies (dsmythies) wrote :

When you say "Using the Greek translation I get "#" characters with the current makefile." Do you mean everywhere, or just someplaces, where odd unicode characters have been used in the master files? For example chapter 7 sub-section 1.2, near the start.

I guess I am asking if there is a bigger question here: Should 3 byte Unicode (or whatever the correct name for them is) characters be allowed in the master .xml files? There are not very many (about 60) in the entire document and they have other side effects such as: Messing up the "bzr diff" command; Not displaying correctly in some editors, and not being easily editable; Masking any real odd character searches when one uses "grep --color='auto' -P -n "[\x80-\xFF]" *.xml" to check for any, where, and for example, there is an odd character sequence right now in the first few bytes of the file installation.xml.

Of course, I understand that they are essentail for the translated documents.

Revision history for this message
Doug Smythies (dsmythies) wrote :

I have an "old" serverguide build environment and a "new" one.
I applied bzrpatch to the old one and bzrpatch2 to the new one, and compiled both English and Latin serverguide PDFs.

The issue of Chapter 7 sub-section 1.2 was still present (which I don't yet know if that is the problem we are trying to solve). In addition there were some other side effects of the change, such as font size changes and font type changes, that I do not think were for the better.

Revision history for this message
Savvas Radevic (medigeek) wrote :

I can't remember if anything has changed recently.

I have noticed that the characters affected are
a) characters with greek acute accents (tonos):
ά ή ύ ί ό έ
b) The letters in headings are all converted to "#" characters. See example pdf and screenshots attached.

Revision history for this message
Doug Smythies (dsmythies) wrote :

Thank you for the added detail. I will try to look in more detail into the other side effects of the change.

Revision history for this message
Doug Smythies (dsmythies) wrote :

There are font type and size differences inside of <screen> and <programlisting> directives.

Also there still seems to be issues in the "serverguide_with_patch.pdf" with UTF-8 multi-byte characters, many created from the <quote></quote> directives in the master files. See the attached screen shot.

If some change is going to be made, then it should done such that the other fonts are not altered and other characters are rendered properly also.

John Kim (kotux)
tags: added: serverguide
Revision history for this message
Anton Patsev (patsev-anton) wrote :

Savvas Radevic
Could you update the patch for the new version of Ubuntu Server Guide ?

Revision history for this message
Savvas Radevic (medigeek) wrote :

The patch still works for the latest ubuntu server guide. I've just tried it.
You need these packages installed:
sudo apt-get installed fop xsltproc docbook-xsl gnome-doc-utils

description: updated
description: updated
Revision history for this message
Savvas Radevic (medigeek) wrote :

Sorry, this is the correct command:
sudo apt-get install bzr bzrtools fop xsltproc docbook-xsl gnome-doc-utils yelp-tools

description: updated
Revision history for this message
Doug Smythies (dsmythies) wrote :

You should not need bzrtools to be able to work with the serverguide bzr branch.
You should need some other things, as per:
https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation/UbuntuServerGuide#Kickstart

Revision history for this message
Savvas Radevic (medigeek) wrote :

You need bzrtools for the "bzr patch" command. :)

Revision history for this message
Doug Smythies (dsmythies) wrote :

The serverguide is no longer published in other languages, only U.S. English

Changed in serverguide:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.