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
{{ message }}
Repository navigation
Swiss QRCode: New character set are available on 18.November 2022 #431
[ ] Bug
[ ] Question (e.g. about handling/usage)
[x] Request for new feature/improvement Swiss QRCode: New charaterset is available on 18. November 2022
Expected Behavior
A customer reported that he cannot use his company name with degree characters in the QRCode information (Contact / Name) and gets the following error message:
Contact: Name must match the following pattern as defined in pain.001: ^([a-zA-Z0-9.,;:'\ +-/()?*[]{}\`´~ )
Now I wrote with Sixpayment about the problem and answer to me, that on 18.November are new character set are allowed.
Here the message:
_Guten Tag Frau Frick,
Vielen Dank für Ihr e-Mail.
Die restlichen Zeichen werden dann umgewandelt.
Im folgenden [Dokument|Swiss Payment Standards 2022 (six-group.com)] sind auch die Zeichen aufgeführt. Der Zeichensatz wird ab dem 18. November, verglichen mit der vorherigen Version, erweitert werden.
Partner Support
SIX
Banking Services_
Current Behavior
Possible Solution (optional)
customize/update in class Contact the variable charsetPattern
Steps to Reproduce (for bugs)
Insert in the adress the name with YXZ°
Contact WithStructuredAddress(string name, string zipCode, string city, string country, string street = null, string houseNumber = null);
Activity
RamonaFrickCH commentedon Nov 11, 2022
Fix Issue in PayloadGenerator
Line989
var charsetPattern = @"^([a-zA-Z0-9.,;:'\ +-/()?*[]{}\`´~ ^|]|[!""#%&<>÷=@_$£¡¢¤¥¦§¨©ª«¬®¯°±²³µ¶·¸¹º»¼½¾¿×Ø€]|[àáâäãåāăąçćĉċčďđèéêëēĕėęěĝğġģĥħìíîïĩīĭįıijķĸĺļľŀłñńņňʼnŋòóôöōŏőõŕŗřśŝşšșţťŧțùúûüũūŭůűųŵýÿŷźżžßÀÁÂÄÃÅĀĂĄÇĆĈĊČĎĐÈÉÊËĒĔĖĘĚĜĞĠĢĤĦÌÍÎÏĨĪĬĮİIJĴĵĶĹĻĽĿŁÑŃŅŇŊÒÓÔÖÕŌŎŐŔŖŘŚŜŞŠȘŢŤŦȚÙÚÛÜŨŪŬŮŰŲŴÝŶŸŹŻŽÆÐÞæðøþŒœſ])*$";
Update PayloadGenerator.cs
Update PayloadGenerator.cs
codebude commentedon Apr 20, 2024
Fixed with PR #432 . Bugfix will be part of QRCoder 1.5.0. Thanks for your support @RamonaFrickCH