|
YafaRay Plug-in - reviewing for Yafaray 3.0
|
|
08-02-2016, 10:12 PM
(This post was last modified: 08-02-2016 10:18 PM by tkbd.)
Post: #119
|
|||
|
|||
|
RE: YafaRay Plug-in - reviewing for Yafaray 3.0
Thanks for support UTF-8 file encoding.
Encoding of the file (UTF no problem in my environment too(MacOSX 10.11.6).The Characters that has a diacritical mark was able to be displayed on the badge. But it did not display the non-Latin characters for UTF-8. ![]() One of the benefits of using the UTF-8 encoding,It can dealing with multiple languages. For test sample Quote:ABC_abc_àßõäçöü_あいうえお_春夏秋冬_로마자목록_拉丁字母_देवनागर If these characters can be displayed in the badge's comments and titles. It is very helpful for users of non-alphabet-language. So I think that it is need that corresponds to ~ts. And...in currently,Wings's Yafaray plug-ins can't write out these strings. So,as an test, I added manualy a following data to badge tags of XML file prepared for Yafaray. Code: <logging_badge name="logging_badge">Yafaray hadn't occuer particularly an error in the XML file rendering. And In badge display,of cause an characters that don't exist in a font becomes "Tofu". Tofu : Slang for the empty boxes shown in place of undisplayable code points in computer character encoding, a form of mojibake (https://en.wikipedia.org/wiki/Tofu_(disambiguation)) But This test shows a possibility of multi-language display at Yafaray. So I think that it's meaningful which corresponds to ~ts for Yafaray plug-in, again. (The test tried on MacOSX 10.11.6) By the way, I tried another test that customIcon path for Yafaray side. For example Quote: <logging_customIcon sval="/Users/machdd/Desktop/画像/ねこ.png"/>Even if containing japanese charactors in the file path or filename,the custom icon image was displayed well. I suprised for the result. ![]() (Note: Current Wings's Yafaray plug-ins can't write out these strings.) (The test tried on MacOSX 10.11.6) Cheers! |
|||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 2 Guest(s)




no problem in my environment too(MacOSX 10.11.6).
