REGR: errors='replace' when encoding/errors are not specified
- [x] closes #38989
- [x] tests added / passed
- [x] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [x] whatsnew entry

Should 1.3 use `errors='replace'` when no `encoding/errors` are specified or use `errors=None` (strict)?
I would say replace only when encoding is Not set and inferred to utf-8. 

This should go back to 1.2.x Should a follow-up PR intentionally revert this PR for 1.3? Personally, I would want to know when `read_csv` fails to read certain characters (`errors = None` by default). I don't think that content from skipped rows should matter and it should raise no error if the rest of the file is ok. Maybe you could add a test withouth skiprows, this raises on 1.1.5 which is good and should keep raising I thought `errors` is exposed in `read_csv`. It isn't. In that case it makes sense to keep `'replace'` as the default.

I don't think it is feasible to ignore encoding errors only for skipped rows. (We could read everything in binary mode but we would need to decode it to determine line endings.)  This errors parameter is Not exposed  yes, it isn't exposed. Sorry, that is what I meant to say :) thanks @twoertwein  @meeseeksdev backport 1.2.x Something went wrong ... Please have  a look at my logs. Thanks