omachi

Many of suggestions here still haven't been applied yet.

There are so many inconsistent and improper translations in Affinity.
I must say it's unprofessional. Serif has to be aware of it.
Please apply suggestions here at least.

Hi all,
The team has been making good progress. I don't have any updates on a release date but please be assured we are not sitting on our haunches - we want to get this feature out as much as you want it out!
Naturally we've been exposing more of the apps' functionality to scripts, but we've been working on plugin-specific technology too. For example, there's a new asynchronous file i/o and networking API, initially driven by the Javascript layer but then we thought it would be good for the lower level C/C++ plugins to have access too. Obviously with local and remote i/o, we've had to be careful that a script isn't covertly sending user data somewhere, so we've introduced a permissions system for Javascript plugins - unless you allow a particular script network access, it won't be able to use the networking API. It may not be a big shiny WOW! feature, but it's important to get these things right.
Anecdotally, I can tell you we've actually used some scripts internally to do some genuinely useful stuff that would have taken literally days to do manually. One script I wrote optimised a document and removed about 60000 layers. There have also been relatively simple layout and alignment tasks that scripts can munch through in the blink of an eye. Last week I wrote a script that split a pixel layer into new pixel layers containing the blocks of grouped pixels. Even the pixel processing was done in the script - I didn't have to rely on the app to do the heavy lifting for me because our performance is good enough to implement DBSCAN in Javascript.
Please be patient. We know you all want scripting available yesterday, but we're getting there!

Thanks for suggesting. I had the same issue and was able to install using PowerShell.

Thanks for suggesting. I had the same issue and was able to install using PowerShell.

Thanks for this: I have now managed to install and register all 3 programs.

In case it might help someone else, here'a step-by-step idiots guide to what I did:-
To install on Windows after dowloading:-
Go to Windows search (bottom left of screen), type “powershell” and open Windows Powershell
At end of line after prompt - PS C:\Users\UserPC>
paste in:-
add-appxpackage C:\Users\UserPC\Downloads\affinity-designer-2.0.0.msix  (Check where you have downloaded to and change location if necessary)
and press 'Enter' (Return) – and wait for it to finish running.
When it has finished, the prompt will appear again – same as before:-
PS C:\Users\UserPC>
Repeat for :-
add-appxpackage C:\Users\UserPC\Downloads\affinity-photo-2.0.0.msix (or wherever you have downloaded to)
and
add-appxpackage C:\Users\UserPC\Downloads\affinity-publisher-2.0.0.msix (again, change location, if needed)
To add shortcuts to Desktop
Go to Windows search (bottom left of screen)Type “Run” and enter
Copy and paste:-
Shell:AppsFolder
and press OK. This will take you to a folder where you can drag and drop a copy of the Affinity V2 shortcuts to your desktop.
You can then open each program and register/import settings from v.1
 

There are multiple ways to install programs on Windows. .exe, .msi, and .msix (new one to me). So it SHOULD work, but for some reason it's not working for quite a few of us.

I have exactly the same problem in Windows 10. On all 3 apps I get this... This should not happen! What should we do about this? Why is there not an .exe file like before. 

My computer / OS information for reference:
Device name    DESKTOP-VG8E0C1
Processor    Intel(R) Core(TM) i7-3612QM CPU @ 2.10GHz   2.10 GHz
Installed RAM    16.0 GB (15.9 GB usable)
Device ID    0657B689-F862-4C75-AEF4-7B0B454E2BD5
Product ID    00330-80000-00000-AA634
System type    64-bit operating system, x64-based processor
Pen and touch    No pen or touch input is available for this display
Edition    Windows 10 Pro
Version    21H2
Installed on    ‎18/‎05/‎2021
OS build    19044.2130
Experience    Windows Feature Experience Pack 120.2212.4180.0
 
I have had (Windows) v.1 of Affinity Designer, Photo & Publisher for between 12-18 months.  I've never had problems installing / updating / moving to new laptop (all of which I have done previously).
Today I have purchased the Universal Licence for v.2.  I have downloaded, but, rather than the Application file (as it was previously) they have downloaded as MSIX files (of which I have no previous experience, to my knowledge).  Clicking on the 'box' icon brings up an error message of  "Cannot open app package" "Error in parsing the app package." (Screen shot attached). 

Can anybody please assist me by advising what I am doing wrong / what I need to do? (And if you could please treat me like an idiot with very detailed advice, I would be grateful!  I don't have a great deal of technical knowledge, but can usually follow instructions!)

Suggestion for the "Text as Curve" in Export > PDF > Export Settings > Embed fonts

テキストをカーブに変換
or
カーブに変換

Current translation ( 曲線状のテキスト ) sounds like text on a path.

Using the corner tool on a vector object smaller than 1px will result in an unintended strange display.

Translation suggestion for the tooltip of visibility checkbox on the Layers panel.
Currently it's 可視状態です that sounds like it's talking about its current visibility state.
In order to describe the checkbox itself, these words would be more proper.
表示/非表示
表示状態
P.S. Adobe uses this sentence
English: Indicates layer visibility
Japanese: レイヤーの表示/非表示
 
 

Translation suggestion for the Node tool

Join Curves = カーブを連結
Current translation カーブを結合 is not so intuitive word and confusing with Merge Curves.
Also Adobe uses 連結

Translation for the Geometry is inconsistent between Mac and Windows.
Suggestion:
Add - 追加
Subtract - 型抜き
Intersect - 交差
Xor - 中マド
Divide - 分割
I referred Adobe's translation. they are using casual words instead of technical terms.
Also I suggest you to change the translation for Merge Curves to カーブをまとめる
Current translation カーブを結合 is also used as the translation for Join Curves of the Node tool so it's confusing.

Translation suggestion for the Flatten(Document>Flatten)

画像の統合 or 統合 is better than フラット化.
Adobe translate Flatten Image to 画像の統合.

Translation suggestion for the Export dialog
”Export Preview” should be 書き出しプレビュー, not プレビュー書き出し
 

When I run the Japanese version of Affinity Photo, the text surrounded by a yellow frame is NOT a Japanese font.
It is probably a Chinese font.
It is very ugly as it is, so please use a Japanese font.
In general, the Japanese version of macOS uses a font included in macOS such as "Hiragino Kaku Gothic" in such cases.

I am also one of the members.

Corner/Contour tool  in Affinity Designer:
アピアランスをベイク would be better as the translation for the "Bake Appearance" on the context bar.

Just Googled the translation for "Baked Potato"
Results of ベイクドポテト is 1,730,000
Results of ベークドポテト is 122,000

It seems that ベイクド is more common than ベークド, also ベイクド sounds more natural to me.
so "Bake" should be ベイク but ベーク, I think.

This is mainly about Windows version.(some are applied to Mac version too)
Since this is a frequent word and affects creation of tutorials, please fix them ASAP.

Please check thoroughly all Export & Import.

Export windows in all Affinity:

Area
Selection Area = 選択エリア
Selection Only = 選択オブジェクトのみ or 選択オブジェクト

Word-for-word translation for "Selection Only" is 選択のみ but this is kind of fuzzy what it is, sounds like the same as "Selection Area."
So 選択オブジェクトのみ(Selected Object(s) only) or 選択オブジェクト(Selected Object(s)) may be better I think...

Translation for the word "Export" and "Import" can be improved.
They are inconsistent or not common.
This is common translation and Adobe uses.
Export = 書き出し 
Import = 読み込み

Suggestion for the File menu in Photo
Export = 書き出し
Export LUT = LUTを書き出し
Import ICC Profile = ICCプロファイルを読み込み

Suggestion for the Export Persona in Photo/Designer
"Export Options" panel = 書き出しオプション
"Export preset" on Slices panel = 書き出しプリセット
In the hamburger menu on Slices panel, please replace all エクスポート with 書き出し.

Suggestion for the hamburger menu on studio panels
Swatch panel
Import palette = パレットを読み込み
Export palette = パレットを書き出し
Assets panel
Import assets = アセットを読み込み
Export assets = アセットを書き出し
Brushes panel
Import brushes = ブラシを読み込み
Export brushes = ブラシを書き出し
Styles panel
Import style category = スタイルカテゴリを読み込み
Export style category = スタイルカテゴリを書き出し
Text Styles panel
Import styles = スタイルを読み込み
Export styles = スタイルを書き出し

Window menu in all Affinity:
This is more suitable translation
Float = 分離
Float All = すべて分離

Current translation is フロート but this is not so common and Adobe uses 分離.

Panorama window in Affinity Photo:
Translation for the "stitch" button should be 縫い合わせる or 繋ぎ合わせる
縫い合わせる is usually used for only fabrics. 
繋ぎ合わせる is universal expression for attaching something together.

Current translation is パノラマの切り替え means "switching panorama" in English.
Not switch, should be stitch.

Translation for the word "Export" is inconsistent.

File menu
Export => エクスポート
Persona
Export Persona => 書き出しペルソナ

Either of 書き出し or エクスポート  is ok but 書き出し is more common and Adobe uses this word.

Translation for the Astrophotography is inconsistent.

File menu
New Astrophotography  Stack => 新しい天体写真術スタック

Filters menu
Astrophotography  => 宇宙写真

「天体写真」is common translation.
So this would be better.
File menu
New Astrophotography  Stack => 新規天体写真スタック
Filters menu
Astrophotography  => 天体写真