Re: [ready for proofreading] Re: [translating] [CS] Ada & Zangemann

Tomas Stary <[email protected]> Sat, 8 Mar 2025 12:11:00 +0100
Newsgroups gmane.org.fsf.europe.translators
Message-ID <[email protected]>
Hi Nico,

I'm sorry for a long delay in the response. (reaction to your email 
filled below in the text)

I wonder what are next necessary steps. At the moment I see the 
translation of the text in the illustrations and adding the chapters 
capitals. Would Sandra Brandstätter do it for us?

Once that is done, the book would be basically ready to get to the 
publisher. What is the procedure there? Would we need native Czech 
publisher or could it be published with some of the publishers or other 
language versions?

Best regards,

Tomas


On 15/02/2025 08:07, Nico Rikken wrote:
> Hi Tomas,
>
> Tomas Stary schreef op do 13-02-2025 om 20:24 [+0100]:
>> Hi Nico,
>>
>> Thanks for merging the czech version.
>>
>>   >  Besides the capitals, a different font is needed as Heebo
>> (variant of
>> Roboto font) lacks the necessary glyphs. Reading online it sees that
>> default Roboto would work just fine.
>>
>> Is that a problem in all language versions? I noticed that the font
>> is a
>> bit different than in physical book even in German and English
>> version,
>> and also that the spacing is a bit bigger.
> I agree that the fonts look different among the German and English
> book. In those cases a publisher was involved, having a hand in the
> publishing. I would like to find out the exact differences, but haven't
> gotten around to it yet. I did some analysis of different books on this
> feature branch:
> https://git.fsfe.org/FSFE/ada-zangemann/src/branch/feature/docbook-format/docbook#user-content-notable-differences-between-editions
>
> At the moment the Roboto font variants are used in the templates, which
> seems a reasonable choice. If no Czech variant is available feel free
> to suggest another option.

To me it seams that the current font choice works fine.


>
>> This is something to change in the templates, isn't it?
>>
>> Also, as I already mentioned in one of the previous emails, I believe
>> that the alignment to block would look better if it's not too
>> difficult
>> to change in the templates.
> In Scribus the properties of the text frames can be changed to
> justify.
>
> This will introduce issues for the pages with text next to images,
> because the templates lack frame borders and rely on hard line breaks
> to make sure that there is no text on top of images. This text with
> hard line breaks will still overlap the images if justified.
>
> Also, in my limited publishing experience I was told repeatedly that
> justification is mostly for the looks at the cost of reducing
> readability. It can introduce formatting issues like wide spaces that
> need to be resolved.
>
> So I would advise not to justify the text, but if you want to try it
> you can create a variant of the Scribus template and change the font
> frame settings, or change it in the rendered Scribus template.

Thanks for the explanation. If that is so, I take your advice to stay 
with the aligned text for now.

>
> To be clear: I'm fine questioning the status quo, that way we can make
> things better. Thanks for that.
>
> Best,
> Nico
>
>> Best,
>>
>> Tomas
>>
>>
>> On 10/02/2025 20:27, Nico Rikken wrote:
>>> Hi Tomas,
>>>
>>> Thanks! I merged it. There was a file conflict I resolved. I also
>>> aligned the file content with the English version:
>>>
>>> https://git.fsfe.org/FSFE/ada-zangemann/pulls/74
>>>
>>> Besides the capitals, a different font is needed as Heebo (variant
>>> of
>>> Roboto font) lacks the necessary glyphs. Reading online it sees
>>> that
>>> default Roboto would work just fine.
>>>
>>> Let's collaborate to tackle these issues one by one.
>>>
>>> Best,
>>> Nico
_______________________________________________
Translators mailing list -- [email protected]
To unsubscribe send an email to [email protected]

This mailing list is covered by the FSFE's Code of Conduct. All
participants are kindly asked to be excellent to each other:
https://fsfe.org/about/codeofconduct