-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
subscripts #71
Comments
I agree, and the same is true for superscripts. I thought it would be reasonable to implement a mini-markup language such as follows: R_1 for R1 or I^2 for I2 and braces for longer stuff such as h_{fe} for hfe. What do you think about it? |
As LaTex programming languages. Yeah it would be perfect |
Exactly. I love LaTeX! |
After much thought, I decided against it. This would require to implement a sort of a mini-language and I don't really want to do that. Instead, I think a good solution may be to use a very simple convention:
The meaning of those rules is the following one:
In other words, in the second example the _ cancels the effect of ^ and vice versa. Parsing this is much easier than the LaTeX-style syntax. |
…unt the zoom level, but parsing ^ and _ commands is now active.
…ess correct. Remain to be updated: calculation of text boundaries for selection and dirty area calculation during redraw, exporting towards vector formats.
…tring length calculation is still missing.
It has not been very easy, but at the end the implementation of superscripts and subscripts in the vector file export could be done relatively smoothly. I finally opted for this description:
(resource I close this issue now, as the implementation is complete. |
They would be really usefull, expecially to differenciate resistors and capacitors (and so on).
The text was updated successfully, but these errors were encountered: