Overview

Project website postgis.net
Project maintainers User avatar komzpa User avatar cvvergara User avatar strk User avatar 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 using Weblate (French) 774abf9f7
Vincent Bre authored 2 weeks ago
Weblate repository https://weblate.osgeo.org/git/postgis/postgis/
File mask doc/po/*/administration.xml.po
Translation file Download doc/po/fr/administration.xml.po
Last change May 15, 2023, 2:54 p.m.
Last author Vincent Bre

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 88 1,987 14,568
Approved 0% 0 0% 0 0% 0
Waiting for review 100% 88 100% 1,987 100% 14,568
Translated 100% 88 100% 1,987 100% 14,568
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 37 changes 6 changes 0 changes 8 changes 0 changes 4 changes 0 changes 0 changes 0 changes
May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr

Quick numbers

1,987
Hosted words
88
Hosted strings
100%
Translated
2
Contributors
and previous 30 days

Trends of last 30 days

−4%
Hosted words
—
−6%
Hosted strings
—
+62%
Translated
—
+100%
Contributors
—
User avatar None

Resource update

postgis / administration.xml — French

The "doc/po/fr/administration.xml.po" file was changed. 5 days ago
User avatar None

Resource update

postgis / administration.xml — French

The "doc/po/fr/administration.xml.po" file was changed. 2 weeks ago
User avatar None

String updated in the repository

postgis / administration.xml — French

Version "&last_release_version;" of extension "postgis" is already installed
La version "&last_release_version ;" de l'extension "postgis" est déjà installée
2 weeks ago
User avatar None

String updated in the repository

postgis / administration.xml — French

No migration path defined for … to &last_release_version;
Pas de chemin de migration défini pour ... vers &last_release_version ;
2 weeks ago
User avatar vincentbre

New translation

postgis / administration.xml — French

psql -h localhost -p 5432 -U postgres -d newdb -f olddb-without-IGN.sql 2> errors.txt
psql -h localhost -p 5432 -U postgres -d newdb -f olddb-without-IGN.sql 2> errors.txt
2 weeks ago
User avatar vincentbre

New translation

postgis / administration.xml — French

In order to fix this you should copy your custom SRS to a SRID with a valid value (maybe in the 910000..910999 range), convert all your tables to the new srid (see <xref linkend="UpdateGeometrySRID"/>), delete the invalid entry from spatial_ref_sys and re-construct the check(s) with: <programlisting>ALTER TABLE spatial_ref_sys ADD CONSTRAINT spatial_ref_sys_srid_check check (srid &gt; 0 AND srid &lt; 999000 );</programlisting> <programlisting>ALTER TABLE spatial_ref_sys ADD PRIMARY KEY(srid));</programlisting> If you are upgrading an old database containing french <ulink url="https://en.wikipedia.org/wiki/Institut_g%C3%A9ographique_national"> IGN </ulink> cartography, you will have probably SRIDs out of range and you will see, when importing your database, issues like this : <programlisting> WARNING: SRID 310642222 converted to 999175 (in reserved zone)</programlisting> In this case, you can try following steps : first throw out completely the IGN from the sql which is resulting from postgis_restore.pl. So, after having run : <programlisting>perl utils/postgis_restore.pl "/somepath/olddb.backup" > olddb.sql</programlisting> run this command : <programlisting>grep -v IGNF olddb.sql > olddb-without-IGN.sql</programlisting> Create then your newdb, activate the required Postgis extensions, and insert properly the french system IGN with : <ulink url="https://raw.githubusercontent.com/Remi-C/IGN_spatial_ref_for_PostGIS/master/Put_IGN_SRS_into_Postgis.sql"> this script </ulink> After these operations, import your data :
Pour résoudre ce problème, vous devez copier votre SRS personnalisé dans un SRID avec une valeur valide (peut-être dans la plage 910000..910999), convertir toutes vos tables au nouveau SRID (voir <xref linkend="UpdateGeometrySRID"/>), supprimer l'entrée invalide de spatial_ref_sys et reconstruire le(s) contrôle(s) à l'aide de : <programlisting>ALTER TABLE spatial_ref_sys ADD CONSTRAINT spatial_ref_sys_srid_check check (srid &gt; 0 AND srid &lt; 999000 );</programlisting> <programlisting>ALTER TABLE spatial_ref_sys ADD PRIMARY KEY(srid));</programlisting> Si vous mettez à niveau une ancienne base de données contenant des <ulink url="https://en. wikipedia.org/wiki/Institut_g%C3%A9ographique_national"> IGN </ulink> cartographie française, vous aurez probablement des SRID hors plage et vous verrez, lors de l'importation de votre base de données, des problèmes comme celui-ci : <programlisting> WARNING : SRID 310642222 converted to 999175 (in reserved zone)</programlisting> Dans ce cas, vous pouvez essayer les étapes suivantes : d'abord supprimer complètement l'IGN du sql qui résulte de postgis_restore.pl. Ainsi, après avoir exécuté : <programlisting>perl utils/postgis_restore.pl "/somepath/olddb.backup" > olddb.sql</programlisting> lancer cette commande : <programlisting>grep -v IGNF olddb.sql > olddb-without-IGN.sql</programlisting> Créez ensuite votre newdb, activez les extensions Postgis nécessaires, et insérez correctement l'IGN du système français avec : <ulink url="https://raw.githubusercontent.com/Remi-C/IGN_spatial_ref_for_PostGIS/master/Put_IGN_SRS_into_Postgis.sql"> ce script </ulink> Après ces opérations, importez vos données :
2 weeks ago
User avatar vincentbre

New translation

postgis / administration.xml — French

Some custom records of spatial_ref_sys in dump file have an invalid SRID value. Valid SRID values are bigger than 0 and smaller than 999000. Values in the 999000.999999 range are reserved for internal use while values > 999999 can't be used at all. All your custom records with invalid SRIDs will be retained, with those > 999999 moved into the reserved range, but the spatial_ref_sys table would lose a check constraint guarding for that invariant to hold and possibly also its primary key ( when multiple invalid SRIDS get converted to the same reserved SRID value ).
Certains enregistrements personnalisés de spatial_ref_sys dans le fichier dump ont une valeur SRID invalide. Les valeurs SRID valides sont supérieures à 0 et inférieures à 999000. Les valeurs comprises entre 999000 et 999999 sont réservées à un usage interne, tandis que les valeurs supérieures à 999999 ne peuvent pas être utilisées. Tous vos enregistrements personnalisés avec des SRID invalides seront conservés, avec ceux > 999999 déplacés dans la plage réservée, mais la table spatial_ref_sys perdrait une contrainte de contrôle protégeant cet invariant et peut-être aussi sa clé primaire (lorsque plusieurs SRIDS invalides sont convertis en la même valeur SRID réservée).
2 weeks ago
User avatar vincentbre

New translation

postgis / administration.xml — French

Some of your views or functions make use of deprecated PostGIS objects. In order to fix this you may try loading <filename>legacy.sql</filename> script prior to restore or you'll have to restore to a version of PostGIS which still contains those objects and try a migration again after porting your code. If the <filename>legacy.sql</filename> way works for you, don't forget to fix your code to stop using deprecated functions and drop them loading <filename>uninstall_legacy.sql</filename>.
Certaines de vos vues ou fonctions utilisent des objets PostGIS obsolètes. Pour y remédier, vous pouvez essayer de charger le script <filename>legacy.sql</filename> avant la restauration ou vous devrez restaurer vers une version de PostGIS qui contient encore ces objets et réessayer une migration après le portage de votre code. Si la méthode <filename>legacy.sql</filename> fonctionne pour vous, n'oubliez pas de corriger votre code pour arrêter d'utiliser les fonctions dépréciées et de les supprimer en chargeant <filename>uninstall_legacy.sql</filename>.
2 weeks ago
User avatar vincentbre

New translation

postgis / administration.xml — French

Errors may arise in the following cases:
Des erreurs peuvent survenir dans les cas suivants :
2 weeks ago
User avatar vincentbre

New translation

postgis / administration.xml — French

perl utils/postgis_restore.pl "/somepath/olddb.backup" | psql -h localhost -p 5432 -U postgres newdb 2> errors.txt
perl utils/postgis_restore.pl "/somepath/olddb.backup" | psql -h localhost -p 5432 -U postgres newdb 2> errors.txt
2 weeks ago
Browse all translation changes