ayan fun

Totally agree!

同问题，中文翻译错误的不少，有时候中文的错误意思反而会找不到一些功能😖，暂时换回英文语言了。导出角色里右侧的切片->批量生成工具中有导出"spine骨骼动画"的json文件的选项。但是被翻译为了"自旋json"，所以之前一直找不到这个功能

Totally agree!

Cool! Thanks for sharing the tip. Can be a temporary workaround for small projects I think.

With APub you can use a character style with the propriety "no break" to keep some pontuation with the previous character, or to keep the following character of some ponctuation with this ponctuation.
That's just a trick, but you can do it easily with Find and replace, or using a shortcut to this style while typing.

 
ponctuation.afpub
1.a Search a character—between brackets, you can add more to them—that should stay with the previous one:
([，」。]) 1.b Replace with this applying the character style "no_break":
$1  
2.a Search a character preceded by the ones between brackets—you can add more to them—that should stay with it:
(?<=[「《])(.) 2.b Replace with this applying the character style "no_break":
$1 (+character style no_break)

Now, about the second expression, more complexe. Keeping the "regular expressions" enabled.
(?<=[「《])(.)
We've got 2 groups of parenthesis.
The second group is simple, the parenthesis only contain a dot, and a single dot . means "any character". It's powerfull!
If you try  searching only . (a single dot), the app will list all the characters of your text one by one. If you search .. (two dots), it'll list you couples of characters, etc.
 
In the first parenthesis, you can reconize the brackets that means again "one of those characters", with the options 「 or《.
But at the begining, inside the parenthesis, you've got ?<=, those characters mean: "find the following characters before the next group".
Using this expression, we can have:  (?<=a)(b). It'll search a b preceded by a a. Like in "absolute". It won't count the a as a result, only the b, that's why we use $1 in the replace input.
If I search (?<=absol)(u), it'll find the u in absolute.
If we add brackets, it'll have a list of characters instead of a single one, that's why we use [「《].
 
There are 4 of those options "before" and "after" with  "should be" and "can't be":
Positive lookahead (the pattern should be after the element): element(?=pattern)
a(?=b) Negative lookahead (the pattern can't be after the element): element(?!pattern)
a(?!b) Positive lookbehind (the pattern should be before the element): (?<=pattern)element
(?<=a)b Negative lookbehind (the pattern can't be before the element): (?<!pattern)element
(?<!a)b  
 
The "no_break" character style is simple: have your cursor out of text (to not get unwanted characteristics) and create a new character style with only the option "no break" checked (last option in Character > Position and Transform).

First, in the search option, you need to check "regular expressions". I didn't mention it, sorry.

 
You need to copy the full expression (like in the sample file), and in this expression you only add or replace the red characters.
([，」。])
The parenthesis mean "find and remember the character(s) inside". For example, (a) would only find the character a.
(home) would find the characters home in the same order.
The brackets mean "one of the characters in this list". With [home], it will find either a h, a o, a m or a e.
With [，」。], it will find either a ，, a 」or a 。.
The interesting part with the parenthesis, is that you can have more than one group, and call them in the replace input with numbers.
(a) is a single group you can call using $1
(a)(b) with this, I've got 2 groups, $1 and $2
If I search (a)(b) and only replace by $1, everytime the application will find the character a followed by a character b, it'll replace them by only a.
If I search (a)(b) and only replace by $2, everytime the application will find the character a followed by a character b, it'll replace them by only b.
There's another expression: $0. It means everything that is found. Not usefull in this case.

Thank you very much! Very happy today! Please accept my kneel!😎

Hello guys, I am starting to use affinity publisher for my work. It is so great app, and I love it. But I am using Chinese and I can't make the typographical errors gone. As shown in the image below.  In chinese language we should not let punctuation in the head of a line. Hope you guys can check it out! Thank you always!

1.8 is comming, and I installed it. BUT the problem still exist!  Pray Again! Thanks. Before this problem solved. I can't do my job with affinity production in my country. Sigh!

1.8 still not function in asian language breaking line rules! Before this problem solved. I can't do my job with affinity production in my country. Sigh!

The one thing I liked about Adobe PhotoShop's timeline was that you could perform simple timeline animations using keyframes on layer/object properties which means, for each layer you could keyframe difference on:
X&Y position of layer (including under a mask to make something disappear) Alpha % Visibility (on/off) Being able to do this would allow you to create one time or looping animations of a UI to simulate UX quickly.  You could also create cool little simple character looping animations. I don't think it should ever try to compete with super complicated timeline animation tools for animation. That would be an entirely different product. But simple property in-betweens (tweens) over time would be nice.

Haha, happy to hear this!  Yeah!