Cyrilic nicknames in irc side #105
-
I want to make some changes from irc side. Our server have cyrilic nicknames like абвгд I found the letter script in irc/nick/charAttrs and include the whole alphabet but the script accept this type on discord side only. My question is what i need to change to make this happend ? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
@h1x0r1 - You're saying if a nick 'абвгд' exists on IRC server and sends a message "message" that it doesn't get relayed into discord? If so (trying to check that I understood the issue properly), the other part you describe sounds like it's only used by the bridge to be sure to generate puppets that acquire a nick that is compatible with any IRC server. If it's not sending IRC -> Discord when nick is like 'абвгд' is it printing any errors? If not then I guess you'd need to look into a) debugging (I'm unsure how to do this with go, so can't help) or b) print debugging (instrumentation, and I can explain this one a bit). If you go with option b you need to find where '*han <-' is in the code and surround it by fmt.Printf/fmt.Println code that captures the data around the call and prints it out so you can see what happens. If you find the printing functions don't get encountered then need to search up the call stack from where '*han <-' is and insert prints until you find where the creation of the message that happens before it's sent is dropped and thus never sent. I don't have a way to test against cyrllic nicks or I'd try to be more helpful :( |
Beta Was this translation helpful? Give feedback.
@h1x0r1 - You're saying if a nick 'абвгд' exists on IRC server and sends a message "message" that it doesn't get relayed into discord?
If so (trying to check that I understood the issue properly), the other part you describe sounds like it's only used by the bridge to be sure to generate puppets that acquire a nick that is compatible with any IRC server.
If it's not sending IRC -> Discord when nick is like 'абвгд' is it printing any errors? If not then I guess you'd need to look into a) debugging (I'm unsure how to do this with go, so can't help) or b) print debugging (instrumentation, and I can explain this one a bit). If you go with option b you need to find where '*han <-' is in the co…