Inconsistent reference to menu entry navigation

I also don't care what we use, as long as it looks like some kind of arrow and do it consistently.
Why the plain ">"?
1 Even Apple use it in their documentation, e.g. from the Safari Help Page

Save an entire webpage: Choose File > Save As, then choose Format > Web Archive or Format > Page Source.

2 No funny characters that could trip up translators like the mini->> or →

I have added the other string currently using > to the issue description at the top, so that we have all known strings like this in one place and can change everything to whatever we decide on. I personally like the ≫ if we are not going for >, but I don't have strong feelings about it either way.

I found a bunch of extra strings by searching for ${MENUENTRY}:, e.g. File:
(some overlap - This contains the English, the Afrikaans translation (Where I already switched to > so they stand out on my end and I know that I have identified them, which will make it easier to change if we go with a different submenu-indicator char) and the stringno

File: Open | Lêer > Maak oop 3284
File: Save | Lêer > Stoor 3285
File: Save online | Lêer > Stoor aanlyn 3286
File: Save as | Lêer > Stoor as 3287
File: Save a copy | Lêer > Stoor 'n kopie 3289
File: Close | Lêer > Maak toe 3291
File: New | Lêer > Nuwe 3292

Not sure if I follow you
The pipe can be a menu navigation separator, e.g. File | New
however I have seen it more in the context of separating the high-level menu entries, e.g.
File | Edit | View | Add ...

Tried looking for occurrences of the pipe symbol in Transifex. There either (a) are none or (b) I was unable to get it escaped properly.

The reason there is a pipe, is because I added it for legibility in the output between source and destination languages, e.g. to turn
File: Save Lêer > Stoor 3285
into
File: Save | Lêer > Stoor 3285

The problem with / is it will create ambiguity since that character is already used for "or". Why reuse the same character when we have so many to choose from.
I understand the argument for menus being similar to a directory hierarchy, however
a) regular users do not think of it as a directory / hierarchy
b) the majority of users are on Windows meaning "\" would be a more representative delimiter.

In addition to the Apple help reference (using >) I provided above, I can also provide Microsoft as a reference, e.g.

https://docs.microsoft.com/en-us/style-guide/procedures-instructions/de…

#

> Use a greater-than symbol (>) to separate sequential steps.

Only use this approach when there's a clear and obvious path through the UI and the selection method is the same for each step. For example, don't mix things that require opening, selecting, and choosing.

Don't bold the greater-than symbol. Include a space before and after the symbol. Select Accounts > Other accounts > Add an account.

#

I have provided two references from some of the biggest IT vendors. As counter arguments I have seen various personal preferences which I have provided arguments against) and zero references to support those preferences.

Thanks Isaac.

Jojo - are you ok to do the PR? I will update the style guide.