Translations update from OSGeo Weblate

[osgeoweblate]

Translations update from OSGeo Weblate for postgis-workshop/index.

It also includes following components:

• postgis-workshop/spatial_relationships_exercises

• postgis-workshop/geography_exercises

• postgis-workshop/joins_exercises

• postgis-workshop/projection_exercises

• postgis-workshop/advanced_geometry_construction

• postgis-workshop/simple_sql_exercises

• postgis-workshop/3d

• postgis-workshop/backup

• postgis-workshop/license

• postgis-workshop/installation

• postgis-workshop/knn

• postgis-workshop/equality

• postgis-workshop/joins_advanced

• postgis-workshop/welcome

• postgis-workshop/topology

• postgis-workshop/tuning

• postgis-workshop/security

• postgis-workshop/upgrades

• postgis-workshop/clusterindex

• postgis-workshop/introduction

• postgis-workshop/linear_referencing

• postgis-workshop/loading_data

• postgis-workshop/about_data

• postgis-workshop/rasters

• postgis-workshop/history_tracking

• postgis-workshop/de9im

• postgis-workshop/geometries

• postgis-workshop/glossary 1

• postgis-workshop/validity

• postgis-workshop/simple_sql

• postgis-workshop/schemas

• postgis-workshop/creating_db

• postgis-workshop/geometries_exercises

• postgis-workshop/postgis-functions

• postgis-workshop/joins

• postgis-workshop/geometry_returning

• postgis-workshop/projection

• postgis-workshop/spatial_relationships

• postgis-workshop/geometry_returning_exercises

• postgis-workshop/indexing

• postgis-workshop/geography

Current translation status:

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The pull request includes updates to localization files for PostGIS documentation in German, Spanish, Japanese, and Korean. Key changes involve updating the "POT-Creation-Date," correcting the command name from "rasterpgsql" to "raster2pgsql," and clarifying the description of the overview_factor. Additionally, a new section has been added to describe the touched argument in the ST_Clip function. These changes improve the accuracy and clarity of the documentation across multiple languages.

Changes

File Path	Change Summary
postgis-intro/sources/locale/de/LC_MESSAGES/rasters.po	- Updated POT-Creation-Date to "2024-11-02 22:32+0000" - Corrected command name to raster2pgsql - Clarified overview_factor explanation - Added touched argument description for ST_Clip function
postgis-intro/sources/locale/es/LC_MESSAGES/rasters.po	- Updated POT-Creation-Date to "2024-11-02 22:32+0000" - Corrected command name to raster2pgsql - Clarified overview_factor explanation - Added touched argument description for ST_Clip function
postgis-intro/sources/locale/ja/LC_MESSAGES/rasters.po	- Updated POT-Creation-Date to "2024-11-02 22:32+0000" - Corrected command name to raster2pgsql - Added touched argument description for ST_Clip function - Enhanced explanations of raster functions
postgis-intro/sources/locale/ko/LC_MESSAGES/rasters.po	- Updated POT-Creation-Date to "2024-11-02 22:32+0000" - Corrected command name to raster2pgsql - Clarified overview_factor explanation - Added touched argument description for ST_Clip function

Possibly related PRs

• Typos #131: This PR corrects the command name from rasterpgsql to raster2pgsql and updates the overview_factor description, which directly relates to the changes made in the main PR regarding the same command name and explanation of overview_factor.

Poem

In the land of data where pixels play,
The command's name changed, hip-hip-hooray!
From rasterpgsql to raster2pgsql,
Clarity blooms, and confusion does stall.
With touched in ST_Clip, pixels unite,
In PostGIS, our mapping takes flight! 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.