Back

If your email is not recognized and you believe it should be, please contact us.

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 23 total)
  • Author
    Posts
  • in reply to: Numbering list restart at 1 on next page #111623

    Thanks Aaron for not giving up on my issue here…
    I thought your last solution would be a lot of work, so I explored again the option of converting numbering to text. The automatic exporting option didn’t work for me, but I found that if I used a script on every single document before exporting to epub, then it worked.
    The script is: app.activeDocument.stories.everyItem().convertBulletsAndNumberingToText();

    I’ve tested the epub in Google Play and the numbers appear just as they should. Problem solved!

    in reply to: Numbering list restart at 1 on next page #111452

    Just an update to say that the epub option in the export settings didn’t change nothing. So my issue is still ongoing and a mistery. Any other idea how to fix it?

    in reply to: Numbering list restart at 1 on next page #111194

    I just noticed though tha there is an option in the epub export settings to do what you says, convert the numbering into text. I’ll try it on monday!

    in reply to: Numbering list restart at 1 on next page #111191

    That would work for the epub issue, but in my case I can’t do that because the text I’m using is linked to InCopy, and I’m using the same text synchronised in 2 other books with different formats. I need the verses of the other versions to still be legit numbered lists. Can’t break the links to InCopy either because we’re often updating this text and publishing new versions.

    in reply to: Numbering list restart at 1 on next page #111189

    Hello Dieter,

    Do you mean the number style by default which is ^#^. ?
    I just tried it, and whether I leave or I remove the dot it doesn’t change anything, it will show a dot after each verse number in my epub.

    I don’t know what this dot is for in the number style of my paragraph settings, but I don’t have a dot showing in my InDesign files. But it appears by default when exporting to epub unless I add a css code to remove it.

    I didn’t get an answers on Twitter so no other developments on my side…

    Is there a programmer here who would know why addind the css piece of code in my earlier post will have an ebook reader like PlayBooks to bug? My concern is that it would bug also on other widely used epub readers.

    in reply to: Numbering list restart at 1 on next page #111133

    Hello Aaron,

    I guess you’re right, it must be a bug on PlayBooks because I just tested my epub on Calibre and IceCream reader and it’s working fine.
    I’ve noticed though that this issue of numbered list appeared after I added a code in my CSS file to remove the dot between the verse number and the text of the verse :


    ol {
    counter-reset: item;
    list-style-type: none;
    }
    li { display: block; }
    li:before {
    content: counter(item) " ";
    counter-increment: item
    }

    So maybe somehow this code is conflicting with something else in PlayBooks.
    Thanks for your suggestion, I’ll post now on Twitter and see what comes out.

    in reply to: Ewe characters shown as a red box #105126

    Following up on my question, encoding the characters worked.

    Although it didn’t work perfectly, it caused many errors in the text. The best would be for the Bible translation team in ewe and myself to have the same font. Because they send me text in a Word document or PDF, an everytime they make a change to their text I have to start over the encoding process, which creates again new errors.

    So my question is: can I add unicode characters into the Times New Roman font ? Or create a font for ewe that would be unicode compatible? Please advise on what would be best, I have zero experience in doing this sort of things with fonts.

    Thanks

    in reply to: Ewe characters shown as a red box #104491

    Thank you so much Theunis. So I did as you said and it took me about 2h to encode everything. I found an ewe alphabet online which helped me copy and paste most of the “correct” ewe characters in unicode. Some others were not there, I think they were characters from another african dialect, but eventually I found their unicode on wikipedia.

    No more white or red boxes, and now I can put ewe text in italic or bold using Times New Roman.
    Thanks again, greatly appreciate your help. I couldn’t have figured this out on my own.

    in reply to: Ewe characters shown as a red box #104481

    Thank you both for your replies !

    Theunis I’m willing to work on this and make it right. I can’t stay with squares in my text anyway, and I agree this Capecoast isn’t great bu I thought I didn’t have any choice.

    How can I make the encoding right ? If you have a link or document explaining the process that would greatly help me as I don’t know what encoding is. I suppose I’ll need an ewe keyboard which I already have, and then…?

    Using Times New Roman would be good if I could, that’s what I’m using for my text in french. We kept it simple.

    in reply to: Align to grid and justification #97720

    So I’m pretty much done with testing to solve my issue.

    I tried different settings, for 2 different results:

    1. All text is aligned: I obtained this by creating a new paragraph style with different justification settings (higher word and letter spacing, and glyph scaling) which I applied to a whole page or a few verses on 7% of the pages (100 pages in total) falling short of text because of the Keep options (keeping the chapter titles with its description + 2 verses).

    https://bibleostervald.org/wp-content/uploads/2017/09/Capture.jpg

    I got this result whether I forced all lines to align to the grid within the paragraph styles settings, or whether I didn’t force anything to snap to the grid but the 1st verse of each chapter. I calculated the margins size accordingly, so that the text frames were an exact multiple of the baseline grid.

    2. 93% of the text is aligned, and 7% is justified : I got this by having all my text boxes set to “Justify” in the text frame options. Most of the text aligned, except the same 7% of pages as case 1, which got justified. The result is random: if the number of lines is equal in both columns, the text will align, if not it wont.

    In conclusion, after all this testing I havent found a perfect solution. The cost of having ALL text to align is high: 130 pages to adjust in order to fix columns not fully filling the text bloc (and the difference of text justification is very noticeable), and widows created because I can’t have proper keep options without creating significantly more problems. Plus I havent found a solution to have an equal amount of space between the chapter description (which is 7,5 pts and the 1st verse 11,25pts). I worry about having that many pages to fix, while the text of our Bible isnt fixed yet. Its still being revised, and some word modified there and there to be closer to the KJV.

    Because of all the downsides of having all text aligned, I’m thinking letting go of it and just keep it to justify everywhere. Unless that I’m still missing something, and a solution is still out there…

    in reply to: Align to grid and justification #97193

    Thank you so much Joel and Dwayne, I am very grateful for both your help.
    I’m currently testing out your ideas, to see what will work best for me.
    After I’m done with trials, I’ll let you know with another post what worked best (in case that would help someone else in a similar situation). Thanks again.

    in reply to: Align to grid and justification #97151

    Hi Joel,

    Thank you so much for your detailed answer.
    I’ll try everything you said to have a more professional look and maybe avoid other issues (I didnt know at all about character styles and the baseline shift option).

    Although as I’m reading I’m wondering how that will help with the source of my problem, which is my paragraph keeping rules. The title that says “CHAPTER 2” is set to stay with all lines of the smaller text below it (which is description of the chapter). And this description has for rule to stay with at least the 2 first verses. So on the left page of my screenshot, you can see what sort of problem that creates. If I turn off justification of the text bloc, the CHAPTER 1 will end short of several lines, with the columns uneven.
    This problem occurs in about 5% of pages in my book.

    I have a Bible in my hands as exemple which has the same system of chapter title and description, and never across this Bible I’ve seen any block of text fall short because of paragraph rules. I have no clue how they’ve done it (and even if they were using ID). I didnt notice either any page where the text isnt aligned to the grid.

    If there is a way to get everything to look perfect, that’d be great. But if not, I have to find a way to try to limit the damages by at least having the justified text to align across the 2 columns of the page.

    in reply to: Align to grid and justification #97142

    I wanted to also specify that all my text boxes are set to justify, and my text for verses are set to align to grid. I only need to justify some part of text so that all the columns end at the same point instead of leaving whites lines til the next chapter starts on the next page.

    I tried setting my text on a single bloc of text divided into 2 columns with a gutter, and also 2 seperate blocs of text per page. To see if that would change the way InDesign spreads text when having to justify it. Since I hacent found a way to have everything always to line up perfectly across all pages, I thought if it could at least line up within a same page that would be a progess.

    I hope these infos help to see where I’m coming from.

    Does anyone know about this ?

    To rephrase my question, I’m looking to change my document presets all at once. Specifically the document page size, gutter, and margin measurements, while having the layout adjustment ON. I have looked into the book synchronize options and did some tests, but couldn’t find a way to make it happen. Maybe I’m missing something, or this feature doesnt exist yet ? I found this online which is the same question as mine, but unresolved: https://forums.adobe.com/thread/700281

    Any insight on this would be much appreciated.

    in reply to: what is this P SEP box ? #95847

    Yes @Lindsey, it was a Unicode separator ! My weird p-sep box is the character U+2029

    I tracked it in all my documents thanks to the GREP tab of the find/change dialog box, and searching for \x{2029}
    This saved me so much time !

    Thanks everyone for your help, I so much appreciate this community of InDesign experts.

Viewing 15 posts - 1 through 15 (of 23 total)