-
-
Notifications
You must be signed in to change notification settings - Fork 257
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
i cannot see tp, fc, de on the profile after the roast #1323
Comments
Could you please also attach the profile shown in that linked screen shot (btw. you could have just drag-drop that screenshot here on a comment box to have it inline). Please rename the *.alog file to end in *.txt or zip it before you drag-drop it here on GitHub to a comment box. A reply by email will not work! |
is that work? |
You uploaded the settings file again. The Artisan profile ending .alog is missing. Please upload that in the same way by renaming it to *.txt. |
so what could be the reason sone that it not visible ? |
ok |
I can reproduce this now. Will try to fix it.... Thanks a lot for reporting! |
What is this screenshot about? |
Fixed by Commit f613f77. This was indeed a language specific issue. Our graphing lib does not support right-to-left languages like Hebrew out of the box thus we need to reverse characters in our code. There was an issue related to argument substitution in that code. The fix will be in the next Artisan release v2.10 to be released later today. In case you see Hebrew translation issues, please report them separately! |
Describe the bug
i cannot see tp, fc, de marks
on the profile after the roast
only the charge in appearance
Screenshots
Setup (please complete the following information):
Please attach your current Artisan settings file (as exported via menu Help >> Save Settings as *.aset) file.
Please attach any relevant Artisan *.alog profiles.
yarino 25.aset.zip
Note that you need either add a
.txt
extension or zip the files before uploading. Otherwise you will receive a "Not a supported file type" error on uploading.The text was updated successfully, but these errors were encountered: