Jump to content
You must now use your email address to sign in [click for more info] ×

David in MA

Members
  • Posts

    25
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. Loukash - I use a similar technique to transfer text on a curve from AI to Ade. However, I also have many years of work with hundreds, perhaps thousands of text on a curve items, so having part or all of the process automated would be a big help.
  2. When I import files from Adobe Illustrator, text on a curve is imported with each character in an individual text box with no connection to the rest of the text. The curve is not imported. This makes editing the text on the curve a nightmare. Please import text on a curve as text on a curve, or at least import the curve so text can be attached and positioned correctly.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. 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.
  14. 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.
×
×
  • Create New...

Important Information

Terms of Use | 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.