Convert Kruti Dev 010 Text from Excel Safely
This guide covers the currently supported Excel workflow: convert selected text cells from a confirmed Kruti Dev 010 source while keeping formulas, dates, IDs, numbers and the original workbook safe. It does not claim public native XLSX conversion.
Know the boundary before opening the workbook
The published SahayakTools capability is text conversion, not an XLSX upload-and-rebuild workflow. The registered Kruti Dev 010 engine does not claim spreadsheet capability, and the native Office workflow definitions remain draft and non-indexable.
Work on a duplicate workbook and convert only the intended cell text. This keeps formulas, number formats, workbook relationships, charts and unrelated sheets outside the conversion path.
Identify text cells before copying
First make an untouched backup. In the working copy, identify the cells that actually contain legacy Hindi text and verify that their source font is Kruti Dev 010 rather than 020, 030 or an unknown variant. If the source is not confirmed as Kruti Dev 010, do not use the 010 converter.
A cell that looks like Latin codes under a normal font may be legacy text, but appearance alone is not enough for a large workbook. Check the original cell font and inspect representative rows before deciding the mapping.
Mark the exact target range or add a temporary review column. Do not select entire rows, columns or sheets when only a few text cells need conversion.
Text cells and formula cells need different handling
Plain text cells can be copied to the converter and reviewed as text. Formula cells must not be overwritten with their displayed result, because pasting converted text back would replace the formula itself.
If a formula displays Hindi or combines text, treat the formula and its dependencies as workbook logic. Do not paste the formula string into the font converter and do not replace it unless you have deliberately chosen to convert that cell to a fixed value in a separate working copy.
Keep a clear list of original cell addresses so each reviewed Unicode result returns only to its intended text cell.
Dates, IDs, numbers and mixed Hindi-English cells
Native Excel dates and numbers are structured values, not legacy-font text. Leave them untouched. A date or number stored as text inside a confirmed Kruti Dev 010 run should be reviewed as text rather than silently changed to an Excel value.
The exact legacy regression 25@05@2016 → 25/05/2016 proves that @ can be the Kruti Dev 010 slash glyph. Separately, mixed-output regressions preserve structured values such as QID-2026, A-17, 15/08/2026, plain numbers, English, 10% and ₹500 outside legacy font runs where appropriate.
Mixed Hindi-English cells need the same source evidence as Word: convert the confirmed Kruti Dev 010 text and verify that English, IDs, dates and numbers remain exact. Do not apply the legacy mapping to an entire mixed range just because one Hindi cell uses Kruti Dev.
Copy only the intended cells
Use a small, clearly identified set of text cells. For the safest review, process one cell or one simple contiguous text range at a time so line and cell boundaries are easy to match on paste-back.
Do not include headers, formulas, hidden helper columns, totals, date columns or ID columns unless their cell text is deliberately part of the conversion review.
After conversion, compare the output with the correctly rendered original rows before touching the workbook. Names, reference numbers and punctuation deserve explicit checks.
Safe paste-back workflow
1. Save an untouched backup and a separate working copy.
2. Confirm Kruti Dev 010 on the intended text cells and record their addresses.
3. Copy only those cells, convert them as text, and review dates, IDs, numbers, punctuation and mixed English.
4. Paste the verified Unicode result only into the matching text cells or a temporary review column. Never paste over formulas or structured-value columns.
5. Apply a Unicode Devanagari display font if needed, recalculate the workbook, compare totals and formulas, then save under a new filename.
Why native XLSX conversion is not claimed publicly yet
A reliable native XLSX converter must preserve formulas, number formats, cell types, workbook relationships, mixed-font runs and other package structure while changing only verified legacy text. Repository code and Office tests are not being used to broaden the current public claim before that workflow is ready for publication.
For now, the deliberate public boundary is reviewed text-level copy and paste. Keeping the native workflows draft avoids implying that users can upload any workbook and safely receive a rebuilt XLSX file.