Path Resolution Mode SASServer/SASWorkstation and encoding - #3
Open
MartialP-G wants to merge 5 commits into
Open
Path Resolution Mode SASServer/SASWorkstation and encoding#3MartialP-G wants to merge 5 commits into
MartialP-G wants to merge 5 commits into
Conversation
Hy Tim,
First, I want to say that these works are really useful for teaching Actuarial Sciences in SAS.
I'm a actuary and teaching at Le Mans University (France).
My GitHub push aims to solve two issues :
First, the encoding of ouput: utf8 is a better standart than ANSI for langage that use accentuated character (I'm french). I mainly handled this issue with filenames using the encoding option. By default, it is utf8, but it can be changed by a new custom variable or deduced from the encoding option in the inputenc package.
The second issue is the current path. You solved it in a super simple and effective way with ./. Howerver on Viya for Learners/Educators, I receive the following log message:
80 %include "./myfile.sas";
WARNING: Physical file does not exist,
/opt/sas/viya/config/var/tmp/compsrv/default/08273935-f335-49d5-b522-7415a65871c3/SAS_workF53C000001F5_sas-compute-server-8
934936c-0b94-4d1c-8a57-fc1b6768a86b-12955/myfile.sas.
It appears that the package references a computation directory rather than the directory where my file is located. To address this issue, I have modified the .sty file by adding a SASmode option. I would be happy to share this update with you.
I would be happy to share this update with you.
Best regards,
Martial
I corrected the FILENAME statement (forgetted in my previous commit) used for the .lst output in line 990 of the statrep_macro file to ensure proper file handling and avoid conflicts when writing results. In addition, I extended the statrep macros to automatically generate a LaTeX-ready file named \jobname_SAStoTex.tex containing definitions of all numeric and date variables from a one line dataset of parameters. The macros apply pre-defined formats depending on the type and magnitude of each variable—handling small numbers, large numbers, percentages, and dates—and write each variable as a \def command. This enhancement allows seamless inclusion of SAS results directly into LaTeX documents, maintaining consistent formatting across reports and simplifying the workflow for automated report generation.
Created the dtx file for the LaTeX package. Updated the LaTeX documentation Minor corrections to the statrepmanual file Reorganized into separate directories for each file: * statrepmanual * quickstart * testcases Licence was updated
Add <1k and >1B range handling to STATREPL/STATREPK picture formats Improve SAS environment compatibility with ODS PATH configuration
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
1 participant
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.
Hy Tim,
First, I want to say that these works are really useful for teaching Actuarial Sciences in SAS. I'm a actuary and teaching at Le Mans University (France). My GitHub push aims to solve two issues :
First, the encoding of ouput: utf8 is a better standart than ANSI for langage that use accentuated character (I'm french). I mainly handled this issue with filenames using the encoding option. By default, it is utf8, but it can be changed by a new custom variable or deduced from the encoding option in the inputenc package.
The second issue is the current path. You solved it in a super simple and effective way with ./. Howerver on Viya for Learners/Educators, I receive the following log message:
80 %include "./myfile.sas";
WARNING: Physical file does not exist,
/opt/sas/viya/config/var/tmp/compsrv/default/08273935-f335-49d5-b522-7415a65871c3/SAS_workF53C000001F5_sas-compute-server-8
934936c-0b94-4d1c-8a57-fc1b6768a86b-12955/myfile.sas.
It appears that the package references a computation directory rather than the directory where my file is located. To address this issue, I have modified the .sty file by adding a SASmode option. I would be happy to share this update with you.
I would be happy to share this update with you.
Best regards,
Martial