Flux ArtTranslating a page does not mean translating the keyboard
When changing the language of keyboard product images, first identify the actual keyboard being sold, then decide which text can be translated. Page titles can be localized, but existing keycap legends are part of the product's appearance and must not be rearranged just to look familiar to the target market. When creating visual candidates with Flux Art (https://flux-art.net/en), supply clear overhead originals and version documentation first, and list the key positions to preserve in a review checklist. This article concerns image delivery. It does not determine whether system settings can give a keyboard particular input functions, or treat generated images as proof of a real hardware layout.
Separate three types of information on the brief
The first layer is physical structure: keycap positions, long-key shapes, spacing, and visible sections. The second is keycap legends: letters, symbols, and multiple sets of markings on a single key. The third is input mapping in software. These layers can be related, but cannot stand in for one another. Switching the system language does not change the characters printed on keycaps; similar legends on two keycap sets do not prove that their long-key structures match. Keep the sales SKU, photographed version, and approved character chart separately in the brief. Mark unconfirmed fields as awaiting evidence rather than inferring the layout from the target market's name.
Check long keys and neighboring positions before letters
First mark Return, both Shift keys, the area around the space bar, and the arrow-key area on the original. Compare long-key shapes and their relationships with neighboring keys. Do not shorten long keys to space lettering evenly, or merge two separate keys into one. Apple's keyboard identification guidance uses the Return key's shape and markings at specified positions to identify its keyboard layouts: https://support.apple.com/en-us/102743 . This guidance covers only the Apple versions listed and cannot replace photos and layout charts for another manufacturer's current SKU. The table below is a team review method, not a universal key-count standard for any brand.
| Review layer | Evidence | Action if inconsistent |
|---|---|---|
| Sales version | SKU, packaging, and manufacturer documentation | Isolate versions of unknown origin |
| Physical layout | Same-version overhead and key-area close-ups | Restore key shapes and neighboring relationships |
| Keycap legends | Character chart recorded by position | Check key by key; do not translate globally |
| Software mapping | Corresponding product and system documentation | Do not infer functions from images |
| Page language | Approved marketing copy | Change only the approved descriptive layer |
| Angled views and thumbnails | Content visible in final placements | Add images if critical key areas are unclear |
Record characters by position, not recognition order
Assign row-and-column positions or other stable internal coordinates to the keyboard under review, and record the characters visible in each position in the original. These coordinates are for review only and must not be printed in the product image. If a key has two rows of characters, record them separately; do not simply lay an automatically recognized text string back onto the keys in sequence. Obtain close-ups for blurred, reflective, or obscured characters. An illegible character is not permission to replace it with a common symbol. Check both the character and which key it belongs to, avoiding correct text in the wrong positions. Keep marketing titles separate from physical keycap text so that later typesetting does not cover the original key-surface evidence.
Map language versions before making bulk replacements
When given keyboard images in two languages, first confirm whether they represent different sales SKUs and whether each has supporting evidence for the case, layout, keycaps, and packaging. Do not globally replace text in the first image set and label it as the second physical version. If the task only changes page descriptions, retain the original keyboard photo and translate the accompanying text. Use real references for the corresponding version when another keycap set needs to be shown. Some symbols look similar; reviewers must still confirm each approved character rather than accepting a recognition tool's language label.
Hypothetical revision: correct letters, wrong Return key
Suppose an English-page candidate preserves every letter but changes the photographed Return key into a horizontal bar, displacing neighboring keys. This is not a test or a real customer record. The primary error is the physical layout, so merely pasting the Return legend back is not enough. Restore the actual key area of that sales version first, then check neighboring positions and legends, and finally review the page copy. If the new layout has no corresponding original photo, stop publication of that image. Do not splice in a close-up from another product to make the current product appear complete.
Angles and lighting do not justify skipping key checks
After the overhead baseline passes review, check angled scene images section by section too. Perspective may make distant keys look narrower, but must not add or remove key positions. If glare or backlighting makes legends illegible, record them as not visible instead of assuming they match the overhead view. Key images explaining product structure should retain a sufficiently clear viewpoint. Purely atmospheric images can serve another purpose, but must not be the only images buyers use to judge the layout. After cropping for mobile, verify that labels still point to the correct key area; readability established for the larger image does not automatically carry over.
Deliver originals, the character chart, and final images
For each language version, list the sales SKU, physical-layout documentation, original-photo IDs, per-key character chart, approved copy, and final files. Distinguish structural approval, legend approval, and unknown mapping in the review record. Confirm software input functions separately against product documentation. Do not simply write that the English version is complete when only the page title was translated. If the client requests changed keycaps rather than changed page copy, first confirm that documentation for the corresponding physical product exists; until then, keep it as an internal concept. Log the specific key area changed so the next review can check affected neighbors without reworking unrelated backgrounds.
Start with the actual sales version
Check the most easily confused long keys and multi-character keys in the originals before preparing the required product visuals in Flux Art. Generation tools can provide candidates, not determine product versions. This article does not describe the platform as a system that automatically identifies keyboard layouts or validates input mappings. Flux Art's generated content can be used commercially. Separately verify rights to input photos, fonts, trademarks, and other materials. This article contains no keyboard input tests or image-generation success-rate data. It provides an image-review process; actual sales pages still need acceptance checks against current product documentation.