Use WFP's language, formatting, and measurement settings to work comfortably on your own device while keeping shared projects and deliverables consistent.
Choose the Right Settings
What you want to change | Where to change it | Who uses the setting |
Interface language and number/date formatting | File → Preferences... | Your application or browser profile |
Message text sorting | Project → Project properties... → Message ordering locale | Everyone opening the project |
Geometry, walking-distance, and sign-dimension units | Project → Project properties... | Everyone opening the project |
Default report language and formatting | Project → Project properties... → Presentation and reports | Future exports from the project |
Language or formatting for one export | File → Export project reports... | That export only |
Starting from v1.5 WFP includes 121 message-sorting conventions and 115 regional formatting variants. These are independent of the available interface translations. English (UK) is the initial interface and output language; further translations will be delivered separately.
Changing a language or formatting setting does not translate destination messages, project names, descriptions, or other text you have entered.
Set Your User Interface Preferences
Open File → Preferences.... The File menu is also available on the Welcome screen.
Review Interface language.
Choose Number and date formatting. Search by language, region, or locale code to find the convention you need.
Close the dialog when finished.
These choices are available without an open project and remain local to your application or browser profile. Opening a colleague's project does not replace them. WFP saves its initial suggestions; later changes to your device's language do not replace your saved preferences.
Regional formatting controls how numbers and dates appear. Dates use numeric Gregorian dates and Latin digits; formatting does not change time zones, trial periods, or expiry dates.
Set Shared Project Conventions
When creating a project, review its conventions before clicking Create. WFP then creates its starter content and opens the configurator for levels, sign types, and other project settings. Note that you can change these settings, if you change your mind later on.
For an existing project, open Project → Project properties.... Set the measurement choices and, under Presentation and reports, choose Output language, Message ordering locale, and Output formatting.
The message ordering locale controls how message text is compared, such as natural sorting of Gate 2 before Gate 10. It is independent of the output language and number formatting. See Message Display and Ordering for sorting and per-face manual order.
Shared conventions are saved with the project and participate in its Undo/Redo history. Personal interface preferences do not. Existing projects retain their geometry unit and sorting convention; missing presentation settings start with metres for walking distances, millimetres for sign dimensions, and English (UK) output conventions.
Choose Measurement Units
Three independent unit choices serve different purposes:
Geometry unit — coordinates, elevations, and drawing calibration.
Walking distances — route, signing, and disclosure distances, in metres or feet.
Sign dimensions — physical width, height, and depth, in millimetres or inches.
Use Measurement preset to set a common combination:
Preset | Geometry | Walking distances | Sign dimensions |
Metric | Metres | Metres | Millimetres |
Imperial | Feet | Feet | Inches |
You can then change individual choices for a custom combination. A preset is one undoable project edit. Changing units preserves physical sizes and distances; it does not resize the building or signs.
Enter decimals using your interface's selected number formatting, without thousands separators. For example, a locale using a decimal comma expects 1,5 for one and a half. Feet and inches use decimal values, not fractional notation. You can enter finer precision than WFP normally displays; changing presentation does not round untouched values.
If an input is invalid, correct it or use Cancel numeric edits before changing units or formatting. The invalid draft remains visible and unit controls stay disabled until you resolve it; cancelling restores the saved numeric value.
Export for Your Recipient
Open File → Export project reports....
Choose the levels and reports to include.
Review the output language and formatting, initially taken from the project. Choose overrides if this recipient needs a different formatting convention.
Choose Compatible or Localised report for the CSV files.
Choose PDF, SVG, or both for location plans, then export the report.
Export overrides affect this operation only. To change future exports, edit the project's output defaults.
Output | Conventions and intended use |
Compatible CSV and existing clipboard TSV | Stable column names and numeric conventions for existing data workflows and WFP re-import where supported |
Localised report CSV | Output language, regional formatting, and project units for readable deliverables; not for WFP re-import |
PDF/SVG location plans | Project output language and formatting, or the current export overrides, regardless of the CSV choice |
Destination Dictionary interchange keeps its template headers and metre-based distance fields even when the interface displays feet. See CSV Import and Export.
WFP 1.5 changes the canonical Direction values in compatible message CSV/TSV exports, including UpLeft, ForwardThenRight, UTurnCW, and UTurnCCW. Update downstream text matching if it used the older display labels. Localised report CSV instead uses readable headings and direction labels from the output language, such as Main message and Forward then right in English (UK). See Export Ordered Messages.
Choose PDF or Editable SVG
Use PDF when recipients need to view or print plans without installing fonts: PDF reports embed their fonts.
Use SVG when recipients need to edit text or artwork. SVG keeps text editable and references font families; recipients need matching fonts in their editor. WFP uses Inter for Latin, Greek, and Cyrillic, and Noto Sans SC, TC, HK, JP, KR, and Arabic for the corresponding scripts. Text from an imported SVG drawing can also require its original fonts. A substituted font can change glyph forms, spacing, and layout.
WFP checks required fonts and glyphs before generating reports. If a required font download fails, use Retry. If an output language or glyph is unavailable, resolve the font issue or select an available export override. A successful export confirms WFP could generate the report, not that the recipient has the SVG's fonts. WFP does not offer an outlined-SVG option.
Share Projects Across Versions
Every project saved by WFP 1.5 requires WFP 1.5 or newer to reopen, even if you do not use the new arrows or other new features. Before first saving an older project, keep its original file and use Save As... to create a separate v1.5 copy.
WFP 1.5 opens supported older project files. Ask collaborators to update before exchanging newly saved files. Earlier development builds that understand the new file format may still discard unfamiliar color or presentation settings when resaving; builds without Japanese sorting support may replace that convention with English (UK).
Related Workflows
Getting Started — create and configure a project.
Message Display and Ordering — sorting, direction icons, visibility, and manual order.
User Interface — report selection and export controls.



