Advanced Search and Replace: emojis to text in a specific font

[drmajorbob]

@xiamenese

LibreOffice or NWP, that can be done as a single operation for each glyph in turn. That’s why compiling and re-importing is the way to go

Couldn’t Compile replacement rules do that? Hundreds of rules would be a pain to create, but how easy is it in LibreOffice?

[drmajorbob]

@kewms

That is, leave it the way it is in Scrivener. Make the change only when/if you are taking the text (or part of the text) out of Scrivener for good, and therefore don’t need to worry about re-importing it back

Yes. I’d do almost anything to avoid the round trips.

[drmajorbob]

@marksealey

Aren’t they all just holders?

They’re all just documents, folders or not. If two documents need the same formatting, give them the same section type. Levels don’t matter, and whether they’re folders or not doesn’t matter. Only the formatting matters.

[marksealey]

@kewms and @xiamenese - thanks again for your patience!

@kewms

I’ve been suggesting that you assign a Style to the Section Title. Scrivener will then use the Styles in the re-imported document to decide where to split things up.

OK. I’ll do that.

Was the example I uploaded with its screenshots as I defined and assigned anywhere close?

If so, would it be reasonable to add, say, a different font size (from 10 pt to 20 pt since there are five each of Folder styles and Note styles) to each Section?

Should my last question have been, perhaps:

If so, am I still failing because - although I have ten styles defined - they all have the same layout? And so I really must assign, say, a different font size (from 10 pt to 20 pt) to each Section’s Layout?
I have not done that so far…

Since we’ve been at this for close to a month and you still seem to be struggling, there is another possibility. Simply ignore the emoji/font problem until a later stage.

You’re so right. I am struggling. And, as I keep saying, grateful for your patience.

But, zookeeping aside, my document on musical theory (the first of others also using music glyphs) isn’t really viable until I have replaced them with those using the appropriate, dedicated, font.

What’s more, I really love Scrivener. I can see that this is an important aspect of its design. I really want to be able to use it as intended.

HOWEVER, you’ll still need to work with the Compile command to get your work out, so in the long term it probably behooves you to wrap your head around how it works.

I agree 100%.

[kewms]

@marksealey

If so, am I still failing because - although I have ten styles defined - they all have the same layout? And so I really must assign, say, a different font size (from 10 pt to 20 pt) to each Section’s Layout?
I have not done that so far…

You don’t have Styles assigned (as far as I can tell), you just have Section Types. That’s a step in the right direction, but not all the way there.

What matters is the Style assignment, not what they look like. You can use any formatting you want (or none), you just need to assign Style names based on the hierarchy you want to preserve.

As I said in response to this post:

Advanced Search and Replace: emojis to text in a specific font

Thanks, @kewms, as always! I first set up in Project > Project Settings… > Section Types what I hope are Section Type definitions (with somewhat cumbersome names - for clarity for me, really) thus: [Section Type definitions] I then assigned them (again in Project > Project Settings… > Section Types), thus: [Section Type Assignments] Was I right, so far? Then, in Compile: [Compile step Section Type assignments] where - as you can see - I had a question. Assuming that was expected, this…

With the Section Type assignments, you’re halfway there. The next step is that they can’t all use the same Layouts.

[marksealey]

So:

1. File > Compile > Assign Section Layouts (at foot of central pane)
2. double click on each of the ten Section Type there (lefthand pane)

Then:

1. scroll to ‘Section Title’ and select it by double-clicking
2. accept Duplicate and Edit

?

Then what?

May I ask you to upload some simple screenshots of exactly where I should be that this point, please, @kewms? Thanks!

First you define a Section Type, say “Note Folder,” and assign it to your Note Folders. This happens in the Inspector or in the right-hand pane of the main Compile screen.
Then, in the Compile Format, you define the Section Layout that should be applied to that Section Type. It could be anything, but let’s call it “Top Level.”
In the Top Level Section Layout specification, you check the box for “Title,” which will cause Scrivener to include the Binder title of that item, and will cause “Section Title” dummy text to appear in the preview area.
Apply whatever formatting you want to the dummy text. For the purposes of this specific problem, assigning the Heading 1 Style will ensure that the destination application recognizes it as a “Heading 1.”

[kewms]

I will try to put together some screenshots, but it may take me a day or two.
In the meantime, Section 24.2.3 of the manual explains how to assign Styles within a Section Layout.

[marksealey]

Thanks very much. Even if they are simple ones that guide me through the correct sequence of menu options, that would be very helpful, please, whenever you have the time to do it. Shall check back by the weekend…

I believe I am a victim of Scrivener’s broad and rich functionality; and (chiefly) of not knowing which features are achieved by which menu and at which point in which processes. That is all that is still holding me back from understanding what - once I do, and once I have fitted it all interlace myself - will be extremely obvious.

Thanks again!

@kewms

I will try to put together some screenshots, but it may take me a day or two.
In the meantime, Section 24.2.3 of the manual explains how to assign Styles within a Section Layout.

[kewms]

Okay, here you go. I’ve attached a short demo project, StyledHeadersDemo, together with a Compile Format, the compiled (to Word) output using that format, and some screenshots.

The Compile Format only has three outline levels, but you can create as many as you need using the same pattern.
AssigningHeaderStyles.zip (244.5 KB)

[marksealey]

Thanks very much for the sample files ands screenshots!

I couldn’t immediately get the ‘round trip’ to work; the compiled doc, changed in LibreOffice after Compile, when imported lacked any kind of structure. My bad, I’m sure; I really want to get this clear. I’m sure it’s second nature to you and to anyone who’s got it to work once and has the conceptual model on which this part of Scrivener is based under their belt.

I’m actually a bright user; I apologize for missing what to you is obvious and every day - and much appreciate your patience

I suspect that that failure was because I didn’t actually apply any of the settings illustrated in your screenshots. Yes?

Is it the case the - in your example file (StyledHeadersDemo.scriv) that All folders have been assigned to the Section Type ‘Heading’? And that All files to the Section Type ‘Section’ because that is how Scrivener’s compile process distinguished portions of the long, continuous, single exported (compiled) document? Is it the case that this has nothing at all to do with ‘Headings’ (likely bold and larger font) in the body of any Note file?

Referring to the other three screenshots, am I right to think that:

1. I get to ‘Section Types’ from Project > Project Settings > Section Types > Default Types by Structure? And that I should do this first? Not sure what action I should take when I get there
2. I change fields in ‘SectionLayout assignments’ at File > Compile > Assign Section Layouts? But I’m still not sure what to enter for each field, or why.
3. I get to ‘Assigning styles’ with File > Compile and then double clicking on each of ‘Heading’, ‘Sub-Heading’,‘Section’? But how (and why!) do I select/check each of: ‘Title’ and ‘Text’? I note that this only works if I also select ‘StyleDemo’ in the Formats list on the left of that window.

Thanks again for any step-by-step process which is perhaps documented somewhere for the entire operation!

[kewms]

@marksealey

I suspect that that failure was because I didn’t actually apply any of the settings illustrated in your screenshots. Yes?

Well, the first thing to check would be to see if the document that I compiled and included in the package re-imported successfully. A second thing to check would be to add some files to the demonstration project, compile with the StyleDemo format, and see if the result will successfully re-import.

The screenshots show:

1. (SectionTypes) Assignment of Section Types based on the Binder hierarchy. Here, the top level folders have the Heading section type, file groups (that is, files with children) have the Sub-Heading section type, and standalone files have the Section type. You can use the ‘+’ icon at the bottom left of that pane to add more levels of hierarchy.

2. (AssigningStyles) In the Level One Section Layout, shown in the screenshot, I’ve assigned the Heading 1 Style to the Section Title preview text. Similarly with the Level 2 and Level 3 Layouts. If you want to use this Format as is, there’s no need for you to do anything here.

3. (SectionLayoutAssignments) With the Section Types assigned as in (1), and the Section Layouts formatted as in (2), this third screenshot brings the two together, assigning the Level One Layout to the Heading Section Type, and so on.

@marksealey

Is it the case the - in your example file (StyledHeadersDemo.scriv) that All folders have been assigned to the Section Type ‘Heading’? And that All files to the Section Type ‘Section’ because that is how Scrivener’s compile process distinguished portions of the long, continuous, single exported (compiled) document? Is it the case that this has nothing at all to do with ‘Headings’ (likely bold and larger font) in the body of any Note file?

Yes, that’s correct. I am assuming that any internal structure in the Note file is irrelevant to this project: you want the Notes to be re-imported exactly as they currently appear, not split into constituent parts.

[marksealey]

@kewms

Well, the first thing to check would be to see if the document that I compiled and included in the package re-imported successfully.

Unfortunately not. Here are the settings I used to import StyledHeadersDemo:

Maybe they are not correct?

This is the result after import into the Scrivener Blank Template - one single Note:

One level only. Is there a setting I’m failing to change at this point, perhaps?

== majority of the remaining material snipped ==
== but retained in your post above ==
== to be re-introduced after fixing the demo import ==

If you feel it more appropriate to switch this to a technical support case and exchange emails, I’d be quite happy with that too, @kewms: this is a monster thread and anyone brave enough to be looking in must be wondering why on earth I can’t comprehend what they do every day!

@marksealey

…Is it the case that this has nothing at all to do with ‘Headings’ (likely bold and larger font) in the body of any Note file?

Yes, that’s correct. I am assuming that any internal structure in the Note file is irrelevant to this project: you want the Notes to be re-imported exactly as they currently appear, not split into constituent parts.

Thanks. I think that clears one thing up, to which you’ve alluded previously: the use of ‘Headings’ and ‘Sections’ during the Compile process only by co-incidence uses the same (‘internal’, so to speak) terminology as conventional documents often do. Namely: a documents ‘crosshead’ to guide the eye; or ‘section’/‘body text’ which contains the substance of the paragraph(s). Yes?

[kewms]

Hmm. The re-import should work, but didn’t work for me either. I’m going to have to do some digging to see if this is a known bug.

The round trip did preserve the Style assignments, which is half the battle.

[marksealey]

Thanks, @kewms.

I still very much doubt that I’ve been doing things anywhere near close to the way Scrivener envisages all along, though .

[kewms]

@marksealey

Thanks. I think that clears one thing up, to which you’ve alluded previously: the use of ‘Headings’ and ‘Sections’ during the Compile process only by co-incidence uses the same (‘internal’, so to speak) terminology as conventional documents often do. Namely: a documents ‘crosshead’ to guide the eye; or ‘section’/‘body text’ which contains the substance of the paragraph(s). Yes?

Well, personally I try to have very little “internal” structure, precisely because it isn’t visible in the Binder. But yes, the Binder structure is in most circumstances all that Scrivener cares about.

Apparently there are indeed some Import and Split bugs, but they actually work in your favor: ODT files import more successfully than .DOCX files. So, try taking the demo file I sent, opening it in LibreOffice, saving to ODT format from there, and then re-importing. Does that work better?

[marksealey]

@kewms,

Thanks. No, it doesn’t seem to. This is what I get from the below attached:

ODT compiled.zip (4.4 KB).

Appreciating that squashing bugs takes time, and still as grateful as always for your patience and perseverance, what would you suggest I do now, please - if this possible bug is what’s causing the phenomenon (I know it’s not the only thing!)?

[kewms]

Do you have the ODT Java converter installed on your system? (If you don’t, Scrivener would have told you so when you imported the file.)

[marksealey]

@kewms - No I don’t; and it does (twice) each time I compile that way.

If that creates a temporary roadblock, though, I’d be all for compiling to a format that does work and them seeing how feasible it is to import into LibreOffice (which I do use) or Nissus (which I haven’t), those being the only two which will allow this font replacement.

[kewms]

The Java-based converter is more capable, and should be able to handle the styles when re-importing the ODT file.

[marksealey]

Would you advise me to thus install Java in order to have this round trip work?

I have been Java-free for as long as I can remember!

Is there any guarantee that it will work even then, please?