User Manual - translations with transifex
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 1.3k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
Hi guys, sorry i've being off party for a long time. now just have a few bits of time and i see there's a need in some work.
I see that there is a GitBook solution for User Manual, but actually there is only 1 japan (chinese?) translation. knowing that there's about 200 people working with translations with many languages on transifex - can we just do the translation work with transifex ? i can't login to https://app.gitbook.com/@lmms
What we need is a base text.
I don't like when they ask me for phone on gitBook, just don't get why and i didn't see what's there and moving whole translation team on new engine... maybe it don't have a proper interface.
i think that nobody knows that it can be translated with GitBook and actually nobody knows how - it isn't mentioned on participate in translation page.
i think that user manual must be included with program in offline mode - if this is an issue - let's do it. just a pdf export can be enough to do and include in installation pkg.
another issue ? - i don't see how to change language on web site - there's no such menu.
oh and one more issue is about "translators list" in credits, because there is about 15 peoples in my team, but only coordinators are listed in "staff", i'd like this list to be little more wider at least with reviewers (i've moved few peoples to coordinators list, but it would be better to make it some other way) and maybe persons who made more than 20 edits or something, that was included in code or just became a base for translation.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository files, tests, or entry points. First split the requests—Transifex workflow, offline PDF/manual packaging, website language selection, and translator credits—and confirm which are in scope; done requires an agreed implementation plan for each accepted item.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation, localization
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100