Updated beta version of Bet Angel v1.56.0 - Now on general release

[sniffer66]

When working with SV's imported from CSV how is Guardian dealing with foreign/special characters ? Circumflexes, accents etc ?

I've created a function to replace with standard encoding but some of the Russian characters I dont even have in my text encoding to create a replace with, therefore the pattern matching is failing between the CSV and Guardian

Seeing as BF don't use them at all in their selection naming is there any way you can pattern match with them in place in the CSV ?

[Bet Angel]

When working with SV's imported from CSV how is Guardian dealing with foreign/special characters ? Circumflexes, accents etc ?

I've created a function to replace with standard encoding but some of the Russian characters I dont even have in my text encoding to create a replace with, therefore the pattern matching is failing between the CSV and Guardian

Seeing as BF don't use them at all in their selection naming is there any way you can pattern match with them in place in the CSV ?

The characters used in the CSV will have to match the text used by betfair, or you could use a * wildcard to ignore the rest of the string. i.e. If you are only confident that the first seven characters in a name will match betfair before it stumbles over a special character then only use those seven followed by a * in the CSV.

[sniffer66]

When working with SV's imported from CSV how is Guardian dealing with foreign/special characters ? Circumflexes, accents etc ?

I've created a function to replace with standard encoding but some of the Russian characters I dont even have in my text encoding to create a replace with, therefore the pattern matching is failing between the CSV and Guardian

Seeing as BF don't use them at all in their selection naming is there any way you can pattern match with them in place in the CSV ?

The characters used in the CSV will have to match the text used by betfair, or you could use a * wildcard to ignore the rest of the string. i.e. If you are only confident that the first seven characters in a name will match betfair before it stumbles over a special character then only use those seven followed by a * in the CSV.

I'm scripting the CSV creation so it's finding the special character via script and chopping the string at that point that's problematic. I cant read a character thats not in my text format easily
Will the pattern matching match on multiple wildcards if I replace all special chars with an asterisk ? i.e Galánte to *Gal*nte*

[Atho55]

Could you do an Auto find and replace. Find the character and replace with nothing. I do it when comparing the Sporting Life ABC of runners to BF historical data.

[sniffer66]

Could you do an Auto find and replace. Find the character and replace with nothing. I do it when comparing the Sporting Life ABC of runners to BF historical data.

I believe the issue is there that Guardian will only match a single string, Galan with an accent on the a would become Galn, which wouldnt match against the selection name. If I replace with a wildcard "*" and there are more than one special character I dont think it will work i.e G*l*n

[Atho55]

You remove the character above the a, not the a itself.

F & R.jpg

Like so

[jimibt]

You remove the character above the a, not the a itself.

F & R.jpg

Like so

i think sniffer was possibly referring to ascii characters that have accents etc, i.e. à ã etc... there are libraries to do replacements, but not every locale is covered

[sniffer66]

You remove the character above the a, not the a itself.

F & R.jpg

Like so

i think sniffer was possibly referring to ascii characters that have accents etc, i.e. à ã etc... there are libraries to do replacements, but not every locale is covered

Yes, its the extended ANSI characters. Gonna try to create a lookup table on the ANSI codes and do a lookup/replace

[Atho55]

VLOOKUP will do it if the accent is not a character in its own right that can be removed.

[Bet Angel]

I believe the issue is there that Guardian will only match a single string, Galan with an accent on the a would become Galn, which wouldnt match against the selection name.

In that case you'd have to just say Gal* in the CSV file.
The best way would still be for you to convert all such characters into the characters that betfair uses before writing to the CSV, but the wildcard will be the quickest way to get it working with only a small risk of matching against other selections starting with the same text.

[LeTiss]

The new 'List' tab on Guardian is a sensational piece of kit

It's amazes me why any serious trader would spend money on other software.

Bet Angel is streets ahead of anything else

[Shaung89]

Is there a way with custom columns to have a 'free text column'?

I used to like making brief notes for things i'd seen as a reminder for when i came back to trade later, now the 'Excel Sheet' column (which i used to use) is a forced drop down and all the custom columns have to show preset info?

[sionascaig]

Left the Bang vs WI cricket match running on overnight and woke up to find the match "suspended" and no prices available in watch list although I could see prices on the main screen. Rebooted BA and market was running as normal. Not sure if this was just me or an issue with new version... I had bets taken at 3:49 so seemed to be working up till then...

[ODPaul82]

There was a planned outage on betfair which probably would have caused that

[sionascaig]

There was a planned outage on betfair which probably would have caused that

ah just noticed that - thks ODPaul )