MediaInfo abnormal display in English for Japanese tranlsation

[1265578519]

MediaInfo git-v25.07-6-gaeb9abbd0;

[JeromeMartinez]

abnormal display in English

Which lines should be better translated from your point of view? the translation file is here, please suggest modifications.

[1265578519]

abnormal display in English

Which lines should be better translated from your point of view? the translation file is here, please suggest modifications.

问题仅出现在英文中，当前版本错误显示为 ｐｒｏｆｉｌｅ 正确显示应当 profile

[JeromeMartinez]

ｐｒｏｆｉｌｅ and profile are same text, the only difference is the monospace modifier, anyway this one is replaced in v25.09 by 形式のプロファイル, I have:

映像
ＩＤ　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　 : 1
形式　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　 : AVC
形式／情報　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　 : Advanced Video Codec
形式のプロファイル　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　 : [email protected]
形式の設定　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　 : CABAC / 1 Ref Frames
形式の設定　ＣＡＢＡＣ　　　　　　　　　　　　　　　　　　　　　　　　　　　　　 : はい
形式の設定　参照フレーム　　　　　　　　　　　　　　　　　　　　　　　　　　　　 : 1 フレーム
形式の設定　ＧＯＰ　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　 : N=1

[1265578519]

ｐｒｏｆｉｌｅ and profile are same text, the only difference is the monospace modifier, anyway this one is replaced in v25.09 by 形式のプロファイル, I have:

映像
ＩＤ　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　 : 1
形式　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　 : AVC
形式／情報　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　 : Advanced Video Codec
形式のプロファイル　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　 : [email protected]
形式の設定　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　 : CABAC / 1 Ref Frames
形式の設定　ＣＡＢＡＣ　　　　　　　　　　　　　　　　　　　　　　　　　　　　　 : はい
形式の設定　参照フレーム　　　　　　　　　　　　　　　　　　　　　　　　　　　　 : 1 フレーム
形式の設定　ＧＯＰ　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　 : N=1

这个问题出现在v25.07及后续MediaInfo版本中，我该如何把这些英文字符改成以前版本的英文小写？ 我需要做的是，所有英文内容修改，下方摘选 ＣＡＢＡＣ 修改为 CABAC ＩＤ改为ID ＧＯＰ改为GOP

你可以在这里下载最新版本来确认问题 https://mediaarea.net/en/MediaInfo

[JeromeMartinez]

@cjee21 the change was made for column alignment, right?

@1265578519 what is the issue with the new style?

[cjee21]

@cjee21 The change was made for column alignment, right?

Yes for alignment. Previously the colons are unaligned due to different widths of ASCII and non-ASCII chars.

[1265578519]

@1265578519 what is the issue with the new style?

你可以在这里下载最新版本来确认问题 https://mediaarea.net/en/MediaInfo

这种改动会导致其它程序调用MediaInfo出现问题，这种英文格式是不常见的，计算机代码可能发生识别错误，并且也对于人类可读性也不美观

[cjee21]

Anyone has better idea for how to align the colons when using usual ASCII chars when mixed with CJK?

[JeromeMartinez]

你可以在这里下载最新版本来确认问题

And it is v25.09, not v25.07.

这种改动会导致其它程序调用MediaInfo出现问题，这种英文格式是不常见的，计算机代码可能发生识别错误，并且也对于人类可读性也不美观

This display is intended for humans, not computers. For computers, XML or JSON outputs shall be used.

For humans, a preference is to have aligned columns hence the change made in newest versions, for the moment we prefer the aligned columns over the minor difference in the Latin characters. Having the old ASCII characters would be good if we find a way to display them without breaking the aligned columns, for the moment we didn't find how to do that (maybe it is just impossible).

For ID or GOP (Group of Pictures), an alternative would be to have a translation (身分 and 圖像群組 fine?) For CABAC, it is an acronym, 前文參考之適應性二元算術編碼 is a bit long (or not?).

[cjee21]

And it is v25.09, not v25.07.

Change to full-width ASCII chars for alignment was made in 25.03 and mentioned in the changelog.

For CABAC, it is an acronym, 前文參考之適應性二元算術編碼 is a bit long (or not?).

This Wiki is Chinese not Japanese?

[1265578519]

This Wiki is Chinese not Japanese?

中文和日文本质上基本相同

有日本或者其它地域的人不喜欢MediaInfo现在这种粗大的英文显示吗？ 我觉得可以进行人员投票回退代码，至少我并不喜欢居中对齐破坏导致英文显示成这样

[opts98]

And it is v25.09, not v25.07.它是 v25.09，而不是 v25.07。

Change to full-width ASCII chars for alignment was made in 25.03 and mentioned in the changelog.在 25.03 中更改了全角 ASCII 字符以进行对齐，并在更新日志中提到。

For CABAC, it is an acronym, 前文參考之適應性二元算術編碼 is a bit long (or not?).对于 CABAC，它是一个首字母缩略词，前文参考之适应性二元算术编码有点长（或者不长？

This Wiki is Chinese not Japanese?这个维基是中文不是日文？

Yes, I encountered the same problem. In the old version, most of the video information could be seen on one page, but in the new version, I have to drag the bottom bar to view it.

[JeromeMartinez]

This Wiki is Chinese not Japanese?

My mistake. Open to suggestion for translations from English to Japanese, it would be a nice way to resolve the issue.

我觉得可以进行人员投票回退代码

A vote is always difficult, people willing the change are more motivated to vote than people not carrying or happy. For the moment you are the first to complain about this change, it is a form of vote.

[JeromeMartinez]

most of the video information could be seen on one page, but in the new version, I have to drag the bottom bar to view it.

As far as I know, this change is about the columns, not the lines, the height topic is another topic, about the font size.

[cjee21]

you are the first to complain

and it has been 7 months since this change was made.

[opts98]

This is a comparison of information between the new and old versions. The old version is easier to view and does not require scrolling the bottom bar.

[opts98]

I believe the reason lies in your changes to the distinction between full-width and half-width English characters. This has also been discussed in the MPC-BE project.https://github.com/Aleksoid1978/MPC-BE/issues/865

[JeromeMartinez]

This is a comparison of information between the new and old versions. The old version is easier to view and does not require scrolling the bottom bar.

I misunderstood. The bottom bar is about the width. we have a column count, 40 characters seems too much with this new style.

In practice, monospace character size is bigger in Japanese compared to english.

If you change Config_Text_ColumnSize;40 by Config_Text_ColumnSize;30 (or Config_Text_ColumnSize;25?), does it look better?

Untranslated strings may be truncated but a "fix" would be to translate them (fewer characters in Japanese).

[cjee21]

Someone can write a better algorithm to calculate CJK chars as width of two chars when calculating the spaces to insert. Then we can revert to using standard ASCII chars. However, the alignment will then depend on whether the text renderer and font displays ASCII chars at exactly half the CJK chars.

[JeromeMartinez]

@cjee21 while thinking about that, as the topic is column alignment, would padding with monospace half-width spaces be better?

Edit:

However, the alignment will then depend on whether the text renderer and font displays ASCII chars at exactly half the CJK chars.

Do you have experience that the full width is not exactly 2x half width?

[JeromeMartinez]

We could have a (yet another) option for having the 2 possibilities (full width, or half width + space padding, actually 3 options with half width without space padding), and users / third party app chooses which ones fits better.

[cjee21]

Do you have experience that the full width is not exactly 2x half width?

Most of the time except in terminals if I am not mistaken.

https://github.com/Microsoft/vscode/issues/47983

[JeromeMartinez]

Most of the time except in terminals if I am not mistaken.

:(. thanks for the link.

[opts98]

This is a comparison of information between the new and old versions. The old version is easier to view and does not require scrolling the bottom bar.

I misunderstood. The bottom bar is about the width. we have a column count, 40 characters seems too much with this new style.

In practice, monospace character size is bigger in Japanese compared to english.

If you change Config_Text_ColumnSize;40 by Config_Text_ColumnSize;30 (or Config_Text_ColumnSize;25?), does it look better?

Untranslated strings may be truncated but a "fix" would be to translate them (fewer characters in Japanese).

I apologize; my explanation was unclear. The bottom bar I referred to is a draggable button. In previous versions, most useful information could be displayed on a single page without dragging this bar. However, in the new version, you must drag the bar to view more information because the line spacing has become too large due to changes in English characters.

[opts98]

These are two images that give a direct comparison between the old and new versions.

[JeromeMartinez]

the line spacing has become too large due to changes in English characters.

More precisely, due to all spaces being now full width. Config_Text_ColumnSize;25 in ja.csvshould resolve that, with risk when there are untranslated strings (truncation).

The issue we resolved with this change is seen in https://github.com/MediaArea/MediaInfo/issues/1183#issuecomment-3473163258 (unaligned :), now we need to figure out how to have a balance between resolving this issue and the too large width.

[opts98]

the line spacing has become too large due to changes in English characters.

More precisely, due to all spaces being now full width. Config_Text_ColumnSize;25 in ja.csvshould resolve that, with risk when there are untranslated strings (truncation).

The issue we resolved with this change is seen in #1183 (comment) (unaligned :), now we need to figure out how to have a balance between resolving this issue and the too large width.

also，it seems this problem only occurs when the language is set to Chinese or Japanese; when these two languages ​​are set, English characters will have issues.

[1265578519]

我查看了现在MediaInfo的输出空格，会占据2个字符 空格显示　 但是我的问题是英文为什么要显示那么大！我要瘦小的那种显示，和电脑与手机系统显示统一化，我所有的电子设备和其它软件都不会出现这种巨大的英文

[cjee21]

only occurs when the language is set to Chinese or Japanese

Only when set to Chinese, Japanese or Korean (CJK) as intended.

When set to these languages, all ASCII characters are using full-width versions that are the same width as the CJK characters to maintain alignment.

[opts98]

Only when set to Chinese, Japanese or Korean (CJK) as intended.

Yes, when these languages ​​are set, the letter spacing of English characters becomes very large.