Re: [Tails-l10n] Translating the Installation Assistant

Delete this message

Reply to this message
Author: sajolida
Date:  
To: Tails localization discussion, tchou
Subject: Re: [Tails-l10n] Translating the Installation Assistant
Muri Nicanor:
> On 12/09/2015 01:11 PM, sajolida wrote:
> [...]
>> So I'm very interested in having feedback from you in case you're
>> blocked by some piece of code that you can't translate. Also make sure
>> to build the website locally and check if all the scenarios are fine
>> once you translated a string. Also tell me if I should write
>> documentation for translators for this or add comments in the code, etc.
>
> this leads my to a question thats maybe a bit offtopic on t10n- but
> where and how is the most convenient way to do upstream documentation
> pull requests?
> should i always create a ticket on rln and provide a link
> to commit there? or should i do git format-patch -o . origin/master &&
> mutt sajolida@??? -a *.patch? or send to tails-devel?


We don't have a dedicated channel for documentation workflows. So I'm
flexible:

a. If it's a very small patch for a typo you can send a patch file or a
branch name on tails-dev or here if it's more convenient you.

b. If it's bigger than a typo, for example if you want to rephrase or
clarify something, then maybe tails-dev is better (to reduce the noise
on this list). You can try sending a patch file or a branch name and if
we see it needs more debate we'll open a ticket.

The choice between a patch file and branch name is up to you, if I had
to do that myself I would send a branch as I would probably find them
quicker to deal with, but maybe it's different for you and patches are fine.

c. If you think there's a problem but you don't feel like fixing it
yourself, then maybe a ticket is better. You can assign it to me if
you're not sure and I'll process it.

> for example, i've attached a small patch which changes some css fields
> for the header of the /install page - because 'Tails
> Installations-Assistent' is one character longer and doesnt't fit in
> #content ;)


In this particular case, where it's not about the content but about the
CSS style, we need to ask tchou (in copy) who's the one working on the
all the HTML and CSS as the patch that you are proposing changes quite a
bit the look of the first page.
From bc3be574cfcdddfc2a8b3c42e183cfbfd4922fe7 Mon Sep 17 00:00:00 2001
From: Muri Nicanor <muri@???>
Date: Wed, 9 Dec 2015 23:12:53 +0100
Subject: [PATCH] fixed width of the header element for langs with longer words

---
wiki/src/install/inc/stylesheets/router-install.css | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/wiki/src/install/inc/stylesheets/router-install.css b/wiki/src/install/inc/stylesheets/router-install.css
index 43fc2a7..02518c8 100644
--- a/wiki/src/install/inc/stylesheets/router-install.css
+++ b/wiki/src/install/inc/stylesheets/router-install.css
@@ -1,6 +1,6 @@
#content {
padding-top: 20px;
- width: 50%;
- margin-left: 25%;
- margin-right: 25%;
+ width: 60%;
+ margin-left: 20%;
+ margin-right: 20%;
}
--
2.6.2