LibreSign / LibreSign/libresign

Non-UTF-8 encoding detected. This may cause issues with accented or special characters

Open
#4,872 36 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
818
Forks
146
Avg merge
11h 31m
Merged PRs (30d)
326

Description

Hello, I'm having an issue since updating to LibreSign 11.1.2.

In the LibreSign system info, I see the following warning:

Status | Message | Resource | Hint
info | Non-UTF-8 encoding detected. This may cause issues with accented or special characters | java | Ensure the system encoding is UTF-8. You can check it using: locale charmap

When signing, if the signer's name contains special characters (such as accents), they are replaced with question marks (?).

Here is the output of my locale command:

root@nextcloud:~# locale
LANG=fr_BE.UTF-8
LANGUAGE=
LC_CTYPE="fr_BE.UTF-8"
LC_NUMERIC="fr_BE.UTF-8"
LC_TIME="fr_BE.UTF-8"
LC_COLLATE="fr_BE.UTF-8"
LC_MONETARY="fr_BE.UTF-8"
LC_MESSAGES="fr_BE.UTF-8"
LC_PAPER="fr_BE.UTF-8"
LC_NAME="fr_BE.UTF-8"
LC_ADDRESS="fr_BE.UTF-8"
LC_TELEPHONE="fr_BE.UTF-8"
LC_MEASUREMENT="fr_BE.UTF-8"
LC_IDENTIFICATION="fr_BE.UTF-8"
LC_ALL=fr_BE.UTF-8

I'm running Nextcloud Hub 10 (31.0.3).

Do you know what might be causing this issue, even though my system is configured in UTF-8?

Thanks in advance!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the LibreSign system info warning, the reported locale output, and the signing flow where accented signer names become question marks. Reproduce the problem with the provided UTF-8 environment and determine whether the Java resource or PHP integration changes the encoding. Done means accented and special characters remain intact and the warning correctly reflects the system encoding.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, php
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.