style: improve and unify the user interface

[sofia-riese]

Improve and unified user interface, enhanced readability, and easy migration from older versions.

[juewuy]

It does indeed look much better.

However, this would affect the consistency across all menus in the script, and the overall workload required to modify everything would be quite substantial. Moreover, it is not strictly necessary, so we would prefer to allocate our time and effort to more important priorities.

[sofia-riese]

It does indeed look much better.

However, this would affect the consistency across all menus in the script, and the overall workload required to modify everything would be quite substantial. Moreover, it is not strictly necessary, so we would prefer to allocate our time and effort to more important priorities.

Yes, this is just the beginning.

For now, I want to improve the parts shown in the diagram. If there are no major issues after testing for a while, I will gradually replace other existing styles with the new ones.

You can continue fixing bugs, and I'll help out sometimes :), while I'll handle the style replacement work; these aren't mutually exclusive.

[juewuy]

@sofia-riese In fact, if time allows, I would be more inclined to prioritize adding multilingual support to the script. In my view, this would be considerably more important than visual improvements, even though it would take a substantial amount of time to implement.

[sofia-riese]

@sofia-riese In fact, if time allows, I would be more inclined to prioritize adding multilingual support to the script. In my view, this would be considerably more important than visual improvements, even though it would take a substantial amount of time to implement.

Yes, multilingual support is equally important.

“If you chase two rabbits, you'll catch neither.”
Since work on improving the user interface has already begun, why not complete it first? This does not preclude future multilingual support.

[juewuy]

Alright, I respect your perspective. However, I won’t merge this into version 1.9.4. I plan to include it when development for version 1.9.5 begins. In the meantime, you can continue refining and improving it during this period.

[sofia-riese]

Alright, I respect your perspective. However, I won’t merge this into version 1.9.4. I plan to include it when development for version 1.9.5 begins. In the meantime, you can continue refining and improving it during this period.

Can this PR be merged into version 1.9.4 as a technical preview for testing? I want to conduct extensive testing and gather feedback to ensure these style changes achieve the intended display effects across various devices.

If these style changes pass testing, I will then migrate the existing styles accordingly. Subsequent modifications can be merged into version 1.9.5.

[juewuy]

I apologize, but version 1.9.4 has already entered the beta stage, which means we are now primarily focusing on bug fixes rather than adding new features or changes. However, no need to worry—the 1.9.5 alpha will be starting soon!

[sofia-riese]

I apologize, but version 1.9.4 has already entered the beta stage, which means we are now primarily focusing on bug fixes rather than adding new features or changes. However, no need to worry—the 1.9.5 alpha will be starting soon!

Okay

[sofia-riese]

I apologize, but version 1.9.4 has already entered the beta stage, which means we are now primarily focusing on bug fixes rather than adding new features or changes. However, no need to worry—the 1.9.5 alpha will be starting soon!

Forgot to mention: the code in the following section of this PR:
===== menu formatter tools =====
...

=============================

needs to be separated out and placed in an appropriate location within the project for unified management and easy access across all menu files.
As for how to manage it, that's up to you to figure out.