docs: add Ja translation in useControl.md

[WataruNishimura]

Overview

• It seems that there are no issues or discussions about japanese translation of useControl.md.
• I translated doc and made this PR by myself(not genAI).

Remarks

• This is a literal translation. ( like other ja docs )
• Some words ( e.g. hidden) are used without translation.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 04d0bd3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

More templates

• chakra-ui-example
• headless-u-example
• material-ui-example
• nextjs-example
• radix-ui-example
• react-aria-example
• react-router-example
• react-spa-example
• remix-example
• shadcn-ui-example

@conform-to/dom

npm i https://pkg.pr.new/@conform-to/dom@1134

@conform-to/react

npm i https://pkg.pr.new/@conform-to/react@1134

@conform-to/valibot

npm i https://pkg.pr.new/@conform-to/valibot@1134

@conform-to/validitystate

npm i https://pkg.pr.new/@conform-to/validitystate@1134

@conform-to/yup

npm i https://pkg.pr.new/@conform-to/yup@1134

@conform-to/zod

npm i https://pkg.pr.new/@conform-to/zod@1134

commit: 04d0bd3

[chimame]

@WataruNishimura

Thank you for creating a PR. And I apologize for the late reply.

We're a little unsure how to handle this Japanese documentation.

1. Because it's a future API, changes are likely to occur. When we update the documentation, we'll also need to translate and update the Japanese documentation.
2. We're not sure whether we should continue to maintain the Japanese documentation in the first place.

The answer to the second question isn't immediately clear, but the first one does appear to be an immediate issue.

So, we're thinking of holding off on creating Japanese documentation for now, but do you have any thoughts on Japanese documentation?