Opened 11 years ago

Closed 6 years ago

#454 closed unknown (fixed)

Names Of Languages Are Uppercase In English

Reported by: guaka Owned by: jsfan
Priority: minor Milestone: 1.3
Component: unknown Keywords: translation
Cc: jsfan

Description

I know it's a very minor issue, but it's been bothering me for a long time now. Names of languages are Uppercase in English.

Change History (32)

comment:1 Changed 11 years ago by guaka

  • Summary changed from Names Of Languages In English Are Uppercase to Names Of Languages Are Uppercase In English

comment:3 Changed 11 years ago by guaka

I fixed it in the code base.

Now it depends on me finding a way to fix all the occurrences of "english" in the database.

comment:4 Changed 11 years ago by guaka

  • follow_up changed from none to move to alpha
  • Owner guaka deleted

r4430 and r4431: database update for languages table

This probably mostly fixes the Capitalization.

comment:5 Changed 11 years ago by micha

I think, this one can only go to production after the forum changes...

comment:6 Changed 11 years ago by micha

  • Milestone changed from unassigned to 0.1.5 - short - xxx

comment:7 Changed 11 years ago by micha

  • Owner set to micha
  • Status changed from new to assigned

comment:8 Changed 11 years ago by philipp

  • Milestone changed from 0.1.5 - short - xxx to 0.5.1-short cleanup I

comment:9 Changed 10 years ago by micha

  • follow_up changed from move to alpha to release

moved to alpha in r5326

comment:10 Changed 10 years ago by micha

  • Cc jeanyves added
  • Owner changed from micha to jeanyves
  • Status changed from assigned to new

Ok, I think dbupdate doesn't have any effect on alpha. So please JeanYVes, move this manually to the production DB! It's only two mods in phpmyadmin

comment:11 Changed 10 years ago by jeanyves

  • Status changed from new to assigned

I have applied it to the production data base (so it is also effective on Alpha)

Can someone confirm the change are right and close the ticket ?

comment:12 Changed 10 years ago by micha

Unfortunately it seems that only some languages are uppercase now. català, deutsch, portugues and others are still lowercase... Could you fix it manually? Sorry to bother..

comment:13 follow-up: Changed 10 years ago by guaka

  • Resolution set to fixed
  • Status changed from assigned to closed

It's actually all fine, as far as I could see. "deutsch" is lowercase in German, francais is lowercase in French, so that's fine. From the "choose your preferred language line": Български Русский catalá deutsch English español français italiano latviešu lietuvių Nederlands Polski Português (bra) portuguese română suomi Türkçe

comment:14 Changed 10 years ago by philipp

  • follow_up changed from release to none

comment:15 in reply to: ↑ 13 Changed 6 years ago by shevek

  • Resolution fixed deleted
  • Status changed from closed to reopened

Replying to guaka:

"deutsch" is lowercase in German,

That's normally true. Unfortunately in this one case it isn't. As it is referring to the language it has to be 'Deutsch'.

comment:16 Changed 6 years ago by shevek

A simple

UPDATE languages SET Name='Deutsch' WHERE EnglishName='German'

on the DB should fix this for the footer.

Last edited 6 years ago by shevek (previous) (diff)

comment:17 Changed 6 years ago by pablobd

I got a report from a translator: "portuguese" should be "português" in the language footer

comment:18 Changed 6 years ago by crumbking

Should we not simply add translatable words Id's instead of always contacting devs for wrong spellings?

comment:19 follow-up: Changed 6 years ago by shevek

No. Then people would start translating the languages. I always thought the idea was to have the language written in that language.

comment:20 in reply to: ↑ 19 Changed 6 years ago by crumbking

Replying to shevek:

No. Then people would start translating the languages. I always thought the idea was to have the language written in that language.

But as far as I know we have some attributes like "not translatable" means only special vols could update such words.

comment:21 follow-up: Changed 6 years ago by shevek

How do we introduce new languages? Because if we fill these into the languages table I can't see a reason why someone with the right to create a new language shouldn't be allowed to change the names directly.

comment:22 Changed 6 years ago by shevek

  • Milestone changed from 0.5.2 to unassigned

Ticket should have no milestone assigned if the original milestone is rather outdated...

comment:23 in reply to: ↑ 21 Changed 6 years ago by globetrotter_tt

Replying to shevek:

How do we introduce new languages? Because if we fill these into the languages table I can't see a reason why someone with the right to create a new language shouldn't be allowed to change the names directly.

The languages (at least all from ISO 639-1) should be all listed in the language table. Have a look at the translation team wiki how to enable a new language: http://www.bewelcome.org/groups/60/wiki

comment:24 follow-up: Changed 6 years ago by shevek

Thanks, globetrotter_tt. Do you know how the languages table was build? Some entries obviously use html entities instead of UTF-8. And the number of rows is 182 while Wikipedia shows 184.

comment:25 in reply to: ↑ 24 Changed 6 years ago by globetrotter_tt

Replying to shevek:

Thanks, globetrotter_tt. Do you know how the languages table was build? Some entries obviously use html entities instead of UTF-8. And the number of rows is 182 while Wikipedia shows 184.

My guess would be an import from an exisiting table. I would ask Jean-Yves for more details.

comment:26 Changed 6 years ago by shevek

  • Milestone changed from unassigned to 1.3
  • Owner changed from jeanyves to jsfan
  • Status changed from reopened to assigned

I'd like to fix the wrong capitalization of Deutsch and the wrong writing of português with 1.3. Could we please run the following queries on the DB (shortly before release)?

UPDATE languages SET Name='Deutsch' WHERE EnglishName?='German'
UPDATE languages SET Name='português' WHERE ShortCode? = 'pt'

Last edited 6 years ago by shevek (previous) (diff)

comment:27 Changed 6 years ago by guaka

Why not run the queries now already? There's no compelling reason to wait... or?

comment:28 Changed 6 years ago by shevek

Right there's no reason to wait. But I'd hope someone else first tries the queries on their local installation to see if they work :-)

comment:29 Changed 6 years ago by globetrotter_tt

  • Resolution set to worksforme
  • Status changed from assigned to closed

Worked for me locally.

UPDATE languages SET Name='Deutsch' WHERE EnglishName = 'German'
UPDATE languages SET Name='português' WHERE ShortCode = 'pt' 

comment:30 Changed 6 years ago by shevek

  • Cc jsfan added; jeanyves removed
  • Resolution worksforme deleted
  • Status changed from closed to reopened

As the queries weren't executed on the production system reopened.

comment:31 Changed 6 years ago by shevek

Queries executed. Ticket closed.

comment:32 Changed 6 years ago by shevek

  • Resolution set to fixed
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.