feat(i18n-HU): Update Hungarian translation

[AntoszHUN]

Update gcode captions.

Signed-off-by: AntoszHUN [email protected]

[pedrolamas]

You need to keep the line endings on the file as LF but they have been changed to CRLF...

Whatever editor you are using to make these changes, the line endings must be kept as LF (Unix style) instead of CRLF (Windows style).

[AntoszHUN]

You need to keep the line endings on the file as LF but they have been changed to CRLF...

Whatever editor you are using to make these changes, the line endings must be kept as LF (Unix style) instead of CRLF (Windows style).

I'm using Windows 10. I've tried all kinds of programs. What do I do to be good?

[pedrolamas]

I'm on Windows too!

My advice, use Visual Studio Code and install these 2 extensions:

• EditorConfig for VS Code - this will ensure you use the same formats as we need to
• i18n Ally - helper extension for translations!
  

[AntoszHUN]

I fixed the bugs. Can it be good now?

[pedrolamas]

I fixed the bugs. Can it be good now?

The line endings were still incorrect, but I fixed that for you on the PR (assuming you don't push more updates here, we should be good to merge it)

[AntoszHUN]

I fixed the bugs. Can it be good now?

The line endings were still incorrect, but I fixed that for you on the PR (assuming you don't push more updates here, we should be good to merge it)

All right. Thanks! I won't update then.

[matmen]

ah, my bad, it should be Gcode not G-Code, will fix that

[AntoszHUN]

ah, my bad, it should be Gcode not G-Code, will fix that

Why did I have to rewrite it? In English, G-Code means something. The Hungarian free translation of this is G-Code. Code = Kód. Why wasn't it good now? I translated the klipper3d.org website into Hungarian in 2.5 months. Everywhere the G-Code was rewritten into Hungarian G-Kód. No one fixed it because it wasn't a bug.

[matmen]

From what I've seen so far fluidd's convention here is to stick to the english locale for "Gcode" - as you can see here and here for example. I think it makes sense to stick to this, as I think it's more universal.

[AntoszHUN]

The translation does not change its meaning.

[matmen]

I am aware of that, but fluidd's localization convention is to leave it untranslated. It's untranslated in all the other translations too.

[AntoszHUN]

I'm on Windows too!

My advice, use Visual Studio Code and install these 2 extensions:

* [EditorConfig for VS Code](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) - this will ensure you use the same formats as we need to

* [i18n Ally](https://marketplace.visualstudio.com/items?itemName=Lokalise.i18n-ally) - helper extension for translations!
  ![image](https://user-images.githubusercontent.com/85504/164196661-0d506438-3251-48a7-bcc6-6a1ddb823e94.png)

I installed the programs. But for the i18N Ally, how can it be made to work? He's not doing anything to me.

[pedrolamas]

if you open the repo (folder) in Visual Studio, it should just detect the translations!