I suggest you ...

Context of translation string could link directly to Github filename+line number for true context

This is in direct relationship to the followin feature being supported in crowdin: https://crowdin.uservoice.com/forums/31787-collaborative-translation-tool/suggestions/10694856-add-to-context-source-file-info-for-ts-files

It would allow the translator to directly press on the Context filename:line# and be linked to the exact filename:line# on Github

150 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Kunda shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    4 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Matt commented  ·   ·  Flag as inappropriate

        I have the opposite problem - I'd like to be able to link from the page to be translated as published, to the equivalent on CrowdIn. I know the source filename, and the current language, but I can't construct a URL that links to CrowdIn, as the pages have URLs of the form:

        https://crowdin.com/translate/project-name/213/en-zhcn

        The directories do have a suitable URL: https://crowdin.com/project/project-name/zh-CN#/path/to/directory, so it would be great if this could be extended to files.

        If I should post this as a separate suggestion, please let me know.

      • Kunda commented  ·   ·  Flag as inappropriate

        Andriy Poznakhovskyy, I'm following up. So this function would of course be more for open source projects that have public repos on Github/Gitlab. The way you could avoid 404s is have the feature disabled by default in the project settings and only the admin can enable it, also maybe it would be for open source projects solely ?

      • AdminAndriy Poznakhovskyy (Head of Customer Success, Crowdin) commented  ·   ·  Flag as inappropriate

        Kunda, can you please tell us the main advantage of such functionality? What should happen after you switch from Crowdin to GitHub? It's just for checking whether translation was exported fine?

        Commonly repos are private, so you translators don't have a direct access there. They might see 404 page quite frequently

      • Kunda commented  ·   ·  Flag as inappropriate

        It doesn't have to be limited to github, it could be used with gitlab or atlassian... etc...

      Feedback and Knowledge Base