postgis/faq_raster.xml @ OSGeo Weblate

Language	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
English		0	0	0	0	24	0	0

French		0	0	0	0	0	0	0

German	83%	12	526	3,860	3	8	0	0

Italian	50%	36	1,285	9,872	33	2	0	0

Japanese		0	0	0	0	0	0	0

Korean	79%	15	659	4,849	8	10	0	0

Polish	0%	73	1,809	13,471	73	0	0	0

Portuguese (Brazil)	79%	15	659	4,849	8	4	0	0

Russian	0%	73	1,809	13,471	73	0	0	0

Spanish	79%	15	659	4,849	8	8	0	0

Please sign in to see the alerts.

Overview

Project website	postgis.net
Project maintainers	komzpa cvvergara strk robe
Translation process	Translations can be made directly. Translation suggestions can be made. Any authenticated user can contribute. The translation uses bilingual files.
Source code repository	`https://git.osgeo.org/gitea/postgis/postgis.git`
Repository branch	master
Last remote commit	Show obtained output on failure, in oriented_envelope test `36fcdd626` Sandro Santilli authored yesterday
Last commit in Weblate	Translated reference_coverage using Weblate (French) `af45bca00` Vincent Bre authored 2 weeks ago
Weblate repository	`https://weblate.osgeo.org/git/postgis/postgis/`
File mask	`doc/po/*/faq_raster.xml.po`

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		730		18,090		134,710
Source		73		1,809		13,471
Approved	0%	0	0%	0	0%	0
Waiting for review	57%	418	49%	8,875	49%	66,018
Translated	67%	491	59%	10,684	59%	79,489
Needs editing	4%	33	8%	1,568	8%	11,816
Read-only	10%	73	10%	1,809	10%	13,471
Failing checks	7%	56	9%	1,666	9%	12,814
Strings with suggestions	0%	0	0%	0	0%	0
Untranslated strings	28%	206	32%	5,838	32%	43,405

Last 12 months Previous

Activity in last 12 months


May	Jun	Jul	Aug	Sep	Oct	Nov	Dec	Jan	Feb	Mar	Apr

Quick numbers

18,090

Hosted words

730

Hosted strings

67%

Translated

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

—

Hosted strings

—

+6%

Translated

—

+100%

Contributors

—

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>=2023-04-29 AND NOT changed_by:anonymous`	Add
Translated strings	`state:>=translated`	Add
Strings with comments	`has:comment`	Add
Strings with any failing checks	`has:check`	Add
Strings with suggestions from others	`has:suggestion AND NOT suggestion_author:anonymous`	Add
Approved strings with suggestions	`state:approved AND has:suggestion`	Add
All untranslated strings added the past month	`added:>=2023-04-29 AND state:<=needs-editing`	Add
Translated strings in a certain language	`is:translated AND language:en`	Add

None Component unlocked postgis / faq_raster.xml	Fixing an alert automatically unlocked the component. 12 days ago
None Component locked postgis / faq_raster.xml	The component was automatically locked because of an alert. 13 days ago
None New alert postgis / faq_raster.xml	Could not update the repository. 13 days ago
vincentbre New translation postgis / faq_raster.xml — French	English As of PostGIS 2.1.3 and 2.0.5, a security change was made to by default disable all GDAL drivers and out of db rasters. The release notes are at <ulink url="http://postgis.net/2014/05/19/postgis-2.0.6_and_2.1.3">PostGIS 2.0.6, 2.1.3 security release</ulink>. In order to reenable specific drivers or all drivers and reenable out of database support, refer to <xref linkend="install_short_version"/>. French 476 characters edited Current translation Translated À partir de PostGIS 2.1.3 et 2.0.5, un changement de sécurité a été effectué pour désactiver par défaut tous les drivers GDAL et les rasters hors db. Les notes de version se trouvent à <ulink url="http://postgis.net/2014/05/19/postgis-2.0.6_and_2.1.3">PostGIS 2.0.6, 2.1.3 security release</ulink>. Pour réactiver des drivers spécifiques ou tous les drivers et réactiver la prise en charge de la sortie de la base de données, consultez <xref linkend="install_short_version"/>. 2 weeks ago
vincentbre New translation postgis / faq_raster.xml — French	English I'm getting error <code>ERROR: RASTER_fromGDALRaster: Could not open bytea with GDAL. Check that the bytea is of a GDAL supported format.</code> when using ST_FromGDALRaster or <code>ERROR: rt_raster_to_gdal: Could not load the output GDAL driver</code> when trying to use ST_AsPNG or other raster input functions. French 354 characters edited Current translation Translated Je reçois l'erreur suivante <code>ERROR : RASTER_fromGDALRaster : Could not open bytea with GDAL. Check that the bytea is of a GDAL supported format.</code> lors de l'utilisation de ST_FromGDALRaster ou <code>ERROR : rt_raster_to_gdal : Could not load the output GDAL driver</code> lors de l'utilisation de ST_AsPNG ou d'autres fonctions d'entrée raster. 2 weeks ago
vincentbre New translation postgis / faq_raster.xml — French	English Gory details of this issue are detailed in <ulink url="http://trac.osgeo.org/postgis/ticket/2209">http://trac.osgeo.org/postgis/ticket/2209</ulink> French 155 characters edited Current translation Translated Les détails de cette question sont détaillés dans <ulink url="http://trac.osgeo.org/postgis/ticket/2209">http://trac.osgeo.org/postgis/ticket/2209</ulink>. 2 weeks ago
vincentbre New translation postgis / faq_raster.xml — French	English export PGCLIENTENCODING=UTF8 French 28 characters edited Current translation Translated export PGCLIENTENCODING=UTF8 2 weeks ago
vincentbre New translation postgis / faq_raster.xml — French	English If you are on Unix/Linux French 28 characters edited Current translation Translated Si vous êtes sous Unix/Linux 2 weeks ago
vincentbre New translation postgis / faq_raster.xml — French	English set PGCLIENTENCODING=UTF8 French 25 characters edited Current translation Translated set PGCLIENTENCODING=UTF8 2 weeks ago
vincentbre New translation postgis / faq_raster.xml — French	English To work around this make sure the client encoding is the same as your database encoding during load. You can do this by explicitly setting the encoding in your load script. Example, if you are on windows: French 268 characters edited Current translation Translated Pour contourner ce problème, assurez-vous que l'encodage du client est le même que celui de votre base de données lors du chargement. Vous pouvez le faire en définissant explicitement l'encodage dans votre script de chargement. Par exemple, si vous êtes sous Windows : 2 weeks ago

Browse all component changes