[postgis-devel] Docs broken for other languages

Mon Jan 30 13:00:16 PST 2017

Okay it seems the BR build is erroring out.  I think it built earlier before the latest commit by strk.

Strk you said they all built fine locally for you right?   So I guess maybe we don't have something set up right on Debbie.

Strange though that japan built okay http://postgis.net/docs/manual-dev/postgis-ja.html which is one I thought I would have problems with.

Es and IT also built okay – 

This is what I get for BR

Anyone know what this means:

/usr/bin/xsltproc --novalid ./xsl/postgis_aggs_mm.xml.xsl postgis-out.xml > postgis_aggs_mm.xml
installation.xml:568: parser error : Opening and ending tag mismatch: para line 565 and ulink
> para um exemplo de problema resolvido configurando com este. NOTA: que você n
 ^
installation.xml:568: parser error : Opening and ending tag mismatch: listitem line 564 and para
arregador GUI que ainda não está documentado e permanece experimental.  </para
                                                                               ^
installation.xml:569: parser error : Opening and ending tag mismatch: varlistentry line 559 and listitem
                 </listitem>
                            ^
installation.xml:570: parser error : Opening and ending tag mismatch: variablelist line 393 and varlistentry
               </varlistentry>
                              ^
installation.xml:583: parser error : Opening and ending tag mismatch: sect2 line 369 and variablelist
          </variablelist>
                         ^
installation.xml:607: parser error : Opening and ending tag mismatch: sect1 line 318 and sect2
        </sect2>
                ^
installation.xml:1465: parser error : Opening and ending tag mismatch: chapter line 2 and sect1
  </sect1>
          ^
installation.xml:1639: parser error : Opening and ending tag mismatch: para line 1634 and code
> onde  <filename
 ^
installation.xml:1641: parser error : Opening and ending tag mismatch: sect1 line 1624 and para
> é a pasta root para o seu pcre incluso e lista lib.</para>
                                                             ^
installation.xml:1684: parser error : chunk is not well balanced
        </sect1>
        ^
installation.xml:1684: parser error : chunk is not well balanced
        </sect1>
        ^
postgis-out.xml:210: parser error : Failure to process entity installation
  &installation;
                ^
postgis-out.xml:210: parser error : Entity 'installation' not defined
  &installation;
                ^
using_postgis_dataman.xml:547: parser error : Opening and ending tag mismatch: para line 544 and ulink
>, <ulink url="http://spatialreference.org/ref/epsg/4269/"
 ^
using_postgis_dataman.xml:553: parser error : Opening and ending tag mismatch: sect2 line 527 and para
TM  são as mais ideais para medição, mas só cobrem 6-graus regiões.  </para
                                                                               ^
using_postgis_dataman.xml:682: parser error : Opening and ending tag mismatch: sect1 line 511 and sect2
        </sect2>
                ^
using_postgis_dataman.xml:2118: parser error : Opening and ending tag mismatch: chapter line 2 and sect1
  </sect1>
          ^
using_postgis_dataman.xml:3060: parser error : chunk is not well balanced
</chapter>
^
using_postgis_dataman.xml:3060: parser error : chunk is not well balanced
</chapter>
^
postgis-out.xml:212: parser error : Failure to process entity using_postgis_dataman
  &using_postgis_dataman;
                         ^
postgis-out.xml:212: parser error : Entity 'using_postgis_dataman' not defined
  &using_postgis_dataman;
                         ^
using_raster_dataman.xml:28: parser error : Opening and ending tag mismatch: para line 25 and ulink
>. Por favor, note que o raster2pgsql python script  pode não funcionar com ver
 ^
using_raster_dataman.xml:29: parser error : Opening and ending tag mismatch: note line 24 and para
></note>
 ^
using_raster_dataman.xml:29: parser error : Opening and ending tag mismatch: sect2 line 13 and note
></note>
        ^
using_raster_dataman.xml:523: parser error : Opening and ending tag mismatch: sect1 line 5 and sect2
    </sect2>
            ^
using_raster_dataman.xml:562: parser error : Opening and ending tag mismatch: chapter line 2 and sect1
  </sect1>
          ^
using_raster_dataman.xml:1099: parser error : chunk is not well balanced
</chapter>
^
using_raster_dataman.xml:1099: parser error : chunk is not well balanced
</chapter>
^

From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of George Silva
Sent: Monday, January 30, 2017 11:39 AM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
Subject: Re: [postgis-devel] Docs broken for other languages

Regarding the README, I'll separate sometime for that.

Regarding the weblate/pootle thing: I need to confirm with my associates if we still can provide the server. The ideal thing is to talk to osgeo to see if they have a spare webserver for that. There are many projects that could use the same resource instead of using transifex. I'll take that to the osgeo list. If they provide the server, we can customize the auth, so it will look at osgeo's LDAP and provide some maintenance.

Now, for what I can see, the resources are pointing to svn-trunk.

@Regina, I took a look at the generated docs, and it looks like they are built from another branch, not svn-trunk. I can tell that because pt-br has the highest number of strings translated and a number of them are not translated.

Perhaps you generated the docs from the master? How are PostGIS branches organized these days btw?

Thanks!

On Mon, Jan 30, 2017 at 2:31 PM, Sandro Santilli <strk at kbt.io <mailto:strk at kbt.io> > wrote:

On Mon, Jan 30, 2017 at 08:31:39AM -0200, George Silva wrote:
> Thanks Regina.
>
> @strk: for what I know the docs are only updated on transifex when the
> changes hit the svn-trunk branch, correct?

George: you know Transifex better than I do, so please find out and
let us know :) --- note I'm still happy to switch from transifex
to weblate if you're up for championing that
(https://weblate.org/en/hosting/)

> Is there anything we can help in these proceedings?

Maybe improve doc/po/README with the recommended workflow
for updates, in both branches and trunk ?

--strk;
_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org <mailto:postgis-devel at lists.osgeo.org> 
https://lists.osgeo.org/mailman/listinfo/postgis-devel

-- 

George R. C. Silva
Sigma Geosistemas LTDA

----------------------------

http://www.sigmageosistemas.com.br/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20170130/d30931ed/attachment.html>