microsoft / microsoft/TUTA_table_understanding
How to generate hierarchy files for excel sheets with those unique keys?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 125
- Forks
- 27
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 1
Description
I'd like to make a simple inference on few excel sheets of mine,
I have noticed the json files holds some keys, which are not mentioned in the data originated from wiki.
T: cell text
V: cell value
NS: number string
DT: data type (internally stored in spreadsheets, text=0,number=1,data_time=2,percentage=3,currency=4,others=5)
HF: if has formula
A1: formula string with A1 form (absolute cell reference)
R1: formula string with R1C1 form (relative cell reference)
LB: if has left border
TB: if has top border
BB: if has bottom border
RB: if has right border
BC: if has non-white background color
FC: if has non-black font color
FB: if has font bold
I: if has font italic
HA: horizontal alignment (center=0, center_across_selection=1,distributed=2,fill=3,general=4,justify=5,left=6,right=7)
VA: vertical alignment (top=0,center=1,bottom=2,justify=3,distributed=4)
@HaoAreYuDong, I couldn't find the script which generates those annotations/keys for the corresponding excel files?
Can you please share it.
Thank you very much,
I appreciate the assistance!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no file, test, or entry point. Start by searching the repository for the listed annotation keys (T, V, NS, DT, HF), then verify any candidate generator against the Excel metadata; done means identifying or documenting the script that produces those keys.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100