Windows Unicode Limitations ought to be documented for boost::process V1

Open
#455 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp

Research direction

Review the Boost.Process V1 documentation and identify where platform limitations are described. Confirm the Windows Unicode-path limitation and contrast it with the stated V2 behavior, then document the limitation clearly so downstream users can understand the constraint and migration context.

Written by the indexing model from the issue text.

Description

We have a non-trivial codebase that was recently built on boost::process::child.
We've come to realise that it works fine on Linux, but will not support running a program with a unicode path on Windows.
Migrating to V2 does work, but the migration is non-trivial, unfortunately.

If this limitation could be clearer in the documentation I think it would be useful to maintainers downstream.

Dominant language
C++
Stars
145
Forks
151
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from boostorg/process

All issues in boostorg/process

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.