| WAP multimedia message - WML page layout |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Petr |
Is it possible to change layout of WML page for WAP multimedia message (for example when I want to use another language or add another text etc.)? | |||
| Bryce Norwood - NowSMS Support |
Petr, We definitely could stand to do some work here to make the WML file more customisable. I can provide you with a way to translate the text of most of the prompts in the WML file, so that you can provide it in another language. But whatever translations you set will apply for all multimedia WAP push messages generated by the gateway (it can't simultaneously support multiple messages). It is possible to define translation text for the text prompts in the multimedia WAP push WML that is generated. You do this by editing the MMSC.INI file, and adding a [TranslateText] section to that file. Under that section, the following translations can be defined: Multimedia Message= Subject= From= Download image= Download audio= Download video= Download file= -bn | |||
| Petr |
Thanks Bryce, but translation text From doesn't work (only this maybe)... Will it be possible in final version better customization of WML page layout? | |||
| Bryce Norwood - NowSMS Support |
Petr, This is one of the strangest bugs that I've seen. I didn't have a problem with the "From" field not being translated. But I did notice that when this particular feature is used ... the first multimedia WAP push message that you send after restarting the service always uses the pre-defined English text strings! Any subsequent multimedia push messages use the translated strings. We should be able to get that fixed before the next update. We introduced this particular feature in the v4.20 release. At this point, we haven't planned any changes for it. I would like to see more customisation possible ... preferrably a user editable template. But we're not sure what the best way is to structure such a template. The problem has to do with how we include different types of links for different content files ... image being the biggest problem because we handle that differently from the other types. -bn | |||
