Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a2861294cd8a4b67

Jump to content

Talk:Chu XP-0

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 8 years ago by ZLEA in topic Edit Warring Over Aircraft Designation

Edit Warring Over Aircraft Designation

[edit]

The history of this aircraft seems to be very little documented. However, that does not negate the need for reliable sources. The history page of this article reveals some light edit warring over the exact designation of this aircraft. Please explain the reason for your changes in this regard with reliable sources when making them. –Noha307 (talk) 00:32, 23 January 2018 (UTC)Reply

When I Google X-PO I get a lot about the aircraft, when I google XP-O I get this page and nothing more, so I assume X-PO is correct. - ZLEA Talk Contribs 18:10, 28 January 2018 (UTC)Reply
Lennart Andersson's A History of Chinese Aviation (Andersson, Lennart (2008). A History of Chinese Aviation: Encyclopedia of Aircraft and Aviation in China until 1949. Taipei, Taiwan: AHS of ROC. ISBN 978-957-28533-3-7. lists on p. 243 what appears to be the same type as the XP-0 (0, not O) - noting that the prototype that flew (and crashed) at Kumming in 1943 was the XP-1 which appears to be a different aircraft (with inverted gull wing) than the "more conventional" XP-0, of which 9 were built (2 in 44, 2 in 45 and 5 in 1946).Nigel Ish (talk) 22:22, 5 February 2018 (UTC)Reply
Good, a non-internet source is better than an internet source in my opinion. - ZLEA Talk\Contribs 23:11, 5 February 2018 (UTC)Reply