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 Never rely on tolerance-based point equality for topology code 4c776d418
Sandro Santilli authored yesterday
Last commit in Weblate Translated reference_coverage using Weblate (French) af45bca00
Vincent Bre authored 3 weeks ago
Weblate repository https://weblate.osgeo.org/git/postgis/postgis/
File mask doc/po/*/using_postgis_dataman.xml.po
Translation file Download doc/po/fr/using_postgis_dataman.xml.po
Last change May 11, 2023, 3:21 p.m.
Last author Vincent Bre

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 532 11,466 80,218
Approved 0% 0 0% 0 0% 0
Waiting for review 100% 532 100% 11,466 100% 80,218
Translated 100% 532 100% 11,466 100% 80,218
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 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 3 changes 0 changes 0 changes 0 changes 174 changes 4 changes 2 changes 6 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 342 changes
Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May

Quick numbers

11,466
Hosted words
532
Hosted strings
100%
Translated
2
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
—
—
Hosted strings
—
+55%
Translated
—
+100%
Contributors
—
User avatar None

Resource update

postgis / using_postgis_dataman.xml — French

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

String updated in the repository

postgis / using_postgis_dataman.xml — French

&/&, ~==, @>>, and <<@, for 3-dimensional indexes.
&/&amp ;, ~==, @>>, et <<@, pour les index à 3 dimensions.
2 weeks ago
User avatar None

String updated in the repository

postgis / using_postgis_dataman.xml — French

<<, &<, &>, >>, <<|, &<|, |&>, |>>, &&, @>, <@, and ~=, for 2-dimensional indexes,
<&lt ;, &&lt ;, &>, >>, <<|, &<|, |&>, |>>, &&, @>, <@, et ~=, pour les index à 2 dimensions,
2 weeks ago
User avatar None

String updated in the repository

postgis / using_postgis_dataman.xml — French

When using the "&&" operator, you can specify either a BOX3D as the comparison feature or a GEOMETRY. When you specify a GEOMETRY, however, its bounding box will be used for the comparison.
Lorsque vous utilisez l'opérateur "&&amp ;", vous pouvez spécifier soit une BOX3D comme élément de comparaison, soit une GEOMETRY. Toutefois, lorsque vous spécifiez une GEOMETRY, c'est sa boîte de délimitation qui sera utilisée pour la comparaison.
2 weeks ago
User avatar None

Resource update

postgis / using_postgis_dataman.xml — French

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

String updated in the repository

postgis / using_postgis_dataman.xml — French

&/&, ~==, @>>, and <<@, for 3-dimensional indexes.
&/&amp ;, ~==, @>&gt ;, et <<@, pour les index à 3 dimensions.
3 weeks ago
User avatar None

String updated in the repository

postgis / using_postgis_dataman.xml — French

<<, &<, &>, >>, <<|, &<|, |&>, |>>, &&, @>, <@, and ~=, for 2-dimensional indexes,
<&lt ;, &&lt ;, &&gt ;, >&gt ;, <<|, &<|, |&&gt ;, |>&gt ;, &&amp ;, @&gt ;, <@, et ~=, pour les index à 2 dimensions,
3 weeks ago
User avatar vincentbre

New translation

postgis / using_postgis_dataman.xml — French

For more information see the Postgres manual section on <ulink url="https://www.postgresql.org/docs/current/runtime-config-query.html">Query Planning</ulink>.
Pour plus d'informations, voir la section du manuel Postgres sur <ulink url="https://www.postgresql.org/docs/current/runtime-config-query.html">Query Planning</ulink>.
3 weeks ago
User avatar vincentbre

New translation

postgis / using_postgis_dataman.xml — French

If <command>SET ENABLE_SEQSCAN TO OFF;</command> does not help your query, the query may be using a SQL construct that the Postgres planner is not yet able to optimize. It may be possible to rewrite the query in a way that the planner is able to handle. For example, a subquery with an inline SELECT may not produce an efficient plan, but could possibly be rewritten using a LATERAL JOIN.
Si la <command>SET ENABLE_SEQSCAN TO OFF;</command> n'aide pas votre requête, il se peut qu'elle utilise une construction SQL que le planificateur Postgres n'est pas encore en mesure d'optimiser. Il peut être possible de réécrire la requête de manière à ce que le planificateur soit en mesure de la traiter. Par exemple, une sous-requête avec un SELECT en ligne peut ne pas produire un plan efficace, mais peut être réécrite en utilisant un JOIN LATERAL.
3 weeks ago
User avatar vincentbre

New translation

postgis / using_postgis_dataman.xml — French

If <command>SET ENABLE_SEQSCAN TO OFF;</command> helps your query to run faster, your Postgres is likely not tuned for your hardware. If you find the planner wrong about the cost of sequential versus index scans try reducing the value of <varname>RANDOM_PAGE_COST</varname> in <code>postgresql.conf</code>, or use <command>SET RANDOM_PAGE_COST TO 1.1;</command>. The default value for <varname>RANDOM_PAGE_COST</varname> is 4.0. Try setting it to 1.1 (for SSD) or 2.0 (for fast magnetic disks). Decreasing the value makes the planner more likely to use index scans.
Si <command>SET ENABLE_SEQSCAN TO OFF;</command> aide votre requête à s'exécuter plus rapidement, votre Postgres n'est probablement pas adapté à votre matériel. Si vous trouvez que le planificateur se trompe sur le coût des balayages séquentiels par rapport aux balayages d'index, essayez de réduire la valeur de <varname>RANDOM_PAGE_COST</varname> dans <code>postgresql.conf</code>, ou utilisez <command>SET RANDOM_PAGE_COST TO 1.1;</command>. La valeur par défaut de <varname>RANDOM_PAGE_COST</varname> est 4.0. Essayez de la fixer à 1.1 (pour les disques SSD) ou à 2.0 (pour les disques magnétiques rapides). En diminuant la valeur, le planificateur est plus enclin à utiliser les balayages d'index.
3 weeks ago
Browse all translation changes