Why only IT and US locales in Webtop

90% is much to high IMHO. When I started using Nethserver in German there were 60-70% translated but it felt likt that 90%. Even now, when the state of the German translation is just 93% but is quite difficult to find any untranslated strings in the UI.

I would never have startet using Nethserver in German and never starting translating and correcting the rest if German would have been no option to select and try. Therefore I repeat my suggestion to have a relative low limit to encourage other people to use it and translating the rest.

50% of all strings should be a good starting point, because it will cover 70-80% of the common dialogs already.

Is it possible to add a link to the translation tool when not translated words/strings are shown?

I see your point, you’re right: 90% is too high. IMO 50% is too low, it seems a not-maintained translation.
I’d say a good compromise could be 70% :slight_smile:

Sorry, I do not understand: where do you imagine such link?

Let’s see if i read correctly @robb: a link into the app for allowing “missing string/language” to be fastly recalled via URL.

I suggest that there is a general settings for language, locale and timezone that is used by as many applications as possible, because nextcloud also has the wrong settings.

I think that this Date Format Short is missing in Webtop. Am I wrong? @lucag @giacomo

That’s another feature request, please do not mixup things. :slight_smile: I will respond on the other thread.

I don’t have the answer since I do not know Webtop enough: you know it better than me :slight_smile:
If Webtop doesn’t have short format, just ignore it.


Do we need three settings language, locale, timezone or do you want to set lanuage and locale with one setting?

IMVHO the “perfect” way to achieve this is double. Both quite not-featurable…
Way 1: when you create a user, for every hypothetical module of NethServer, even one that’s not installed, the configuration step must force the systadmin to choose a language and create it into every app. The list of error codes could be quite titanic.
Way 2: when you install a module, it must look for any user locale and auto-configure it into the settings of the app. And this is quite worse, because the problems that this approach can generate through the version could be… ballistic. Errors of coding, change of approach by packages, change of setting position into configuration file-and/or-db, update and upgrade mayhem.

Both are multiple evocations for bad luck, issues, pain, regressions, overcode, error collect, message building. Quite like disassemble a tanker only with fixed wrenches.

1 Like

Should we wait for next feature release? @lucag

1 Like

No, it is much simpler.

  1. For Webtop there is already such a setting, the only point here is that, German and other languages are missing in the drop down box and also that the Geman locale settings are wrong. A simple fix.
  2. For Nextcloud there are to config-variables in NextCloud which have to be set for the default language and locale.

In esssence: An almost trivial change to solve the problem in the 95% case.

You’re still looking by your perspective. :slight_smile: Three of the servers i am overseeing do not use neither of these modules…

IMVHO you are not goinge to “see” anything different from your concern.

@federico.ballarini I am interested to get the french in the widget, for now far to be fully translated

'hu_HU' => {
        LANGUAGE => 'hu_HU',
        START_DAY => '1',
        DATE_FORMAT_LONG => 'yyyy. MMMM dd.',
        DATE_FORMAT_SHORT => 'yyyy.MM.dd.',
        TIME_FORMAT_SHORT => 'HH:mm',
        TIME_FORMAT_LONG => 'HH:mm:ss'

This could help: https://en.wikipedia.org/wiki/Date_format_by_country

For Dutch it should be like:

'nl_NL' => {
        LANGUAGE => 'nl_NL',
        START_DAY => '1',
        DATE_FORMAT_LONG => 'dddd mmmm yyyy',
        DATE_FORMAT_SHORT => 'dd-mm-yyyy',
        TIME_FORMAT_SHORT => 'hh:mm',
        TIME_FORMAT_LONG => 'hh:mm:ss'

I really think yes @federico.ballarini… but I think you won’t have to wait long :wink:

1 Like

Hi @lucag, for me it’s not a problem. We should also add in Webtop all missing format of supported languages, like HU ones. Could you check?

1 Like

Actually I have set this format (HU, YMD) as default in the properties admin inside webtop, and worked fine. An update changed it back in the admin, but it did not affect current users.

Users see empty values at date settings (they can select the different values), but the actual date is displayed correctly everywhere.

At least the ISO yyyy-mm-dd would be great to have, or custom setting for advanced users.

Hi @federico.ballarini, this control must be asked to @matteo.albinola :wink:

1 Like