Jump to content

Talk:Caipira dialect

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
[edit]

Hello fellow Wikipedians,

I have just modified one external link on Caipira dialect. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 01:20, 29 July 2017 (UTC)[reply]

That chart contains possibility or definately innacurate information

[edit]

The source of the information of the caipira portion of the chart isn't cited Also it doesn't mention some pronounciations in the SP and RJ, coda r can be realized as [ɾ], [ʀ], [ɹ], [χ], [x], [h] and maybe more, the mentioned were only the first two, also /ow/ can be realized as [ow] not just as an [o], non-stressed /o/ being more closed, more like [u], is a feature of some(most?all???) paulista-accents, so [puɾˈke] is also possible. — Preceding unsigned comment added by Semantism (talkcontribs) 09:41, 5 March 2022 (UTC)[reply]