Thanks Tom! I will do some experimenting.
Thanks Tom for the info. So I can embed the new variable but I'm not sure what value to set or how it would auto-update. Would you have any pointers? The only previous embedded variable was something like Variable_A = ${q://QID25/ChoiceTextEntryValue/1}
Hi, OPTION 1: USING SURVEY FLOW TO CREATE A BRANCH This might work? THe respondent will click a Spanish Survey choice which will direct him to the Spanish survey. 1. Create a spanish translation version of your survey. (Tools > Translate Survey > Add a Translation > Choose 1) Spanish EU or 2) Spanish Latam. THen translate.) 2. In the Project, create a new block above your main survey block. Name the "Spanish Selection" or something like that. 3. In the Spanish block, create a Multiple Choice question. 4. Set it to only ONE answer choice. 5. For the question, enter "For the Spanish survey, please click below:" 6. For the single answer choice, you can use something like "Spanish Survey" 7. In the Project tab still, in the top-left, click Distribution. 8. Click Anonymous link on the right side. You will then see the link for this survey. 9. Open Notepad (or Word but Notepad is cleaner since no formatting) 10. Copy that survey link and paste it into Notepad (or Word). 11. Now
BACKGROUND We wanted to display a footer that showed links to different web pages (But you can also set any other kind of footer text that you'd like.). We have different language translations of our survey, so we wanted the footer to show in the language matching the survey. WRONG SET-UP We had gone into Look & Feel > Old Editor > Advanced > Footer > EDIT. We then placed our link code and link label into the Source editor. The problem is that the footer is FIXED to English for all survey languages. To fix this would require coding/programming most likely. PROPER SET-UP STEP 1: Create a Footer Message Go to Library > Messages. Create a New Message and choose Look & Feel for the Type. Name the message "Footer". Create your link code in Source viewer for the footer. This ONE message will hold all language translations. So there is no need to create separate files for Footer-English, Footer-Italian, Footer-Chinese, etc. STEP 2: Add Translations to Footer Message Now th
TWIST #2 - My Survey 1 is setup in the Survey Options to be by Invitation Only. This seems to mean that I can not get an anonymous survey link. In this case, it means that HTTP Referrer Verification can't be used? So, we can't confirm that people who fill out the Draw Ballot actually completed or at least came from Survey 1?
TWIST #1 - Anyone know how someone taking Survey 1 in another language (e.g. French) could be directed to a French Ballot Entry in Survey 2? I just tried going through a French survey path in Survey 1 but got taken to the English Ballot Entry in Survey 2. I have made a French translation in Survey 2.
Hi Kate, thanks for the insight. Yes, part of the jiggle does seem to come from extra tags/formatting in the html. We copied some text from Word and pasted it into the Normal text entry box. Pasting directly from Word adds and unbelievable amount of junk html code. We've found the best way is to go directly into the Rich Content Editor to do any kind of editing (e.g. underline, bold, add extra line spacing. Doing it in Rich Content Editor creates the cleanest html code it seems. For example, if you hit enter for a new line in the Normal text entry box for the question area, it adds more DIV tags. If you hit enter in RIch Content Editor, it uses minimal BR tags. The other cause we found was from scripts in the header/footer. For example, we had a script that moved the Langauge Selector Box. So each time the page loaded, it jiggled things left-right. We've now had help updating that code and there is no more jiggle! SUMMARY - to remove jiggle with page changes 1. Check/test the scr
Hi Tom, Thanks, that worked! Summary for others: (See script Tom posted on Dec.19 - Accepted Answer) * Setup: The survey has other language translations. Page/screen 1 is the landing page showing a welcome message (e.g. Welcome to the ABC satisfaction survey) with a page break after it. By default the Language Selector Box shows in the top-right. * Tom's script moves the Language Selector Box down to the bottom-right, BELOW the next/continue button to advance to the next page/screen. * This script also has an added feature. When you click Next/Continue to advance to the next page, the next page will NOT show the Language Selector Box anymore. How the script works is that the DIV tag at the top, pushes the Language Selector Box out of view. The other code makes it so that only Page/Screen 1 shows the Language Selector Box. This code worked for our needs, especially since we have page breaks every 1 or 2 questions. We also code the Contact List recipients with a primary language code
Hi Tom, Thanks, I'll try that. I am lacking in coding skills. Should I put the div tag outside the script or inside? Should I wrap the function or not? Which of the 4 below? Thanks 1) (div style=height 200px)</div)(script>fcn(/script) 2) (script)(div style=height 200px)(/div)fcn(/script) 3 (script) fcn (div style=height 200px)(/div) fcn end(/script) 4) (script) fcn (div style=height 200px)(/div)(/script)
Hi NiC, Actually, I don't want to hide it. Ideally, I would like the language selector box to show below the Next button on the first page, but then disappear for all other pages. With that likely being difficult, I'd like the Language Selector Box to show below the Next button for all pages. But right now, it flashes for a split second on each page and disappears, which doesn't look very good.
Thanks BStrahin for putting the files together! I'll have a look.
Thanks Pat, I experimented with the Branching that you suggested. It worked quite well. I used an upfront question for them to select En, Fr, Ch. The branching question then took them to the appropriate Language block. The one hiccup is that if you Force a Response, for example, the error messages that pop up are still in English. I would imagine that all error messages would be in English. Thanks Bstrahin, that sounds like a nice set-up but on a pro level that we fresh-on-the-scene newbs would feel a little intimidated by. Also this would mean that we would need to create 1 survey for each language (with same survey layout) right, and then combine them all later? I think we are trying to reduce/avoid having to do any post-data manipulation. By the way, how can we find out the survey links for each project?
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
