Carriage returns break notes on connected accounts

I’m loving the notes feature on connected accounts. :hot_coral_heart:

But unlike native Monzo transactions line breaks don’t work :broken_heart:

I’m on Android. Are iPhone users (and other Androiders) seeing the same problem?

1 Like

I don’t know if I have a bad case of the frequency bias, but carriage return, Peter? :face_with_raised_eyebrow:

Is there a reason folks are starting to use this archaic typewriter term over the simpler return or the modern line break or new line, or am I just seeing you contribute to a pattern that isn’t there?

Yes this happens on iOS too.

And we also know who to blame now. Don’t we @bee? :wink:

Don’t forget to vote on your bug @Peter_G !

1 Like

Thanks for confirming!

I’m not sure it’s ever gone away? :eyes:

1 Like

Until just the past week, I don’t think I’ve seen anyone use that one ever at all in the last few decades!

1 Like

My boss said “there’s a carriage return needed here” and I had absolutely no idea what he meant till he explained it.

Not commonly used, but cool none the less.


I’m not old enough to be the typewriter generation but it’s probably gone a bit the way of cassette tapes - ununderstanderable by the youth!

1 Like

First part time job I went for while a student needed me to demonstrate how many words per minute I could type on a traditional typewriter. I can’t remember how many words it was but I got the job.


There are two ASCII codes relevant for a ‘return’. If you press return on a Windows computer it usually generates CR and LF (carriage return and line feed) and on a Unix (or Linux) box it will be just LF. (For completeness I think the Mac just uses CR).

On the old teletype computer terminals, CR would send the cursor back to the beginning of the line and LF would move the paper up one line.

So, even nowadays, you’ll find many systems engineers will commonly refer to carriage returns and line feeds when talking about text formatting.


Narrator: upon learning this, @N26throwaway referred exclusively to carriage returns for as long as they lived.


Nah! Too archaic for me! I’m hippier than a teenage roadman! :sunglasses:


I thing the mac using CR was a legacy thing from the old system 7 days… OSX is unix based so will primarily use LF even for its system files.

Windows remains the outlier…

I’m having this problem at work. New system installed. Users copying and pasting into the user interface - sort code, account number, account name, reference. CR/LF getting into the database fields and then into bank payment files, causing payments to fail at the bank.

Supplier claiming it can’t be a problem because they can’t “see” the characters. Trying to explain they’re control characters and not visible to the naked eye. Wondering what they teach supposedly technical people…

Even after using a programmer’s editor with “Show all special characters” on to demonstrate, they can’t get their head around it.


Yes, the CR alone was pre-OSX. OSX is BSD Unix so LF, as you say.


1 Like

I’m stunned. A little input validation would surely solve this issue in minutes. There’s probably a solution in Perl somewhere on Stack Overflow.

1 Like

I’ve suggested several areas they could apply a solution (and you’re right, the best would be to prevent this at input). It’s years since I was on the technical side but this should be basic stuff.

1 Like