Translation status

5,756 Strings 100%
Browse Translate
104,656 Words 100%
745,546 Characters 100%

Strings status

Strings Words Characters
5,756 104,656 745,546
All strings Browse Translate Zen
142 2,368 17,425
Approved strings Browse Translate Zen
5,756 104,656 745,546
Translated strings Browse Translate Zen
5,614 102,288 728,121
Strings waiting for review Browse Translate Zen
626 9,562 69,431
Strings with any failing checks Browse Translate Zen
626 9,562 69,431
Translated strings with any failing checks Browse Translate Zen
230 758 6,147
Translated strings with dismissed checks Browse Translate Zen
167 569 5,408
Failing check: Unchanged translation Browse Translate Zen
430 8,013 56,346
Failing check: Mismatched full stop Browse Translate Zen
34 1,025 8,146
Failing check: XML markup Browse Translate Zen
151 305 2,200
Strings with comments Browse Translate Zen
5,756 104,656 745,546
Strings without a label Browse Translate Zen

Other components

Component Approved Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Glossary Glossary 77% 0 0 0 0 0 0 0
Browse all components

Overview

Project website postgis.net
Project maintainers User avatar strk User avatar komzpa User avatar cvvergara User avatar robe
Translation license Creative Commons Attribution Share Alike 3.0 Unported
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Translations are reviewed by dedicated reviewers.
  • 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 BRIN SUPPORT Upgrade 2845d3f3
Regina Obe authored 6 days ago
Last commit in Weblate BRIN SUPPORT Upgrade 2845d3f3
Regina Obe authored 6 days ago
Weblate repository https://weblate.osgeo.org/git/postgis/postgis-manual/
File mask doc/po/*/postgis-manual.po
Translation file Download doc/po/ja/postgis-manual.po
Last change Jan. 7, 2025, 3:47 a.m.
Last author None
11 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 5,756 104,656 745,546
Approved 2% 142 2% 2,368 2% 17,425
Waiting for review 97% 5,614 97% 102,288 97% 728,121
Translated 100% 5,756 100% 104,656 100% 745,546
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 10% 626 9% 9,562 9% 69,431
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 20 changes 0 changes 0 changes 0 changes 179 changes 0 changes 0 changes 0 changes 4 changes 0 changes 84 changes 0 changes 315 changes 0 changes 65 changes 6,033 changes 64 changes 78 changes 4 changes 286 changes 210 changes 156 changes 67 changes
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

Quick numbers

104 k
Hosted words
5,756
Hosted strings
100%
Translated
2
Contributors
and previous 30 days

Trends of last 30 days

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

Changes committed

  1. postgis
  2. PostGIS Manual
  3. Japanese
Changes committed 11 days ago
User avatar yellow73

Translation approved

  1. postgis
  2. PostGIS Manual
  3. Japanese
Create then your newdb, activate the required Postgis extensions, and insert properly the french system IGN with : <link xlink:href="https://raw.githubusercontent.com/Remi-C/IGN_spatial_ref_for_PostGIS/master/Put_IGN_SRS_into_Postgis.sql"> this script </link> After these operations, import your data :
その後、新しいデータベースを生成し、必要なPostGISエクステンションを有効化して、<link xlink:href="https://raw.githubusercontent.com/Remi-C/IGN_spatial_ref_for_PostGIS/master/Put_IGN_SRS_into_Postgis.sql">このスクリプト</link>で確実にフランスIGNの系を挿入します。これらの処理の後、次のようにデータのインポートを行います:
11 days ago
User avatar yellow73

Translation approved

  1. postgis
  2. PostGIS Manual
  3. Japanese
run this command :
次のコマンドを実行します:
11 days ago
User avatar yellow73

Translation approved

  1. postgis
  2. PostGIS Manual
  3. Japanese
In this case, you can try following steps : first throw out completely the IGN from the sql which is resulting from postgis_restore. So, after having run :
この場合には、次のステップを試すことができます。最初にpostgis_restoreから出たIGNをSQLから完全に破棄します。そのために次のコマンドを実行します:
11 days ago
User avatar yellow73

Translation approved

  1. postgis
  2. PostGIS Manual
  3. Japanese
If you are upgrading an old database containing french <link xlink:href="https://en.wikipedia.org/wiki/Institut_g%C3%A9ographique_national"> IGN </link> cartography, you will have probably SRIDs out of range and you will see, when importing your database, issues like this :
フランス<link xlink:href="https://en.wikipedia.org/wiki/Institut_g%C3%A9ographique_national">IGN</link>地図を含む古いデータベースをアップグレードする場合には、おそらくSRIDが範囲外になり、データベースのインポート時に次のような問題に遭遇します:
11 days ago
User avatar yellow73

Translation approved

  1. postgis
  2. PostGIS Manual
  3. Japanese
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:
これを修正するために、独自のSRSを妥当な値 (910000..910999の範囲)のSRIDに複写し、全てのテーブルを新しいSRIDに変更 (<xref linkend="UpdateGeometrySRID"/>)して、spatial_ref_sysから不正なエントリを削除します。そして、次のようにチェック制約を再構築します:
11 days ago
User avatar yellow73

Translation changed

  1. postgis
  2. PostGIS Manual
  3. Japanese
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 &gt; 999999 can't be used at all. All your custom records with invalid SRIDs will be retained, with those &gt; 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 ).
ダンプファイル内のspatial_ref_sysにあるカスタムレコードが不正なSRIDになっていることがあります場合。妥当なSRID値は0より大きく999000より小さくなります。999000から999999の間は内部利用のための予約領域ですが、SRID値 &gt; 999999 の場合は、その値は一切使用できません。全ての不正なSRIDを持つ独自レコードは、SRID値 &gt; 999999 の場合は予約領域に移動して、保持されます。しかし、値を保持するために設定されているspatial_ref_sysテーブルから、値が保持されるように設定されているのチェック制約が外れます。場合によっては (複数の不正なSRIDが同じ予約領域のSRID値に変換されるとき)、主キーも外れます。
11 days ago
User avatar yellow73

Translation changed

  1. postgis
  2. PostGIS Manual
  3. Japanese
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>.
ビューまたは関数の中に非推奨のPostGISオブジェクトを使っているものがある場合。これの訂正には、リストア前に<filename>legacy.sql</filename>スクリプトのロードを試してみることができます。非推奨オブジェクトをまだ持っている版バージョンのPostGISにリストアして、コードを作り替えた後に再び移動させを試みることもできます。<filename>legacy.sql</filename>を利用する場合は、コードを非推奨関数を使うのをやめたコードわないように訂正して、また<filename>uninstall_legacy.sql</filename>をロードして非推奨オブジェクトを削除するのを忘れないでください。
11 days ago
User avatar yellow73

Translation approved

  1. postgis
  2. PostGIS Manual
  3. Japanese
Errors may arise in the following cases:
エラーは次の場合に起こりえます:
11 days ago
User avatar yellow73

Translation approved

  1. postgis
  2. PostGIS Manual
  3. Japanese
Restore your backup into your fresh <varname>newdb</varname> database using postgis_restore. Unexpected errors, if any, will be printed to the standard error stream by psql. Keep a log of those.
バックアップを新しい<varname>newdb</varname>データベースにリストアするには、postgis_restoreを使います。psqlが予期せぬエラーを標準エラー出力に出すことがあります。これらのログをのエラーのログは保存しておいて下さい。
11 days ago
Browse all translation changes