Go Back   MarcomCentral (PTI) and FusionPro User Communities > Software-Related Talk > The JavaScript Library > Formatting Text

Notices

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old March 8th, 2019, 08:20 AM
dml1280 dml1280 is offline
Forum n00b
 
Join Date: Apr 2016
Posts: 8
Default Ampersand doesn't work when changing to uppercase

I have already figured out that some fonts won't display the "&" when using "ToUpper". So when I have the issue I use <uppercase></uppercase>.

It works when composing the file, but this time it's changing the "&" into the HTML value when used in MarcomCentral.
What should I adjust?

Here is my rule:
Code:
if (Field("Title Line 1") == "")
    return "";
    
else return '<uppercase>'+Field("Title Line 1")+'</uppercase>';
Here is a link to the screenshot of the output in Marcom
Link to Screenshot

Last edited by dml1280; March 8th, 2019 at 08:55 AM..
Reply With Quote
  #2  
Old March 8th, 2019, 10:21 AM
Dan Korn's Avatar
Dan Korn Dan Korn is offline
FusionPro Senior Engineer / Forum Moderator
 
Join Date: Aug 2008
Location: Chicago, IL
Posts: 4,293
Default Re: Ampersand doesn't work when changing to uppercase

So first, questions like this which are specific to MarcomCentral should really go in the MarcomCentral sub-forum.

Anyway, this is a frequently-asked question. The reason for the ampersand difference is because MarcomCentral generates tagged markup data files, where the ampersand is a control character denoting an entity, while most FusionPro jobs in Creator (Acrobat) use flat-file data, where an ampersand has no special function. Fortunately, FusionPro has a TaggedDataField function designed to handle this properly in both types of data. This rule should do what you want, in both local Creator compositions and in online MarcomCentral compositions:
Code:
return '<uppercase>' + TaggedDataField("Title Line 1") + '</uppercase>';
__________________
Dan Korn
FusionPro Developer / JavaScript Guru / Forum Moderator
PTI Marketing Technologies | Printable | MarcomCentral
LinkedIn

I am a not a Support engineer, and this forum is not a substitute for Support. My participation on this forum is primarily as a fellow user (and a forum moderator). I am happy to provide help and answers to questions when I can; however, there is no guarantee that I, or anyone else on this forum, will be able to answer all questions or fix any problems. If I ask for files to clarify an issue, I might not be able to look at them personally. I am not able to answer private messages, emails, or phone calls unless they go through proper Support channels. Please direct any sales or pricing questions to your salesperson or inquiries@marcom.com.

Complex template-building questions, as well as all installation and font questions or problems, should be directed to FusionProSupport@marcom.com. Paid consulting work may be required to fulfill your template-building needs.

This is a publicly viewable forum. Please DO NOT post fonts, or other proprietary content, to this forum. Also, please DO NOT post any "live" data with real names, addresses, or any other personal, private, or confidential data.

Please include the specific versions of FusionPro, Acrobat, and your operating system in any problem reports or help requests. I recommend putting this information in your forum signature. Please also check your composition log (.msg) file for relevant error or warning messages.

Please post questions specific to the MarcomCentral Enterprise and Web-to-Print applications in the MarcomCentral forum. Click here to request access. Or contact your Business Relationship Manager (BRM/CPM) for assistance.

Please direct any questions specific to EFI's Digital StoreFront (DSF) to EFI support.

How To Ask Questions The Smart Way

The correct spellings are JavaScript, FusionPro, and MarcomCentral (each with two capital letters and no spaces). Acceptable abbreviations are JS, FP, and MC (or MCC). There is no "S" at the end of "Expression" or "Printable"! The name of the product is FusionPro, not "Fusion". "Java" is not is not the same as JavaScript.

Check out the JavaScript Guide and JavaScript Reference! FusionPro 8.0 and newer use JavaScript 1.7. Older versions use JavaScript 1.5.

return "KbwbTdsjqu!spdlt\"".replace(/./g,function(w){return String.fromCharCode(w.charCodeAt()-1)});
Reply With Quote
  #3  
Old March 8th, 2019, 11:45 AM
dml1280 dml1280 is offline
Forum n00b
 
Join Date: Apr 2016
Posts: 8
Default Re: Ampersand doesn't work when changing to uppercase

Thank you, that worked like a charm!
Reply With Quote
  #4  
Old April 9th, 2019, 02:19 PM
gdellaiera gdellaiera is offline
Regular Contributor
 
Join Date: Nov 2016
Posts: 78
Default Re: Ampersand doesn't work when changing to uppercase

I too am having the exact same issue (only in WebCRD). But when I check the box for tagged text I get the &amp & if its unchecked I get the entire line of code above (I thought it would work -_-).

If I use the preloaded XML rule for all CAPS, it blanks out the '&' completely.

I've also tried the below code (from another post)

function NoBreak(s)
{
return s.replace(/&amp;/g,'&').replace(/ /g, "&nbsp;");
}
return NoBreak(TaggedDataField(“Department”));


Am I going crazy here? Thanks for the look
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 01:47 AM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
(c) 2011, PTI Marketing Technologies™, Inc.