Skip to content

Commit 76cd73f

Browse files
committed
fix: Update changelog
1 parent 9c92041 commit 76cd73f

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

user_guide_src/source/outgoing/localization.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -370,13 +370,13 @@ Detailed information can be found by running the command:
370370
.. _sync-translations-command:
371371

372372
Synchronization Translation Files via Command
373-
=============================================
373+
---------------------------------------------
374374

375375
.. versionadded:: 4.6.0
376376

377-
After working on your translation for the current language for a long time, in some cases you will need to create files for another language.
378-
The ``spark lang:find`` command can be used, it is not prohibited. But it cannot fully detect absolutely all translations. Especially if the parameters are dynamically set as ``lang('App.status.' . $key, ['payload' => 'John'], 'en')``.
379-
In this case, the best solution is to copy the finished language files and translate them. This way you can save your unique keys that the command did not find.
377+
You may need to create files for another language when you've finished translating for the current language. You can use the spark ``lang:find`` command to help with this. However, it might not detect all translations, particularly those with dynamically set parameters like ``lang('App.status.' . $key, ['payload' => 'John'], 'en')``.
378+
379+
To ensure no translations are missed, it's best to copy the completed language files and translate them manually. This approach preserves any unique keys the command might have overlooked.
380380

381381
All you need to do is execute:
382382

0 commit comments

Comments
 (0)