Jump to content

David in MA

  • Content Count

  • Joined

  • Last visited

About David in MA

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'm trying to resurrect some design files originally created with Illustrator and saved as Adobe PDF. Many use gradient shading or blended shapes. These look fine in any PDF viewing app, but Designer is still not able to render or work with these. Very frustrating. I hope they implement gradient shading and blended shapes soon.
  2. Thanks Thomaso. To be clear, when a Shad immediately follows a Tsek, the line break should be after the Shad, not after the Tsek. In all other cases I can think of, a line break can be after the Tsek. Prior to vs 1.8.4, Publisher did not allow line breaks after a Tsek. v1.8.4 fixed that, but there is this one exception that needs to be implemented. Thanks.
  3. Yay! v1.8.4 fixed line-wrapping after Tsek ... almost. There is one exception that still needs fixing. When Tsek(U+0F0B) is followed immediately by Shad ( either U+0F0D, U+0F14, or U+0F07F ), then the line wraps after the shad, not the tsek. This is a great improvement - thanks, but still needs one more tweak.
  4. Once again my hopes were up that the latest release, v1.8.3 , would fix the Tibetan "Tseg" bug that doesn't allow lines to break after a tseg. Unfortunately, fixing that bug didn't make this cut. PLEASE fix this. Thanks.
  5. I just tried laying out some Tibetan text in Publisher 1.8.2 with hopes that the new version fixed the problem with lines not wrapping after the Tsek character. They are referring to it as hyphenation, which I suppose is accurate since Tsek is a syllable delimiter and there is no actual word delimiter for multi-syllabic words. At any rate, it still doesn't work properly. I'm hoping the next update will fix this.
  6. Not exactly. That would work for a square or circle, but for irregularly shaped paths/objects it would scale the whole shape toward the center, even if locally at a point on the curve the interior is away from the center. For example, the outline of a thick letter 'C'. Your method would reduce the size of the whole shape proportionately. What I'm thinking is if you shrink the outline so the C becomes skinnier, ie, the outline of the C moves toward the interior, not toward the center of the whole object.
  7. In Tibetan, especially in pechas, it is considered a special case, if the last syllable of an expression that is terminated by a shad ། breaks to a new line. In that case the shad ། ( U+0F0D ) is replaced by rin chen spungs shad ༑ ( U+0F11 ). This serves as an optitical indication that there is a left-over syllable at the beginning of the line that actually belongs to the preceding line. There does not seem to be a regular expression to find such orphaned syllables when the new lines is a result of formatting rather than an inserted line-break character. It's very tedious to hunt through a text to find and replace shads that occur after the first syllable on a line, so it would be a great help to have a feature that does this.
  8. I'd just like to add another vote for this feature. It's important to our work and we are in the process of switching from Adobe to Affinity. The lack of this feature is a bit of a stumbling block. In the process of trying to find a workaround, I came up with an idea for another tool as well. In Photos, the grow/shrink option under the Selection menu allows one to expand or contract the selection marquee by a specified number of pixels. It would be great to have a similar option in Designer that grows/shrinks a closed path or shape by a specified distance. It should be easy to implement since they've already coded this for selection marquees.
  9. Since you are curious, there is an odd grammar point in Tibetan. "Sentences" usually end with a Shad character ( ། ). If there is just the last syllable of a sentence at the beginning of a line, then the Shad character is replaced by a Rinchen Spungs Shad ( ༑ ), I suppose to indicate that it's connected to the sentence on the preceding line. So I want to be able to search for those orphaned last syllables and replace the Shad with a Rinchen Spungs Shad.
  10. The ^ and $ in regular expressions search for begging and end of lines which are delimited by paragraph or newline characters. I want to search for the beginning or end of a line that has been wrapped by the formatting. For example, if the last word of a paragraph is the only word on that line. I can search for the last word of the paragraph, but there seems to be no way to search for the line wrap just before it.
  11. Walt, I saw your earlier message, but there is no Edit link in my initial post. Dan C edited my second post and renamed the thread in the process. I'm not able to override that, or make any edits to any of my posts. Dan C, if you're listening, please change the name of this thread to "Tsek character not functioning properly in Tibetan", or at least something with Tibetan in the Title. thx.
  12. I was happy to see that Publisher v1.8 added the IDML import feature. This is a big help. But unfortunately, the Tibetan Tsek bug has not been fixed. I wish they would name this thread more appropriately. It strongly affects anyone working in Tibetan as it prevents lines from wrapping properly and paragraphs being justified. Better yet, I wish they would fix the bug. It can't be that difficult to adjust the properties of a single unicode character to work properly.
  13. installing a Tibetan spelling dictionary per instructions did not help. See the bug report at
  14. It looks like this topic was renamed from my original post while I was replying to the previous comment. The new name doesn't exactly fit. There is no hyphenation in Tibetan as syllables are already delimited by Tseks. Words are either a single or multiple syllables which must be recognized as there is no additional grammatical character separating words. The point is that Publisher is treating the Tsek character as an alphabetical letter that is part of a word rather than delimiting words and allowing line breaks after them when needed. Thomaso - you did good research. Those points are all valid. In general, there can be multiple grammatical characters in a sequence that should not be broken up. Line breaks can occur after Tseks or spaces, but if there are additional grammatical characters adjacent to the Tsek, they should not be broken up. I hope they rename this topic to something more fitting. Perhaps "Tibetan Tsek not recognized as a word delimiter"
  15. I followed the directions for installing a spelling dictionary for Tibetan in the Mac OS. (Wow, that feature is really hidden.) It now appears as an option for Spelling Language in Publisher, but does not solve the problem with Tseks not being recognized as word delimiters. To be clear, a Tsek should not force a line break, but should allow a line break when needed, much like a space between words in English except that it appears as a dot. In Tibetan, words and syllables all end with a Tsek. As is, Publisher only wraps new lines where spaces exist between sentences and treats the whole sentence as a single word, breaking it at random places is there is no room on the line. If I add zero width spaces after every Tsek, then line wrapping and paragraph justification work as they should because the added zero-width space allows Publisher to wrap the line after a tsek when needed. But I shouldn't have to add those zero width spaces. Otherwise, I'm finding Publisher to be a good replacement for InDesign and hope that you soon get the feature to import IMDL files working so we can import our old InDesign work without having to reflow all the text. Thanks, David EDIT - This post was merged from a separate topic as it best fits with your thread here.
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.