A line break is a non-printable character. So it would only work in the scope of electronic storage. The minute it hits other media, the line break character is subject to how that media handles its presence, and then it is lost permanently from that step forward.
Plus, many input forms make use of validation that will just trim anything that isn’t a character or number, removing the line break character.
Corporate cuts should always start with the greatest fat that does the least work - the ones at the top.
Because if the company has found itself in a place where headcount needs to be reduced, these are the people who led it there and deserve all of the blame for hurting the company to that degree. Plus, you should always start cutting where you get the lowest volume of productive work for the greatest money spent, and that is always at the top.
Scottish/Irish?
Which kind of apostrophe?
A straight apostrophe, fine - that can and does get used in valid SQL injection attacks. I would be disgusted at any input form that didn’t sanitize that.
But a curly apostrophe? Nothing should be filtering a curly apostrophe, as it has no function or use within SQL. So if you learn how to bring that up in alt codes (Windows, specifically), Key combos (Mac) or dead keys (Linux), as well as direct Unicode codes for most any Win/Mac/*Nix platform, you should be golden.
Unless the developer of that input form was a complete moron and made extra-tight validation.
Plus, knowing the inputs for a lot of extended UTF-8 characters not found on a normal keyboard is also a wee bit of a typing superpower.