Attention translators: moving to Transifex

[kovidgoyal]

That would be rather more work than I am willing to undertake. Most screenshots are present in order to help people recognize parts of the interface in any case, the text on them is mostly unimportant.

[Divingduck]

Kovid,
a question about using special characters like en dash ( –, – ) or Ampersand ( &, & )in translations in the user manual. Should I use these characters as glyph or entity code?

[Jellby]

But sometimes the main text refers to the text of the screenshots, like here. That may be confusing for someone who doesn't know English at all. Well, let's translate the text first, we can worry about that later

[Divingduck]

That's a problem I sometimes have too. Maybe we should refer for names like value in English as "Wert (value)" if refer to a screenshot. Then this is more flexible and Kovid do not need to manage tons of screenshots for translations (only a guess)

An additional question for Kovid,
Is it possible for me to make a test build for the manual and if yes how can I do this?

[kovidgoyal]

@Divingduck: Use whatever form is used in the source text for special characters. The manual is built using the sphinx documentation tool. You would need to install it run it something like this:

mkdir -p .build/html
sphinx-build -b html -t online .build/html (in the manual directory in the calibre source code)

However, I have not tested this on anything other than my development machine and I doubt it will work on anything other than a linux machine with calibre installed and available in the system python.

@Jellby: certainly, there are places where the text refers to text in the images, but they are relatively rare.

[Divingduck]

Kovid,
thanks, I'll look in and try to become sphinx running.

[Jellby]

How do internal links work? Are the anchor names hardcoded or parsed from the translated text? For example, in:

This action is the inverse of the :ref:`Save to disk <save_to_disk_multiple>` action

should I translate "<save_to_disk_multiple>" and make sure it matches with some some other string or should I leave untouched?

[kovidgoyal]

Leave it untouched. The part inside the <> is like an HTML anchor and should not be translated. The rest of it is text and should be translated.

[Jellby]

What about:

:ref:`excluded_genres`
:ref:`Custom catalog covers`

If I had to guess, I'd say the first is fixed, and the second is translatable. But guessing is always dangerous.

[kovidgoyal]

:ref: without anything in <> must not be translated at all.

[Divingduck]

Kovid,

There is a change to entity code necessary for the following help string:

#: /home/kovid/work/calibre/src/calibre/gui2/tweak_book/editor/smart/html.py:493

String old (picture1):
Cannot change text alignment as the cursor is not inside a block level tag, such as a <p> or <div> tag.

String new(picture2, sorry in german):
Cannot change text alignment as the cursor is not inside a block level tag, such as a &lt;p&gt; or &lt;div&gt; tag.

Best regards,
Armin

[kovidgoyal]

Thanks, fixed.

[Jellby]

The code samples in the manual are not translatable, as far as I can see. That's often OK, because code is code, but sometimes some keywords are translated or the code blocks contain some English explanation.

For example, the date search syntax explanation in The Search Interface:

pubdate:>2000-1 Will find all books published after Jan, 2000
date:<=2000-1-3 Will find all books added to calibre before 3 Jan, 2000
pubdate:=2009 Will find all books published in 2009

date:>10daysago
date:<=45daysago

(this second sample is not so important, because "daysago" is always available regardless of the language, but it would be nice to include the translated keywords in the samples).

[kovidgoyal]

That's a decision made by sphinx, the documentation system calibre uses. It does not make literal code blocks available for translation, not much I can do about it.

[Jellby]

Originally Posted by kovidgoyal

That's a decision made by sphinx, the documentation system calibre uses. It does not make literal code blocks available for translation, not much I can do about it.

I guess only pester sphinx developers and/or rewrite the code blocks so that they contain only code