Date: Fri, 20 Dec 2024 15:40:22 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 283443] net-mgmt/unifi8: set UTF-8 java encoding to allow UTF-8 in wireless SSIDs Message-ID: <bug-283443-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283443 Bug ID: 283443 Summary: net-mgmt/unifi8: set UTF-8 java encoding to allow UTF-8 in wireless SSIDs Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: otis@FreeBSD.org Reporter: lily@lily.flowers Assignee: otis@FreeBSD.org Flags: maintainer-feedback?(otis@FreeBSD.org) Created attachment 255989 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D255989&action= =3Dedit Patch to add '-Dfile.encoding=3DUTF-8' to default 'unifi_javaflags' in net-mgmt/unifi8 rc file Currently, attempting to use UTF-8 characters in SSID names (or at trying to use emoji) does appear correctly in the UniFi interface, but the characters= get ascii-fied to '?' when pushing to access points and so the broadcast SSID is different and incorrect. This appears to be because the rc file for UniFi in the FreeBSD port does n= ot include '-Dfile.encoding=3DUTF-8' in the Java flags (and both the systemd u= nit and LSB init script provided in the upstream UniFi package for Debian do include this flag and do not suffer from this issue). I've manually added t= he relevant flag by setting 'unifi_javaflags' in rc.local and confirmed that it does fix the issue. I've attached a patch to ports that should fix the default 'unifi_javaflags' value in the port's rc file to include the UTF-8 flag itself. Let me know if you need more info, thanks! --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-283443-7788>