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

Mark down input translation issue - Guidance text inside code/code blocks is not translated #10132

Closed
2 tasks done
Kavithay123 opened this issue Oct 10, 2023 · 3 comments
Closed
2 tasks done
Labels
enhancement Adding or requesting a new feature. translate-toolkit Issues which need to be fixed in the translate-toolkit wontfix Nobody will work on this.

Comments

@Kavithay123
Copy link

Kavithay123 commented Oct 10, 2023

Describe the issue

Guidance text inside the code block content is not translated. Please find below source content and translated content.

Source Content:

**Network configuration**

All machines in our scenario are configured to use DNS and all of them have internet access. The initial entry point is nginx.example.com, which in our case can be reached from the internet. Your NGINX might reside behind a load balancer instead. To let the machines interoperate properly, consider the following inbound ports to be opened on your firewall:
    
    -   connections.internal.example.com:
        -   443 from nginx.example.com
        -   443 from cpmaster.internal.example.com
    -   cpmaster.internal.example.com:
        -   30301 from connections.internal.example.com \(Customizer\)
        -   30301 from nginx.example.com \(Customizer\)
        -   30098 from connections.internal.example.com \(Elasticsearch 7 – Connections 7 only\)
        -   30099 from connections.internal.example.com \(OpenSearch – Connections 7 or 8, Elasticsearch 5 – Connections 6.5 only\)
        -   32080 from connections.internal.example.com \(Ingress Controller\)
        -   31810 from connections.internal.example.com \(Microsoft Outlook add-in – Connections 7 only\)
    -   nginx.example.com:
        -   443 from everywhere
        -   80 from everywhere \(in case you plan to redirect to 443 and no load balancer does this job\)

Translated content screenshot:
image

I already tried

  • I've read and searched the documentation.
  • I've searched for similar issues in this repository.

Steps to reproduce the behavior

  1. Go to Weblate site, create new project and component
  2. Upload the markdown input file (source content is provided in the Issue Description)
  3. Translate the input file
  4. Notice the guidance text from code block is not translated (provided the screenshot in the Issue Description)

Expected behavior

No response

Screenshots

No response

Exception traceback

No response

How do you run Weblate?

weblate.org service

Weblate versions

No response

Weblate deploy checks

No response

Additional context

No response

@nijel nijel added enhancement Adding or requesting a new feature. translate-toolkit Issues which need to be fixed in the translate-toolkit labels Oct 10, 2023
@github-actions
Copy link

The issue you've reported needs to be addressed in the translate-toolkit. Please file the issue there, and include links to any relevant specifications about the formats (if applicable).

@nijel nijel added the wontfix Nobody will work on this. label Oct 10, 2023
@nijel
Copy link
Member

nijel commented Oct 10, 2023

Duplicate of translate/translate#5048

@nijel nijel marked this as a duplicate of translate/translate#5048 Oct 10, 2023
@nijel nijel closed this as not planned Won't fix, can't repro, duplicate, stale Oct 10, 2023
@Kavithay123
Copy link
Author

Thanks Michal for your quick response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Adding or requesting a new feature. translate-toolkit Issues which need to be fixed in the translate-toolkit wontfix Nobody will work on this.
Projects
None yet
Development

No branches or pull requests

2 participants