Hi all,
While translating getfedora.org, I got confused about the various variants "Fedora Cloud Base Images".
First, the letter case. Actually I see "Fedora Cloud Base image" on the new website [1], "Fedora Cloud base images" on the wiki page [2], and "Fedora Cloud Base Image" on fedoramagazine and cloud trac [3]. I wonder which is the correct spelling.
Second, should the term be translated or not?
Besides, there is a "Cloud Base Images" on the new website [4]. I guess it should be translated. Am I right?
[1] http://stg.getfedora.org/en/cloud/download/ [2] https://fedoraproject.org/wiki/Cloud/Cloud_PRD [3] https://fedorahosted.org/cloud/ticket/55 [4] http://stg.getfedora.org/en/cloud/
Regards, Alick
On Sat Nov 29 2014 at 5:53:41 PM Alick Zhao alick9188@gmail.com wrote:
First, the letter case. Actually I see "Fedora Cloud Base image" on the new website [1], "Fedora Cloud base images" on the wiki page [2], and "Fedora Cloud Base Image" on fedoramagazine and cloud trac [3]. I wonder which is the correct spelling.
I think 'Image' in [3] is a typo, which should be image, and 'base' in [2]
is also a typo, which it should be 'Base'.
Second, should the term be translated or not?
Besides, there is a "Cloud Base Images" on the new website [4]. I guess it should be translated. Am I right?
I guess Cloud Base should be left untranslated. While Image(s) can be translated.
On Sat, Nov 29, 2014 at 11:40:15AM +0000, tiansworld wrote:
On Sat Nov 29 2014 at 5:53:41 PM Alick Zhao alick9188@gmail.com wrote:
First, the letter case. Actually I see "Fedora Cloud Base image" on the new website [1], "Fedora Cloud base images" on the wiki page [2], and "Fedora Cloud Base Image" on fedoramagazine and cloud trac [3]. I wonder which is the correct spelling.
I think 'Image' in [3] is a typo, which should be image, and 'base' in [2]
is also a typo, which it should be 'Base'.
Second, should the term be translated or not?
Besides, there is a "Cloud Base Images" on the new website [4]. I guess it should be translated. Am I right?
I guess Cloud Base should be left untranslated. While Image(s) can be translated.
"Fedora Cloud" should be left as a proper name, but "Base Image" can be translated. The word "base" here is in the sense of foundation or underlying, if that helps.
On Sat, Nov 29, 2014 at 11:40:15AM +0000, tiansworld wrote:
First, the letter case. Actually I see "Fedora Cloud Base image" on the new website [1], "Fedora Cloud base images" on the wiki page [2], and "Fedora Cloud Base Image" on fedoramagazine and cloud trac [3]. I wonder which is the correct spelling.
I think 'Image' in [3] is a typo, which should be image, and 'base' in [2] is also a typo, which it should be 'Base'.
It's not exactly a typo -- it's more that we've been a bit inconsistent here.
Second, should the term be translated or not?
"Fedora Cloud" shouldn't, but "base image" should. In fact, if it helps, it might be appropriate to put the translated word cloud into "base image" — that is, "Fedora Cloud [foundational cloud system image]".
I'm far from an expert here, but "image" should use the word used for virtual machine images, if that's different from photographs. (In English, it's "image" in the sense of "exact reproduction / likeness" rather than "picture".)
"Fedora Cloud" shouldn't, but "base image" should. In fact, if it helps, it might be appropriate to put the translated word cloud into "base image" — that is, "Fedora Cloud [foundational cloud system image]".
I'm far from an expert here, but "image" should use the word used for virtual machine images, if that's different from photographs. (In English, it's "image" in the sense of "exact reproduction / likeness" rather than "picture".)
Thanks.
There are other words confusing us in website translation too(For example, keys for signing packages. We are not sure the type of key, public key or private key or what else.).
So I hope you can put this kind of simple explanation into comment part of the string in future, so every translator can see them and know what should be translated or whether the words should be translated.
On Tue, Dec 02, 2014 at 08:01:00PM +0800, tiansworld wrote:
There are other words confusing us in website translation too(For example, keys for signing packages. We are not sure the type of key, public key or private key or what else.).
Where is this example?
So I hope you can put this kind of simple explanation into comment part of the string in future, so every translator can see them and know what should be translated or whether the words should be translated.
I'm not familiar with the tools used here, really. Might it be easier to have a wiki page with notes for translators?
On Tue, Dec 02, 2014 at 07:41:08AM -0500, Matthew Miller wrote:
On Tue, Dec 02, 2014 at 08:01:00PM +0800, tiansworld wrote:
There are other words confusing us in website translation too(For example, keys for signing packages. We are not sure the type of key, public key or private key or what else.).
Where is this example?
So I hope you can put this kind of simple explanation into comment part of the string in future, so every translator can see them and know what should be translated or whether the words should be translated.
I'm not familiar with the tools used here, really. Might it be easier to have a wiki page with notes for translators?
Not really, since it adds complexity, an and there's no easy way to refer translators to the right page from the content itself (which is a barrier).
The best solution would be for our templating system to do the right thing about allowing comments for translators. However, this seems to be an issue with the "genshi" templating system used on the site. Ricky Elrod was looking into it and it may in fact be a bug.
On Tue, Dec 2, 2014 at 8:41 PM, Matthew Miller mattdm@fedoraproject.org wrote:
On Tue, Dec 02, 2014 at 08:01:00PM +0800, tiansworld wrote:
There are other words confusing us in website translation too(For
example,
keys for signing packages. We are not sure the type of key, public key or private key or what else.).
Where is this example?
After I view the whole po file again, the example I took seems not a good one :) But it can reflect that confusion occurs sometime.
This string tells us that they are public keys.
#: data/content/keys/index.html:21 msgid "" "This page lists the public GPG keys used for signing packages in Fedora."
So we can conclude that keys related to packages signing in the po file should be public keys.
Then what about this one: #: data/content/verify.html:75 162 msgid "Next, import Fedora's GPG key(s):"
We may not sure whether it is a public or private at once.
So I hope you can put this kind of simple explanation into comment part
of
the string in future, so every translator can see them and know what
should
be translated or whether the words should be translated.
I'm not familiar with the tools used here, really. Might it be easier to have a wiki page with notes for translators?
This is not a good choice. The better way is integrate them into po files. Although I don't know how to make this happen.
On 12/03/2014 06:16 PM, tiansworld wrote:
On Tue, Dec 2, 2014 at 8:41 PM, Matthew Miller <mattdm@fedoraproject.org mailto:mattdm@fedoraproject.org> wrote:
On Tue, Dec 02, 2014 at 08:01:00PM +0800, tiansworld wrote: > There are other words confusing us in website translation too(For example, > keys for signing packages. We are not sure the type of key, public key or > private key or what else.). Where is this example?After I view the whole po file again, the example I took seems not a good one :) But it can reflect that confusion occurs sometime.
This string tells us that they are public keys.
#: data/content/keys/index.html:21 msgid "" "This page lists the public GPG keys used for signing packages in Fedora."
So we can conclude that keys related to packages signing in the po file should be public keys.
Then what about this one: #: data/content/verify.html:75 162msgid "Next, import Fedora's GPG key(s):"
We may not sure whether it is a public or private at once.
> So I hope you can put this kind of simple explanation into comment part of > the string in future, so every translator can see them and know what should > be translated or whether the words should be translated. I'm not familiar with the tools used here, really. Might it be easier to have a wiki page with notes for translators?This is not a good choice. The better way is integrate them into po files. Although I don't know how to make this happen.
-- Regards,
Tian Shixiong Fedora Project Contributor
Maybe Source String Contextualization Group under Fedora SIG could be of help here.
https://fedoraproject.org/wiki/SSCG
Thanks,
2014-12-03 13:46 GMT+01:00 tiansworld tiansworld@fedoraproject.org:
On Tue, Dec 2, 2014 at 8:41 PM, Matthew Miller mattdm@fedoraproject.org wrote:
On Tue, Dec 02, 2014 at 08:01:00PM +0800, tiansworld wrote:
There are other words confusing us in website translation too(For
example,
keys for signing packages. We are not sure the type of key, public key
or
private key or what else.).
Where is this example?
After I view the whole po file again, the example I took seems not a good one :) But it can reflect that confusion occurs sometime.
This string tells us that they are public keys.
#: data/content/keys/index.html:21 msgid "" "This page lists the public GPG keys used for signing packages in Fedora."
So we can conclude that keys related to packages signing in the po file should be public keys.
Then what about this one: #: data/content/verify.html:75 162 msgid "Next, import Fedora's GPG key(s):"
We may not sure whether it is a public or private at once.
Well, yes, these are all public keys of course, although I don't get why you should mention it in that string. If you look at the page where these strings are (the keys.html page) you will understand the context, and as the string is part of the instructions, it should be obvious for all users you are speaking about the same public keys.
So I hope you can put this kind of simple explanation into comment part
of
the string in future, so every translator can see them and know what
should
be translated or whether the words should be translated.
I'm not familiar with the tools used here, really. Might it be easier to have a wiki page with notes for translators?
This is not a good choice. The better way is integrate them into po files. Although I don't know how to make this happen.
Yes, comments would be nice, but actually we are not able to provide them. We discussed this already and hope to find a solution for the near future. Anyway, don't expect there will be comments for all strings you are going to translate. Reading the webpage to get the context will be much more useful, IMHO. In the meanwhile I tried to advice about particular strings in the notes I've sent out for F21 websites and you all did a very good work with them.
-- Regards,
Tian Shixiong Fedora Project Contributor
Kind regards.
On Wed, Dec 03, 2014 at 08:46:29PM +0800, tiansworld wrote:
Then what about this one: #: data/content/verify.html:75 162 msgid "Next, import Fedora's GPG key(s):" We may not sure whether it is a public or private at once.
I don't think that's a translation problem. It's unclear in English. :)
On 12/01/2014 10:35 PM, Matthew Miller wrote:
On Sat, Nov 29, 2014 at 11:40:15AM +0000, tiansworld wrote:
First, the letter case. Actually I see "Fedora Cloud Base image" on the new website [1], "Fedora Cloud base images" on the wiki page [2], and "Fedora Cloud Base Image" on fedoramagazine and cloud trac [3]. I wonder which is the correct spelling.
I think 'Image' in [3] is a typo, which should be image, and 'base' in [2] is also a typo, which it should be 'Base'.
It's not exactly a typo -- it's more that we've been a bit inconsistent here.
Second, should the term be translated or not?
"Fedora Cloud" shouldn't, but "base image" should. In fact, if it helps, it might be appropriate to put the translated word cloud into "base image" — that is, "Fedora Cloud [foundational cloud system image]".
Thanks for clearing it up!
I'm far from an expert here, but "image" should use the word used for virtual machine images, if that's different from photographs. (In English, it's "image" in the sense of "exact reproduction / likeness" rather than "picture".)
Fortunately they are different in Chinese :)
Regards,
2014-11-29 3:53 GMT-06:00 Alick Zhao alick9188@gmail.com:
Hi all,
While translating getfedora.org, I got confused about the various variants "Fedora Cloud Base Images".
By the way, we do translate "Fedora Atomic" or we don´t translate it?
On Mon, Dec 01, 2014 at 09:21:53AM -0600, William Moreno wrote:
2014-11-29 3:53 GMT-06:00 Alick Zhao alick9188@gmail.com:
Hi all,
While translating getfedora.org, I got confused about the various variants "Fedora Cloud Base Images".
By the way, we do translate "Fedora Atomic" or we don´t translate it?
"Atomic" comes from Project Atomic: http://projectatomic.io
So treat this the same way you would treat other project names that are not Fedora. In other words, "Fedora Atomic" is not a single term. Here it means, an Atomic offering by the Fedora project.
On 12/02/2014 12:33 AM, Paul W. Frields wrote:
On Mon, Dec 01, 2014 at 09:21:53AM -0600, William Moreno wrote:
2014-11-29 3:53 GMT-06:00 Alick Zhao alick9188@gmail.com:
Hi all,
While translating getfedora.org, I got confused about the various variants "Fedora Cloud Base Images".
By the way, we do translate "Fedora Atomic" or we don´t translate it?
"Atomic" comes from Project Atomic: http://projectatomic.io
So treat this the same way you would treat other project names that are not Fedora. In other words, "Fedora Atomic" is not a single term. Here it means, an Atomic offering by the Fedora project.
Hmm. Not the same as Matthew suggested:
https://lists.fedoraproject.org/pipermail/trans/2014-November/011706.html
-
Alick Zhao -
Ankit Patel -
Matthew Miller -
Paul W. Frields -
Robert Mayr -
Tiansworld -
William Moreno