> On Feb 21, 2010, at 6:17 AM, Simon wrote: >> Interested to know how many Kagi suppliers have experienced this and >> have also raised this issue over the years. I have. Yet still >> nothing gets fixed. Not to mention they still mangle the >> registrationName, so if you're in Japan, your name could end up being >> **** because foreign character sets aren't handled properly. >> >> This is not to knock Kagi, as every payment processor has their >> problems, but I think suppliers have been quite patient. If a group >> of us got together and highlighted the main improvements we would like >> Kagi to focus on, do you think they would listen? > > I have my doubts but count me in. I find the mangling of non-ascii characters > in the registration name unacceptable, reported it 18 months ago and nothing > happened. This affects a great many of our customers, turning one, a couple or > all characters in the name into *. I love ** as a name.
Kagi's lack of a parsable TFYP format as well as lack of support for non-Roman characters and the inability to edit templates without Kagi's involvement led us to drop them from a primary provider to just an emergency backup system. We used them for nearly 10 years, but their systems changed little - it seems like they never scaled very well. -- Trygve Inda | Xeric Design, Ltd. President | a software development company http://www.xericdesign.com
