Bug#880696: debian-refcard: Debian Reference Card translation to russian contains errors in command definitions

[Alex]

Package: debian-refcard
Version: 10.0:all
Severity: minor
Tags: l10n

I have found 2 errors in russian translation of Debian Reference Card.
https://www.debian.org/doc/manuals/refcard/refcard.ru.pdf

They are not actually translation errors but they were introduced in the
commands during translation.

Firstly, in "Daemons and System" section (ru: "Службы и система") the first
command, the one to restart a service, is missing sevice name:
- english version - systemctl restart name.service
- russian version - systemctl restart
It's not actually missing, but it's invisible due to being out of cell bounds.

Secondly, in "Important Shell Commands" (ru: "Важные команды оболочки командной
строки"), move command is spelled "mv file1file2" (ru: "mv файл1файл2") - no
whitespace between "file1" and "file2".



-- System Information:
Debian Release: 9.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

debian-refcard depends on no packages.

Versions of packages debian-refcard recommends:
ii zathura-pdf-poppler [pdf-viewer] 0.2.7-1

Versions of packag

[Alex]

Post by Alex
Secondly, in "Important Shell Commands" (ru: "Важные команды оболочки командной
строки"), move command is spelled "mv file1file2" (ru: "mv файл1файл2") - no
whitespace between "file1" and "file2".

I double checked and found that the part above is also the issue for the original english version.
https://www.debian.org/doc/manuals/refcard/refcard.en.pdf


Best Regards,
Alex

[Baptiste Jammet]

Control: tag -1 patch

Hello,

Post by Alex

Post by Alex
move command is spelled "mv file1file2"
no whitespace between "file1" and "file2".

I double checked and found that the part above is also the issue for
the original english version.

This seems to be due to "<literal> </literal>". Maybe this was useful
for some old build engine?

Attached patch remove it, and take care of translations.
As fr & es should shorter the word used for "file" to be displayed, I
corrected this too.

Baptiste

[Holger Wansing]

Control: retitle -1 debian-refcard: PDFs have various problems (layout broken, missing spaces or line breaks ...)
Control: found -1 10.0

Post by Baptiste Jammet
Control: tag -1 patch
Hello,

Post by Alex

Post by Alex
move command is spelled "mv file1file2"
no whitespace between "file1" and "file2".

I double checked and found that the part above is also the issue for
the original english version.

This seems to be due to "<literal> </literal>". Maybe this was useful
for some old build engine?
Attached patch remove it, and take care of translations.
As fr & es should shorter the word used for "file" to be displayed, I
corrected this too.

The reported issues are not to be corrected in the english dbk files or in
the po files.
In the stretch version (9.0.4) of the package, everything is fine. So
the reason for those issues is somewhere in the build chain of the pdfs.

In fact, it's not only russian and french versions which have problems,
but all languages!

I will leave this bug open as a reminder for later, when buster settles down
a bit ...


Thanks for reporting anyway!


Holger

[Baptiste Jammet]

Hi Holger,

Post by Holger Wansing
The reported issues are not to be corrected in the english dbk files
or in the po files.

Yes, in general.
But the only 3 others literal-spaces seems not more useful.
(command --help, tar, and dpkg --compare-versions)
They look like hacks used to give a nice output...
And the german version already removed it.

Post by Holger Wansing
In the stretch version (9.0.4) of the package, everything is fine. So
the reason for those issues is somewhere in the build chain of the pdfs.

For the record, I made all my test locally with Stretch (9.1).

Thanks for taking care of the refcard.

Baptiste

[Holger Wansing]

Control: tags -1 + pending

Post by Holger Wansing
Control: retitle -1 debian-refcard: PDFs have various problems (layout broken, missing spaces or line breaks ...)
Control: found -1 10.0

Post by Baptiste Jammet
Control: tag -1 patch
Hello,

Post by Alex

Post by Alex
move command is spelled "mv file1file2"
no whitespace between "file1" and "file2".

I double checked and found that the part above is also the issue for
the original english version.

This seems to be due to "<literal> </literal>". Maybe this was useful
for some old build engine?
Attached patch remove it, and take care of translations.
As fr & es should shorter the word used for "file" to be displayed, I
corrected this too.

The reported issues are not to be corrected in the english dbk files or in
the po files.
In the stretch version (9.0.4) of the package, everything is fine. So
the reason for those issues is somewhere in the build chain of the pdfs.
In fact, it's not only russian and french versions which have problems,
but all languages!
I will leave this bug open as a reminder for later, when buster settles down
a bit ...

I have committed a fix for this in git now.
Tagging this bug as pending.


Holger

[Debian Bug Tracking System]

tag -1 patch

Bug #880696 [debian-refcard] debian-refcard: Debian Reference Card translation to russian contains errors in command definitions
Added tag(s) patch.

[Debian Bug Tracking System]

Post by Holger Wansing
retitle -1 debian-refcard: PDFs have various problems (layout broken, missing spaces or line breaks ...)

Bug #880696 [debian-refcard] debian-refcard: Debian Reference Card translation to russian contains errors in command definitions
Changed Bug title to 'debian-refcard: PDFs have various problems (layout broken, missing spaces or line breaks ...)' from 'debian-refcard: Debian Reference Card translation to russian contains errors in command definitions'.

Post by Holger Wansing
found -1 10.0

Bug #880696 [debian-refcard] debian-refcard: PDFs have various problems (layout broken, missing spaces or line breaks ...)
Marked as found in versions refcard/10.0.

[Holger Wansing]

Hi all,

today I played around with refcard to get a solution (or a workaround) for this
problem (no progress for more than one year; sorry for this :-( )


The underlying problem seems to be somewhere in the tool chain, which is
somewhat complex here for the refcard, so this might somewhere between
dblatex, texlive-* and friends.
As it seems, strings within <literal> ... </literal> no longer get line
breaks, so several URLs are now too long to be correctly displayed on the
refcard.

Maybe someone can find the real cause of this, but I found a workaround
to fix this:
replacing all 'literal' tags by 'filename' !

The displayed output seems identical (means: apparently the same fonts are
used), and the URLs get their line breaks correctly as it was in version 9.0,
so there is no difference for the user, which looks as a sensible
workaround/solution for this problem, at least for the moment.

Since the freeze for Buster is not so far away, I would be willing to consider
this as a way to go, at least for Buster.



Greetings
Holger

[Debian Bug Tracking System]

Post by Holger Wansing
tags -1 + pending

Bug #880696 [debian-refcard] debian-refcard: PDFs have various problems (layout broken, missing spaces or line breaks ...)
Added tag(s) pending.

[Debian Bug Tracking System]

Your message dated Sun, 13 Jan 2019 22:41:05 +0000
with message-id <E1gioRF-000Hp8-***@fasolo.debian.org>
and subject line Bug#880696: fixed in refcard 10.3
has caused the Debian Bug report #880696,
regarding debian-refcard: PDFs have various problems (layout broken, missing spaces or line breaks ...)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)