[PR 32-bit Mac-Print paychecks]-In the Payslip, "Year to date" not showing full and employee name merged with SSN. screenshot: https://drive.google.com/file/d/1fpQ9qm7HMYWlfok7gEbMEo5YRg8xySEq/view?usp=sharing #2.Headers are need to show bold with highlighted with line, and need to give some space in between two values. screenshot: https://drive.google.com/file/d/1MEsWdOUkdXgRYvY7QECp3X2aLwTryzkc/view?usp=sharing DB: https://drive.google.com/file/d/1u2pAp-Rs8JqKKjm_QQowkVmaiPjVSh-X/view?usp=sharing PDF: https://drive.google.com/file/d/1EoiA6rECSFxLAWJ8Vgs8m4yIFDzUx1mC/view?usp=sharing
Fixed in Win/Mac, available in version 02
Re-open: #In the Payslip, "Year to date" not showing full. #Headers are need to show bold with highlighted with line and need to give some space in between two values(both the values are merged). #3.In the check no and company name not showing properly. screenshot: https://drive.google.com/file/d/1x3SEzaLVpfcmUA6fSUE9TDJGjKqnMey9/view?usp=sharing https://drive.google.com/file/d/1gpcPxzKLpBk9DZHAezE3heYCSAYBtsHc/view?usp=sharing
Fixed in Win/Mac, available in version 03. For bold there is no scope in Mac OS like windows.
in win working fine as expected need to verify in mac.
In the Mac 32-bit Mojave: #1.In the year to date, decimal values in the bottom not showing properly. #2.In the view format,Company name and date is not showing properly. in the print, YTD decimal value not showing properly. screenshot: https://drive.google.com/file/d/12LfBP0k-zai3_PHg1Ia3N4R3VTxmOW5H/view?usp=sharing https://drive.google.com/file/d/1M26OFV9D7RFT_6_JMqygMo2mYdmQtSmA/view?usp=sharing
As per the IT team, the above-mentioned points are displayed in the correct format. However, there is a line alignment issue in the displayed content. Actual Result: The content format is correct, but the line alignment is inconsistent. Expected Result: The content should be displayed with proper line alignment and consistent formatting. screenshot: https://drive.google.com/file/d/19HQetIgZFhfeAtZVUsKvlXxbPGFFBadw/view?usp=sharing
The above-added issues are working fine except for the last comment; that one is added as a new bug.