Hi! We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
But as we’re losing ad-revenue from this then why not make a donation towards website running costs?. Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
The 0 is inside so that 440 becomes 4-40. So I don't think it's that because it should be detected by rule 4 not 8. Also it is being said as 4404, ie it is not matching in the first place.
Also I've found that the ; at the end does not work correctly in all the other cases, when there is a street name.
So I think I'm stuck as far as this method goes. Without being able to replace 'M' with 'M ' to turn off \s.
Only other route would be avoid \s altogether. Which means using 'em', 'aa' and 'be' for road names. I know that works, but I had dropped it as the number of \Nx's was getting cumbersome. But even so it will mean 36 rules as I'll need 1 set for each of M, A and B. (Well actually a little less that 27, as I don't need to worry about 4 digit M roads.) Wonder how many it can stand? _________________ Go Premium X / Go 1005
Joined: Nov 27, 2005 Posts: 132 Location: Stroud, Gloucestershire
Posted: Wed May 26, 2010 5:48 pm Post subject:
I think the \Nx is probably a red herring, as the original US code had o rather than oh; It was replaced with oh to stop TT saying west (which was a by product of having o = west and w = west for french / canadian directions)
I've been playing with ohs, double ohs, hundreds and thousands...
What's the underline for, any idea? I couldn't see a pattern, so ditched that as well. ;-)
Hundreds and thousands can be dealt with same as 10-99, just pass it all in one parameter (\3 in your case I think) and let Kate et al sort it out. Saves a rule or 2.
I've made up my new \s free version, but not yet had time to test. 29 rules! _________________ Go Premium X / Go 1005
Joined: Nov 27, 2005 Posts: 132 Location: Stroud, Gloucestershire
Posted: Wed May 26, 2010 9:36 pm Post subject:
I think the underline tells it to say the numbers as separate digits rather than together, ie. 431 as \1 \2 \3 would be four hundred and thirty one, but \1_ \2_ \3 would be four-three-one.
I just left 1 - 99 out completely so kate sorts it out, just added hundred and thousand so that they arn't said as individual digits. All other 3 and 4 digit numbers are.
Yeah, that's what I thought. But just \1 \2 \3 achieves the same thing. So wondered if it was something else.
In same vein, I'm wondering how TT says "em" in A239M. Or the A for that matter. Perhaps the \s isn't really needed either???
Quote:
just added hundred and thousand so that they aren't said as individual digits
Agreed. But what I was trying to say was if you place them altogether in 1 parameter, then it would be, say, 4000 which would be said as four thousand. That's what I was doing with the 0 inside the parentheses. But I've just reminded myself that \\0 in preg_replace gives access to entire string, so there may be a chance to reduce all those cases which can be left to Kate to a single rule that replaces with \0... _________________ Go Premium X / Go 1005
Posted: Fri May 28, 2010 1:26 pm Post subject: Just an update
Not made any further progress on TT per se as I need my TT working this weekend , but have updated my app. You can now enter new rules and/or edit existing ones. (To delete one, just erase the rule.)
Each rule is tested against a static set of 15 commands, the last one of which is a nonsense command, just to ensure that you aren't passing everything! Matches are listed after each command. (You only want 1 match, unless we can determine that TT always takes 1st/last in case of a dup.)
Nothing is saved after you leave the app, but the suitably formatted .rex file entry is available at the bottom of the page to just cut-n-paste into TT.
The start point rule set is my latest from 2 days ago, with the semi-colon announced when road number without a road name is used to confirm a roundabout exit (as in "take the exit, A-3-2-5-;"), and 0 in any of last 2 positions of a 4 digit road number is pronounced TT style (as in A4404 is A-four-thousand-and-four, and similar for A4440, A4004 & A4400). I know cause of 1st issue, but the the 2nd as yet. _________________ Go Premium X / Go 1005
Joined: Apr 07, 2006 Posts: 249 Location: Kent , England
Posted: Sat May 29, 2010 4:54 pm Post subject:
mikealder wrote:
geddit wrote:
Or have I missed the obvious.
Quite possibly, the file you need to re-name is in the Western_Europe map folder and is called:
cphoneme.dat
Which you rename to:
cphoneme.old
The other part of the fix doesn't seem to apply to the European based devices as the file that MVL mentioned to add/ edit phrases in simply isn't present on a European machine - Renaming the file in the map folder though will make a noticable difference - Mike
Now I apologise in advance for the question I am about to ask , as I am sure that it is me being thick................but here I go anyway.
When renaming cphoneme ( which is a DAT file ) , do I rename it to cphoneme.old ( which is STILL a DAT file )
Because the way I read the above quote is that it is originally a DAT file but is then renamed to an OLD file.
Apologies again for this , but I just want to be sure that I am not going to cock something up. _________________ Keith
TomTom GO 730T App 8.392 (1909/091109) , W and CE 2GB v835.2419
You can rename it to anything - as long as you stick to letters and numbers plus . _ or - and not much else.
The idea is to fool TT into thinking that the file is missing/deleted without actually deleting it lest you wish one day to restore it.
The suggested name is so that you, not TT, isn't fooled when it comes to finding it again should you wish to do the aforesaid rename to its original name trick. _________________ Go Premium X / Go 1005
Joined: Apr 07, 2006 Posts: 249 Location: Kent , England
Posted: Sat May 29, 2010 5:18 pm Post subject:
layingback wrote:
You can rename it to anything - as long as you stick to letters and numbers plus . _ or - and not much else.
The idea is to fool TT into thinking that the file is missing/deleted without actually deleting it lest you wish one day to restore it.
The suggested name is so that you, not TT, isn't fooled when it comes to finding it again should you wish to do the aforesaid rename to its original name trick.
Thanks for that ! _________________ Keith
TomTom GO 730T App 8.392 (1909/091109) , W and CE 2GB v835.2419
Did a big test of TT changes today, made worse by travelling along a wilderness M road - the M3(!) - which is so far out in the boonies that it is totally void of RDS Traffic carrying stations, but which was filled to total capacity by vehicles.
But the voice worked as expected, just the semi-colon pronunciation getting a bit wearing on all the roundabouts on our off-M detour. SWHTBO seemed to find it quite amusing, and felt it "added something". But I do seem to have introduced a pause after "towards .... " which will need to be cured - once the cause has been located.
Will have to try a new technique or 2 that I've thought up, because having the road numbers read "correctly" was such an improvement. I didn't actually notice the road numbers being read at all, I just heard them. I guess they just seemed right. Normally the "3 thousand 4 hundred and ... " stuff just grates. _________________ Go Premium X / Go 1005
NP! Seriously though, what I do is rename to something like:
cphoneme.orig.dat
that I can recognise and easily convert back at any time down the road, without having to reference back somewhere to find out what it was originally called. _________________ Go Premium X / Go 1005
Joined: Nov 27, 2005 Posts: 132 Location: Stroud, Gloucestershire
Posted: Sun May 30, 2010 4:43 pm Post subject:
I don't seem to get the 'comma' problem, I think it is because I made the rules only look for the letters and digits - I removed the last ([^0-9].*) and put the 4 digit rules before the 3 digit ones.
As soon as a rule is met it seems to stop looking.
I get the older comma problem with your rules, so I suspect that it is due to another TT setting being enabled/disabled.
You reckon that first match is only match? I haven't tested, but will try to confirm your assertion, as this may potentially make some of the rules simpler. To date I've been working on 1 match per rule to avoid this. _________________ Go Premium X / Go 1005
Posted: Today Post subject: Pocket GPS Advertising
We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
Have you considered making a donation towards website running costs?. Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
Hi! We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
But as we’re losing ad-revenue from this then why not make a donation towards website running costs?. Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
Forum FAQ
Search
Usergroups
Profile
Log in for private messages
Log in
, but have updated my app. You can now enter new rules and/or edit existing ones. (To delete one, just erase the rule.)
Matches are listed after each command. (You only want 1 match, unless we can determine that TT always takes 1st/last in case of a dup.)
But I do seem to have introduced a pause after "towards .... " which will need to be cured - once the cause has been located.
