Skip to content
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

Migrate translated content #37

Closed
crandmck opened this issue Sep 1, 2016 · 9 comments
Closed

Migrate translated content #37

crandmck opened this issue Sep 1, 2016 · 9 comments

Comments

@crandmck
Copy link
Contributor

crandmck commented Sep 1, 2016

In addition to the English content (which is mostly migrated--still some work to do, but maybe 80% done atm), we need to migrate community-translated content from Confluence to Jekyll/Markdown in the following languages:

NOTE: even though we have https://docs.strongloop.com/display/PTBR, there doesn't seem to be any content translated into Portuguese, so there's nothing to migrate.

Several caveats:

  • In every language, only part of the content has been translated, so we need to migrate only the translated articles.
  • For untranslated content, we should just have the English content.
  • Depending on the language, some/all titles in the sidebar navigation has been translated, and sometimes not.

ASAP, I will export the translated content, and (time permitting) run the migration script and check in the markdown files. If I run into problems, I may need to ask for help from @marc-ed-raffalli again :-)

I need to write up a short explanation about how people can contribute translations (for both existing and new languages). Cf #33.

@crandmck
Copy link
Contributor Author

crandmck commented Sep 7, 2016

I think we're ready for the final phase: QA / testing of the content.

@jaimeneeves
Copy link
Contributor

@crandmck what's the first step that I have to follow, because I'm going to do the translation to Portuguese?

@crandmck
Copy link
Contributor Author

crandmck commented Sep 7, 2016

Hi @dejaneves The first step is for me (with help from anyone who wants to contribute) to clean up the English content, since that's what you'll translate from. We're close to being "done" with that. Then, I'll create a section where you can translate the articles "in place" to Portuguese and I'll provide simple instructions.

It should just be a little longer... thanks for your patience!

@crandmck
Copy link
Contributor Author

crandmck commented Sep 23, 2016

OK, it turns out that there is also no existing translated content for French, in addition to Portuguese.

I imported the Russian and Japanese content, and created stub areas for French, Portuguese, and Korean.

I ran out of time to actually add the Korean content. But here's a zip with the converted files:
ko-export.zip

I created the Chinese "space" but ran into problems running the migration script on the Chinese content @marc-ed-raffalli. I'm attaching the zip file of the Confluence HTML export:

zh-Confluence-space-export-211432-851.html.zip

I realize the script was created for English content, but it worked reasonably well for Russian, Korean, and Japanese.

The error was:

...
Found invalid JSON/JS code tagged as js in file Installing-the-Oracle-connector_6094965.html
Found invalid JSON/JS code tagged as js in file Oracle-connector_6094964.html
/Users/rand/StrongLoop/Confluence-export/confluence-to-jekyll/src/content-conversion-flow/md-converter/converters/info-macros-conversion.js:27
      var iconClassName = node.querySelector('.aui-icon').classList.item(1)
                                                         ^
TypeError: Cannot read property 'classList' of null
    at Function.replacement (/Users/rand/StrongLoop/Confluence-export/confluence-to-jekyll/src/content-conversion-flow/md-converter/converters/info-macros-conversion.js:27:58)
    at process (/Users/rand/StrongLoop/Confluence-export/confluence-to-jekyll/node_modules/to-markdown/index.js:182:31)
    at toMarkdown (/Users/rand/StrongLoop/Confluence-export/confluence-to-jekyll/node_modules/to-markdown/index.js:216:5)
    at mdConverter (/Users/rand/StrongLoop/Confluence-export/confluence-to-jekyll/src/content-conversion-flow/md-converter/index.js:6:10)
    at module.exports (/Users/rand/StrongLoop/Confluence-export/confluence-to-jekyll/src/content-conversion-flow/steps/html-to-md.js:17:12)
    at nextTask (/Users/rand/StrongLoop/Confluence-export/confluence-to-jekyll/node_modules/async/dist/async.js:5021:18)
    at /Users/rand/StrongLoop/Confluence-export/confluence-to-jekyll/node_modules/async/dist/async.js:5015:17
    at /Users/rand/StrongLoop/Confluence-export/confluence-to-jekyll/node_modules/async/dist/async.js:339:31
    at /Users/rand/StrongLoop/Confluence-export/confluence-to-jekyll/node_modules/async/dist/async.js:847:20
    at module.exports (/Users/rand/StrongLoop/Confluence-export/confluence-to-jekyll/src/content-conversion-flow/steps/attachments-migration.js:46:3)

@crandmck
Copy link
Contributor Author

crandmck commented Sep 23, 2016

For instructions one what you need to do to use the exported/converted content, see Importing existing translations.

@marc-ed-raffalli
Copy link
Contributor

Hi @crandmck, the script should be language agnostic.
What I suspect is the markup has some differences, will check that out and send an MR for each

@marc-ed-raffalli
Copy link
Contributor

I created the MR #74

The root of the issue was the macro were assumed to all have an icon.
But in these pages, 7 had a macro without icon.

Also, fair to you @crandmck, the script has hard codded en, could be more agnostic ;)
I left the original file name when it contains chinese / special chars.

@nuba
Copy link

nuba commented Oct 15, 2016

Muito bom! Awesome! Really happy to see this up! The old wiki thing with the shared account and login workarounds wasn't really cutting it for a community-driven translation effort. Hope we'll get things going now! :)

@crandmck
Copy link
Contributor Author

I'm closing this issue since most of the existing content has been migrated. If there are any more questions or issues around translation, please just open a new issue... Thanks!

@crandmck crandmck removed the #tob label Nov 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants