Board index FlightGear The FlightGear project

Wiki translation challenge for the default FG aircraft!

Questions about the FlightGear organisation, website, wiki etc.

Re: Wiki translation challenge for the default FG aircraft!

Postby dot_sent » Sun Jan 21, 2018 11:03 pm

Thanks, Edward! I'll take a look.

I've also just found a serious drawback to the Mobile View workaround: in this mode, I could not edit/add external links. The page does not allow me to perform save (I get Javascript error in browser console) and I can't even get back to my markup from the preview :/ I'm going to add a note about this to your warning at the top of Translation Requests article.
Best regards,
Dot_sent
dot_sent
 
Posts: 11
Joined: Wed Jan 03, 2018 1:49 pm
Location: Netherlands
Version: 2017.3.1
OS: XUbuntu Linux

Re: Wiki translation challenge for the default FG aircraft!

Postby dot_sent » Mon Jan 22, 2018 12:03 am

bugman wrote in Sun Jan 21, 2018 8:00 pm:Cheers! Though I still see a bit of English text, so it's not quite done ;)

  • Civil utility aircraft
  • Cessna
  • Advanced production
  • This is the default FlightGear aircraft and is distributed as part of the base package.
  • Civilian aircraft
  • Military aircraft

I'll give you hints if you cannot work out where these should be changed.

Regards,
Edward

Hi Edward,

I think I've fixed all of those except for "Cessna".

It looks like {{craft manufacturer}} template is not localized at all yet. For Russian and Cessna specifically it's not a big deal - I've seen the brand used in a lot of Russian docs without anyone bothering to translate it to Russian/cyrillic script (although the proper transliteration does exist). I'd be happy to try and localize this template from scratch, though.
Best regards,
Dot_sent
dot_sent
 
Posts: 11
Joined: Wed Jan 03, 2018 1:49 pm
Location: Netherlands
Version: 2017.3.1
OS: XUbuntu Linux

Re: Wiki translation challenge for the default FG aircraft!

Postby bugman » Mon Jan 22, 2018 8:28 am

Thank you! Translating manufacturer names into different character sets is really optional. In most non-latin character languages, you would embed the Latin characters within the text and preserve the original company's name. That is why I put the infrastructure in place for translating the [wiki] Template:craft manufacturer content. By the way, why is Ru/Cessna_172P page set to 90% on the translation requests page? To me it looks like you have translated everything.

For the external links, I have to test that out. Maybe that information will help trace down what is causing this non-latin character in title bug.

Cheers,
Edward
bugman
Moderator
 
Posts: 1524
Joined: Thu Mar 19, 2015 9:01 am
Version: next

Re: Wiki translation challenge for the default FG aircraft!

Postby dot_sent » Mon Jan 22, 2018 7:30 pm

bugman wrote in Mon Jan 22, 2018 8:28 am:Thank you! Translating manufacturer names into different character sets is really optional. In most non-latin character languages, you would embed the Latin characters within the text and preserve the original company's name. That is why I put the infrastructure in place for translating the [wiki] Template:craft manufacturer content. By the way, why is Ru/Cessna_172P page set to 90% on the translation requests page? To me it looks like you have translated everything.

For the external links, I have to test that out. Maybe that information will help trace down what is causing this non-latin character in title bug.

Cheers,
Edward

Hi Edward,

In that case, I'll skip manufacturer name. I have updated the Ru/Cessna_172P page to 100% at translation requests page.

Regarding the external links, I think the problem lies in the protective captcha script that is activated on all pages if external links are added or edited. Specifically, when I try to edit the section of the page with an external link, the following HTTP message exchange happens (here I tried to add a URL for example.com to External Links block on original Cessna_172P):

Code (HTTP request): Select all
POST http://wiki.flightgear.org/api.php
Payload:
action=edit
format=json
title=Cessna+172P
summary=/*+External+links+*/Added+Example+external+link
basetimestamp=2018-01-13T23:36:55Z
starttimestamp=2018-01-13T23:36:55Z
text===+External+links+==
*+[http://en.wikipedia.org/wiki/Cessna_172+Wikipedia+article]
*+[http://www.aerodynamicaviation.com/wp-content/uploads/2016/03/C172P-checklist.pdf+Cessna+172+checklist+at+aerodynamicaviation.com]
*+[http://Example.com+Example.com]

{{Appendix}}

{{Cessna}}

[[Category:Aircraft+with+a+cockpit-only+autopilot]]

[[ar:Cessna+172P]]
[[ca:Cessna+172P]]
[[de:Cessna+172P]]
[[es:Cessna+172P]]
[[fr:Cessna+172P]]
[[nl:Cessna+172P]]
[[ru:Cessna+172P]]
[[zh:Cessna+172P]]
section=14
token=506518bd958c4ab30d6cebb3fd07ad3f5a663a21+\

Code (HTTP Response): Select all
{"edit":{"captcha":{"type":"question","mime":"text/plain","id":"1283592003","question":"<img src=\"images/spamquestion.png\" alt=\"\" title=\"\" />"},"result":"Failure"}}

and at this point the whole process breaks because of the following Javascript error:
Code (javascript): Select all
TypeError: response is undefined at load.php:31:59


So, the script that processes the server response does not know how to handle captcha, expects "response" key to be defined in response JSON and dies when attempts to access it. It is thus not related to the encoding bug that prevents non-latin char names. I'm pretty sure that one has something to do with encoding that is used either in the database itself or in the database connection string that is fed to the PHP MySQL (or whatever DB you are using) driver.

P.S. Maybe we should move to a separate topic for discussing and debugging problems with Wiki?
P.P.S. Are you aware that this very forum does not allow to put cyrillic charactes in the posts either? If I try to add any cyrillic char, I get DB error message from forum.
Best regards,
Dot_sent
dot_sent
 
Posts: 11
Joined: Wed Jan 03, 2018 1:49 pm
Location: Netherlands
Version: 2017.3.1
OS: XUbuntu Linux

Re: Wiki translation challenge for the default FG aircraft!

Postby wkitty42 » Tue Jan 23, 2018 4:31 pm

dot_sent wrote in Mon Jan 22, 2018 7:30 pm:P.P.S. Are you aware that this very forum does not allow to put cyrillic charactes in the posts either? If I try to add any cyrillic char, I get DB error message from forum.

the proper term is "UTF-8 characters"... especially those outside the old standard code pages...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 4736
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: Wiki translation challenge for the default FG aircraft!

Postby dot_sent » Tue Jan 23, 2018 5:25 pm

wkitty42 wrote in Tue Jan 23, 2018 4:31 pm:
dot_sent wrote in Mon Jan 22, 2018 7:30 pm:P.P.S. Are you aware that this very forum does not allow to put cyrillic charactes in the posts either? If I try to add any cyrillic char, I get DB error message from forum.

the proper term is "UTF-8 characters"... especially those outside the old standard code pages...

Thanks for the correction. I have only tried characters from latin and cyrillic charsets, so I tried to stay close to my personal experience.
Best regards,
Dot_sent
dot_sent
 
Posts: 11
Joined: Wed Jan 03, 2018 1:49 pm
Location: Netherlands
Version: 2017.3.1
OS: XUbuntu Linux

Previous

Return to The FlightGear project

Who is online

Users browsing this forum: No registered users and 2 guests