i18n: tc translation update for 03-hw

[ooo-Jay]

skipped some of the dungeons which are no longer function after patch 6.x rework

[xiashtra]

skipped some of the dungeons which are no longer function after patch 6.x rework

Which dungeons are you referring to?

[ShadyWhite]

Due to usage habits, almost all N/S/W/E directional indicators in cactbot triggers are translated as Front/Back/Left/Right in the Simplified Chinese version. I'm not sure if this needs to be changed according to Traditional Chinese user habits.

[xiashtra]

• When updating the older Extreme fights that have Unreal versions associated with them, you should run sync_files, which will auto-generate the Unreal triggers and timelines (Ref: https://github.com/OverlayPlugin/cactbot/blob/main/docs/RaidbossGuide.md#sync-files).
• if you've completely finished translating an encounter, you can remove the 'missingTranslations': true, line from the tc block.

[ooo-Jay]

skipped some of the dungeons which are no longer function after patch 6.x rework

Which dungeons are you referring to?

ui\raidboss\data\03-hw\dungeon\aetherochemical_research_facility.ts

Lahabrea & Igeyorhm and Ascian Prime didn't fire any trigger, i think the fight is adjusted for the duty support

[xiashtra]

skipped some of the dungeons which are no longer function after patch 6.x rework

Which dungeons are you referring to?

ui\raidboss\data\03-hw\dungeon\aetherochemical_research_facility.ts

Lahabrea & Igeyorhm and Ascian Prime didn't fire any trigger, i think the fight is adjusted for the duty support

Yes, this is one of the ones that was updated for Duty Support and needs a review. However, some of the earlier triggers should still apply, such as those for Harmachis. I think you should add translations for what you can.

[ooo-Jay]

skipped some of the dungeons which are no longer function after patch 6.x rework

Which dungeons are you referring to?

ui\raidboss\data\03-hw\dungeon\aetherochemical_research_facility.ts
Lahabrea & Igeyorhm and Ascian Prime didn't fire any trigger, i think the fight is adjusted for the duty support

Yes, this is one of the ones that was updated for Duty Support and needs a review. However, some of the earlier triggers should still apply, such as those for Harmachis. I think you should add translations for what you can.

yes, tested they are still working, the only missing translation are for "Lahabrea & Igeyorhm and Ascian Prime".

The timing is not 100% correct, a little bit shifting. But i think it is caused by current TC version of FFXIV_ACT_Plugin cannot output "will be sealed off" message, I will test again when new TC version is available.

[ooo-Jay]

Due to usage habits, almost all N/S/W/E directional indicators in cactbot triggers are translated as Front/Back/Left/Right in the Simplified Chinese version. I'm not sure if this needs to be changed according to Traditional Chinese user habits.

I suggest changing back to N/S/W/E indicators for better universality.
Since TC server spans across multiple regions with different speaking languages and written languages, so i think a more internationally recognized style would serve well.

[xiashtra]

You will need to run sync_files to pass the lint checks.

[ooo-Jay]

You will need to run sync_files to pass the lint checks.

Thanks.
i am new to GitHub and node.js, i was confusing i should press something in the web or run this locally.
The command caused some warnings, i believe it is a expected warning?
the generated files from the command should be fine?

(node:297504) ExperimentalWarning: `--experimental-loader` may be removed in the future; instead use `register()`:
--import 'data:text/javascript,import { register } from "node:module"; import { pathToFileURL } from "node:url"; register("ts-node/esm", pathToFileURL("./"));'
(Use `node --trace-warnings ...` to show where the warning was created)
(node:297504) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
(Use `node --trace-deprecation ...` to show where the warning was created)

[xiashtra]

You will need to run sync_files to pass the lint checks.

Thanks. i am new to GitHub and node.js, i was confusing i should press something in the web or run this locally. The command caused some warnings, i believe it is a expected warning? the generated files from the command should be fine?

npm run sync-files will execute the script locally.

(node:297504) ExperimentalWarning: `--experimental-loader` may be removed in the future; instead use `register()`:
--import 'data:text/javascript,import { register } from "node:module"; import { pathToFileURL } from "node:url"; register("ts-node/esm", pathToFileURL("./"));'
(Use `node --trace-warnings ...` to show where the warning was created)
(node:297504) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
(Use `node --trace-deprecation ...` to show where the warning was created)

These warnings are ok to ignore.

[xiashtra]

Due to changes from #891, you will need to update your local copy of the repository to resolve the conflicts. Unfortunately, a lot of changes were introduced between this PR and that one.

The rule for locale ordering is also being enforced as tc last, which will require some updates to this PR.

[ooo-Jay]

Due to changes from #891, you will need to update your local copy of the repository to resolve the conflicts. Unfortunately, a lot of changes were introduced between this PR and that one.

The rule for locale ordering is also being enforced as tc last, which will require some updates to this PR.

sorry for another noob question, does it mean not only moving the tc locale to the last of the locale order, i also have to merge the "main" into my branch, resolve the changes, and commit again?

[xiashtra]

Due to changes from #891, you will need to update your local copy of the repository to resolve the conflicts. Unfortunately, a lot of changes were introduced between this PR and that one.
The rule for locale ordering is also being enforced as tc last, which will require some updates to this PR.

sorry for another noob question, does it mean not only moving the tc locale to the last of the locale order, i also have to merge the "main" into my branch, resolve the changes, and commit again?

Yes, that would be the way to handle it. Unfortunately, an issue was caught and resolved which caused a lot of conflicts with your PR; normally it is not this difficult.

[Souma-Sumire]

sorry for another noob question, does it mean not only moving the tc locale to the last of the locale order, i also have to merge the "main" into my branch, resolve the changes, and commit again?

Sorry, the conflict was my mistake.

You can follow the instructions in this image:

~edited~

---

run git checkout --ours .

---

Great to see you handled the problem by yourself!

[ooo-Jay]

sorry for another noob question, does it mean not only moving the tc locale to the last of the locale order, i also have to merge the "main" into my branch, resolve the changes, and commit again?

Sorry, the conflict was my mistake.

You can follow the instructions in this image:

edited

run git checkout --ours .

Great to see you handled the problem by yourself!

no worries!
Once the TC server drops 7.0 Savage, more people will probably jump in to help with the TC translation.
Stuff like this will probably happen again, i’m glad i learnt how to handle it now

Thanks for the detailed image guide

[xiashtra]

This looks ready to merge from a technical standpoint; I can't review the actual translations.