Cannot add LinkedIn profile name

[Bushido1]

Describe the issue

Hi!

After filling "LinkedIn profile name" at https://translations.documentfoundation.org/accounts/profile/#profile with https://www.linkedin.com/in/olav-m%C3%A4gi-80208b5, I get an error "Enter a valid “slug” consisting of letters, numbers, underscores or hyphens.".

Is it because my profile name includes "ä" i.e. "%C3%A4"?

I already tried

• I've read and searched the documentation.
• I've searched for similar issues in this repository.

Steps to reproduce the behavior

1. Go to https://translations.documentfoundation.org/accounts/profile/#profile
2. Scroll down to LinkedIn profile name
3. Fill it with https://www.linkedin.com/in/olav-m%C3%A4gi-80208b58
4. Click on 'Save'
5. See error "Enter a valid “slug” consisting of letters, numbers, underscores or hyphens."

Expected behavior

No such error

Screenshots

Exception traceback

No response

How do you run Weblate?

weblate.org service

Weblate versions

No response

Weblate deploy checks

No response

Additional context

No response

[nijel]

Yes, the assumption was that the service allows only ASCII characters there.

[github-actions]

This issue seems to be a good fit for newbie contributors. You are welcome to contribute to Weblate! Don't hesitate to ask any questions you would have while implementing this.

You can learn about how to get started in our contributors documentation.

[Kaushik-Iyer]

Can someone explain what is to be changed where? I want to try to work on this

[nijel]

The type of the field probably needs to be changed to something more generic, but some validation will be still needed there:

weblate/weblate/accounts/models.py

Lines 551 to 556 in 5498a1e

	linkedin = models.SlugField(
	verbose_name=_("LinkedIn profile name"),
	help_text=_("Your LinkedIn profile name from linkedin.com/in/profilename"),
	blank=True,
	db_index=False,
	)

[Kaushik-Iyer]

SlugField.allow_unicode¶

If True, the field accepts Unicode letters in addition to ASCII letters. Defaults to False.

Apologies for the bad copy pasting, but this was in the django docs, so do I just need to make this value to true, instead of changing the type of field?

Found from (https://docs.djangoproject.com/en/2.0/ref/models/fields/#django.db.models.TextField)

[nijel]

Yes, that could do the trick as well.

[nijel]

Fixed by #8619, thanks!

[github-actions]

Thank you for your report; the issue you have reported has just been fixed.

• In case you see a problem with the fix, please comment on this issue.
• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.