Text Changes on Waypoints Text Name

[Lluis Arasanz]

Hi!.

First, I suppose this message goes here... but if I'm wrong, please, change to correct location.

Second... English is not my primary language, so, please apologies for incorrect orthography and grammatical mistakes.

Now, going to share my "problem": I use text name on Waypoint to put info about route as, exit names, next road name, go write or left and so on. I show a capture with an example:

As you can see I'm trying some differents ways to mark directions. On Planner characters are shown perfect, but....

whe I see this same text on Navigator (next) or in Waypoint list on Planner.... some characters changes:

the change of "-->" to "--&gt" only happens if I use 2 dash before, and only with '>'...

Is not a great Inconvenient,'cause now I'm trying to use "emoticons" and those works also very well although they are more difficult to "write".

Is a normal behavior that must be in mind when writing?

Thanks for reading and apologies for mistakes.

Regards

[Rob Verhoeff]

@Lluis-Arasanz Why do you want to include the direction of the route in the name of the waypoint? When you navigate the route, won't you be guided by the directions provided by the navigation itself? or am I missing something?

[Lluis Arasanz]

@Rob-Verhoeff

Navigation works fine and routing is perfect.
But I use as a extra info where I put the Way point: something to look, the correct way to follow, the road name...
These extra info helps and complements routing info.

Of course, the main idea of the post is about character coding changes in some situations.

Best Regards

[Con Hennekens]

@Lluis-Arasanz, I think you are stressing the boundaries of ANSI characters and codepaging... It is a really good idea to stay away from non-standard characters ALWAYS. It always bytes (pun intended ) you in the ass sooner or later.

[Lluis Arasanz]

@Con-Hennekens
Hi... I do not think that a '>' character was going to the limits of ANSI. also, characters beyond ASCII 127 works fine.

It seams more a html coding that changes meta identifiers "<>" to avoid confusion with '<' or '>' using other form of representation "&gt ;" (I forced separation of t and ; with a white space to show code)

Even ... Emoji characters work better tan text ones! but are difficult to write on website (is easier on mobile app).

Best Regards

[Herko ter Horst]

@Lluis-Arasanz said in Text Changes on Waypoints Text Name:

the change of "-->" to "-->" only happens if I use 2 dash before, and only with '>'...

That looks like an HTML-encoding bug in the specific locations where the > is shown. This should be relatively simple for the devs to fix.

[Con Hennekens]

@Lluis-Arasanz, no the > character in it self not, but what it turns into (the blue bordered arrow) does. I always restrict myself to characters that are allowed in (window) filenames. Often things like ', ", [ or other characters my interfere with behind the scene translations, or pose a problem while exporting and importing things later.

[Hans van de Ven MR.MRA]

@Lluis-Arasanz

Use colored route or via points and fill in the note at the route point. This will be shown in Navigation (Next)
Simply enter the name of the point at the route point name.
You can add 512 characters in the notes

[Lluis Arasanz]

@Hans-van-de-Ven-MRA-Master

Hi, This will be second part. I'm trying both WP Name and text to see what is better for Next use.

so... problem with "-->" code on WP name can be resolved by other way.

Thread closed.

Thank's to all for info