Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#25077 closed Uncategorized (invalid)

Named links in the documentation it is impossible to translate into other languages.

Reported by: Grigoriy Kramarenko Owned by: nobody
Component: Documentation Version: 1.8
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

For Russian-speaking users, there is a translation of the Django documentation. Working on it for a few people. Periodically translations are synchronize with upstream. And there is one, but the big problem with the translation links in the documentation.

Example:

Although you can use Django without a database, it comes with an
`object-relational mapper`_ in which you describe your database layout in Python
code.

.. _object-relational mapper: http://en.wikipedia.org/wiki/Object-relational_mapping

If translate text link object-relational mapper in the paragraph, then in some versions of shpinx such links are crumbling.

Safer work anonymous links (In the file intro/contributing.txt it's done that way):

Although you can use Django without a database, it comes with an
`object-relational mapper`__ in which you describe your database layout in Python
code.

__ http://en.wikipedia.org/wiki/Object-relational_mapping

It certainly does not concern slug links, such as:

`link-to-other-page`_ and `translated link to page <link-to-page-2>`_

Might be worth globally in all of the original documentation named links to replace to anonymous?

Thanks.

Change History (5)

comment:1 by Tim Graham, 9 years ago

Maybe you'd like to contribute to the official effort to translate the documentation rather than maintain a fork? It seems this problem doesn't exist in our workflow (checked French translation).

comment:2 by Grigoriy Kramarenko, 9 years ago

I see several reasons why not everyone wants to work with Transifex.

  1. Don't see the translated files in docs/.
  2. How then to build documentation on our language with the used of shpinx for yourself?
  3. One big file translate on the entire section is not convenient. It is not clear what part of the documentation string is translated. The same string in a different context most likely must be translated to another phraseological form.

Our translations can be safely would be to pour (using git) to the upstream of Django docs.
It has already made 76% far fewer people than 12% on Transifex.

Last edited 9 years ago by Grigoriy Kramarenko (previous) (diff)

comment:3 by Tim Graham, 9 years ago

Resolution: invalid
Status: newclosed

comment:4 by Tim Graham, 9 years ago

Sorry, but I don't think it's really a sustainable solution. For example, enforcing "no named links" in new pull requests will be annoying.

comment:5 by Claude Paroz, 9 years ago

@djbaldey Feel free to discuss documentation translation on django-i18n mailing list.
https://groups.google.com/forum/#!forum/django-i18n

Note: See TracTickets for help on using tickets.
Back to Top