Re: Weirdness with account title in register window
Kobac <slatus@*delete_this_part_to_reply*optonline.net>
| Newsgroups | alt.comp.software.financial.quicken |
|---|---|
| Organization | A noiseless patient Spider |
| Message-ID | <[email protected]> |
On 09/20/2023 14:33, John Pollard wrote: > On Tuesday, September 19, 2023 at 6:38:24 PM UTC-5, Kobac wrote: >> On 09/19/2023 19:32, Kobac wrote: >>> A little while back, I changed all of the account names in my Quicken >>> file to include an em dash (using ALT+0151 on my keyboard) as opposed to >>> a regular dash because it just looked better when looking at the account >>> names in the account bar. >>> >>> Today I was in Quicken and noticed that any account name that had the em >>> dash in its name had been truncated in the upper left of the register >>> window, with the last 3 characters of the account name being replaced >>> with an ellipsis (...). Name length did not appear to be a factor since >>> it happened even with accounts containing only ten characters, including >>> spaces. I started changing the em dashes back to regular dashes and the >>> full account names then appeared in the register window. > >>> Has this happened to anyone else > > I can reproduce it in 552.20 and R50.16. It also happens in Q2017 ... but not in Q2013. > >>> and does anyone know *why* this happens? > > Not really. > > Quicken may not even realize that it is happening or why. > > Or perhaps they intentionally changed the way they processed > characters in the account register row that holds the Account Name > and the Account Action Bar - thinking no one would be using (or > needing to use) undocumented ascii characters in their account names). > > An en-dash does not exhibit the problem in any of > the above Quicken versions. > >> I should mention I'm using the latest Quicken version 27.1.52.20 >> under Windows 10 Pro version 22H2. > > I'm using the same Windows version. > > Since the problem is easy to reproduce; I suggest you create a > Quicken test file with one account that demonstrates the problem. > Then use the Quicken Help > Report a problem feature to tell > Quicken about the problem - and send the test data file with the > report. Don't expect an answer from Quicken. Thanks, John. I think I'll set up that test file and send it to them.