-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Translate Dancing Goat to Spanish #20
Comments
@JanLenoch will add data to the dump file and give you more information about how to translate them. |
The items.json contains just the list of IDs. You can pretty much ignore it. But, alongside that, I've exported the texts into other .json files named by items' IDs. Some of them already contain a Spanish variant. These have two sets of the "item", "elements", "language" and "last_modified" fields. It'd be great if you checked these translated items for possible errors. Apart from the translated files, some other files do not contain the Spanish variant at all. You can add the Spanish variant simply by:
That way, you'll make the original .json files ready to be imported back. You don't have to do any importing, just adjust the files. If you have any questions, feel free to ask. I'll be happy to help. Thanks! |
Hi guys, how "translated" you want it? Machine translation for demo purposes will do? |
Question: Do you want a more formal language or informal? (Basically, referring to people as Usted or Tú?) |
@JanLenoch could you please give @beemtz some guidance? thx |
Hi Bee! Don't worry, you got it right this time. The "this" that you've referred to is the desired outcome. It contains both language variants (although in that file, it cannot be seen at the first sight, just because a street address was translated into, well, that same street address). As for formality: Good question. I'd stick with being rather formal. The sample site is not a community-held site, rather a fictional company's promotional asset. Thank you! |
Hi @beemtz, |
Hi @beemtz , I was just wondering if there were any nuisances you've come across during the translation process. I mean, apart from the fact that Kentico Cloud Content Management API didn't support the rich text fields at the time of exporting the .json files for you (which we've discussed earlier). I suppose you've paused your efforts until we do the re-export for you (that also contains the rich text fields). Is that correct? Or, was there any issue you've hit? If there is any issue, just let me know if I can be of any help to you. Thank you! |
Hi Petr,
First of all, I went to the postal office to pick up the Kentico stickers
and goodies this weekend. Thank you so much!
Second, let me explain... I made a list of the links I was going to
translate, and when I was done with it, it didn't occur to me to check if
there were *new* links... but I know now!
Third, I don't have a local repo and my computer is pretty much
exploding-level full. Do you mind if I keep working like before or do you
have a suggestion that might be less spammy/bothersome for you?
In short: Didn't know there was more to translate. Will proceed as soon as
I have your green light.
Thanks!
Bee
…On Fri, Dec 1, 2017 at 9:06 AM, Jan Lenoch ***@***.***> wrote:
Hi @beemtz <https://github.com/beemtz> ,
I was just wondering if there were any nuisances you've come across during
the translation process. I mean, apart from the fact that Kentico Cloud
Content Management API didn't support the rich text fields at the time of
exporting the .json files for you (which we've discussed earlier). I
suppose you've paused your efforts until we do the re-export for you (that
also contains the rich text fields). Is that correct? Or, was there any
issue you've hit?
Thank you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AVmnvhHSebioB1ZE1MQ0Myb4B9QXgevYks5s8BXkgaJpZM4QEBan>
.
--
*B*ee *M*artinez
developer
*front-end | wordpress | content*
*956 231 69 89 | @thebeeletter*
|
Hi Bee, Don't feel compelled to explain things. We're glad you've come up with the idea of translating the sample site. We would like to thank you for your commitment! (And I'm glad you like the stickers.) As for the way of working--no problem at all. Whatever makes your work easier and perhaps more fun, just let's do it that way. All right, if you plan on crunching the rest of the texts, I'll wait until you're done with that, and then I'll do the re-export, with the rich text content elements included. Thanks! Jan |
Hi, Jan!
Could I be assigned those issues then? Or a new link list? (Maybe an email
or google doc?) Or... is the old list updated? I just to get a sense of
how to start again :)
Thank you!
B
…On Mon, Dec 4, 2017 at 2:08 PM, Jan Lenoch ***@***.***> wrote:
Hi Bee,
Don't feel compelled to explain things. We're glad you've come up with the
idea of translating the sample site. We would like to thank you for your
commitment! (And I'm glad you like the stickers.)
As for the way of working--no problem at all. Whatever makes your work
easier and perhaps more fun, just let's do it that way.
All right, if you plan on crunching the rest of the texts, I'll wait until
you're done with that, and then I'll do the re-export, with the rich text
content elements included.
Thanks!
Jan
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AVmnvs88gO_Gx2651p97SjqgumkxZe6Rks5s9FE4gaJpZM4QEBan>
.
--
*B*ee *M*artinez
developer
*front-end | wordpress | content*
*956 231 69 89 | @thebeeletter*
|
I was thinking of the files that have either the "Added exported content items for translation into Spanish. DC-306" or the "Added remaining files for translation. DC-306" description displayed with them. These files are in the original state, i.e. as they were exported from Kentico Cloud, before you've started the translation process. Some of them already have a Spanish variant in them. Like the 18689ab0-e5ff-4ca5-bd13-ae3b5997c2d9.json file. Some do not have the variant at all, like the 33389c83-dcfe-48f9-b0ee-f94aeabd2b08.json file. But, maybe I've misunderstood your intentions. Did you mean that the first sort of files (those that have a Spanish version) is OK and doesn't need any re-phrasing? And that the second sort of files could be just copy-pasted (because there is nothing to be translated)? Jan |
It’s all clear now! This files <https://github.com/Kentico/cloud-sample-app-react/blob/master/localization/> link and the clarifying notes about where translations are needed are what I was asking for.
Thanks!
B
|
Update: Instead of translating via .json files in https://github.com/Kentico/cloud-sample-app-react/blob/master/localization/ , @beemtz now does the translations/proofreadings in a dedicated content project in Kentico Cloud. The current state of the content project can be seen via a sample app at https://kentico-cloud-sample-app-translation-workspace.azurewebsites.net/es-es . After the translations are completed, the texts will be merged into the initial sample project that's built every time a new customer creates their Kentico Cloud account. Thank you @beemtz for your great translations! |
This is being handled separately. |
https://github.com/Kentico/cloud-sample-app-react/blob/master/localization/items.json contains a dump of existing untranslated content items.
We need to translate the "name", "description" and "value" fields to Spanish.
The text was updated successfully, but these errors were encountered: