Talk:Manila–Cavite Expressway

Latest comment: 7 months ago by 223.25.62.214 in topic Logo

Conflicting info edit

In the article, the expressway is stated as being 6.6 km, however the infobox claims it is 12.5 km. The exit numbers seem to total up to 15 km. These should all be corrected ASAP. Thanks, "Pepper" 01:04, 10 August 2011 (UTC)Reply


Two groups of toll rates edit

The article only has the original coastal road toll rates. The ones for the recently opened Cavitex segment has different rates (class 1 is 58.00 PHP, the rest I forgot). Plus I'm not sure how to show two toll rates tables without confusion of the two. --R A D Talk 17:06, 30 August 2011 (UTC)Reply


Commons files used on this page or its Wikidata item have been nominated for speedy deletion edit

The following Wikimedia Commons files used on this page or its Wikidata item have been nominated for speedy deletion:

You can see the reasons for deletion at the file description pages linked above. —Community Tech bot (talk) 09:23, 4 October 2020 (UTC)Reply

A Commons file used on this page or its Wikidata item has been nominated for deletion edit

The following Wikimedia Commons file used on this page or its Wikidata item has been nominated for deletion:

Participate in the deletion discussion at the nomination page. —Community Tech bot (talk) 06:32, 1 March 2022 (UTC)Reply

edit

It is clearly stated on Wikipedia:Logos that "reasonable diligence should be taken to ensure that the logo is accurate and has a high-quality appearance", therefore implying that SVG formats, which are far more superior to raster versions (PNG, JPG, etc) are highly preferred. There's someone who keeps on reverting the logo to the raster version which is undesirable and therefore destructive and vandalizing. Therefore, the current SVG logo version should always be the top choice and must be kept as it is, unless the subject undergoes a rebranding and changes their logo, which an SVG version of it should be prioritized as replacement on the infobox (talk) 10:55, 7 October 2023 (UTC)Reply