On Wed, Jan 09 2019, Ævar Arnfjörð Bjarmason wrote: > > I think a way to have early exposure of these to a lot more people > would be to have these on the git-scm.com site. Jeff knows more about > the build process there. > > I see the general completion of French & German is at ~10%, but > maybe there's some pages that are fully translated already? We could > then have some UI or git-scm.com that allows you to switch between > languages along with some general overview page per-language. Publishing on git-scm is on my TODO list. It' s a bit more difficult than updating the original manpages, because the translation process with po4a cannot be done in memory, which does not fit with the way the publishing is done directly from gitster/git repo on github into the database, plus the underlying data structure of the website needs to evolve to account for new languages (and Ruby on Rails is a special beast) . > > > Are the translations contributed through > https://hosted.weblate.org/projects/git-manpages/translations/ > something that license-wise (Signed-off-by etc.) we'd eventually be > able to upstream in git.git? I retained the same license as Git for the translation repo, to prevent future issues with integration of the result in other projects. Right now, there's no Signed-off-by line in Weblate issued commits. I opened an issue to have them added. Should this policy have been enforced from the start or is it too late for later inclusion in git.git? > > It would be great to eventually have something we can build as part > of our build process, so e.g. Debian can have git-man-de similar to > manpages-de now. I don't understand you remark. The point of the proposed patch is to allow to build and install the translated manpages from a working tree of git, by adding a checkout of git-manpages-l10n in a subdir of Documentation (note to self: propose a patch to document this). From this setup, generating proper localized manpage packages is perfectly doable. Am I missing anything?
