During Friday's FESCo meeting we were asked to approve a change to
the release schedule to accommodate translation string freeze deadlines
that somehow got left out of the new "no-alphas" schedule.
Several participants pointed out that Fedora has not enforced the
"string freeze" in many years, despite it being on the schedule until
now. Thus, we would like to revisit the string freeze policy to
determine if it is still valuable, and if so, how can/should it be enforced?
We'd like to explore a couple of questions:
* What exact things are frozen? Things like comps make sense to follow
Fedora freezes, but do things like anaconda? or system-config-printer?
* Can we automate some way of enforcing or at least detecting when
something changes a string in the freeze?
This ticket tracks the issue:
My name is Takuro Nagamoto. I am a Japanese translator at Red Hat, based in Brisbane, Australia.
I just wanted to let you know that I took over a coordinator role for Fedora Japanese translation from Noriko, who left Red Hat in January (greatly missed).
Hope to contribute to the Fedora Japanese translation team as a coordinator/translator/reviewer (I already have those privileges granted on zanata).
I need some help with Fedora documentation. I have uploaded on GitHub
the german .po-files for the Flatpak documentation sitting here:
First of all: Is there interest in this one? If yes:
What is it that I have to do now in this special case? There is need
for a review of course. I could imagine some revisions eventually, but
it is something you can work with ... ^^
Somebody who is willing to do a review on this? Or maybe give me an
helping hand to find the needed information to optimize the
translation? And do all this here the Fedora-way? I have read the l10n-
guide, but i am lost now a little bit.
I apologize for the missing introduction of my person, but I have lost
my poetry album for today. I will write some words in the following
during discussion on the FLOCK it has been realized we have some issue
with Software String Freeze milestone. The issue is caused mostly by
changing some key milestones as a consequence of "No More Alphas"
In the past the Software String Freeze milestone was tight together
with Alpha Freeze. After we implemented the "No More Alphas" Change
 and we moved Branching closer to Beta Freeze, we are now in the
situation when we need to come up with some conclusion how to plan the
Software String Freeze milestone. AFAIK there are two requirements
this milestone should fulfil:
* The milestone needs to be planned after Branching
* There should be enough time for translators to do the job before
Software Translation Deadline (which is currently planned two weeks
before Beta Freeze)
Having the Branching 3 weeks before Beta Freeze does not give enough
room for translations (comparing to the state before implementation of
"No More Alphas" Change ). What I see as a possibility now is to
have the Software String Freeze milestone one week after Branching and
move Software Translation Deadline to the same date as Beta Freeze.
This gives us the maximum time period between the "Software String
Freeze" and "Translation deadline" we can currently have (even it is
just two weeks).
What do you think ? Will such a timing works for these two milestones
( Software String Freeze & Software Translation Deadline ) ? Or anyone
have a better proposal ?
Thanks for any feedback,
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
I have received an translation task, where we creating an expression
dictionary, but for pronouncing I need to create a transscription of the
words. The issue is that I have the pronounciation pairs, but for easier
transscribe would be an amazing help if I could feed into an program that
does this for me.
Any idea what kind of app can do this?
Dear localization team,
I've updated this page about L10N Meetings:
This page includes the agenda of our next meeting (Monday 11th, at noon).
Finding a good schedule is difficult, I hope it will at least be ok for
Europe, Asia & Australia.
Please note we're still looking for information for the following list
of translators, please answer to me directly if you know (or are) one of
flavius Ukrainian EMEA
aurisc4 Lithuanian EMEA
feonsu Slovak EMEA
ouesten Portuguese (Brazil) LATAM
peartown Czech EMEA
ricardopinto Portuguese EMEA
lstemmle German EMEA
tiansworld Chinese (China) APAC
mosquito Chinese (China) APAC
sujiniku Japanese APAC
sewerx Korean APAC
evillagr Spanish EMEA
laskov Bulgarian EMEA
Have a nice day,
we are going towards F27 Beta and we have some changes in ARM this time. We
might have also updates in the Server section, but for now we still don't
I'm sending this email just to let you know that we will update the
websites source files very often in the next week, so please take a look
from time to time to see if there are new strings.
Furthermore, we chose to not freeze translations this time, as we don't
expect any conflicts with the new content and translations. Just remember
that not all strings are in production, but they are pulled also to the F27
At the beginning of next week we will run staging websites also from F27
Beta branch, so you can look and check your strings online.
For any questions just ask here.
Thank you for all your work.
Since my last post, I havn’t looked back, so didn’t read such many of your
kind and warm comments to my post. I really thank you all.
A few weeks back, I had a chance to google “fedora”. The results showed
https://getfedora.org/ja/ link top. I clicked it, and could see two “join”
links. I clicked bottom one, and was moved to “Join” page. In the “Join”
page, I found that the “Translator” section contained irrelative
information with no link to any of l10n related wiki.
Then I remembered that we used to have many of people who wanted to become
translator got lost and reached wrong place, and realized that this page
possibly was the cause.
I pondered, but I wanted to give a correction to that section, stopping
people get lost.
This is revised page, https://fedoraproject.org/wiki/Join#Translator
If you do not like the change, please feel free to revert it back.
Good day to you all.