{"thread":{"id":"51276","subject":"Inclusion of translated git manpages into the packaging systems","startedAt":"2019-06-09T15:55:06Z","lastAt":"2019-06-11T20:37:48Z","messageCount":5,"participants":["Jean-Noël AVILA","Johannes Schindelin","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"376886","messageId":"1979608.xhrAu3A07H@cayenne","threadId":"51276","inReplyTo":null,"subject":"Inclusion of translated git manpages into the packaging systems","fromName":"Jean-Noël AVILA","fromEmail":"jn.avila@free.fr","sentAt":"2019-06-09T15:47:29Z","receivedAt":"2019-06-09T15:55:06Z","isPatch":false,"sender":{"key":"jn.avila@free.fr","avatar":"https://avatars.githubusercontent.com/u/156172?v=4"},"body":"Hi,\n\nI took on the task of creating a project for the translation of man-pages at \nhttps://github.com/jnavila/git-manpages-l10n\n\nUp to now, the translations have started for 3 languages:\n\n* German (2 pages)\n* Brazilian Portuguese (6 pages)\n* French (11pages)\n\nIn order to provide feedback to translators, it's time to have these pages \nincluded with the distributions of git. Right now the process of compilation \nof the man-pages is still a bit off-tree, because it relies on a recent version \nof po4a (v0.56) which has not yet reached most distros.\n\nI miss expertise in the process of packaging. Depending on the type of \ndistribution, the route to packaging might differ (for Mac OS and Windows, \nmaybe a direct inclusion, for Linux dists sister packages). That's why I need \nyour help to correctly perform this integration.\n\nThanks in advance,\n\nJean-Noël \n\n\n"},{"id":"376949","messageId":"nycvar.QRO.7.76.6.1906101906140.789@QRFXGBC-DHN364S.ybpnyqbznva","threadId":"51276","inReplyTo":"1979608.xhrAu3A07H@cayenne","subject":"Re: Inclusion of translated git manpages into the packaging systems","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2019-06-10T17:09:54Z","receivedAt":"2019-06-10T17:09:50Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Jean-Noël,\n\nOn Sun, 9 Jun 2019, Jean-Noël AVILA wrote:\n\n> I took on the task of creating a project for the translation of man-pages at\n> https://github.com/jnavila/git-manpages-l10n\n>\n> Up to now, the translations have started for 3 languages:\n>\n> * German (2 pages)\n> * Brazilian Portuguese (6 pages)\n> * French (11pages)\n\nNice!!!\n\n> In order to provide feedback to translators, it's time to have these\n> pages included with the distributions of git. Right now the process of\n> compilation of the man-pages is still a bit off-tree, because it relies\n> on a recent version of po4a (v0.56) which has not yet reached most\n> distros.\n\nMaybe there is a way to skip the Makefile task when a too-old po4a is\ndetected, with a warning?\n\n> I miss expertise in the process of packaging. Depending on the type of\n> distribution, the route to packaging might differ (for Mac OS and\n> Windows, maybe a direct inclusion, for Linux dists sister packages).\n> That's why I need your help to correctly perform this integration.\n\nHistorically, Git for Windows punts on translations, excluding any\nnon-en-US documentation (to save on bandwidth for the installer, which did\ngrow from <30MB to 44MB in the last four years alone).\n\nThere were a couple of motions to change that (maybe in the form of add-on\npackages/installers, maybe in the form of a \"full\" installer), but nothing\ncame of it so far.\n\nTherefore, as far as Windows is concerned, I hate to admit that my answer\nis \"don't worry for now, we only include US-English documentation\nanyway\"... :-(\n\nCiao,\nDscho\n"},{"id":"376964","messageId":"1835964.yutTd2aTbA@cayenne","threadId":"51276","inReplyTo":"nycvar.QRO.7.76.6.1906101906140.789@QRFXGBC-DHN364S.ybpnyqbznva","subject":"Re: Inclusion of translated git manpages into the packaging systems","fromName":"Jean-Noël AVILA","fromEmail":"jn.avila@free.fr","sentAt":"2019-06-10T19:02:17Z","receivedAt":"2019-06-10T19:02:25Z","isPatch":false,"sender":{"key":"jn.avila@free.fr","avatar":"https://avatars.githubusercontent.com/u/156172?v=4"},"body":"On Monday, 10 June 2019 19:09:54 CEST Johannes Schindelin wrote:\n> Hi Jean-Noël,\n> \n> On Sun, 9 Jun 2019, Jean-Noël AVILA wrote:\n> \n> > I took on the task of creating a project for the translation of man-pages \nat\n> > https://github.com/jnavila/git-manpages-l10n\n> >\n> > Up to now, the translations have started for 3 languages:\n> >\n> > * German (2 pages)\n> > * Brazilian Portuguese (6 pages)\n> > * French (11pages)\n> \n> Nice!!!\n> \n> > In order to provide feedback to translators, it's time to have these\n> > pages included with the distributions of git. Right now the process of\n> > compilation of the man-pages is still a bit off-tree, because it relies\n> > on a recent version of po4a (v0.56) which has not yet reached most\n> > distros.\n> \n> Maybe there is a way to skip the Makefile task when a too-old po4a is\n> detected, with a warning?\n\nThe project is provided with a script that downloads the correct version of \npo4a from the root repo (this is needed for ci).\n\nI can provide an archive comprising the precompiled manpages so that packagers \ndon't need to mess up with po4a.\n\n> \n> > I miss expertise in the process of packaging. Depending on the type of\n> > distribution, the route to packaging might differ (for Mac OS and\n> > Windows, maybe a direct inclusion, for Linux dists sister packages).\n> > That's why I need your help to correctly perform this integration.\n> \n> Historically, Git for Windows punts on translations, excluding any\n> non-en-US documentation (to save on bandwidth for the installer, which did\n> grow from <30MB to 44MB in the last four years alone).\n\nIt might not be the correct argument for now, but a tgz of the manpages \npresently weights 230kB.\n\n> \n> There were a couple of motions to change that (maybe in the form of add-on\n> packages/installers, maybe in the form of a \"full\" installer), but nothing\n> came of it so far.\n\nIf there's any chance to get this move alive, who should I refer to? \nOtherwise, where can an additional package be built?\n\n> \n> Therefore, as far as Windows is concerned, I hate to admit that my answer\n> is \"don't worry for now, we only include US-English documentation\n> anyway\"... :-(\n> \n> Ciao,\n> Dscho\n\n\n\n\n"},{"id":"376965","messageId":"xmqqmuipmett.fsf@gitster-ct.c.googlers.com","threadId":"51276","inReplyTo":"1835964.yutTd2aTbA@cayenne","subject":"Re: Inclusion of translated git manpages into the packaging systems","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2019-06-10T19:15:58Z","receivedAt":"2019-06-10T19:16:04Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jean-Noël AVILA <jn.avila@free.fr> writes:\n\n> I can provide an archive comprising the precompiled manpages so that packagers \n> don't need to mess up with po4a.\n\nThat's an interesting thing to hear---if this effort eventually\nrelieves me from having to supply preformatted manpages and HTML\ndocs (after all, en/C is just one more locale from your point of\nview, right?), that would be an excellent news for me ;-)\n\nThe last-mile packagers that are directly facing end-users would be\nhappy to have a place (or two) that they can pull the pre-built docs\nfor these locales from, and they would not particularly care where\nexactly those places are, I think.\n"},{"id":"377028","messageId":"7802960.VzbTMjdsy5@cayenne","threadId":"51276","inReplyTo":"xmqqmuipmett.fsf@gitster-ct.c.googlers.com","subject":"Re: Inclusion of translated git manpages into the packaging systems","fromName":"Jean-Noël AVILA","fromEmail":"jn.avila@free.fr","sentAt":"2019-06-11T20:37:39Z","receivedAt":"2019-06-11T20:37:48Z","isPatch":false,"sender":{"key":"jn.avila@free.fr","avatar":"https://avatars.githubusercontent.com/u/156172?v=4"},"body":"On Monday, 10 June 2019 21:15:58 CEST Junio C Hamano wrote:\n> Jean-Noël AVILA <jn.avila@free.fr> writes:\n> \n> > I can provide an archive comprising the precompiled manpages so that \npackagers \n> > don't need to mess up with po4a.\n> \n> That's an interesting thing to hear---if this effort eventually\n> relieves me from having to supply preformatted manpages and HTML\n> docs (after all, en/C is just one more locale from your point of\n> view, right?), that would be an excellent news for me ;-)\n\nI wasn't expecting this one ;-D In fact, the translation project is different \nin two points:\n\n * Not all the sources have been copied; only sources for some manpages\n * the en version is the source for translation. It's not compiled (why \nbother? it's already done in the main repo).\n\n> \n> The last-mile packagers that are directly facing end-users would be\n> happy to have a place (or two) that they can pull the pre-built docs\n> for these locales from, and they would not particularly care where\n> exactly those places are, I think.\n\nBTW, who is using the preformatted docs? If it's useful to anybody to have \naccess to the compound of en + translated docs, such repo can be set up.\n\nPlease note that Johannes clearly stated that git-for-windows cannot afford \nmore weight, so English only manpages are still required.\n\n\n\n\n"}]}