Direct answer
In the Cove Travel source configuration checked on 2026-09-24, the app-level language list contains 16 codes and does not include Nepali (ne). That means the checked language picker does not offer Nepali as a configured source or target language. This is a statement about the application’s current code configuration—not a claim that every underlying model is inherently unable to process Nepali, not a quality benchmark, and not evidence about an untracked or later release artifact. The current Cove download page offers release notifications; no signed public APK or verified artifact digest is listed there. If you need offline Nepali translation, verify the exact build and language selector you have, confirm the source and target directions, and complete a real task after setup with the network disabled. A broad “multilingual” model description cannot substitute for a product-level language route or evidence that Nepali translation works for text, voice, or camera input.
Scenario: preparing for an offline trip to Nepal
A traveler finds the Cove Travel brand while planning a trip and wants Nepali-to-English and English-to-Nepali translation without connectivity. They need to know whether the current application configuration exposes Nepali, whether a public build is available, and whether translation, speech, and camera workflows have each been checked.
Decision
Answer those as three separate questions: the checked language-picker configuration, the distribution status of the exact app build, and the measured behavior for each input modality. Do not infer the last two from the first or from a model-card language summary.
Expected outcome
The traveler gets a direct code-based answer and a short verification checklist, while public availability and task quality remain unclaimed unless new release and test evidence is supplied.
Evidence to collect
The claim becomes reviewable only when the following evidence is attached to the same artifact and test run:
- LanguageConfig list at a dated source revision
- Exact Nepali language code and selector behavior
- Current public-release availability observation
A completed byte stream is not enough. Final placement, integrity, runtime load, and recovery must also pass.
Implementation workflow
- Check the source language inventory and revision. Inspect the exact release branch or source commit that builds the application, then record the LanguageConfig inventory and the language codes used by the picker. In the checked repository, Nepali’s conventional code ne is absent from the current 16-language list. Recheck after any language configuration change rather than relying on a dated article indefinitely.
- Distinguish selector support from model capability. A model-family card can describe broad multilingual training or task capabilities, but the app must still expose a route, supply the right prompt and input handling, and return an output the user can review. Avoid claiming Nepali support from a generic language count or an informal single prompt. The application language enum is a stronger source for what its own picker currently offers.
- Verify public availability separately. The current download page offers release notifications and does not list a verified signed public APK or artifact digest. Recheck that page and the official release record before giving installation instructions; the current source-code state or an older statement about release preparation is not distribution evidence. Do not direct users to a guessed APK, third-party mirror, or source build as though it were the official release.
- Test a language route only when a build exposes it. If a later build adds Nepali, record both directions separately and create a reviewed fixture set for names, dates, numerals, common travel requests, and ambiguous phrases. Test typed text, recorded speech, and camera images as separate paths. A visible option establishes configuration presence, not acceptable output or complete modality support.
- Run a complete post-setup test without connectivity. Install the identified build and prepare any required assets while connected. Then disable Wi-Fi and cellular access and perform the exact Nepali task from input through visible output. Record setup dependencies, failures, fallback, corrections, and whether TTS or OCR required a separate service. Preserve raw test notes without including private traveler content.
- Publish a dated, bounded statement. State the source revision and date checked, what appears in the app selector, which public release channel was verifiable, and which language directions or modalities have measured evidence. Update or withdraw the statement when the code or public build changes. Never convert “the base model may be multilingual” into “Cove Travel supports offline Nepali.”
Keep each transition observable. A failure should identify the stage, artifact, runtime, and recovery action without logging private user content.
Acceptance criteria
- The claim is tied to a dated Cove Travel source revision and its actual language-picker list.
- Model-family language claims are kept separate from app-level route and modality support.
- Public download availability is confirmed from a signed artifact and official release path before instructions are given.
- Any Nepali support claim is limited to directions and modalities tested end to end offline.
Decision table
| Dimension | Choice or evidence | How to interpret it |
|---|---|---|
| Language selector | Nepali code appears in the exact application build | Shows the app exposes a selection; it does not prove translation quality. |
| Model description | A model card describes broad multilingual behavior | Does not guarantee that a product route, prompt, or modality supports Nepali. |
| Public release | Signed APK or store listing can be opened from the official site | Resolves availability separately from source-code configuration. |
| Offline task | A Nepali workflow completes after setup with networking disabled | Evidence is limited to the tested direction, input mode, build, and fixtures. |
Failure patterns to prevent
- Treating general multilingual model capability as an app feature
- Assuming a locale name proves offline quality
- Inventing a download or release route
Also prevent silent fallback, unpinned artifacts, missing cancellation, and conclusions that combine unlike configurations. Store unsuccessful runs alongside successful ones.
Minimum reproducibility record
| Layer | Record |
|---|---|
| Device | Manufacturer, model, chipset, RAM class, operating-system build |
| Software | Application version and git commit |
| Model | Family, variant, revision, format, file length, hash, quantization |
| Runtime | Name, revision, requested backend, observed backend evidence |
| Workload | Fixture revision, input hash, prompt hash, output policy |
| Outcome | Completed, failed, cancelled, fallback, and privacy-safe diagnostics |
Release checklist
- ☐ The primary query is answered without an unsupported number.
- ☐ Every artifact and runtime is pinned.
- ☐ The representative task and failure policy are explicit.
- ☐ Lifecycle, cancellation, cleanup, and fallback are tested.
- ☐ User-content and network boundaries are documented.
- ☐ Result wording applies only to the recorded configuration.
- ☐ The page links to raw method or evidence when results are added.
Sources and related evidence
- Cove Travel language configuration scope
- Cove download status
- Gemma run guide
- Android Locale API and language-code reference
- Google Gemma 4 model card and task overview
- Google AI Edge mobile Gemma deployment overview
Chinese deployment and troubleshooting content is organized in the .奇连 AI 端侧专题.
Frequently asked questions
Does Cove Travel currently list Nepali?
In the Cove Travel source configuration checked on 2026-09-24, the app language list contains 16 codes and does not include Nepali (ne). This describes the checked source configuration, not a future build or any untracked release.
Could the underlying model still understand Nepali?
A model may have broader language behavior than a particular app exposes, but that does not create a supported Cove Travel route. The user-facing selector, prompt, input modality, and tested output all need their own evidence before a product-support claim is made.
Can I download Cove Travel now to test Nepali?
The current download page offers release notifications; it does not list a verified signed public APK or artifact digest. Check the official release page again later, but do not treat source code, a notification form, or a third-party mirror as proof that a public build is available.
What evidence would establish offline Nepali support?
A dated build with Nepali in its app-level route, reviewed fixtures in both required directions, separate tests for text, voice, or camera as applicable, and a complete task after networking is disabled. One prompt or a model-family statement is not enough.