Added Translation support and Spanish translation. - #6
Open
EdgarJRobles wants to merge 269 commits into
Open
Conversation
|
@EdgarJRobles does the translation work correctly ? |
luzpaz
reviewed
May 20, 2020
| @@ -0,0 +1 @@ | |||
| pylupdate5 ./../InitGui.py ./../fCmd.py ./../CPipe.py ./../CUtils.py ./../dodoDialogs.py ./../dodoPM.py ./../fForms.py ./../fObservers.py ./../CFrame.py ./../pFeatures.py ./../pCmd.py -ts ./dodo_es-ES.ts No newline at end of file | |||
There was a problem hiding this comment.
Update code.txt ?
@EdgarJRobles Is this file name auto-generated or what you named it?
Author
There was a problem hiding this comment.
It's a comamnd that use to upgrade and generate TS file from python files.
Author
There was a problem hiding this comment.
Update code.txt?
@EdgarJRobles Is this file name auto-generated or what you named it?
It is not auto-generated, i do it manually
Author
|
Same here, translation working as expected, there are still some strings on dialogs missing like @oddtopus We would love your feedback to make translation support happen. |
hasecilu
force-pushed
the
master
branch
4 times, most recently
from
March 15, 2024 02:00
b0a2205 to
b1ee9e3
Compare
|
STATS:
|
Addobject name translated Release last revision es-ES QM file
Wrong typo syntax
Added locale update function
The previous way on which the files were updated is done is by creating some temporal files and then merging them to the original file. Doing this merge would let us to NOT lost the translations already done. It was done like that because we got the string from Python files and UI files because `lupdate` from Qt5 couldn't extract strings from Python files. Now the `lupdate` from Qt6 can do, so we have no need to merge different temp files, instead, we can do the update in a single command. The new advantage is that the `<location>` tag is updated with all new occurrences.
Intended to be used in conjunction with Neovim & LazyVim. The default LazyVim's Python specification use ruff-lsp to format files, this file let you configure ruff, mainly, the line width to 100 chars.
Using the ones are used on main FreeCAD plus codespell
Add plug valve support
Add flanged swing check valves
feat(dodoDialogs): add rotation on valves fix(trimOrExtend): fix AttachmentOffset direction fix(addBeams): fix nest new beam into existing frameBranch object feat(FrameBranch): Allow FrameBranch object to toggle Visibility
Expand socket-weld fitting data
Add knife gate valve support
Add XXS butt-weld tee data
Add pinch valve support
The init_toolbar function has been removed from the Draft code.
Two independent defects stopped pFeatures/pCmd being driven from a headless process. Both are small; neither touches geometry. 1. NameError in Valve._execute_legacy `rating` was read but never bound, so constructing a butterfly, globe, wafer-check or generic ball valve raised NameError before it could build a shape -- 30 catalogue rows dead. Introduced by the "Add gate valve support" change, which replaced `fp.PRating.find(...)` with a bare `rating.find(...)` without binding the local. Knife gate and pinch survived only because they early-return above the fault. Fixed by binding `rating = fp.PRating.lower()` before use, which also makes the comparison case-insensitive as the surrounding early-returns already are. 2. ViewProvider assumed a GUI In console mode DocumentObject.ViewObject is None -- FreeCAD returns Py::None when FreeCADGui holds no Gui::Document for the App document -- so `obj.Proxy = self` raised AttributeError and every make*() factory died before returning. Guarding once inside ViewProvider covers all 17 call sites and any added later. Two direct ViewObject attribute writes (makeTank's colour/transparency, makePypeLine2's provider) are guarded the same way, on the pattern fFeatures.py already uses for Draft. The geometry itself never needed the GUI: pFeatures is pure Part/BRep. Verified under FreeCAD 1.1.0 with QT_QPA_PLATFORM=offscreen, FreeCAD.GuiUp=0: butterfly/globe/wafer-check/ball now build valid solids, and pCmd.makeElbow returns a valid 4-face shell with both ports.
Both only bite without a GUI, which is why they have gone unnoticed.
Flange.execute sets fp.ViewObject.Deviation unconditionally. ViewObject is None
in console mode, the resulting AttributeError is swallowed by recompute, and
every Flange comes back with a NULL shape and no error to explain it.
Tessellation quality is a display setting, so it is now set only when there
is a GUI to set it on.
Tee's fillet fallback crashes inside itself. fillet_r is a Base.Quantity and
"{:.2f}".format(Quantity) raises TypeError, so the handler written to keep a
failed fillet from taking down the recompute is the thing taking down the
recompute. float() at the format site.
Also: the flange neck is built from ODp/T1 even when both are zero. They are
documented OPTIONAL, and Part.makeCylinder(0, 0, ...) fuses a degenerate solid
that leaves the flange isValid() False. Built only when the dimensions are real.
Reproduced under FreeCAD 1.1.0 with QT_QPA_PLATFORM=offscreen: before, Flange
returns a null shape and Tee raises TypeError; after, both build valid solids.
Thanks to vorteccpi@carolina.rr.com Paul Bercker and also added a 2d drawings markdown files to explain CVS estructure and variables
merge missing changes from remote master
Updated image paths in the Nomeclature.md file to use relative paths instead of absolute paths.
…InitGui.py Remove call to init_toolbar from InitGui.py
Fix three defects that stop pFeatures being used without a GUI
-Remove old qt form variable from previous dialog versions -Added extra CVS files for Tee category thank again to Paul Becker vorteccpi@carolina.rr.com
Add beam clamp support
Add rectangular HVAC duct elbows
Add rectangular HVAC duct reductions
Add catalog-backed pipe reducer schedules
only BIM profiles were extrated during profile selection
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
14 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Menu bar were translated.
object name were translated.