You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UTF-8 in labels (addressbooks, subscriptions, ...), like umlauts, does not display correctly. Also, it could be that if it is invalid UTF-8, the Bitmessage window does not show at all (one bug reporter), but I cannot reproduce that.
That part I can reproduce too. But one guy reported that his PyBM does not start at all (the main QT thread crashes in rerenderSubscriptions) and that I can't reproduce.
@Erkan-Yilmaz can you try now? The UI should be fixed, just left is checking what happens if you manually create invalid utf8 in keys.dat or the database.
@PeterSurda I have tested my use case above ( "erkan äöü")
OK: "erkan äöü" stays when I switch between tabs
BUT: when I restart bitmessage it is again only "erkan"
I can't reproduce this (Windows and Linux). Are you editing an entry in the addressbook (rather than one of your own addresses)? The black ones in the "Send" tab?
Activity
Erkan-Yilmaz commentedon Feb 25, 2016
I tried and it seems I can reproduce it.
a. e.g. adding umlauts in the text of a message + subject works
b. the umlaut is shown (also after receiving when I sent to myself this msg)
but: when I add the umlaut in the address book as description (1) of the BM address:
it discards the text and takes the original text (2) again
(1) e.g. "erkan Nö"
(2) "erkan"
nothing more done than above 2 points, so I can at least try those again when a fix would be available
using https://github.com/mailchuck/PyBitmessage v 0.5.7
with commit: 2f9501f
PeterSurda commentedon Feb 25, 2016
That part I can reproduce too. But one guy reported that his PyBM does not start at all (the main QT thread crashes in rerenderSubscriptions) and that I can't reproduce.
UTF fixes
More unicode fixes
PeterSurda commentedon Mar 12, 2016
@Erkan-Yilmaz can you try now? The UI should be fixed, just left is checking what happens if you manually create invalid utf8 in keys.dat or the database.
Erkan-Yilmaz commentedon Mar 12, 2016
@PeterSurda I have tested my use case above ( "erkan äöü")
OK: "erkan äöü" stays when I switch between tabs
BUT: when I restart bitmessage it is again only "erkan"
I am on commit c6b4237
PeterSurda commentedon Mar 12, 2016
@Erkan-Yilmaz what OS?
Erkan-Yilmaz commentedon Mar 12, 2016
@PeterSurda I am sending this info right now to you via BM's support mail
PeterSurda commentedon Mar 13, 2016
I can't reproduce this (Windows and Linux). Are you editing an entry in the addressbook (rather than one of your own addresses)? The black ones in the "Send" tab?
Erkan-Yilmaz commentedon Mar 13, 2016
yes, I was editing one of the "Address book" entries (1) from the Send tab (not the Address field which holds the BM-address)
(1) which is also called "Label" when one creates a new contact
PeterSurda commentedon Apr 29, 2016
I'm sorry but I can't reproduce this. I'll postpone this until there is a more reliable way for me to reproduce.