Add support for Giara

2020-10-13 Thread Gabriele Musco via gnome-i18n
Hey everyone! I was asked to add in support for Damned Lies into my app
Giara (an GTK app for Reddit). I already added the @translations user
as a developer in the repo (by the way, here's the link:
https://gitlab.gnome.org/gabmus/giara).

I understand that if this goes through, I'll have to feature freeze and
notice the mailing list 1 week prior to tagging a new release, is there
anything else I should know?

Also, let me know if you need anything else, thank you all in advance!

Gabriele Musco.


signature.asc
Description: This is a digitally signed message part
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


[gdm] Created branch gnome-3-38

2020-10-13 Thread Ray Strode
The branch 'gnome-3-38' was created pointing to:

 688309c... meson: Bump to 3.38.1

___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: Technical feasibility to translate a project on Github

2020-10-13 Thread Piotr Drąg via gnome-i18n
wt., 13 paź 2020 o 15:45 Alexandre Franke  napisał(a):
> I think you are omitting a possible scenario. We can have it on Damned
> lies and not take responsibility for it, like we do for the
> Freedesktop modules. You don’t need to have teams on board to do that:
> the i18n coordinators just have to decide that it is part of our
> extended platform, like Freedesktop is, and we can add it immediately
> so we see its status alongside the rest of the platform.
>

https://l10n.gnome.org/module/flatpak/ has been here for years. :)

Best,

-- 
Piotr Drąg
https://piotrdrag.fedorapeople.org
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: Technical feasibility to translate a project on Github

2020-10-13 Thread Alexandre Franke
On Fri, Oct 9, 2020 at 2:22 PM Thibault Martin  wrote:
> Now the audience for this question would probably be the translation
> coordinators: would we accept to take the responsibility of translating
> flatpak software?

I think you are omitting a possible scenario. We can have it on Damned
lies and not take responsibility for it, like we do for the
Freedesktop modules. You don’t need to have teams on board to do that:
the i18n coordinators just have to decide that it is part of our
extended platform, like Freedesktop is, and we can add it immediately
so we see its status alongside the rest of the platform.

As for taking responsibility, I would say yes but with a lower
priority than GNOME itself. Also, I expect flatpak people to
communicate with us and have a freeze so we can do our work in good
conditions.

--
Alexandre Franke
GNOME Hacker
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: Pitivi release in the very near future (or not)

2020-10-13 Thread Thibault Martin
I didn't expect to update you this soon, but the maintainer confirmed 
they postponed the release for one week.


Happy translating/proofreading!

Le mar. 13 oct. 2020 à 14:14, Thibault Martin  a 
écrit :

Hello,

Pitivi maintainers have released 2020.09 version a few days ago. I 
reached out to the maintainer to ask them to notify us next time, and 
asked if they expected a .1 release anytime soon.


The maintainers were about to release it. I asked them to postpone it 
for one week to leave us some time to properly translate and 
proofread Pitivi. Today the discussion is not done, but the 
maintainers would like to postpone the release as asked. They also 
have other constraints, including deadlines set by distributions to 
have their packages integrated.


The maintainers will reach out to distributions packagers to see 
whether they can postpone the release by one week indeed. In the 
meantime, I think we probably should update and proofread our 
translations, but I leave that decision to each coordinator since 
we’re not sure whether these translations will be shipped or not.


I’ll update you when I get more solid information from the 
maintainers about postponing the release.


Best,


___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n



___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Pitivi release in the very near future (or not)

2020-10-13 Thread Thibault Martin

Hello,

Pitivi maintainers have released 2020.09 version a few days ago. I 
reached out to the maintainer to ask them to notify us next time, and 
asked if they expected a .1 release anytime soon.


The maintainers were about to release it. I asked them to postpone it 
for one week to leave us some time to properly translate and proofread 
Pitivi. Today the discussion is not done, but the maintainers would 
like to postpone the release as asked. They also have other 
constraints, including deadlines set by distributions to have their 
packages integrated.


The maintainers will reach out to distributions packagers to see 
whether they can postpone the release by one week indeed. In the 
meantime, I think we probably should update and proofread our 
translations, but I leave that decision to each coordinator since 
we’re not sure whether these translations will be shipped or not.


I’ll update you when I get more solid information from the 
maintainers about postponing the release.


Best,


___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: Technical feasibility to translate a project on Github

2020-10-13 Thread Daniel Mustieles García via gnome-i18n
Thanks for the quick response!

Doing a quick review of the PO file I see the strings are (in the most of
cases) very short and often used in GNOME, so using a translation memory
would be really easy to have it done.

Yes, I was thinking in the same examples. Just adding a link in the
module's page in DL to directly open an MR in the target repo would be a
medium-directly way to have it.

Taking this into account, I give a +1 for having this available for
translation in Damned Lies. Of course, now it's time to hear another
coordinator's opinion about this.

Regards


El mar., 13 oct. 2020 a las 13:09, Thibault Martin ()
escribió:

> Hello Daniel and thanks for your answser,
>
> There seems to be 1112 strings to translate for the Flatpak software
> only.
>
> Those strings are in files in the PO format. I’m not quite sure about
> how (often) those are generated, but if we need adjustments, I’m
> quite sure we can ask them a few things. Let’s not forget Alexander
> Larsson is working on it :)
>
> The files can be found here:
> https://github.com/flatpak/flatpak/tree/master/po
>
> As of today, DL is used to follow the translation status of several
> projects it can't commit on. The two examples I have in mind are the
> freedesktop and Librem 5 ones. To commit our translations, someone
> manually opens a MR on the Gitlab, and then reports to their
> translation coordinator. It’s far from ideal, but still preferable to
> a completely manual process in my opinion.
>
> Best,
>
>
> Le mar. 13 oct. 2020 à 12:58, Daniel Mustieles García
>  a écrit :
> > Hi Thibault,
> >
> > I have some questions about this, hope you can help us with them
> >
> > 1 .To have a better idea about the necessary work for this, how many
> > translatable strings (aprox) Flatpak Software has?
> >
> > 2. Are those translatable strings in a PO file format? If answer is
> > no, which format does it use and which tool is recommended for it?
> >
> > 3 - If finally DL is not able to directly commit translations, how
> > will be the workflow to send and commit them?
> >
> > In a first stage I would not opposite to this idea, but I would like
> > to solve these questions before giving a final vote (just my personal
> > opinion about this, it would be necessary other coordinator's
> > opinion).
> >
> > Thanks in advance
> >
> > El vie., 9 oct. 2020 a las 14:22, Thibault Martin
> > () escribió:
> >> Hello,
> >>
> >>  Thanks for this quick answer Claude. So that solves the technical
> >>  feasibility.
> >>
> >>  Now the audience for this question would probably be the translation
> >>  coordinators: would we accept to take the responsibility of
> >> translating
> >>  flatpak software?
> >>
> >>  Best,
> >>
> >>  Le jeu. 8 oct. 2020 à 23:12, Claude Paroz  a
> >>  écrit :
> >>  > Le 08.10.20 à 14:13, Thibault Martin a écrit :
> >>  >> Hello,
> >>  >>
> >>  >> Flatpak doesn't have a proper translation platform. So far people
> >>  >>  retrieve and submit po files manually.
> >>  >>
> >>  >> I know Flatpak doesn’t necessarily want to be too associated
> >> with
> >>  >> GNOME  so it doesn’t shy out other systems.
> >>  >> Still, a translation provided by one of the major DE could be an
> >>  >> huge  improvement to today’s situation.
> >>  >>
> >>  >> I have two questions here:
> >>  >> * Would we accept to take responsibility of Flatpak’s
> >> translations?
> >>  >> * Is it technically feasible for DL to handle the translations
> >> of a
> >>  >>  project stored on GitHub?
> >>  >>
> >>  >> If we answer "yes" to both, I would offer to Flatpak’s team to
> >>  >> take care  of their translations, which they may or may not
> >> accept.
> >>  >
> >>  > Hi Thibault,
> >>  >
> >>  > There is more or less two level of translation supports in D-L.
> >>  > The first one is "simply" a status of current module translations
> >> +
> >>  > updated pot and merged po files ready for translators to use.
> >>  > That's the case for all freedesktop modules.
> >>  >
> >>  > The second is ability to commit translations from the Web
> >> interface.
> >>  > We do not support Github currently for this feature.
> >>  >
> >>  > So I would say that hosting translation stats would be fine IMHO.
> >>  > Adding commit support is another story, even if it should not be
> >> so
> >>  > much effort (to be evaluated, still).
> >>  >
> >>  > Claude
> >>  > --
> >>  > www.2xlibre.net
> >>  > ___
> >>  > gnome-i18n mailing list
> >>  > gnome-i18n@gnome.org
> >>  > https://mail.gnome.org/mailman/listinfo/gnome-i18n
> >>
> >>
> >>  ___
> >>  gnome-i18n mailing list
> >> gnome-i18n@gnome.org
> >> https://mail.gnome.org/mailman/listinfo/gnome-i18n
>
>
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Release of Solanum in about a month

2020-10-13 Thread Thibault Martin

Hello translators,

Solanum’s maintainer Christopher Davis (@brainblasted on Gitlab) 
expects to release Solanum in about a month.


They believe Solanum is feature-complete and don't expect to make new 
release soon after that, so let's not miss the slot we have to 
translate it :)
They also don’t think the strings will change by then. I’m asking 
them to warn us if it does.


Solanum on Gitlab: https://gitlab.gnome.org/World/Solanum
Solanum on DL: https://l10n.gnome.org/module/solanum/

Best,


___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: Technical feasibility to translate a project on Github

2020-10-13 Thread Thibault Martin

Hello Daniel and thanks for your answser,

There seems to be 1112 strings to translate for the Flatpak software 
only.


Those strings are in files in the PO format. I’m not quite sure about 
how (often) those are generated, but if we need adjustments, I’m 
quite sure we can ask them a few things. Let’s not forget Alexander 
Larsson is working on it :)


The files can be found here: 
https://github.com/flatpak/flatpak/tree/master/po


As of today, DL is used to follow the translation status of several 
projects it can't commit on. The two examples I have in mind are the 
freedesktop and Librem 5 ones. To commit our translations, someone 
manually opens a MR on the Gitlab, and then reports to their 
translation coordinator. It’s far from ideal, but still preferable to 
a completely manual process in my opinion.


Best,


Le mar. 13 oct. 2020 à 12:58, Daniel Mustieles García 
 a écrit :

Hi Thibault,

I have some questions about this, hope you can help us with them

1 .To have a better idea about the necessary work for this, how many 
translatable strings (aprox) Flatpak Software has?


2. Are those translatable strings in a PO file format? If answer is 
no, which format does it use and which tool is recommended for it?


3 - If finally DL is not able to directly commit translations, how 
will be the workflow to send and commit them?


In a first stage I would not opposite to this idea, but I would like 
to solve these questions before giving a final vote (just my personal 
opinion about this, it would be necessary other coordinator's 
opinion).


Thanks in advance

El vie., 9 oct. 2020 a las 14:22, Thibault Martin 
() escribió:

Hello,

 Thanks for this quick answer Claude. So that solves the technical
 feasibility.

 Now the audience for this question would probably be the translation
 coordinators: would we accept to take the responsibility of 
translating

 flatpak software?

 Best,

 Le jeu. 8 oct. 2020 à 23:12, Claude Paroz  a
 écrit :
 > Le 08.10.20 à 14:13, Thibault Martin a écrit :
 >> Hello,
 >>
 >> Flatpak doesn't have a proper translation platform. So far people
 >>  retrieve and submit po files manually.
 >>
 >> I know Flatpak doesn’t necessarily want to be too associated 
with

 >> GNOME  so it doesn’t shy out other systems.
 >> Still, a translation provided by one of the major DE could be an
 >> huge  improvement to today’s situation.
 >>
 >> I have two questions here:
 >> * Would we accept to take responsibility of Flatpak’s 
translations?
 >> * Is it technically feasible for DL to handle the translations 
of a

 >>  project stored on GitHub?
 >>
 >> If we answer "yes" to both, I would offer to Flatpak’s team to
 >> take care  of their translations, which they may or may not 
accept.

 >
 > Hi Thibault,
 >
 > There is more or less two level of translation supports in D-L.
 > The first one is "simply" a status of current module translations 
+

 > updated pot and merged po files ready for translators to use.
 > That's the case for all freedesktop modules.
 >
 > The second is ability to commit translations from the Web 
interface.

 > We do not support Github currently for this feature.
 >
 > So I would say that hosting translation stats would be fine IMHO.
 > Adding commit support is another story, even if it should not be 
so

 > much effort (to be evaluated, still).
 >
 > Claude
 > --
 > www.2xlibre.net
 > ___
 > gnome-i18n mailing list
 > gnome-i18n@gnome.org
 > https://mail.gnome.org/mailman/listinfo/gnome-i18n


 ___
 gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n



___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: Technical feasibility to translate a project on Github

2020-10-13 Thread Daniel Mustieles García via gnome-i18n
Hi Thibault,

I have some questions about this, hope you can help us with them

1 .To have a better idea about the necessary work for this, how many
translatable strings (aprox) Flatpak Software has?

2. Are those translatable strings in a PO file format? If answer is no,
which format does it use and which tool is recommended for it?

3 - If finally DL is not able to directly commit translations, how will be
the workflow to send and commit them?

In a first stage I would not opposite to this idea, but I would like to
solve these questions before giving a final vote (just my personal opinion
about this, it would be necessary other coordinator's opinion).

Thanks in advance

El vie., 9 oct. 2020 a las 14:22, Thibault Martin ()
escribió:

> Hello,
>
> Thanks for this quick answer Claude. So that solves the technical
> feasibility.
>
> Now the audience for this question would probably be the translation
> coordinators: would we accept to take the responsibility of translating
> flatpak software?
>
> Best,
>
> Le jeu. 8 oct. 2020 à 23:12, Claude Paroz  a
> écrit :
> > Le 08.10.20 à 14:13, Thibault Martin a écrit :
> >> Hello,
> >>
> >> Flatpak doesn't have a proper translation platform. So far people
> >>  retrieve and submit po files manually.
> >>
> >> I know Flatpak doesn’t necessarily want to be too associated with
> >> GNOME  so it doesn’t shy out other systems.
> >> Still, a translation provided by one of the major DE could be an
> >> huge  improvement to today’s situation.
> >>
> >> I have two questions here:
> >> * Would we accept to take responsibility of Flatpak’s translations?
> >> * Is it technically feasible for DL to handle the translations of a
> >>  project stored on GitHub?
> >>
> >> If we answer "yes" to both, I would offer to Flatpak’s team to
> >> take care  of their translations, which they may or may not accept.
> >
> > Hi Thibault,
> >
> > There is more or less two level of translation supports in D-L.
> > The first one is "simply" a status of current module translations +
> > updated pot and merged po files ready for translators to use.
> > That's the case for all freedesktop modules.
> >
> > The second is ability to commit translations from the Web interface.
> > We do not support Github currently for this feature.
> >
> > So I would say that hosting translation stats would be fine IMHO.
> > Adding commit support is another story, even if it should not be so
> > much effort (to be evaluated, still).
> >
> > Claude
> > --
> > www.2xlibre.net
> > ___
> > gnome-i18n mailing list
> > gnome-i18n@gnome.org
> > https://mail.gnome.org/mailman/listinfo/gnome-i18n
>
>
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-i18n
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n