Sep
14th
2014
Another one about LibreOffice · 10:20pm Sep 14th, 2014
Well, I've been using it for maybe a week now, and I've run into a problem.
There's no way to do format find-replace. :(
With Word, you can select a format, like italic, and then replace it with "^&" which will put bbcode tags around the word or phrase found. LO can search on italics, but it's horrendously stupid. I just tried it and it kept highlighting random, non-italicized phrases, sometimes as short as a single letter.
This is intolerable. I can't format my crap manually for this site, it would take ages. Even if it could locate italicized passages, I could deal, but it can't. It's useless. So unless someone knows a workaround, this mess is outie and soon.
Report
PresentPerfect · 247 views
·
Upload to google docs, use fimfic importer?
Try the Find and Replace LibreOffice Extension.
Witchcraft.
Do what I do when I write.
Put the BBCode in manually as you type. If you bold something, stop and put the code around it and then move on.
2455176 I'll second that. It's bloody marvellous.
I'm forced to use Libre Office at work and it sucks. Even the "Find and Replace LibreOffice Extension" does very little to make it better.
So I simply use Notepad++ for text editing (I use Word at home). It has its limitations, but there are many cool features, and it doesn't require you to be one of the app's developers to be able to actually use it.
Well, for BBCode, the suggested alternative search extension seems to perfectly fit the bill. It even comes with premade batch substitutions (click the "Batch >>" button to see), one of which will convert everything selected to BBCode with a couple clicks.
The batch search and replace does wreck havoc with undo, though, so save your file before trying it.
"When you have a software headache
You've only made but one mistake:
If all it does is break
then you throw the program out!
You can download word or gdocs
Create your own inside of codeblocks
Document or it will flummox
Or you can just go back to vim
So I don't want to see you crying
When your word software is dying
Just remember: keep on writing
Until the next catastrophe"
I always upload from GDocs. A little time smoothing out the formatting (indents never carry properly) is still miles better than doing all the BBCode manually.
That's Linux for ya. It does nearly everything, except for some finicky (but very convenient) features.
I agree with the folks who upload from GDocs, though. You just have to examine the upload to make sure nothing was lost.
2455170
Bite me. (That shit don't work.)
2455176
The kind of thing I was looking for! (Hopefully.) I'll give it a try, thanks. :)
2455214
Then I have to take it all out when I save my copy. :|
2455268
I always copy the text into a new file to format it so I don't have to deal with that kind of thing. :V
2455273
what
2455423
Sunday is a slow day
2455194 WHAT?
Why was I not told of this magic?
2455294 But note fimfiction doesn't upload gdocs to a blog post. You gotta upload your blog post to a story chapter, then copy-paste it into a blog post.
2456912
And with that plugin linked above, the code is actually "&", no carets necessary.
2456914 On one hand, I honestly hadn't though of that; on the other it took me about 0.6 of a second to realise you can keep a fake story up to import, then copy/paste the BBCode-inclusive data into a blogpost.
2455273
upvoted for vim
downvoted so I could upvote it again
upvoted for FiW
2456964 That's what I do. But it's a pain if, like me, you keep revising your blog post after posting it. Now I paste the first uploaded version back over my gdoc and use bbcode from then on.