Thank you for correcting the text in this article. Your corrections improve Papers Past searches for everyone. See the latest corrections.

This article contains searchable text which was automatically generated and may contain errors. Join the community and correct any errors you spot to help us improve Papers Past.

Article image
Article image
Article image
Article image

RAPID WITHDRAWAL

JAPANESE IN CHINA Rec. 1 p.m. CHUNGKING, June 21. The Chinese, driving towards Hangrchow Bay, crossed the Wu River and advanced 31 miles Jbeyond Wenchow i against fitful resistance from the rapidly withdrawing enemy, says- the j United Press correspondent. With the exception of a half-hearted and futile attempt to check the Chinese coastal drive with . a seaborne relief force shortly after the fall of Foochow in May, the Japanese have ■ made no apparent move to reduce the threat to their Hangchow Bay front through which is funnelled much vital material. The Japanese coastal garrisons continue to-withdraw towards the tough defensive system around Ningpo. It now appears that the entire constline below that point, except the heavily-fortified Canton-Hong Kong area, may be abandoned. A Chinese communique announces that the Chinese are fighting in the suburbs of Liuchow.

Permanent link to this item

https://paperspast.natlib.govt.nz/newspapers/EP19450622.2.64

Bibliographic details

Evening Post, Volume CXXXIX, Issue 146, 22 June 1945, Page 6

Word Count
139

RAPID WITHDRAWAL Evening Post, Volume CXXXIX, Issue 146, 22 June 1945, Page 6

RAPID WITHDRAWAL Evening Post, Volume CXXXIX, Issue 146, 22 June 1945, Page 6

Help

Log in or create a Papers Past website account

Use your Papers Past website account to correct newspaper text.

By creating and using this account you agree to our terms of use.

Log in with RealMe®

If you’ve used a RealMe login somewhere else, you can use it here too. If you don’t already have a username and password, just click Log in and you can choose to create one.


Log in again to continue your work

Your session has expired.

Log in again with RealMe®


Alert