postgis_branch_32/faq_raster — German @ OSGeo Weblate

Translation status

73	Strings		83%	Browse Translate
1,809	Words		70%	Browse Translate

Strings status

73	All strings — 1,809 words	Browse Translate Zen
61	Translated strings — 1,283 words	Browse Translate Zen
12	Unfinished strings — 526 words	Browse Translate Zen
3	Untranslated strings — 111 words	Browse Translate Zen
9	Strings marked for edit — 415 words	Browse Translate Zen
12	Unfinished strings without suggestions — 526 words	Browse Translate Zen
8	Strings with any failing checks — 161 words	Browse Translate Zen
5	Translated strings with any failing checks — 70 words	Browse Translate Zen
1	Failing check: Unchanged translation — 1 word	Browse Translate Zen
2	Failing check: Double space — 47 words	Browse Translate Zen
2	Failing check: Mismatched full stop — 51 words	Browse Translate Zen
1	Failing check: Mismatched colon — 6 words	Browse Translate Zen
2	Failing check: XML markup — 56 words	Browse Translate Zen

Other components

Component	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
reference_troubleshooting	0%	26	407	3,121	26	2	21	0

reference_bbox	0%	117	1,991	19,058	117	7	31	0

reference_overlay	0%	143	2,782	24,240	143	3	11	0

reference_version	0%	88	709	8,318	88	1	6	0

database_tuning	0%	33	543	3,893	33	0	1	0

reference_cluster	0%	55	1,131	9,962	55	1	5	0

using_postgis_query	0%	109	2,146	16,760	109	0	4	0

reference_relationship	0%	273	5,065	46,644	273	6	46	0

reference_srs	0%	54	978	8,949	54	3	12	0

reference_validation	0%	68	1,270	11,073	68	4	8	0

Browse all components

Overview

Project website	postgis.net
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	stable-3.2
Last remote commit	Push to 3.2.6dev milestone `6e2c5206d` Regina Obe authored yesterday
Weblate repository	`https://weblate.osgeo.org/git/postgis_branch_32/postgis/`
File mask	`doc/po/*/faq_raster.xml.po`
Translation file	Download `doc/po/de/faq_raster.xml.po`
Last change	None
Last author	None

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		73		1,809		13,471
Translated	83%	61	70%	1,283	71%	9,611
Needs editing	12%	9	22%	415	22%	3,083
Read-only	0%	0	0%	0	0%	0
Failing checks	10%	8	8%	161	8%	1,087
Strings with suggestions	0%	0	0%	0	0%	0
Untranslated strings	4%	3	6%	111	5%	777

Last 12 months Previous

Activity in last 12 months


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

Quick numbers

1,809

Hosted words

Hosted strings

83%

Translated

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

—

Hosted strings

—

Translated

—

Contributors

—

None New strings to translate postgis_branch_32 / faq_raster — German	12 new strings to translate appeared to the translation. a year ago
None Resource update postgis_branch_32 / faq_raster — German	File `doc/po/de/faq_raster.xml.po` was added. a year ago
None String updated in the repository postgis_branch_32 / faq_raster — German	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"/>. German 380 characters edited Current translation Translated Seit PostGIS 2.1.3 und 2.0.5 sind alle GDAL Treiber und out-db Raster aus Sicherheitsgründen standardmäßig deaktiviert. Die Release Notes sind unter <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>. Um bestimmte oder alle Treiber und out-db Unterstützung zu aktivieren, siehe <xref linkend="install_short_version"/>. a year ago
None String updated in the repository postgis_branch_32 / faq_raster — German	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. German 339 characters edited Current translation Translated Ich erhalte die Fehlermeldung <code>ERROR: RASTER_fromGDALRaster: Could not open bytea with GDAL. Check that the bytea is of a GDAL supported format.</code> wenn ich ST_FromGDALRaster verwende, oder <code>ERROR: rt_raster_to_gdal: Could not load the output GDAL driver</code> wenn Ich ST_AsPNG oder andere Rastereingabefunktionen verwende. a year ago
None String updated in the repository postgis_branch_32 / faq_raster — German	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> German 170 characters edited Current translation Translated Mörderische Einzelheiten zu diesem Themadetails finden sich unter <ulink url="http://trac.osgeo.org/postgis/ticket/2209">http://trac.osgeo.org/postgis/ticket/2209</ulink> a year ago
None String updated in the repository postgis_branch_32 / faq_raster — German	English export PGCLIENTENCODING=UTF8 German 28 characters edited Current translation Translated export PGCLIENTENCODING=UTF8 a year ago
None String updated in the repository postgis_branch_32 / faq_raster — German	English If you are on Unix/Linux German 38 characters edited Current translation Translated Falls Sie sich auf Unix/Linux befinden a year ago
None String updated in the repository postgis_branch_32 / faq_raster — German	English set PGCLIENTENCODING=UTF8 German 25 characters edited Current translation Translated set PGCLIENTENCODING=UTF8 a year ago
None String updated in the repository postgis_branch_32 / faq_raster — German	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: German 278 characters edited Current translation Translated Um dieses Problem zu umgehen, können Sie während des Ladens sicherstellen, dass die Zeichenkodierung für den Client und für die Datenbank die gleiche ist. Sie können dies durch ein explizites Setzen der Zeichenkodierung in Ihrem Ladeskript erreichen. Zum Beispiel unter Windows: a year ago
None String updated in the repository postgis_branch_32 / faq_raster — German	English This generally happens if for example you have your database in UTF8, but to support windows apps, you have the client encoding set to <code>WIN1252</code>. German 192 characters edited Current translation Translated Dies passiert üblicherweise, wenn die Datenbank z.B. in UTF8 vorliegt, aber die Zeichenkodierung für die Clients auf <code>WIN1252</code> gesetzt ist, um Windows Applikationen zu unterstützen. a year ago

Browse all translation changes

Quick downloads

73	File in original format as translated in the repository	gettext PO file
73	All strings, converted files enriched with comments; suitable for offline translation	CSV	gettext MO	gettext PO	TBX	TMX	XLIFF 1.1 with gettext extensions	XLIFF 1.1	XLSX
12	Unfinished strings, converted files enriched with comments; suitable for offline translation	CSV	gettext MO	gettext PO	TBX	TMX	XLIFF 1.1 with gettext extensions	XLIFF 1.1	XLSX

Customize download

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>=2023-04-30 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-30 AND state:<=needs-editing`	Add