Re: [ESD-translators] Synchronizing enc and enc-live

[Thérèse Godefroy]

Hi Zoë, hi all,

Le 28/07/2021 à 23:51, Zoë Kooyman a écrit :
[...]
> Hi Everyone,
> 
> So i wanted to run this through the technical team for some info, which
> is why it took me a little longer to respond. But it looks like we
> cannot set up permissions for branches in the repo, so that leaves some
> sensitivity issues. However, Andrew suggested that we can look into
> having 2 remotes instead, that that might be a more elegant solution,
> but it brings it's own set of issues again not too different from where
> we are now. But if people think this is a great idea we can look into
> this further.
> 
> I don't think any of the solutions so far really address the issues we
> have now to merit changes. And as for the current workflow, I think I am
> probably the person that messed up the enc to enc-live synching order of
> doing things with the changes, and I can adapt of course to doing that
> the other way around again. I assume generally no one makes changes to
> the enc/en files unless there is some agreement here on the translators
> list, though, or without synching to enc-live, right, or am i missing
> something?
>

I do sometimes make changes to the en files, when they are purely
cosmetic. For instance, I fixed main.css so it wouldn't make <p>'s
smaller in the <dl> lists, and replaced a few anonymous boxes with <p>'s
to make font size and spacing consistent throughout the page. (This css
is really weird!)


> Anyhow, I can commit to making changes to enc, then sync to enc-live,
> and keep people in the loop!
>

That would be great!

You can probably use a simple script to copy the en/ directory to
enc-live, cd to enc-live, pull from origin, and commit your changes with
a message that refers to the id of the enc commit. This is what I used
to do with translations.
The script can even push the enc-live commit after asking whether it's
OK. And if you are very lazy you can make a launcher that will let you
synchronize in one click. :)


> Let me know if there is something else, or other ideas!
> 

I'd like to make a few more cosmetic changes:

- use <code> for commands and <samp> for program output, instead of
<span style="...">, and move the style definitions to main.css. I would
also give <code> and <samp> a small horizontal padding, and <code> would
be displayed as inline-block to prevent wrapping.

- define a class for the other colored <span>'s.

If you wish, I will push these changes to enc so you can look at them.

> Thanks!
> 
> -- 
> Zoë Kooyman // Program Manager
> Free Software Foundation

Thanks to you!
Thérèse