I would like to gather localized adventure and tradeskill class names.
Some functions like market window "my class/lvl" buttons or the class background images on my persona window currently only work for English class names. To support these functions on localized servers it is necessary to know the localized class names.
If you are interested in a localized version could you please take the English list of classes below, translate it to your localized version (please double check that they are spelled correctly, as otherwise it will not work), and post it in this thread. Make sure to either keep the order of my list or to append to my list, i.e. assassin=XXX.
Then I and other mod authors can use this list to make the above mentioned functions support localized versions.
Would it be possible to just use the localization codes for them instead?
I would think that they would check the correct version in the language files associated with that code. So if you only put the code there, it should parse it and place the proper name for that class, would it not?
Also note drop down menus that list these things may use a different order in other languages, thus completely hosing scripted menu selections.
Very good point, I had forgotten about that. I already knew that at least some of the dropdowns on the market window have a different order, I had already generalized some of my presets because of that.
Hmm, I guess this will be more work than I thought...
A somewhat complicated select and compair routine could probably be written to derive the proper numbering on first window open. It would also safeguard against future menu changes but might add to the initial Market window lag.
It would work something like this...
On initial window open, iterate over the menu's data source doing text compairs to extract the index number of matches and assign those to variables.
Rewrite your menu selector code to use the derived variables rather than preset numbers.
You still have to localize your favorites and the comparison strings, but order wont be an issue.
Good idea, I think I'll do that. I'll only invoke the routine when someone hits the "my class" button for the first time, however, and then keep the calculated list order persistent over the play session. That would speed things up a bit and not cause any initial lag.
EDIT: Yes, for the favorites you'd have to do it on initial window open, but since I suppose most favorites will have to be translated to localized versions, anyway, since item names are localized as well, I don't think it is necessary to implement the code for those menu choices as well.
Btw, if anyone did translate the favorites for the ProfitUI market window, just post them in the ProfitUI thread and I can include them.
I made some disk space and checked on the French and German servers. The sorting of the dropdowns on the market window is actually identical to the English sorting, so no need for fancy code after all.
If SOE wouldn't convert all math done to a real no matter what instead of a integer this could be easily done just by enumerating though the dropdown and making a check vs the players class.
Hello, gm9. I'm syahal in EQ2Players.
I come for leave Japanese class info. Hope this helps.
But as you know, Japanese subclass names dosen't work like other languages in the same way.
Hello, gm9. I'm syahal in EQ2Players.
I come for leave Japanese class info. Hope this helps.
But as you know, Japanese subclass names dosen't work like other languages in the same way.
Thanks. Unfortunately the UI engine still does not handle non-ASCII Unicode characters correctly. I found no way to manipulate them in any way, which includes copying them from one element to another. I /bugged this a long time ago to no avail - and this clearly is a bug since it was originally working fine.
This does not only apply to Japanese, but also French and German adventure/tradeskill classes and subclasses that contain non-ASCII characters.
Hello,
I seem to have succeeded in recognition of a Japanese subclass name.
I output LocalText of a class name with OnPress of a button.
It seems to be output in form such as [\rc:アサシン\:Assassin\/r] in a Japanese server.
I was successful after having added these if I stored a file in new line form [CR+LF].
Oh, great news, thanks for letting me know. I will test your code on the other servers Guruguru and put it in the ProfitUI release, also in the market window. Thank you very much!
Oh, great news, thanks for letting me know. I will test your code on the other servers Guruguru and put it in the ProfitUI release, also in the market window. Thank you very much!
Hello.
I download recent version 3.2 of ProfitUI Reborn.
However, code of Japanese description changed and did not seem work well.
こんにちわ、最新バージョン3.2のProfitUI Rebornをダウンロードさしてもらいました。
しかし日本語の記述のコードが変化してしまってうまく動かないようです。
Therefore I made a patch file for Japanese server.
I added a level acquisition button of a market window incidentally.
I have only some classes and do not test all classes.
In addition, a description of a Japanese trade class name is wrong now.
(For example) [right description]=\rc:ウェポンスミス\:Weaponsmith\/r
[wrong description]=ウェポンスミス (now)
Because SoE forget use of a T4 engine, this description may be revised.
そこで日本のサーバー向けのパッチファイルを作りました。
ついでにマーケットウインドウのレベル取得ボタンも書き加えました。
私は一部のクラスしか持っておらず、全てのクラスをテストしていません。
また今現在、日本語の生産クラスの名前の記述は間違っています。
(例) 正しい記述=\rc:ウェポンスミス\:Weaponsmith\/r
間違っている記述=ウェポンスミス
SoEはT4エンジンの使用を忘れているので、この記述は修正される可能性があります。
--------------------------------------------------------------------------------
It's my class(Fury & Sage)
Adventure class botton
Trade class botton
[追記 / Postscript for Japanese]
ProfitUI Rebornの作者のgm9さんに対応していただいたので
最新版のProfitUI Reborn ver3.3をお試し下さい。
Thank you Guruguru, I apologize for having taken so long to implement this after you kindly provided the original file to me.
In v3.2 I had not yet tested it, which is why it did not appear in the release notes although I had put your file into the styles.xml. As it appears UIbuilder is not compatible with the file, which is what you saw in that release.
I just released v3.3 which should have fully compatible market and persona windows now. It did some testing on Sebilis myself and found that there are even two different encodings that work if you put them in the file, but for now I went with the Japanese characters as they appear on screen. Interestingly, the French and German non-ASCII characters can now just be written as pure UTF-8 without the \rc: notation you see on the Japanese servers.
Thank you very much for your help on this (I hope it works now)! This is the list I came up with for v3.3:
Thank you Guruguru, I apologize for having taken so long to implement this after you kindly provided the original file to me.
In v3.2 I had not yet tested it, which is why it did not appear in the release notes although I had put your file into the styles.xml. As it appears UIbuilder is not compatible with the file, which is what you saw in that release.
I just released v3.3 which should have fully compatible market and persona windows now. It did some testing on Sebilis myself and found that there are even two different encodings that work if you put them in the file, but for now I went with the Japanese characters as they appear on screen. Interestingly, the French and German non-ASCII characters can now just be written as pure UTF-8 without the \rc: notation you see on the Japanese servers.
Thank you for your investigation and correspondence in ProfitUI Reborn ver3.3 for our Japanese Sebilis server.
I did not notice what code of UI changed into with UI Builder because I remodeled it with editer many times.
How about dividing this class recognition code into another file?
Like <include>_ProfitUI_Market_ClassBotton.txt</include>
日本のSebilis サーバーのための調査とProfitUI Reborn バージョン3.3での対応ありがとうございました。
私はよくエディターで改造するので、ビルダーでコードが変化するのには気づきませんでした。
このクラス認識コードを別のファイルに分割するのはどうでしょうか?
<include>_ProfitUI_Market_ClassBotton.txt</include>の感じで
Quote:
Originally Posted by gm9
Thank you very much for your help on this (I hope it works now)! This is the list I came up with for v3.3: Adventurers:
(Abbreviation)
I noticed that there was a mistake in the description of trade class name that I uploaded.
私のアップロードした生産クラス名の記述には間違いがあることに気がつきました。
This is log file screenshot of trade class search in Japanese server.
(*I sort necessary log)
I notice three class names being different from other descriptions.
Such a mistake often happens with a Japanese server.
これは日本のサーバーでの生産クラス検索のログファイルのスクリーンショットです。
(*必要なログを並べ替えています)
3つのクラス名が他の記述と違うことに気づきます。
日本サーバーではこのような間違いはたびたび起こります。