IdahoMtnSpyder
Active member
It appears BRP has just in the past few days discontinued making available downloadable PDF copies of instructions. All the links on the search results page from this page, https://instructions.brp.com/e-instruction.html#tab=1, all go to individual web pages for the individual instructions. The change even includes instructions for accessories that have not been available for years, such as the CB radio for pre-2018 RTs. I believe one of the reasons for the change is to make other language translations readily available without having to store individual translated copies on the BRP servers. The translation is instantly available by selecting a language from the language drop down box.
This change causes a significant issue for SL forum users. Once you are on the instruction page and want to post a link so others can go there, the usual practice is to copy the entire URL shown in the browser address box. Unfortunately, the address of every instruction page ends with "&googtrans(en|en_US)." This last phrase causes the SL forum edit box software to delete the address from the post.
Changes need to be made to the SL forum message editing software to permit a URL ending with "&googtrans(en|en_US)" to not be deleted. If this change isn't made there will be many frustrated forum members when their attempts to include links to instructions are thwarted.
The SL webmaster states that since the url ends with &googtrans(en|en_US) it is an invalid URL and that is why it gets deleted. Here is why I unequivocally state a URL ending in &googtrans(en|en_US) is a perfectly valid URL, not an invalid one.
1. The URL is generated by the BRP search engine. That search engine absolutely would not generate an invalid URL because then the subject web page would not open up.
2. When the URL in the address box of the instruction page is copied and pasted into a new browser window the page opens right up. It would not do so if the URL was invalid.
3. The instruction page contains a button to email a link. That button opens up a new email message page in your default email program. The link that is automatically inserted by the BRP web site into the email body contains the above ending. When that email is received by another user and he clicks on the link, it opens up the instruction page. Again, that would not happen if the URL is invalid.
This change causes a significant issue for SL forum users. Once you are on the instruction page and want to post a link so others can go there, the usual practice is to copy the entire URL shown in the browser address box. Unfortunately, the address of every instruction page ends with "&googtrans(en|en_US)." This last phrase causes the SL forum edit box software to delete the address from the post.
Changes need to be made to the SL forum message editing software to permit a URL ending with "&googtrans(en|en_US)" to not be deleted. If this change isn't made there will be many frustrated forum members when their attempts to include links to instructions are thwarted.
The SL webmaster states that since the url ends with &googtrans(en|en_US) it is an invalid URL and that is why it gets deleted. Here is why I unequivocally state a URL ending in &googtrans(en|en_US) is a perfectly valid URL, not an invalid one.
1. The URL is generated by the BRP search engine. That search engine absolutely would not generate an invalid URL because then the subject web page would not open up.
2. When the URL in the address box of the instruction page is copied and pasted into a new browser window the page opens right up. It would not do so if the URL was invalid.
3. The instruction page contains a button to email a link. That button opens up a new email message page in your default email program. The link that is automatically inserted by the BRP web site into the email body contains the above ending. When that email is received by another user and he clicks on the link, it opens up the instruction page. Again, that would not happen if the URL is invalid.
) thing to make changes to the Forum Software at developer or at site level. At least if the developer does it, then it'll probably be incorpororated in any upgrades/new versions; but any change made to the Forum platform, even if it seems to be just a minor change, requires exhaustive (& expensive) testing to make sure it doesn't impact anywhere else, and there are many thousands of lines of code to go thru/processes to ensure aren't impacted - and all that will then need to be repeated with every fix &/or update that's made to the platform software ever after!! So unless you want to pay for it, (and it'll cost A LOT) then it's not something that'll happen quickly, if at all!! :lecturef_smilie:
); only once it gets coded, then it needs to be developed & tested within its particular module for functionality & passed back if any issues are detected (usually that involves at least a few iterations); released to be tested for inclusion on the platform; tested for integration with the entire system (& possibly passed back for changes, rinse, repeat); included in the next system update & scheduled for eventual release with the next update &/or issued as an interim fix; and then finally put to work in the real world, where even more 'undocumented features' are discovered very often!! :gaah: 
