Editing Tag Text in PSE 13

I migrated from PSE 9 to PSE 13. I had text which described each tag. How do I access and edit this text using PSE 13? Using PSE 9, I right-clicked the tag and selected Edit. All text appeared. Using PSE 13, only the name appears for editing.

Michael,
Thank you for responding. Perhaps the definition of objects has changed. Using PSE 9, I created tags within three categories: People, Places, and Events. For each People tag, I created Notes which defined information about that person; e.g., when and where they were born, when and where they died, who were their parents, names of their children, etc. These tag categories and names migrated to PSE 13 correctly, but I can see nor edit any of the notes associated with them. Where did all of that information go when I migrated to PSE 13?
In PSE 13, I can create and edit Notes associated with Categories and Sub-categories. But they do not contain the tag information from PSE 9. oes PSE no longer support Notes for Tags?
Gary

Similar Messages

Keyword tags text box poorly designed, crashes PSE 8

I was very interested to see that PSE 8 allows you to enter keyword tags using a text box, as other programs do, promising much faster tagging with large sets of tags. But the feature has serious bugs rendering it unusable.
After trying the keyword-tags text box for less than a minute on my large catalog with 426 tags, PSE 8 crashed.    Even with a fresh catalog and the default tag categories, it will crash after using the text box about 40 times.   (See below for a recipe.)
Another bug concerns tags with commas in them, e.g. "Truckee, CA" (I have a couple hundred such Place tags). If you type "Tru" in the text box, select the tag with the mouse, and hit enter, PSE 8 will create two new tags, Truckee and CA, in the Other category, and apply them to the photo.
A design misfeature: After you select and apply a tag with the text box, it loses the keyboard focus. So to select another tag for the same photo, you have to move your hand to the mouse and click in the text box again. Partially defeats the whole purpose.
Recipe for reproducing the bug:
1. Create a new catalog.
2. Import 50 photos.
3. Select the next photo.
4. In the keyword tag text box, type "p" and then enter.
5. Go to step 3.
On the 40th or 41st photo, my PSE 8 reliably crashes (Vista 32, 4 GB of memory).   If after step 1 you use the Keyword Tags > + > From File command to load a tag heirarchy of 210 tags (see the attached file), it will crash after just 9 photos.   And with 426 tags, it crashes after 5 photos.
Interestingly, on my Vista 64 system (unsupported by Adobe, 8 core x 2.7 GHz), PSE 8 doesn't crash, but the text box gets unusably slow very quickly. WIth 210 keyword tags in the catalog, it soon takes about 12 seconds to find a tag after you type a unique prefix.   That time gradually gets longer the more you use the text box. With 426 tags, it takes almost 20 seconds to apply a tag using the text box.
On both systems, it's clear what the nature of the bug is: Each time you use the text box, the process's memory grows by many megabytes. I believe my Vista 64 system doesn't crash (at least not immediately) because it provides 3.5 GB of memory for use by PSE 8, while Vista 32 only provides about 1.5 GB.
I'm getting a sinking feelilng...

Is the white triangle to the left of "Keyword Tags" pointing down or pointing to the right? See this screen shot:
Click on the white triangle -- does that make a difference?
If not, try deleting the Organizer's preferences:
http://www.johnrellis.com/psedbtool/photoshop-elements-faq.htm#Delete_the_Organizers_prefe rences

How to avoid sorrouding p tag added by the default text component on editing a text in a page

We are using Default Text component(foundation/components/text) within a CQ5 Page. The text component is automatically adding a tag surrounding the text in the text area. We would like to control this behavior of auto addition of the tag in the text component. Please suggest us a solution to avoid the tag around the text.
Here is the brief backgroud- We are doing a migration of html pages into CQ5. The editable sections of the page are converted to CQ5 Text components with in the page. While we are creating the page from the backend, we are not adding the tag surrounding the page. However after creating the page, if users goes to the page and edits a text block within a page, the additional tags are getting added which is disturbing the styling.
Let us know if we need to provide more information on this.
Thanks & Regards,
Vamsi

Hi Vamsi,
I am facing same kind of issue.
As of now I am thinking of overritng the css applied by this tag.
If this p tag is fallowing same strucute then though of putting reqular expression to catch hold of this tags on the page.
Some thing like it always creates with id



Do you have any better approach..

Tagged text export unicode

hi,
is there any possibility to set the ITaggedTextImportPreferences before exporting to a tagged text file with an IExportProvider?
i need to export it in Unicode, but default is ASCII.
best regards

As far as I can tell, this isn't a new bug in as much as InDesign CS3, CS4, CS5 and CS5.5 (Mac) all exhibit the same problem exporting soft-returns in Unicode encoded Tagged Text where they are replaced with hard returns on import. Unfortunately it appears that we may be the only ones that care and thus it's unlikely that Adobe will fix it (unless someone adopts it as a JDI bug).
Update: after testing some more it appears this is an export bug for Mac OS-only. In other words, if you use a PC to export a story that contains soft-returns to Tagged Text (Unicode), the soft-returns are preserved when placing into a document using a Mac. And vice-versa, using a Mac to export a story with soft-returns to Tagged Text (Unicode) and then placing this into a document using a PC exhibits the same substitition of soft-returns for hard-returns.
Message was edited by: Caleb Clauset

Linked Adobe Tagged Text files importing without styles

I have several data-heavy weekly publications where suddenly, the link to all Adobe Tagged Text format files have the proper paragraph styles and character styles stripped on being placed. I'm aware of the default settings issue, where you deselect all and make sure the character styles is none, and that does not seem to be the issue. Specifics are
Working in CS 5 (Version 7.0.4)
The Adobe Tagged Text format files are exported from Excel spreadsheets
The InDesign documents have links to the Adobe Tagged Text format files, and Update Link is used inside InDesign to update the text when the file is exported from the spreadsheet.
When the publications are opened on my workstation, ALL files linked to Adobe Tagged Text files are not imported correctly, they revert to the Basic Paragraph style.
These are not new documents I'm designing or new Adobe Tagged Text files, this is part of a production process that has worked without issue for years.
When the same documents are opened on another workstation, and Update Links used, they come in perfectly, so it doesn't seem to be a document or file corruption problem, but a problem with my environment or ID settings.
It's not one specific document or file, it is every single document that has a link to an Adobe Tagged Text file (and we have lots, I tried several!)
I've opened the text files in the text editor to check them, but as I mentioned: same document, same files, I'm the only one who can't update without stripping out the styles.
Thanks! Nancy

Hi, Peter! Thanks for the response. Yes, it's really Tagged Text. See below. After exporting from the spreadsheet and database, opening the document in InDesign, and selecting update link, we do no editing in InDesign after the fact because everything is already setup exactly as we want it with the Tagged Text format.
I have literally hundreds of these among several different documents, updated weekly, mainly dealing with prices and numbers. Every one of the links to Tagged Text format files in every publication now strips out the Tagged Text paragraph style and character style formatting on Update Link on my workstation only. On my other two workstations, the links update without issue, and everything is correct in the final document.
So I'm beginning to think I need to look at rebuilding something, maybe as Joel said, replacing preferences. I keep looking for a workstation or ID option that might effect this.
<ANSI-WIN>
<vsn:6><fset:InDesign-Roman><ctable:=<Black:COLOR:CMYK:Process:0,0,0,1>>
<dps:Pnl Comp\:Pnl Comp \$Numbers=<Nextstyle:Pnl Comp\:Pnl Comp \$Numbers>>
<dps:Pnl Comp\:Pnl Comp Bold \$Numbers=<BasedOn:Pnl Comp\:Pnl Comp \$Numbers><Nextstyle:Pnl Comp\:Pnl Comp Bold \$Numbers>>
<dps:Pnl Comp\:Pnl Group \$Numbers=<BasedOn:Pnl Comp\:Pnl Comp \$Numbers><Nextstyle:Pnl Comp\:Pnl Group \$Numbers>>
<pstyle:Pnl Comp\:Pnl Comp Bold \$Numbers> $302 $302 $278
<pstyle:Pnl Comp\:Pnl Group \$Numbers> 203 202 211
<pstyle:Pnl Comp\:Pnl Group \$Numbers> 456 458 393

Exporting Table from Indesign to tagged text.

Hi, all! I need to export table from InDesign to tagged text by the script. I found ExportAllStories.jsx in samples. It's good example but I have some questions 1. In my document more then one table and I need to export only some of them. So, how can I export only one of them? May be Tables have some "labels" or something other differential sign? 2. How can I ser encoding type of distanation file (by the default InDesing set <ASCII-WIN>, but I'm need to set <Unicode>).

Edit>InCopy>Export All Strories.
Open the INDD in InCopy.
This assumes everyone involved has access to the files.

How I generate index markers using Applescript and tagged text!

One of the challenges I've faced in automating the book making process using Applescript with inDesign is that there don't seem to be any AS commands for making new index markers (anyone please correct me I if I'm wrong about this).
I've tried various js scripts which do an OK job, but they don't make the actual native markers. This means you have to wait until the book (consistiing of multiple ID files) is complete (so that all the page numbers have been established) to generate the index.
Recently, I read a tweet from someone with a link to a technique which uses tagged text and find and replace with GREP to edit the tags, inserting the tagged text index tags in the text file and then re-placing the text file in the ID page. In itself, this works great. But I'm dealing with literally thousands of separate text frames, none of them connected in a story.
The books typically consist of around 1200 pages with almost that many people, each of whose names I need to index with "Lastname, Firstname" references. And those particular strings don't (can't) appear anywhere on the pages. There will also be about 50 ID files all combined into one book. So it is imperative that I have ID generate the native index markers. To help keep things straight and efficient, I'm creating separate small text frames to hold the lastname, firstname strings. I created an object style for these frames which sets the attributes to "nonprinting", and I place the frames in the margin.
Then I realized that I don't actually have to have ID export the tagged text files for each. I exported one prototype and copied its tags to properties in my script, and then I concatenate them with the respective list item values I import from the database.
At the proper point in the page building script, I tell "textwrangleer" to make a new document, set its contents to the index string for the current record, save it to disk, overwriting the previous one, and then tell ID to "place" it in the index text frame, which generates the ID index mark.
I actually got an AS error when I first tried this: "file doesn't exist" or some such. Then I realized that the "place" command was happening too soon, so I inserted a .5 sec delay in the script, and it worked.
This is actually my first major script for actual work, and I'm so excited about it! I promises to cut production time down to about a thenth of what it was.
I still have to add some logic to branch between handlers with slightly different parameters for five different page formats, but the same page building handler will work on all of them.

A note on this:
Daniel Swanson wrote:
I've tried various js scripts which do an OK job, but they don't make the actual native markers. This means you have to wait until the book (consistiing of multiple ID files) is complete (so that all the page numbers have been established) to generate the index.
These scripts typically search for words and immediately write out the page numbers they are found on -- one shot indexing.
The solution is to add both the topic and its page reference to the current document's index:
if (app.activeDocument.indexes.length == 0)
app.activeDocument.indexes.add();
app.activeDocument.indexes[0].topics.add(app.selection[0].contents).pageReferences.add(app.selection[0]);
The first lines only make sure there is an index to add to (per default, a new document has none).
The last line adds a selected word to the index (it must be a plain text string, hence the use of its 'contents'), and then adds a reference to the selection in the text itself.
Adding the same word a second time will for a change (quite untypically for ID's Scripting) not result in an error but simply add another page reference to the existing one.
When doing this in a loop: remember to work backwards, because the index marker itself gets inserted into the running text, and that will throw off your text indices.

Importing Adobe Tagged Text

Hello,
So here's what's happening…
I've installed a Wordpress plugin that exports posts as Adobe Tagged Text.
When I import, the text still shows up marked up with tags, just as it looks in the .txt file:
<ANSI-MAC>
<DefineParaStyle:NormalParagraphStyle=<Nextstyle:NormalParagraphStyle><cColor:Registration ><cSize:10><cLeading:11><pFirstLineIndent:12><cFont:Times New Roman>>
<ParaStyle:NormalParagraphStyle>This <cTypeface:Italic>is<cTypeface:> a <cTypeface:Bold>test<cTypeface:>
<ParaStyle:NormalParagraphStyle>Test paragraph
<ParaStyle:NormalParagraphStyle>Testing this out
Does it have something to do with the first line of code, <ANSI-MAC>?
Regards,
Eric

You're using a very old InDesign workflow which I've never used. But it's referenced in Olav Kvern's and David Blatner's excellent "Real World InDesign" (I'm looking at the CS4 edition).
On page 235, it reads, "The first characters in a tagged text file must state the character encoding (ASCII, ANSI, UNICODE, BIG5, or SJIS), followed by the platform (MAC or WIN). So the typical Windows tagged text begins with <ASCII-WIN> , and the Macintosh version begins with <ASCII-MAC> ."
It looks to me like it should work. Have you tried exporting some tagged text from InDesign to see how it looks? File > Export > Adobe InDesign Tagged Text.

Tagging Text in a document

Hey all,
I haven't used swing in a while. Here is my problem:
A user can view a document at a time. The document is tagged with <begin><end> tags. I would like to process the document and show text between <begin><end> highlighted. The user can remove any tagged text by right clicking and clear. Also the user can add new tags by simply highlighting.
e.g.
The quick <begin>brown fox<end> jumped over the <begin>lazy dog<end>.
brown fox and lazy dog would be pre-highlighted when the doc is loaded.
Has anyone done something like this before in swing? Any help would be great to get started. Thanks.

1. <begin><end> is not proper XML and is thus a bad idea. Use <highlighted></highlighted>
2. Better yet, just use the html tags for setting the background color (check out )
user12374594 wrote:
Hey all,
I haven't used swing in a while. Here is my problem:
A user can view a document at a time. The document is tagged with <begin><end> tags. I would like to process the document and show text between <begin><end> highlighted. The user can remove any tagged text by right clicking and clear. Also the user can add new tags by simply highlighting.
e.g.
The quick <begin>brown fox<end> jumped over the <begin>lazy dog<end>.
brown fox and lazy dog would be pre-highlighted when the doc is loaded.
Has anyone done something like this before in swing? Any help would be great to get started. Thanks.Edited by: tjacobs01 on Jul 18, 2011 11:08 AM

Need help with creating text anchors with tagged text.

Can anyone tell me how to determine the correct value for a "Hyperlink Dest Index" value?
I have a script which creates a tagged text file that specifies about about 280 pages of tables (thank heavens for autoflow) , and would like to add live links between different parts. I can create a text anchor and a hyperlink to it in InDesign. The tagged text definition for the link source is simple and in-line and exports and imports nicely as tagged text. However, I see that all the link destinations, aka text anchors, are all exported at the very end of the tagged text files as global definitions, and thier location iin the document is specified by the property HyperlinkDestIndex. However, I can't figure out how to set this value progammatically. I've spent over an hour exporting links, and it sure isn't anything as obvious as character index in the story.
Any advice appreciated,
Read Roberts

Read, I'm not sure the following is going to help you. It works for external hyperlinks, but you want internal links, right? Anyway, it might give you some clues.
A funny thing: I was reviewing some script where I got links to work, and I spotted a tiny coding error. Links seemed to be defined by two separate identifiers: a "link name", which is what appears in Edit Hyperlink dialog, and a "Dest Key", which seems to be a simple increasing number. However, due to aformentioned coding error, the dest keys between the actual link and its definition were off by '1', so there was no way that ought to have matched. But it still worked! So "Dest Key" is a red herring ...
As far as I understand, it works like this (for hyperlinks): in your text, you have
HplName -- this is actually the 'title' that appears in the Hyperlink palette
HplDest -- this is the 'internal name'
DestKey. Hm. Perhaps you could omit this, per above obsvn.
CharStyleRef, the name of the auto-applied style
Hid -- seems to be always '0'
HplOff: the "offset" from this entire command to the start of the hyperlink, in InDesign characters.
HplLen: the "length" from the hyperlinked text, in InDesign characters.
and in the list of 'proper' definitions, those that appear at the very end of your file:
HplDestDfn -- the internal name again
DestKey -- see above
HplDestUrl -- finally! A real URL! (But you must escape lots of characters, such as the forward slash and colon.)
Hid -- again, always seems to be '0'.
Some of these items are perhaps optional, but experimenting with what may be left out only lead to frustration The Tagged Text guide is far from complete, as I'm sure you already knew.
As noted, some (or all) of the named items need a backslash escape for a few characters, but I can't find a definitive way to determine in advance what is 'good' and what is 'not good'.
The following script creates a Tagged Text file with a couple of working hyperlinks in it -- I don't know if this is of any help for your internal links.
var hyperlinkDest = [];
var text = "This is some text with a link [http://www.jongware.com/idjshelp.html] and another one [http://forums.adobe.com/thread/1014617?tstart=0] in it.";
var tagtext = text.replace (/\[(.+?)\]/g, function (full, match)
 return makelink (match, 'title:'+match, match, match);
// When done processing plain text, add the destinations at the end:
tagtext += hyperlinkDest.join('');
tagFile = File(Folder.myDocuments+'/__tmp.txt');
if (tagFile.open('w') == false)
 alert ("Unable to create temporary file!");
 exit();
if (File.fs == "Windows")
 tagFile.write ("<ASCII-WIN>\n");
else
 tagFile.write ("<ASCII-MAC>\n");
tagFile.write ("<dcs:HYPERLINK=<cu:1>>\n");
 tagFile.write (tagtext);
tagFile.close();
// 'text' is the actual text that will be clickable
// 'title' is what will appear in the Hyperlinks palette
// 'name' is the internal name in the Edit Hyperlink dialog
// 'url' is the actual URL that will be linked to
function makelink (text, title, name, url)
 var destkey = hyperlinkDest.length;
 // In URL you must escape forward slashes and colons
 // .. and some other characters as well, by the way. There seems to be no list
 url = url.replace(/\//g, '\\/').replace(/:/g, '\\:');
 hyperlinkDest.push ('<HplDestDfn:=<HplDestName:'+name+'><DestKey:'+String(destkey)+'><HplDestUrl:'+url+'><Hid:0>>');
 return '<Hpl:=<HplName:'+title+'><HplDest:'+name+'><DestKey:'+String(destkey)+'><CharStyleRef:HYPERLINK><Hid:0><Brdrv:0><HplOff:0><HplLen:'+String(text.length)+'>>'+text;

Repeating Regions and Editable Tag Attributes?

I want to produce a template that will let users create pages
that list items as a thumbnail image and a short text description,
one after the other.
I can set this up as a repeating region, but I would also
like to make only certain attributes of the image editable (src and
alt for example). However, when I use editable tag attributes to do
this, the image in each repeated region ends up with the same
attribute values - when I add a new repeat region and then change
the src tag through the Template Properties dialog,
all of the images take on the same src value. Looking at the
code, it looks like the editable instances in each repeated region
get the same name, and so I can see that DW will get confused.
Is this a limitation in DW? Is there a work around anyone can
suggest?
TIA

So, you have some number of people who are editing the child
pages and you
want to constrain their editing choices? Are you using
Contribute?
Anyhow, I am not aware of any convenient way you can do
something like this
using DW's Template features.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"manicbananic" <[email protected]> wrote in
message
news:g7pimq$fvg$[email protected]..
>I want to produce a template that will let users create
pages that list
>items
> as a thumbnail image and a short text description, one
after the other.
>
> I can set this up as a repeating region, but I would
also like to make
> only
> certain attributes of the image editable (src and alt
for example).
> However,
> when I use editable tag attributes to do this, the image
in each repeated
> region ends up with the same attribute values - when I
add a new repeat
> region
> and then change the src tag through the Template
Properties dialog,
>
all
> of the images take on the same src value. Looking at the
code, it looks
> like
> the editable instances in each repeated region get the
same name, and so I
> can
> see that DW will get confused.
>
> Is this a limitation in DW? Is there a work around
anyone can suggest?
>
> TIA
>

Editing saved text on Element 7

I have Adobe Photoshop Elements 7. After saving texts on pictures, I can't edit the text at all???? Can saved text even be edited????

When you look in your layers palette is the layer thumbnail a capital T? If it isn't, the text is simplified and can't be edited with the text tool.
Edit: If the thumbnail has a capital T, make a note of the font and size. Then reset the Text Tool. It may be corrupt.I didn't catch which version of PSE you have. To reset the tool, select the Text tool and look in the options bar. In older versions of Elements the reset will be the first T on the options bar...not the tool box. It will be a different color than other menu items. Click and select "Reset Tool". If you have PSE 7, Look in the menu bar for a tiny arrow...first or second thing in the options bar with the text tool selected. Click the tiny arrow and select "Reset Tool". If this does not work, next reset the application preferences.
If it's merged with your photo, you'll have either start from scratch or repair the photo either by using the clone stamp or covering the area with a copy of some "good photo". How you repair really depends on the photo.
Sometimes you get lucky and can just marquee some good area and feather the selection edges and use the good to cover the lettering.
Sometimes you can select the letters, expand the selection by 1-2 pixels and then use that selection to copy material to cover the letters.
Other times you need to do as Hatstead suggests and use the clone stamp to cover the area.

Why can I not edit tags properly when I click on the star/bookmark icon?

Firefox 6.0
When I try to edit tags, I cannot see the text I'm typing and when I type something and say "Done". The changes are saved so that's fine. I also noticed when I choose the folder for where the bookmark goes via clicking the star/bookmark icon, it doesn't update the choice I've made visually.

What happens when you click the star (now colored gold) a second time? See the steps in the process of adding a bookmark by the method you are using. Step 1, step 2....
See: http://support.mozilla.com/en-US/kb/Bookmarks#Making_new_bookmarks

Import ID tagged text file results in paragraph style overrides

I have been working on a project that requires the import of a large amount of information from a database. I have defined all the paragraph styles in InDesign and have a program to apply the paragraph style to the database information creating the InDesign Tagged Text file. When I place it into my document the paragraph styles are recognized but there is an override. If I clear the override, the text looks fine. I have an example document that I have exported and imported some text to rule out the program, but even in this case, an override occurs. Text is there, the paragraph format is there, but font size (for example) is wrong. Where should I be looking to correct this issue?
Harold

I don't recognize any of those being wrong, per se. I have the file on another computer, so I mocked up yet another one. Sorry
Again in this one I did ASCII export, no fancy characters. And this one demonstrates the problem, too. I have two kinds of paragraphs. A big one and a small one. I create those paragraph styles. I select the only two lines in the file. Export and then bring them in underneath themselves to compare.
The paragraph styles for the newly Placed paragraphs are gone. The font color is the same. But the font size and font have not changed.
I manually edited the IDTT and removed the <Japanese feature> tag. Placed it again. Font color is the same, but the size and font are wrong.
In other words, my problem is that ID does not seem to apply the paragraph style to the text when it is imported. Aren't the font size and font defined in the Paragraph Style?
My end goal is to define some paragraph styles and create the IDTT automatically from a database. My hope was that the paragraphs would be formated properly based on the predefined styles when the IDTT comes in. I cannot get it to do this even for a pared down example. Aren't other users doing this?
Here is the IDTT on pastebin (with the <Japanese...> tag removed)
http://pastebin.com/Vdc6NVDV
And what it looks like after the intial Place with <Japanese...> tag in, edited line from Small to "Deleted Japanese feature...", removed tag from IDTT and then did another Place.

Editing Hidden Text with PDF

We currently are in the process of scanning our historic documents and we had them scanned with OCR and now we are using a indexer that looks at the hidden text for indexing. We will be using this for searching for documents. However some of these documents are older. Which means OCR did not work and great as expected. I want to see if there is a way to edit that hidden text from the OCR to change minor things in order to ensure the ability to find the documents. Any hints would be greatly appricated.
Thank you,
Jeff

Jeff,
Historical documents - implies you'd not want to adversely effect the scanned image. If so, then OCR Searchable Image (Exact) (SIE) is desired.
As to editing the OCR output. Neither Searchable Image (Exact) nor Searchable Image lend themselves to this.
Yes, there are work around's; but... labor intensive and awkward from within Acrobat.
If you use SIE, consider exporting out the OCR of each PDF to a text file. Referencing the PDF or the source paper you can edit this text (migrated to a word processor perhaps). Output a second PDF. Use these for the catalog index. Link each second PDF to the first PDF.
Search gets you to PDF 2, the link gets you to the scanned PDF.
Alternatively, hold off for Acrobat X.
Today's Adobe Acrobat X: First Look eSeminar demonstrates how Acrobat X can export an OCR'd scanned image directly to Word with impressive retention of layout and format (without coming from a Tagged PDF). This process would permit getting cleaned up text back into PDF(s) to serve as the source of a Cataloged index.
The eSeminar will be presented again Thurs., Oct. 21.
See: http://acrobatusers.com/events/49361/adobe-acrobat-x-first-look
Be well...

Editing Tag Text in PSE 13

Similar Messages

Maybe you are looking for