Overview

GitLab provides a robust platform for version control and CI/CD pipelines. When deploying GitLab in Chinese-speaking environments, localizing the interface improves user experience significantly. This guide covers the complete process of applying Chinese language patches to a GitLab installation.

Prerequisites

Before beginning the localization process, ensure the following requirements are met:

• A working GitLab Community Edition or Enterprise Edition installation
• Root or sudo access to the GitLab server
• Internet connectivity to clone the patch repository
• The patch utility installed on the system

Install the patch utility on RHEL-based distributions:

yum install -y patch

Step 1: Clone the Chinese Localization Repository

The GitLab Chinese localization project maintains localized versions of GitLab. Clone the repository to obtain the necessary patch files:

git clone https://gitlab.com/xhang/gitlab.git

This repository contains localized versions aligned with official GitLab releases. After cloning, archive the repository for future use to avoid repeated downloads during production deployments:

tar -czvf gitlab-localization.tar.gz gitlab/

Step 2: Determine Your GitLab Version

Accurate version matching between your GitLab installation and the patch is critical for successful localization. Retrieve your installed version from the manifest file:

head -1 /opt/gitlab/version-manifest.txt

The output displays the exact version string, such as v11.1.4. Note this value for the next step.

Step 3: Generate the Localization Patch

Navigate to the cloned repository directory and generate a diff file comparing the original English version with the Chinese localization:

cd gitlab
git diff v11.1.4 v11.1.4-zh > ../gitlab-v11.1.4-zh.patch

This command creates a patch file (gitlab-v11.1.4-zh.patch) that contains all localization changes. Store this file in a accessible location for the application step.

Step 4: Apply the Localization Patch

Stop all GitLab services before applying the patch:

gitlab-ctl stop

Apply the generated patch to the GitLab Rails application directory:

patch -d /opt/gitlab/embedded/service/gitlab-rails -p1 < ../gitlab-v11.1.4-zh.patch

The -p1 option strips the first path component from file paths in the patch, ensuring correct file matching. Review the output for any errors or warnings during the application process.

After successful patch application, restart GitLab services:

gitlab-ctl start

Access the GitLab web interface. The interface should now display Chinese text throughout the application.

Troubleshooting Common Issues

Web Interface Returns 502 Error

A 502 Bad Gateway error sometimes occurs after applying patches due to service initialization problems. Resolve this by restarting the services and reapplying the configuration:

gitlab-ctl start
gitlab-ctl reconfigure

The reconfigure command rebuilds GitLab's internal configuration and often resolves service communication issues.

Patch Application Fails with "Can't Find File to Patch"

This error indicates that the patch references files not present in your GitLab installation. The most common causes include version mismatches or patches intended for newer GitLab releases.

When prompted to skip files during patch application, press Enter to continue through each skipped file. The patch utility displays the following message:

can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
diff --git a/app/assets/javascripts/awards_handler.js b/app/assets/javascripts/awards_handler.js
|index 976d32a..7967edb 100644
|--- a/app/assets/javascripts/awards_handler.js
|+++ b/app/assets/javascripts/awards_handler.js
--------------------------
File to patch:

Press Enter repeatedly to skip files that cannot be patched. Non-critical localization changes can be safely skipped without affecting core functionality.

Version Compatibility Considerations

Localization patches must match your GitLab version exactly. Before appplying any patch, verify that the patch version aligns with your installed version. Using patches from different versions may result in:

• Partial localization with English text remaining in some areas
• Application errors due to mismatched code references
• Inconsistent terminology across the interface

Maintain a mapping document linking your GitLab version to the corresponding patch file for future reference and reproducibility.